KDE

6869 readers

114 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 2 years ago

MODERATORS

carlschwan@lemmy.kde.social

Bro666@lemmy.kde.social

herzenschein@pawb.social

Aniqakhokhar@lemmy.kde.social

PC not shutting down fully sometimes. Unable to wake it up, just have to force shut down through the power button (lemmy.ml)

submitted 1 month ago by absurdity_of_it_all@lemmy.ml to c/kde@lemmy.kde.social

5 comments fedilink hide all child comments

I'm on Solus Plasma. It's worth noting that this never happened on Solus GNOME which I was driving for a few months before switching to KDE.

So this doesn't happen every time I shut down, but it's pretty frequent. What usually happens is I initiate shutdown (using either KRunner or from Application menu clicking shutdown). The monitor and keyboard and mouse switch off, but the CPU does not. Fans are running, RGB is on. I can't wake it up with any keys. I can only long press power button on the cabinet to force shutdown.

Couple of things I observed:

I noticed sometimes my external HDD was not auto mounting when I started the PC, so I thought maybe it was automount that was preventing shut down also. So I tried to see if the times automount didn't work, coincided with the times I had to force shutdown - they don't. Even if it shuts down without issues I sometimes notice automount not working. And not every time I force shutdown I have automount issues.
I thought maybe clicking the shut down immediately button on the confirmation screen is what is causing the issue. I tried letting it shutdown on its own after the 10s countdown, but that also yielded inconsistent results.

I'm at a loss for what to do now.

top 5 comments

sorted by: hot top controversial new old

[–] amzd@lemmy.world 5 points 1 month ago (1 children)

I don't think this is just a KDE issue as I'm having it on gnome too. Not sure how to fix. I feel like it happens less when I close all background processes before shutting down but idk.

[–] walthervonstolzing@lemmy.ml 1 points 1 month ago (2 children)

It might be due to display drivers not playing nice on wayland; I've had this problem a couple months ago on arch with the amdgpu drivers, using either one of sway, labwc, or KDE. It did not happen on Xfce, though; and after a kernel update the problem subsided.

[–] IceFoxX@lemm.ee 1 points 1 month ago

Btw Months ago.... At that time it wasn't that long ago that the big DE's started to implement wayland in the first place to get rid of xorg. In the meantime, wayland is running pretty well.

[–] MouldyCat@feddit.uk 1 points 2 weeks ago

FYI I've had this issue on my old XFCE laptop for a while, and I'm still using X there. I thought it was a sign of failing hardware, given that it happens at the very last point of shutdown (and also, if the system was going into hibernation, it wakes up from it successfully even though I had to force poweroff the machine).

[–] IceFoxX@lemm.ee 1 points 1 month ago* (last edited 1 month ago)

You say that even automount causes problems. You should look for a backup HDD before data loss. You should read out the SMART values.

Either way, disconnect the external HDD from the PC and check whether shutdown still causes problems. At least I know the problem myself from problems with external storage.

Either way, you can only guess without any information. Logs would be more helpful.

(systemd-analyze blame)
journalctl -b -1
systemctl --type=mount --all
systemctl --type=service --all |grep running