Bug 439978 - 5.22.2 and 5.22.3 Consistently Locks Up
Summary: 5.22.2 and 5.22.3 Consistently Locks Up
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-17 14:57 UTC by Chris
Modified: 2025-09-20 09:36 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2021-07-17 14:57:30 UTC
SUMMARY
Updating from 5.22.1 to 5.22.2 has caused my system to be completely unstable.  A subsequent upgrade to 5.22.3 did not help matters.

At first, I thought it was my network, because none of my network shares were accessible, and network monitor was complaining. After trying to figure this out by poking around the system, I found it would lock up after about 2-3 minutes. During this 2-3 minute grace period, I would be subjected to all manner of weirdness on the KDE interface... stacatto mouse movements... artifacts on the screens, failure to paint windows properly, etc. After some trouble-shooting I found that the network was not my problem. Very mysteriously, during my trouble-shooting of this issue, the network stopped complaining... but instead, I was getting CPU stalling behaviours that would continuously complain... and nvidia card errors on my VTs... it was very difficutl to see these things and trouble-shoot them because my grace period before lockup seemed to be getting shorter and shorter. Eventually, I removed all the nvidia elements from the system... no more stalling CPUs... but the system was still exhibiting all the same bizarre behaviors that would always wind up with lockups... but now within a couple seconds of login.

During the week, I'd apply any updates that came my way, in hopes that it would fix this issue. It didn't. I reinstalled the Nvidia drivers. It didn't seem to either help or hinder the situation... I disabled compositing on the desktop... this bought a few minutes again before lockup -- but all the same really weird behaviors were still occurring in the interface (mentioned above), with the new addition that the keyboard would stop sending input (mouse still worked, but I couldn't type anything into a field on the screen). I also lost the ability to view my VTs somewhere along the way.

Now, before people start suggesting this is hardware -- I've already ruled that out by booting to alternate USB/DVD media and by booting to the previous KDE Neon/Ubuntu kernel. Using the previous kernel, I cannot get a good resolution, because it isn't loading the nvidia driver -- but the system is stable, with no complaints of any kind. This problem seems to relate to the kernel itself, or the nvidia driver's goodness of fit with the 5.8 kernel. I've tried logging in using the wayland option, just to see if this helped. Of course, it didn't. I imagine there are some other hoops I have to jump through for that to work right... but I'm not interested in that right now.

Using the kde neon installation media current as of 7/17/2021, the problem persists -- even when operating in live mode.  Booting to safe graphics mode is stable, but of course the resolution is terrible.  I also downloaded a bootable copy of Manjaro with KDE -- it works flawlessly, even with the proprietary drivers.  I noticed its stock kernel is 5.10.42 (unlike neon which is currently 5.8).  Manjaro is also using nvidia drivers 465.31-6.

I have plenty of empty hard disk space, and plenty of memory. My video card is an nvidia GTX 970, using the 460 branch proprietary driver in the stable branch of the package manager. I had been using the PPA driver for a long time now, but currently I'm on the mainstream, Ubuntu driver as part of this trouble-shooting process.

My CPU:

cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 21
model           : 48
model name      : AMD Athlon(tm) X4 860K Quad Core Processor
stepping        : 1
microcode       : 0x6003104
cpu MHz         : 1696.041
cache size      : 2048 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 2
apicid          : 16
initial apicid  : 0

from my syslog:
Jul  3 14:03:36 HTPC plasmashell[1382]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1739, resource id: 37748806, major code: 55 (CreateGC), minor code: 0
Jul  3 14:03:36 HTPC plasmashell[1382]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1740, resource id: 37748806, major code: 72 (PutImage), minor code: 0
I appreciate any help.


STEPS TO REPRODUCE
1. Download installation media current as of today.
2. Boot to AMD system like mine with a GTX 970 Card
3. Try to use Firefox. 

OBSERVED RESULT
System locks up, windows are created, but never paint (still look like the portion of the desktop they cover).  You cannot close the window, and it will never load, but the mouse still moves.  Opening a Konsole window does the same.  VTs are inaccessible, and the system cannot be soft-booted.  The system will eventually hard lock.  A hard reset is the only thing it will respond to.

EXPECTED RESULT
Expect it to work  normally

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Current
(available in About System)
KDE Plasma Version: 5.22.3
KDE Frameworks Version: Current
Qt Version: Current

ADDITIONAL INFORMATION
Same hardware works fine under Manjaro (with KDE), Gentoo, and the current system under the 5.4 kernel.
Comment 1 Chris 2021-07-17 15:01:24 UTC
The "select all" link in the forums seems to be broken.  I was tyring to copy over my syslog, but it only took a few lines... but when I try to post it here, it tells me that it suspects it is spam, and won't let me post it.
Comment 2 Charles Bouchard-Légaré 2021-07-23 17:28:33 UTC
After upgrading today, I have also slowness, and windows painted on entire screen as frozen there (the cursor moves on it, but nothing else can be done in the screen).

It is unclear to me if I can downgrade to the previous version.
Comment 3 Charles Bouchard-Légaré 2021-07-23 17:30:54 UTC
Additonal informations in my case

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz
Memory: 15.3 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Comment 4 Charles Bouchard-Légaré 2021-07-26 13:34:33 UTC
Looks like it is a performance regression with the latest kernel.  I booted in 5.8.0-59 instead of 5.8.0-63 and it looks fine.
Comment 5 Charles Bouchard-Légaré 2021-07-26 17:36:26 UTC
After a few tests, the desktop still is really slow since 5.22.3
Comment 6 Chris 2021-07-26 17:49:19 UTC
After the last update, it seemed to work again for about 36 hours or so... then right back to where I was...  I cannot even get a few seconds out of it before it locks up (unless I go back to kernel 5.4.0-77).

I'm assuming it is the graphics card it doesn't like, so I'm thinking of buying a new one.  Not a solution I like... but this has been over a month now and it is really hobbling.  The thing is it seems to work fine under contemporary Manjaro, so I don't think it is truly a hardware issue...
Comment 7 Charles Bouchard-Légaré 2021-07-27 13:52:31 UTC
I installed libkwaylandserver5=5.22.2.1-0xneon+20.04+focal+release+build24 and my performances are back to normal
Comment 8 Chris 2021-07-27 13:57:55 UTC
Charles, I'm glad yours is working... I, however am using X.  I suppose I could try what works for you, and switch to wayland... I'll see if I get some time tonight...
Comment 9 Charles Bouchard-Légaré 2021-07-30 02:35:16 UTC
My issue seams unrelated to yours, I switched to X and that workaround the issue.  I created another bug for my problem.

https://bugs.kde.org/show_bug.cgi?id=440401
Comment 10 Chris 2021-08-10 13:01:34 UTC
I just bought a new graphics card, since that was what most of the chatter was about. I was fairly convinced that this was not a hardware issue, but I had to try something... And, of course, it still doesn't work (same exact problems).  I just cannot believe after all this time, the problem still persists.  There has been 5 kernel revisions and 3 revisions to the Neon version (now I'm on 5.22.4) since it manifested -- and a million updates.  The system only works under kernel 5.4.0-77, and only in a god-awful resolution.

Even the latest media (from 8/6/2021) locks up on the Neon logo early in the boot sequence.  Gentoo media, Manjaro and Debian media all work fine.

I love neon for desktop systems.  It has everything I want... but I think I have to change to another distro, though it pains me to do so.  I just don't have any more time for this.
Comment 11 Chris 2021-08-15 18:59:51 UTC
I applied more updates yesterday. That brought me to kernel 5.11.  Which made the system completely unbootable.  I never even see grub.  It just locks up on the "Gigabyte" splash screen (the maker of my motherboard).

To my surprise, I found that if I tapped escape, I could get into grub if the timing was just right.  I booted into kernel 5.8.0-63 and it worked!  I ran this for about 24 hours, and it never complained.  Again, I thought I was in the clear.  A few moments ago, I noticed it wanted two more updates: Gnome Application platform 3.38 and KDE 5.15.  I applied these -- now I'm back to where I was before.  Everything just locks up, I get weird behaviors and I see nvidia drm errors.  I noticed that the last several times the system was offering these two packages after applying system updates.  They just might be the actual problem here, I'm thinking.

As a side note -- I have another neon system I'm using as the base for my Linux audio Daw.  I use the repos there to get all my DAW related packages and guitar effects etc.  The last update completely killed that system too -- the update that brought it to 5.11. It just came up to a black screen, and I had to do a system rescue. I was able to back that one down to 5.8.0-63, and it is running again... that is also a gigabyte board z390 designaire -- which is an intel board, so that was surprising.  It also has a gigabyte card with proprietary drivers (which must be used due to excessive interrupts caused by neouveau).  That is 2 of 3 systems I use that have been unusable under the updates that have been going out over the past couple months. It might be a coincidence, I don't know.  But I thought I should mention it.
Comment 12 valdikss 2021-08-16 10:31:13 UTC
If booting into older kernel works, than the issue is the kernel, not KDE. You're posting to the wrong bug tracker, use https://bugzilla.kernel.org/

General troubleshooting recommendations:

1. Try the latest _Ku_buntu LiveCD.
2. Try the latest _U_buntu LiveCD.

If the issue happens on both LiveCDs, then this an issue in Ubuntu in general (in one of its components) and not in KDE. In this case, you should report this issue in Ubuntu bug tracker, they will sort it out whether this is a kernel or Mesa or nVidia other issue.

You also said about CPU stalls. When this issue happens, provide full dmesg output.
Comment 13 Bug Janitor Service 2021-08-31 04:36:24 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Chris 2021-08-31 12:46:09 UTC
Hi. 

I have tried the live CD's mentioned above.  Neither of them will complete booting... they lock up in the same fashion that the Neon media does.  

Oddly, I did a manjaro install on this hardware.  Everything works beautifully -- except the sound through the HDMI -- which I need.  I thought that perhaps the support for my older 970 gtx graphics card was soft, so I bought a more contemporary card and the problems still persisted in Neon (unstable), Ubuntu (won't boot) and Manjaro (no sound).

While the source of this issue might be coming from the Ubuntu core of Neon, I have no desire to run ubuntu, and I'm sure if I posted for assistance there, the response would be (either literal or implicit): "Come back when you use Ubuntu".  Even though this may not be a Neon-specific problem, it will likely hold more weight coming from a KDE developer/maintainer than from an end-user that doesn't even use Ubuntu.

I've been 3 months without this PC... that has to be rectified.  As much as it hurts, I have parts on the way to build a replacement.  If you want to continue testing after I swap out components, I could re-assemble the system in a dev environment where it is no longer critical to me -- if you care to pursue this.

The new system will be an intel system, so I'm hoping for better support (fingers crossed).  All my intel systems seem to work fine under neon (except my kx studio install, but that is a custom beast -- it runs ok if I don't use the newest kernel), so I'm hopeful.

Thanks.
Comment 15 Carlos De Maine 2025-09-20 09:36:27 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!