[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=449948| -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #26 from Nate Graham --- *** This bug has been marked as a duplicate of bug 449948 *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #25 from Bernie Innocenti --- (In reply to Nate Graham from comment #23) > Indeed, it is likely that this is the same as Bug 449948, which says that > the issue is 100% reproducible if kwin_wayland has crashed and restarted > automatically, or was killed and restarted manually. > > Can everyone else confirm? Confirming: today kwin_wayland crashed, and after it restarted I immediately tried to logout and plasmashell froze for serveral seconds. I was using Fedora 36 with plasma-desktop-5.24.4-1.fc36.x86_64 (but possibly the session was started when I was still running 5.24.3). -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #24 from Nate Graham --- *** Bug 446143 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #23 from Nate Graham --- Indeed, it is likely that this is the same as Bug 449948, which says that the issue is 100% reproducible if kwin_wayland has crashed and restarted automatically, or was killed and restarted manually. Can everyone else confirm? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 m1st0 changed: What|Removed |Added Version|5.23.90 |5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 postix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=449948 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Oliver Klee changed: What|Removed |Added CC||kde...@oliverklee.de -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #22 from Bernie Innocenti --- I wonder if there's any relation to bug #449948? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added CC||sebastian.p...@gmail.com --- Comment #21 from Nate Graham --- *** Bug 450716 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #20 from Bernie Innocenti --- I'm running Fedora 36 with Plasma 5.24.0 and I just installed the updates to 5.24.1. I was going to restart the session to start using the updated desktop components, but I hit this bug again. ksmserver was indeed dead, exactly as described in comment #19. I restarted it (systemctl --user restart plasma-ksmserver.service), but it did not cure the problem: the menu still freezes when I select Restart. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas | |ma/plasma-workspace/-/commi | |t/022a91662541fd32e54cbfec3 | |71f08368f878fcf | Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #19 from Fushan Wen --- Can still reproduce on git master Information for package plasma5-workspace: -- Repository : unstable-kde-frameworks Name : plasma5-workspace Version: 5.24.80git.20220217T112240~4d68f4b25-ku.33.2 Arch : x86_64 Vendor : obs://build.opensuse.org/KDE:Unstable Installed Size : 27.1 MiB Installed : Yes Status : up-to-date Source package : plasma5-workspace-5.24.80git.20220217T112240~4d68f4b25-ku.33.2.src Summary: The KDE Plasma Workspace Components > systemctl --user status plasma-ksmserver.service --no-pager -l × plasma-ksmserver.service - KDE Session Management Server Loaded: loaded (/usr/lib/systemd/user/plasma-ksmserver.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2022-02-18 15:06:52 CST; 1h 27min ago Process: 14746 ExecStart=/usr/bin/ksmserver (code=exited, status=1/FAILURE) Main PID: 14746 (code=exited, status=1/FAILURE) CPU: 117ms 2月 18 15:05:16 ZHAN66 systemd[2734]: Starting KDE Session Management Server... 2月 18 15:05:16 ZHAN66 ksmserver[14746]: Qt: Session management error: networkIdsList argument is NULL 2月 18 15:05:16 ZHAN66 systemd[2734]: Started KDE Session Management Server. 2月 18 15:06:51 ZHAN66 ksmserver[14746]: The X11 connection broke (error 1). Did the X11 server die? 2月 18 15:06:52 ZHAN66 systemd[2734]: plasma-ksmserver.service: Main process exited, code=exited, status=1/FAILURE 2月 18 15:06:52 ZHAN66 systemd[2734]: plasma-ksmserver.service: Failed with result 'exit-code'. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #18 from Viorel-Cătălin Răpițeanu --- (In reply to Fushan Wen from comment #15) > (In reply to Bernie Innocenti from comment #13) > > (In reply to Nate Graham from comment #12) > > > Interesting. If you get it out of that state (e.g. by killing and > > > restarting > > > plasmashell) does the hang-on-logout issue still happen? If not, then it > > > may > > > be a separate issue. > > > > It just happened to me again in Fedora Rawhide. Killing and restarting > > plasmashell doesn't fix this issue. > > Can you run `systemctl --user status plasma-ksmserver.service` to see if > there is any error message when this bug happens? systemctl --user status plasma-ksmserver.service × plasma-ksmserver.service - KDE Session Management Server Loaded: loaded (/run/user/1000/systemd/user.control/plasma-ksmserver.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-02-08 09:56:01 EET; 1min 18s ago Process: 1688 ExecStart=/home/username/kde/usr/bin/ksmserver (code=exited, status=1/FAILURE) Main PID: 1688 (code=exited, status=1/FAILURE) CPU: 95ms feb 08 09:56:00 hostname systemd[1600]: Starting KDE Session Management Server... feb 08 09:56:00 hostname ksmserver[1688]: Qt: Session management error: networkIdsList argument is NULL feb 08 09:56:00 hostname systemd[1600]: Started KDE Session Management Server. feb 08 09:56:01 hostname ksmserver[1688]: The X11 connection broke (error 1). Did the X11 server die? feb 08 09:56:01 hostname systemd[1600]: plasma-ksmserver.service: Main process exited, code=exited, status=1/FAILURE feb 08 09:56:01 hostname systemd[1600]: plasma-ksmserver.service: Failed with result 'exit-code'. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Fushan Wen changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #17 from Fushan Wen --- (In reply to Nate Graham from comment #16) > Fushan, you just marked this as fixed by a commit that's a week old but you > said you can reproduce it today. Did you not yet have that commit when you > tested it? No, Bugzilla automatically marked this bug as FIXED after I added "Lastest Commit". I will try to revert the commit. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #16 from Nate Graham --- Fushan, you just marked this as fixed by a commit that's a week old but you said you can reproduce it today. Did you not yet have that commit when you tested it? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Fushan Wen changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/022a91662541fd32e54cbfec3 ||71f08368f878fcf -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Fushan Wen changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #15 from Fushan Wen --- (In reply to Bernie Innocenti from comment #13) > (In reply to Nate Graham from comment #12) > > Interesting. If you get it out of that state (e.g. by killing and restarting > > plasmashell) does the hang-on-logout issue still happen? If not, then it may > > be a separate issue. > > It just happened to me again in Fedora Rawhide. Killing and restarting > plasmashell doesn't fix this issue. Can you run `systemctl --user status plasma-ksmserver.service` to see if there is any error message when this bug happens? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #14 from Fushan Wen --- I can reproduce it by running `systemctl --user stop plasma-ksmserver.service` So I guess it's related to crashes or unresponsiveness of ksmserver? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Bernie Innocenti changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #13 from Bernie Innocenti --- (In reply to Nate Graham from comment #12) > Interesting. If you get it out of that state (e.g. by killing and restarting > plasmashell) does the hang-on-logout issue still happen? If not, then it may > be a separate issue. It just happened to me again in Fedora Rawhide. Killing and restarting plasmashell doesn't fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #12 from Nate Graham --- Interesting. If you get it out of that state (e.g. by killing and restarting plasmashell) does the hang-on-logout issue still happen? If not, then it may be a separate issue. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #11 from Bernie Innocenti --- It just happened to me again with plasmashell from plasma-workspace-5.23.90-2.fc36.x86_64. Just before this, I did "something" that made the panel miss some button release event, and the task bar was constantly dragging around the apps while moving the mouse over it. The application menu would open with the Super key, but then would not respond to clicks or keyboard input. After some fiddling, I managed to get out of this state, but now clicking logout freezes the panel with the application menu open for 10 seconds. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #10 from Nate Graham --- I'm not able to reproduce this anymore with current git master code; is anyone else? Possibly it got fixed by one of the recent commits for Plasma 5.24. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Viorel-Cătălin Răpițeanu changed: What|Removed |Added CC||rapiteanu.cata...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added Keywords||wayland --- Comment #9 from Nate Graham --- I can also confirm that it works correctly in the X11 session. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #8 from Nate Graham --- Yep, I see the same symptoms. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #7 from Bernie Innocenti --- I captured the the journal just before a plasmashell crash: ---cut--- trying to show an empty dialog qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.svg: :303:258: Could not add child element to parent element because the types are incorrect. qt.svg: :303:463: Could not add child element to parent element because the types are incorrect. qt.svg: :303:659: Could not add child element to parent element because the types are incorrect. qt.svg: :303:913: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1049: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1251: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1453: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1631: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1739: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1980: Could not add child element to parent element because the types are incorrect. qt.svg: :303:2223: Could not add child element to parent element because the types are incorrect. QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection The Wayland connection broke. Did the Wayland compositor die? ---cut--- No, kwin_wayland did not die. This is not a crash, it's a clean exit with $?=1 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #6 from Bernie Innocenti --- Created attachment 145783 --> https://bugs.kde.org/attachment.cgi?id=145783=edit Plasmashell freezing when you click Logout. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #5 from Bernie Innocenti --- I think I'm hitting this same bug in Fedora Rawhide (plasmashell 5.23.90, sddm 0.19.0). Attaching a screenshot which shows the frozen application menu. In most cases, the shell recovers after about 10 seconds. I've also seen it crash in a couple of cases, but I wasn't able to attach gdb nor get a stacktrace. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #4 from Nate Graham --- SDDM 0.19.0 Switching between VTs works, but does not un-wedge plasma for me. If I return to the VT with the session on it, Plasma is still stuck for a bit. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #3 from Linus Dierheimer --- SDDM: 0.19.0-7 Switching to another TTY just brings up the usual console based login. Switching back to plasma doesn't change anything there, if you are fast enough its sometimes even still frozen. Switching to TTY1, where i think sddm runs, brings up a black screen with just the cursor visible. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #2 from David Edmundson --- Can you include SDDM version? Does switching VTs (control+alt f2 etc) fix anything? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Nate Graham changed: What|Removed |Added CC||n...@kde.org Summary|Logout of wayland session |Logout/shutdown/restart in |doesn't work, if automatic |wayland session sometimes |login for sddm is enabled |freezes the UI you used to |(5.23.90) |trigger it and then doesn't ||do anything Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Priority|NOR |VHI --- Comment #1 from Nate Graham --- > Sometimes the system just becomes unresponsive after the click on logout, > freezes for about 5 seconds, and then acts like log out was never clicked. I can reproduce that without having autologin enabled, so I suspect it's a different thing. It's super annoying. I was planning to file a bug report about it, but you beat me to it. Let's use this bug report for that and get another one for issues that are isolated to being triggered by autologin. -- You are receiving this mail because: You are watching all bug changes.
