You are not logged in.
Recently, my system has started to take a lot of time to shutdown/reboot. It hangs on a black screen with a blinking white cursor and shuts down/reboots after about 2 minutes.
The problem happens when I reboot or shutdown from within my active user session. If I end the session and then reboot/shutdown from the greeter screen, everything works fine and the system doesn't hang.
"reboot -f" and "poweroff -f" don't cause the hanging issue and work as you'd expect.
I'm using gnome with the lightdm slick greeter. I'm also using Nvidia drivers.
Offline
Please post the system journal of the previous boot after such delay:
sudo journalctl -b | curl -F 'f:1=<-' ix.ioOffline
Thank you for the reply! The output to that command is "no results to fetch".
I checked the whole log with "sudo journalctl -b -1" and this part caught my eye:
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Stopping timed out. Killing.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Killing process 1520 (winedevice.exe) with signal SIGKILL.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Killing process 1526 (winedevice.exe) with signal SIGKILL.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Killing process 1530 (n/a) with signal SIGKILL.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Killing process 1535 (winedevice.exe) with signal SIGKILL.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Killing process 1547 (n/a) with signal SIGKILL.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Killing process 1560 (n/a) with signal SIGKILL.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Killing process 1561 (n/a) with signal SIGKILL.
mar 07 09:38:48 benja-arch systemd[723]: app-gnome-alacarte\x2dmade\x2d9-1078.scope: Failed with result 'timeout'.
A couple of lines after that sequence, it says "Reached target shutdown" and things seem to continue without errors after that.
Offline
Ok, so I looked into that and the issue seems to be a windows software (who would've imagined!) I run with bottles. I had set up a shortcut to running that program with alacarte, the program to create menu entries.
If I don't launch the windows software, everything works as usual. If I launch it, the reboot/shutdown process hangs.
The command I placed in alacarte to create the shortcut is as follows:
bottles -b Bottle-Name -e "full_path_to_software.exe"
I now know the source of the issue, but I'm not sure why it makes the system hang on reboot/shutdown. Is there something I can do to keep using that windows software with bottles but make sure that hang doesn't happen?
Offline
The output to that command is "no results to fetch".
The journal might be excessively big and quota'd. Upload the output somewhere - in doubt a google drive.
Can you properly terminate the "full_path_to_software.exe" during the session and does the winedevice.exe process linger around afterwards?
Offline
I checked and yes, I can terminate it and the winedevice.exe doesn't linger if I manually terminate it. The problem is, when I have the application running and I issue a system shutdown, without first terminating the wine process, the shutdown hangs before forcing the computer to shutdown (after about 2 minues). The problem happens even when I launch the program directly with Bottles, without using the alacarte menu entry I've set up, so I assume this is a bug with the Bottles application. I've opened an issue on their github, hopefully the developer can check it out some time in the future. For now, I'm just making sure I manually close anything I run with Bottles, I don't have any issues anymore.
Offline