SUMMARY At random intervals the panel freezes (widgets are inactive, mousing has no effect etc.). It may unfreeze spontaneously after several minutes, but has sometimes gone on for hours and required a reboot. STEPS TO REPRODUCE 1. Unknown 2. 3. OBSERVED RESULT Frozen panel. EXPECTED RESULT Working panel SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Fedora 29, KDE 5.13.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The freeze doesn't seem to be related to any action on my part. Several times it has happened when I've left the system running overnight, and the clock widget shows a time on the small hours (but not always the same time) meaning it has frozen for up to 6 hours or so. Other times it runs fine all night but freezes while I'm using it. In the latter case it usually wakes up itself after 10 or 15 minutes, but may take longer. If this happens there will be a flurry of window flashing as a queue of mouse events is drained. I've tried attaching gdb to the plasmashell process but gdb then hangs. The same happens with strace. A ps run shows the process is in '-Dl' WCHAN state. I can kill it with a -9 and restart it but the new plasmashell is still frozen. I considered it might be related to NFS (I have a local NAS), but that doesn't seem to be it as it happens even when the NAS is disconnected. See discussion at https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/thread/RKCZ4RWNJHEKUMOAZJBLIOMRDLJ7XQMD/ This all started happening with Fedora 29.
Are you using NVIDIA binary OpenGL drivers?
(In reply to Christoph Feck from comment #1) > Are you using NVIDIA binary OpenGL drivers? No. I do have an Nvida card but it's blacklisted (I'm using it for VFIO in a KVM). Fedora is running on the mobo's IGP.
I'm having the same issue, although freezes don't take any longer than a minute. Noticed that when it happens plasmashell is using 100% CPU. Restarting plasmashell unfreezes things immediately. I'm on KDE Neon 5.14, Plasma 5.14.4, nvidia-driver-390 Didn't have this issue when I was using Kubuntu 18.04 on the same hardware, also with the proprietary nvidia driver.
(In reply to Konstantin Pereiaslov from comment #3) > I'm having the same issue, although freezes don't take any longer than a > minute. Noticed that when it happens plasmashell is using 100% CPU. > Restarting plasmashell unfreezes things immediately. > I'm on KDE Neon 5.14, Plasma 5.14.4, nvidia-driver-390 > > Didn't have this issue when I was using Kubuntu 18.04 on the same hardware, > also with the proprietary nvidia driver. I haven't had the problem recently (i.e. more than a month). I'm now on: kernel 4.19.10-300.fc29.x86_64 Plasma 5.14.4 I'm also not automounting my NFS NAS (via systemd). It's unclear which if any of these things has affected the issue.
I believe this is a dupe of https://bugs.kde.org/show_bug.cgi?id=401272
Sorry, commented on the wrong issue, got tabs mixed up, please disregard my prior comment :(
I may have the same or a similar issue (debian-testing, plasma 5.14.5, Intel graphics, nvidia blacklisted) which appeared at the same time as an update about a month ago which also broke kwin_x11. The panel display only freezes at random points while e.g. I can still click on its components and get a reaction. However, of course, state changes are not reflected in the panel any longer as the display remains frozen. I have never observed it unfreeze, even after hours. Kill/restart will get things back to normal. I can attach gdb and get a stack trace - maybe it helps: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007f56fcb96d0f in __GI___poll (fds=0x55ad02e099b0, nfds=14, timeout=27846) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. (gdb) where #0 0x00007f56fcb96d0f in __GI___poll (fds=0x55ad02e099b0, nfds=14, timeout=27846) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f56fb08109e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f56fb0811bf in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f56fd1127f1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f56fd0bb71b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f56fd0c31c2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x000055acf72f9235 in () #7 0x00007f56fcacdbbb in __libc_start_main (main= 0x55acf72f8720, argc=1, argv=0x7ffcbdd75548, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcbdd75538) at ../csu/libc-start.c:308 #8 0x000055acf72f96ba in _start () (gdb)
Do, gdb "bt thread apply all" next time, to get all threads, not just the first one
Created attachment 124631 [details] stack trace of plasmashell (panel with display frozen)
If it reacts to click, it's not frozen, so the stracktrace won't tell us much.
Does everyone experiencing this have NVIDIA hardware? Is anyone able to reproduce it with Plasma 5.21?
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!