Since some update last week, I have trouble to shutdown the system via the quick settings menu in Gnome. However, after click shutdown or reboot, does nothing. There is no error message or failure, there is only no response.
On the other hand, when i open a terminal and use “shutdown” or “reboot” from inside the terminal, this works as expected and the system shuts down as usual.
Has something changed in the shutdown process?
Do you happen to have the Caffeine GNOME Shell Extension installed? If so, make sure to toggle it off before attempting to restart /shut down.
Your logs may yield information about what’s happening:
As a workaround, try logging off then then restart / shut down from there.
Nope. I have no Extensions besides Dash to panel.
I have found the solution. For some reason, the UUID of my swap was changed. As a result swap was not active properly. Found this by checking the errors since boot with journalctl. After re-adding the swap with proper uuid, it works now as before.
There seems to be more to this, because today the same issue occurs again. The Swap is correctly active this time. I have now made a test and opened a terminal before clicking on shutdown in the menu and use journalctl --follow to see whats maybe going on. When i click on shutdown, i get the following in the terminal:
Feb 19 15:01:32 laptop gnome-session-binary[4636]: Entering running state
Feb 19 15:01:32 laptop gnome-shell[4659]: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Vorgang wurde abgebrochen
Stack trace:
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
@resource:///org/gnome/shell/ui/init.js:21:20
Has someone a idea what can cause this or where i should have a look?
Really strange, after waiting 10 minutes and doing some other stuff, i clicked again on shutdown in the quick menu. The error message comes up again, but this time followed by a message, that the system will now shutdown now. Shortly after that, the computer shuts really down. So i assume the above error message has nothing todo with the shutdown error. Im totally clueless.
I experience the same issue, and this is what I see in journalctl /usr/bin/gnome-shell:
Feb 23 05:35:31 monochrome gnome-shell[3074]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 3
Feb 23 05:35:32 monochrome gnome-shell[3074]: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Operation was cancelled
Stack trace:
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
@resource:///org/gnome/shell/ui/init.js:21:20
Maybe this helps:
I found that too. Unfortunately, it doesn’t really help. The problem doesn’t seem to be of a general nature or related to an incorrect package, as it sometimes works but sometimes doesn’t. Polkit is also installed correctly, so I can more or less rule it out. I can’t really make sense of it, but I suspect a problem with Gnome. Gnome doesn’t seem to be aware of such a problem, but nobody responds to such questions.
Started to have the same issue, with the same error in journalctl. Checked the solution in the link above.
I did some testing, When Steam was not started, I can reboot and shutdown without any issue.
If I start Steam it will close Steam but not reboot/shutdown.
If I reboot/shutdown now it will do without a problem.
If I start Steam again, after it was closed by reboot/shutdown, it will still block the reboot/shutdown.
There seems to be something with Steam and potentially some other apps, that blocks something in the system.
I don’t know if this is really a GNOME problem, I also use go-hass-agent to shutdown my desktop with my smarthome and it doesn’t work either.
Seeing the same issue for a few weeks now. Seeing the same error in the journalctl as well. I tried removing a bunch of extensions as it looks like some of them were inhibiting the shutdown but it still doesn’t work.
I do see the correct polkit packages installed as well. I do have steam installed but did not see any difference with it running or otherwise.
One thing that does work is performing a logoff first and then a shutdown.