SUMMARY Plasmashell / the panel freezes after any significant length of time using the desktop environment. STEPS TO REPRODUCE 1. login to kde plasma and use the desktop environment for any reasonable amount of time. 2. the plasma panel will freeze after any time from a few minutes to a few hours. OBSERVED RESULT - Plasma panel completely freezes and is unresponsive. additionally typing on the desktop no longer shows krunner (so maybe more than just a panel issue) - krunner no longer appears when typing on the desktop - right click context menu does not appear - memory use of plasmashell continually increases after the freeze (as of typing this it's using 12.7GB) - plasmashell shows no error logs. EXPECTED RESULT none of the above SOFTWARE/OS VERSIONS OS: Arch linux (up to date as of 11th oct 2024) KDE Plasma Version: 6.2.0 (though the issue has persisted since 6.0.x) KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 ADDITIONAL INFORMATION problem has persisted for several months since a 6.0.x version. attempting to "terminate" plasmashell or running "killall" or "sudo killall" on plasmashell does nothing. running plasmashell --replace shows the following: plasmashell --replace kf.dbusaddons: Failed to register name 'org.kde.plasmashell' with DBUS - does this process have permission to use the name, and do no other processes own it already? running the journalctl command, there are no logs at all from plasmashell when the desktop freezes manually running "kill" on the plasmashell process (from system monitor) will *sometimes* fix the issue and make the panel responsive, however often when plasmashell is restarted the panel does not appear again. running kwin_wayland --replace and then manually killing plasmashell consistently works to make the panel responsive again.
now plasmashell is using 13.3GB.
Sounds like there's a memory leak somewhere that's causing your system to run out of memory. These are unfortunately tricky to pinpoint. To start with, can you create a new clean user account with no Plasma customizations and see if the issue still happens? If it does not, then the issue will be caused by something you've done with customizing Plasma in your normal user account. Then we'll want to figure out what it is.
(In reply to Nate Graham from comment #2) > Sounds like there's a memory leak somewhere that's causing your system to > run out of memory. These are unfortunately tricky to pinpoint. > > To start with, can you create a new clean user account with no Plasma > customizations and see if the issue still happens? If it does not, then the > issue will be caused by something you've done with customizing Plasma in > your normal user account. Then we'll want to figure out what it is. I no longer seem to be experiencing the issue as of the last few days, I believe the issue must have been caused by a plasmoid as since resetting my panel to the default settings I have not experienced the issue again
Sounds good. If you ever manage to figure out which plasmoid it was specifically, that would be very helpful information!
(In reply to Nate Graham from comment #4) > Sounds good. If you ever manage to figure out which plasmoid it was > specifically, that would be very helpful information! I'm almost certain that the plasmoid causing the problem was the media player plasmoid that's built in by default. I dont have any issues when it's running through the system tray however since removing the standalone plasmoid on my panel I'm no longer experiencing the freezes.
hope this helps
Thanks a lot! So when you add it back to your panel as a standalone widget, does the problem return?
(In reply to Nate Graham from comment #7) > Thanks a lot! So when you add it back to your panel as a standalone widget, > does the problem return? yeah exactly that.
can confirm that after re-adding the media player as a standalone widget on my panel the issue has reappeared within a couple of hours
Thanks a lot, that's really helpful!
I was unable to reproduce this with Plasma 6.2 or with git-master I added the Media Player widget to a panel on each, and had it running all day. I was monitoring top. No CPU hogging, no memory hogging, no panel freezes In the past, I *have* seen the Plasma panel freeze when playing Spotify as a snap Today I had Spotify playing from the flatpak install (which also installs a snap, don't ask me), and no problems with it
(In reply to TraceyC from comment #11) > I was unable to reproduce this with Plasma 6.2 or with git-master > I added the Media Player widget to a panel on each, and had it running all > day. I was monitoring top. No CPU hogging, no memory hogging, no panel > freezes > > In the past, I *have* seen the Plasma panel freeze when playing Spotify as a > snap > Today I had Spotify playing from the flatpak install (which also installs a > snap, don't ask me), and no problems with it I'm using youtube music (youtube-music-desktop on the AUR) maybe that's the issue? although I can't be sure if I've always had that open when the issue has occurred
What would be useful to us at this point is to do some debugging and possibly get details on when Plasmashell freezes Take a look at https://community.kde.org/Plasma/Debugging, and see if that gets you any useful logs or backtrace. Thanks!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Created attachment 176528 [details] Results from gdb running on plasmashell during a session when Media Player freezes Hi - sorry, I don't know if this is the right kind of logging, but this is what I got from trying the process at https://community.kde.org/Plasma/Debugging#Attach_gdb_to_the_plasmashell_process - it's not a crash, so if there's a more appropriate kind of log to look for, I'm happy to find it.
Created attachment 176529 [details] System journal entries with the identifier plasmashell
Reproduced on my system - I was able to reproduce this months ago and just wasn't able to file a bug at the time (sorry), so I don't think it's brand-new necessarily. Additional notes: *Moving the cursor over the panel results in the old X cursor appearing *The memory leak is extremely slow for me - it's been 15 minutes, and plasmashell is "only" at 1.0GB of RAM usage, and my system still has 26GB free, so I don't believe there's a system-level out-of-memory state happening *For me, the freeze happens along with a song change in Elisa - when one song changes to the next, and the displayed content of the Media Player widget would then theoretically update, it doesn't update and instead plasmashell enters this state *It's not on every song change, but seems to usually happen after about 15-20 songs have played *There is constant CPU activity from plasmashell once it's visually frozen, on my system happens to be about 7.5% of CPU capacity *This does not happen if the Media Player Plasmoid is opened from the System Tray, then pinned, but it can happen if the Media Player widget is added to a panel and pop-out from the widget (showing the album art/playback controls) is open (that's not required though, it can also happen if the pop-out is not open and it's just in its "resting" state on the panel) Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.11-300.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.4 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4070 SUPER/PCIe/SSE2 Thanks!
*** This bug has been marked as a duplicate of bug 491946 ***
(In reply to Fushan Wen from comment #18) > > *** This bug has been marked as a duplicate of bug 491946 *** Hi - could you please give some guidance here on where/how this issue, as described above, should be reported? The bug this was marked as a duplicate of is indicated as fixed in 6.2.0 - since the symptoms remain, should 491946 be reopened?