shutdown not work

The shutdown button doesn't work for me, I press the shutdown button and all it does is close taskbar and make background black
Solution:
Looks like it's an upstream issue, this is from 4 days ago and it appears that it's specific to x11 https://www.reddit.com/r/Fedora/comments/1da3si7/fedora_kde_not_shutdown/
Reddit
From the Fedora community on Reddit
Explore this post and more from the Fedora community
Jump to solution
19 Replies
PizzaV
PizzaVOP8mo ago
Just give commands and output I need to give for more info I'll do it tomorrow
HikariKnight
HikariKnight8mo ago
do shutdown -P now in terminal and see what that says next time it happens, could be as simple as a raid (if you have one) doing integrity checking while you try to shut down
Potajito
Potajito8mo ago
I have this too, I blame x11 but I have no proof
Texas_Flexas
Texas_Flexas8mo ago
Yep, ive experienced this. x11 as well.
hellfur
hellfur8mo ago
Also having this issue, also x11. Shutdown on the terminal works fine.
wolfyreload
wolfyreload8mo ago
I can also reproduce x11 KDE nvidia image. I have this line in journalctrl getting spammed with not sure if it's related or not though
BAT0: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_control_end_threshold' failed with exit code 1.
BAT0: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_control_end_threshold' failed with exit code 1.
shutting down via terminal works
Solution
wolfyreload
wolfyreload8mo ago
Looks like it's an upstream issue, this is from 4 days ago and it appears that it's specific to x11 https://www.reddit.com/r/Fedora/comments/1da3si7/fedora_kde_not_shutdown/
Reddit
From the Fedora community on Reddit
Explore this post and more from the Fedora community
HikariKnight
HikariKnight8mo ago
probably wont be fixed then if its x11 specific :/
hou6
hou68mo ago
Could rebase to Gnome
HikariKnight
HikariKnight8mo ago
not recommended by us or upstream, enjoy your broken state in $HOME
hou6
hou68mo ago
I mean to bazzite gnome Unless bazzite gnome is broken you mean
antheas
antheas8mo ago
Who is this upstream guy everyone is talking about If you rebase to gnome you might have slight issues if you don't clean your home directory is what they mean
HikariKnight
HikariKnight8mo ago
yeah essentially gnome and kde stomp on each others configs so you can often get weird issues which we cannot help you with.
PizzaV
PizzaVOP7mo ago
Did this get fixed in kde 6.1?
wolfyreload
wolfyreload7mo ago
I'm on the bazzite-nvidia testing branch and it's fixed there, not sure about the bazzite-nvidia stable branch
Kyle Gospo
Kyle Gospo7mo ago
It's fixed in testing because there's no X11 If it still happening on stable today it would happen on testing if I added that package back
zany130
zany1307mo ago
I'm getting this same issue but on Wayland kde Here is the journal http://0x0.st/XLET.txt Is it better if I create a new post since this was already answered? This is on amd GPU though @Kyle Gospo
Kyle Gospo
Kyle Gospo7mo ago
Yes, this bug was specifically X11 on KDE Please make a new thread Why is your host name Garuda Linux?
zany130
zany1307mo ago
idk this is strange I got the log with ujust logs-last-boot | wgetpaste -s 0x0 Ill make a new thread

Did you find this page helpful?