Bug 449021 - After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem temporarily
Summary: After a period of working as intended, the KDE Panel freezes and is unrespons...
Status: RESOLVED DUPLICATE of bug 449163
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.23.5
Platform: Arch Linux Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: regression, wayland
Depends on:
Blocks:
 
Reported: 2022-01-23 17:05 UTC by Isaac Milarsky
Modified: 2022-08-31 13:00 UTC (History)
6 users (show)

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


Attachments
Some of the messages from Journalctl from around the time of a recent freeze (10.86 KB, text/plain)
2022-01-23 17:05 UTC, Isaac Milarsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Isaac Milarsky 2022-01-23 17:05:27 UTC
Created attachment 145808 [details]
Some of the messages from Journalctl from around the time of a recent freeze

SUMMARY
After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem temporarily with "kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell." This is with Arch Linux using a wayland session started using sddm.


STEPS TO REPRODUCE
1.  Boot Arch Linux to SDDM 
2. Login to a Wayland session and do standard browsing on firefox, write code, etc
3. Wait for the panel clock to freeze and not match the current time

OBSERVED RESULT
The Panel is unresponsive for all widgets except the application menu. Otherwise KDE seems to be functioning as intended. KDE needs to be restarted in order for the panel to start working again. 

EXPECTED RESULT
Panel ideally should be responsive as intended and not freeze quietly.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.2-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-01-23 21:50:08 UTC
Just the panel? When it's frozen, can you right-click on the desktop and get a context menu? If that works, do you also get a context menu when you right-click on the frozen panel?
Comment 2 Isaac Milarsky 2022-01-23 21:52:03 UTC
(In reply to Nate Graham from comment #1)
> Just the panel? When it's frozen, can you right-click on the desktop and get
> a context menu? If that works, do you also get a context menu when you
> right-click on the frozen panel?

Yes Right clicking seems to work. However stuff like appmenu buttons are unresponsive and other widgets like the clock are frozen
Comment 3 Nate Graham 2022-01-24 19:27:52 UTC
So right-clicking doesn't make them unfreeze?
Comment 4 Isaac Milarsky 2022-01-24 23:43:29 UTC
(In reply to Nate Graham from comment #3)
> So right-clicking doesn't make them unfreeze?

No. Admittedly, it hasn't happened today though and I've been updating my arch setup daily.
Comment 5 Isaac Milarsky 2022-01-25 04:43:46 UTC
I haven't been able to replicate this bug lately but will update this page if/when it pops up again
Comment 6 Isaac Milarsky 2022-01-25 22:56:55 UTC
The bug happened again today on my other arch machine that I haven't updated in about 2 days. Right clicking doesn't fix the issue but context menus work and I can right click things like normal. It seems only the panel is affected. Right clicking doesn't cause it to unfreeze. However, I haven't been able to replicate the bug on my laptop for a while now and that might be due to it being more up to date.
Comment 7 Isaac Milarsky 2022-01-25 22:58:35 UTC
(In reply to Isaac Milarsky from comment #6)
> The bug happened again today on my other arch machine that I haven't updated
> in about 2 days. Right clicking doesn't fix the issue but context menus work
> and I can right click things like normal. It seems only the panel is
> affected. Right clicking doesn't cause it to unfreeze. However, I haven't
> been able to replicate the bug on my laptop for a while now and that might
> be due to it being more up to date.

These were the arch packages that were out of date when the bug last occurred on my desktop machine
Comment 8 Isaac Milarsky 2022-01-25 22:59:07 UTC
Packages (32) cmake-3.22.2-1  dialog-1:1.3_20220117-1  dune-2.9.2-1  electron-16.0.7-2  ethtool-1:5.16-1  faudio-22.01-1  gdb-11.2-1  gdb-common-11.2-1  git-2.35.0-1  js78-78.15.0-3
              lib32-faudio-22.01-1  lib32-libldap-2.6.1-1  lib32-util-linux-2.37.3-1  lib32-zstd-1.5.2-1  libbsd-0.11.5-1  libldap-2.6.1-1  libplacebo-4.192.0-1  python-3.10.2-1
              python-dnspython-1:2.2.0-1  python-lxml-4.7.1-1  python-tomli-2.0.0-1  python-urllib3-1.26.8-1  python-zipp-3.7.0-1  quazip-1.2-1 [removal]  quazip-qt5-1.2-2  svt-av1-0.9.0-1
              util-linux-2.37.3-1  util-linux-libs-2.37.3-1  vlc-3.0.16-7  wpa_supplicant-2:2.10-1  xf86-input-libinput-1.2.1-1  zstd-1.5.2-1
Comment 9 M. Schulte 2022-01-27 08:58:50 UTC
I have the same problem, can't really replicate it but 1-2 times a day my panel will freeze.
I got the same behavior as OP, so right-clicking appmenu buttons works but they do not unfreeze.

I usually notice it when the clock is stuck or when the task manager applet shows no animations on hovering and is stuck in an old state.
My current workaround is to move the panel to another screen edge, then back to the original one.

The last time it froze was yesterday and my system was completely up to date.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.2-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Comment 10 M. Schulte 2022-01-27 09:06:09 UTC
Also I'm running a dual monitor setup with one panel on each monitor. Usually just one panel freezes, but if I remember correctly they can both freeze.
Comment 11 Joern 2022-01-28 10:29:51 UTC
I've the same problems since a couple of days. The Panel freezes 1 to n times a day. No log entries around the time of freezes and also no clue how to reproduce it. Yesterday I've had no freeze and thought that the bug perhaps has been fixed, but today...


SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Comment 12 Joern 2022-01-28 10:31:01 UTC
Forgot to mention: I've also a dual Monitor setup.
Comment 13 Ryan 2022-01-28 15:02:21 UTC
I'd like to also mention my experience and give any info if needed. I also experience this bug on a fully updated Arch system as well. I'm also not running NVIDIA graphics and am running the latest beta of plasma from the kde-unstable repo and experience this issue a few times per day, where it isn't resolved until I run `plasmashell --replace` from KRunner. The entire system seems responsive, like the task switcher, KRunner, and the desktop, just the panel and its applets (except the application menu) freezes. Also a dual monitor setup, I don't think I've experienced this issue on my purely 1 screen laptop, though I don't use it often enough to really justify that claim. I'll keep an eye out for it, maybe leave it running for a while to see if it ever crops up.

SOFTWARE/OS VERSIONS:
Operating System: Arch Linux
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.2-arch1-1
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 3700U
Memory: 17.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 10 Graphics
Comment 14 Nate Graham 2022-01-28 16:12:20 UTC
This'll be the same as Bug 429211.

*** This bug has been marked as a duplicate of bug 429211 ***
Comment 15 Nate Graham 2022-02-03 17:21:22 UTC

*** This bug has been marked as a duplicate of bug 449163 ***