[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 --- Comment #8 from spyst...@gmail.com --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 feich changed: What|Removed |Added CC||gg0n...@outlook.com --- Comment #7 from feich --- (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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 --- Comment #6 from emele...@gmail.com --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 emele...@gmail.com changed: What|Removed |Added CC||emele...@gmail.com --- Comment #5 from emele...@gmail.com --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 --- Comment #4 from spyst...@gmail.com --- Issue persists on 5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 --- Comment #3 from spyst...@gmail.com --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 --- Comment #2 from spyst...@gmail.com --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475896] Wayland: Task Manager does not track open windows
https://bugs.kde.org/show_bug.cgi?id=475896 --- Comment #1 from Fushan Wen --- 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? -- You are receiving this mail because: You are watching all bug changes.
