SUMMARY Since Plasma 5.27.8 task manager occasionally stops tracking open windows on a wayland session. This issue looks deceptively similar to Bug 429168 however it only appeared between 5.27.7 and 5.27.8. Although they manifest in the same manner they are probably caused by different issues. I also get the same warning as in Bug 429168 when starting up plasmashell from the terminal ("org.kde.kf5.kwindowsystem.kwayland: This compositor does not support the Plasma Window Management interface") and also as in Bug 429168 the issue appears on all flavours of task manager. Reverting plasma-workspace (which provides plasmashell) back to 5.27.7 stops the problem from appearing. I browsed the git commits of plasma-workspace between 5.27.7 and 5.27.8 and there were a few commits that *look* like they might be associated with this, for instance this [0] or this [1] but unfortunately I am not qualified enough to say. [0] https://invent.kde.org/plasma/plasma-workspace/-/commit/b235a5900107ef1cec7d6ac30f5569ee5e3357c1 [1] https://invent.kde.org/plasma/plasma-workspace/-/commit/cb7dfe90f2a91f20c40a7e4744112602534aee38 STEPS TO REPRODUCE 1. Open a graphical application OBSERVED RESULT Task manager does not update EXPECTED RESULT A new icon appears on the task manager to track the status of the new window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION With proprietary NVIDIA driver. Problem appears only on Wayland Sessions.
The two commits are not in 5.27. They are only for 6.0. Did you also see the panel frozen when you see the bug?
Yes, this usually happens after a freeze of the panel which is, from what I understand, a common issue with pre-6.0 and nvidia. However, restarting plasmashell doesn't fix the problem, the taskbar becomes responsive again but no windows are tracked, only pinned applications and applets are shown. Even restarting the session (or the computer) doesn't fix the issue. I tested with a new user, changed nothing in the configuration and waited until the panel froze again and indeed the same thing happened. Then I nuked the new user's .config and .local to force a fresh plasma session. The panel then works again until it freezes, rinse, repeat. The only difference between 5.27.7 and 5.27.8 is that with 5.27.7 a "killall plasmashell && kstart5 plasmashell" or "plasmashell --replace" addresses the issue whereas with 5.27.8 even restarting the shell does not.
Just to add one more piece of information: the difference between a "regular" freeze and the issue I'm describing is the presence of the "org.kde.kf5.kwindowsystem.kwayland: This compositor does not support the Plasma Window Management interface" in the logs when starting plasmashell.
Issue persists on 5.27.9
I have the same problem in Fedora 39, recently upgraded from Fedora 38: Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Symptoms: - Icons in the taskbar remain after the window has been closed. They are not responsive, right-clicking shows the taskbar menu - No new icons beyond the third - Icons for the windows not closed work (i.e., they minimize/restore the window) - The network icon shows the VPN lock even when the VPN has been disconnected (it is reset upon logout-login) - Digital clock has frozen (but "copy to clipboard" shows the correct time) So taskbar is not completely frozen in my system
In addition, the taskbar shows the wrong icon. I closed a chrome browser but the icon remained in the taskbar. On clicking, it restores/minimizes a different window.
(In reply to emelenas from comment #5) > I have the same problem in Fedora 39, recently upgraded from Fedora 38: > Operating System: Fedora Linux 39 > KDE Plasma Version: 5.27.9 > KDE Frameworks Version: 5.111.0 > Qt Version: 5.15.11 > Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) > Graphics Platform: Wayland > > Symptoms: > - Icons in the taskbar remain after the window has been closed. They are not > responsive, right-clicking shows the taskbar menu > - No new icons beyond the third > - Icons for the windows not closed work (i.e., they minimize/restore the > window) > - The network icon shows the VPN lock even when the VPN has been > disconnected (it is reset upon logout-login) > - Digital clock has frozen (but "copy to clipboard" shows the correct time) > > So taskbar is not completely frozen in my system I can confirm this on Fedora 39 Spin and openSUSE tumbleweed. The Task Manager mouse hover + live thumbnail seems to cause problems While xorg live thumbnail showing only video but Wayland showing entire browser or video player. and doing this it sometimes stops responding. KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.6-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: NVIDIA GeForce RTX 2080/PCIe/SSE2
Issue keeps happening in Plasma 6, although there is no panel freeze anymore. The "This compositor does not support the Plasma Window Management interface" error does not appear anymore as well. After login on Wayland the task manager is not tracking the new windows and only shows the pinned applications. Occasionally `plasmashell --replace` or `killall plasmashell; kstart plasmashell` fixes the issue but it is very unreliable. I appreciate that the issue is quite unreliable to reproduce so any hints towards more reliable debugging of the issue are welcome. X11 sessions work as expected.
Created attachment 170730 [details] Task manager not showing active window Currently there is 4 windows active (Firefox, Konsole, System setting - About, Spectacle)
I have the same issue on KDE 6 / Manjaro. KDE Plasma version: 6.0.5 KDE Framework Version: 6.2.0 QT version: 6.7.1 Manjaro 24.0.2 The problem often happens after I wake up the computer from sleep. Login-out and back in doesn't solve the issue. Using `plasmashell --replace` neither. But it's gone after a reboot.
Created attachment 170731 [details] plasma logs journalctl -r -S "2024-06-21 09:00:00" | grep "plasma" > logs.txt
Created attachment 171339 [details] current environment I appreciate this is not very helpful but problem still persists with 6.1 (nvidia 555) with no obvious way to debug. Task manager is essentially non functional under Wayland. I am attaching my current environment in case it's useful.
If I may add, I still have this issue from time to time on KDE 6.1.5, and with Intel graphics on Wayland (no NVIDIA involved). Hardware specs: Mesa Intel® Graphics - Intel Corporation Raptor Lake-P [UHD Graphics] (rev 04) - 00:02.0 Kernel: 6.10.13-3-MANJARO
Just to add one more case, I have the same bug described here. Plasma version 6.2.3, KDE Frameworks 6.8.0, QT 6.8.0, kernel 6.11.6, running on Wayland on NixOS 25.05. GPU is Intel UHD 730. I don't see any error messages in the logs; restarting Plasma has no effect; logging in or out has no effect; torching .config and .local has no effect; and the problem presents constantly. I do not experience a freeze of the panel. Happy to provide any logs or diagnostics upon request.
My experience with this problem leads me to believe that there is a probable relation with hardware, at least in my case, so maybe something at a lower level (Wayland?). My observations in several systems and installations: - No problem in Fedora 40 with a 5800X3D/GTX1080Ti. - Problem appeared by moving the SSD from the previous system to a 4700S/RX550. - Problem persisted in a fresh install of Fedora 41 in the same hardware (4700S/RX550). - No problem in a fresh install of Fedora 41 in a 3600X/W5700.
After a bit more experimentation, I can contribute this: 1. The icons-and-text Task Manager displays exactly the same behaviour. 2. The Window List task manager displays a button on the panel to click on, but does not display any open window when you click on it. I'd hypothesise that there's something going on that makes running applications invisible to the Task Managers. One can still Alt-Tab through running applications and they're displayed during the Alt-Tab process, but Task Managers can't see them. Is there some common code that all Task Managers rely upon to see running applications? If anyone knows the name of the correct plasmoid, perhaps I can try some debugging in plasmawindowed to see what's going on.
Yet information for homing in: I switched NixOS channels from "unstable" to "24.11" and the problem has completely disappeared; all the Task Managers are working exactly as expected again. I am still running Wayland, still the same kernel, still the same Plasma, KDE Frameworks, and QT version. Still the same hardware. When you switch channels (without making any other configuration file changes), no user data is affected; .config and .local and so on stay exactly the same. However, the set of applications that you have available to you, and the (sandboxed) system-level installs of those applications, changes. This leads me to think that there is some mismatch at the level of package installation or system changes or system configuration that is causing this problem. Perhaps that is enough to point developers in the right direction, or at least to remove some red herrings on the trail of this bug.
This is fixed in Plasma 6.3 IIRC.
I am still having this issue in 6.3. Operating System: NixOS 25.05 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.12.28 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 30.5 GiB of RAM Graphics Processor 1: NVIDIA GeForce RTX 3090 Graphics Processor 2: AMD Radeon Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7E26 System Version: 1.0
I should add some additional information. For me restarting my computer fixes the issue but restarting plasma doesn't. I see this at the top of my log for plasmashell when the issue is happening: org.kde.plasma.libtaskmanager: The PlasmaWindowManagement protocol hasn't activated in time. The client possibly got denied by kwin? Check kwin output. I'll add my plasmashell and kwin_wayland logs for when this happened. Not sure if I should make a separate bug about this.
Created attachment 181429 [details] plasmashell logs
Created attachment 181430 [details] kwin_wayland logs
Does that reproduce for you in a new clean user account on the same machine? If not, it may be a local error or misconfiguration of some sort.
I have not had this problem since I posted that comment. So maybe I got the change that fixed this. Operating System: NixOS 25.11 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.12.30 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 30.5 GiB of RAM Graphics Processor 1: NVIDIA GeForce RTX 3090 Graphics Processor 2: AMD Radeon Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7E26 System Version: 1.0
I spoke too soon. Everything on the bar froze up so I ran a `systemctl restart --user plasma-plasmashell.service` and the bug returned. I'll see if I can get a new user to test out things.
I have the same issue, doesn't happen with a fresh user, and I think I was able to narrow down the problem somewhat. I used to be on gnome, switched to KDE about 6 months ago, everything went okay, I started to like it. One day I did some clean-up, removing packages I didn't need any more, mostly gnome stuff, and I broke KDE: empty application launcher, empty window list, this message in the logs : org.kde.plasma.libtaskmanager: The PlasmaWindowManagement protocol hasn't activated in time. The client possibly got denied by kwin? Check kwin output. I tried to diagnose, to no avail, re installed gnome, went back to using it. After a few days, I decided that really I preferred KDE, went back to it and everything was working, I though "great, an updated fixed the problem". Been using it for a few weeks again, today, I removed my gnome stuff again and the issue happened again! Re-installed the gnome metapackage, did kquitapp6 plasmashell && kstart plasmashell and things work again. So there is something in my user config that makes KDE depend on something gnome-y. I don't know what though. Operating System: Arch Linux KDE Plasma Version: 6.3.91 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.7-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 32 GiB of RAM (30.8 GiB usable) Graphics Processor: Intel® Iris® Plus Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9300
I also used to be on Gnome, so perhaps it is related to switching from gnome. I'm not sure what would be left over on my system that would cause a problem though. I'm also noticing that it's mentioning hitting the open file limit, I'll look into that as well.
(In reply to Sam Dinner from comment #27) > I also used to be on Gnome, so perhaps it is related to switching from > gnome. I'm not sure what would be left over on my system that would cause a > problem though. I'm also noticing that it's mentioning hitting the open file > limit, I'll look into that as well. I actually don't think it has to do with gnome any longer. The problem keeps on popping in and out. It happens after I install or update packages with pacman. When it happens, I just have do install or uninstall random stuff, and it fixes the problem. I guess it has to so with one of the icon or desktop file caches.