That was (yes, "was") happening to me too, until one day it stopped. Could be just a streak of fortunate events, I don't know. I'll report back here if it'll happen again.

In T6251#113024, @livingsilver94 wrote:

That was (yes, "was") happening to me too, until one day it stopped. Could be just a streak of fortunate events, I don't know. I'll report back here if it'll happen again.

Thanks! I used to think it only occurred when I forgot to close KeepassXC but sometimes I close all programs before shutting down and yet Solus hangs. I'll post a screenshot when it happens again.

It re-happened yesterday. I clicked on "Restart" (Budgie, stable channel) and I got a total black screen except for a fixed cursor on the upper left corner. I couldn't switch to any of the tty.

This happened for me from time to time 1 - 2 month's ago, but it went away again. When i left the machine with the blinking cursor in the top left corner, it would eventually shutdown or reboot, but i guess it took 1 - 2 min. for it to do so.

Do you have any USB devices connected when it happens ?

Note: This may happen for example if your machine was connected to a network drive that was turned off/disconnected before your machine shutdown; during the shutdown process, your machine will perform a umount of the disks and wait for the network drive that is not reachable until a timeout occurs.

When the problem occurs, wait a few minutes until the machine shuts down then turn it on again and check the logs of the previous boot with: journalctl -b -1. I guess there should be an error message near the end. If you don't see any relevant error message, try the same command with sudo to get more blah-blah.

In T6251#113158, @Lorien wrote:

This happened for me from time to time 1 - 2 month's ago, but it went away again. When i left the machine with the blinking cursor in the top left corner, it would eventually shutdown or reboot, but i guess it took 1 - 2 min. for it to do so.

Do you have any USB devices connected when it happens ?

I have the USB transmitter for my wireless mouse and a bluetooth adapter plugged in. But these are fairly common, aren't they?

In T6251#113161, @kyrios123 wrote:

Note: This may happen for example if your machine was connected to a network drive that was turned off/disconnected before your machine shutdown; during the shutdown process, your machine will perform a umount of the disks and wait for the network drive that is not reachable until a timeout occurs.

When the problem occurs, wait a few minutes until the machine shuts down then turn it on again and check the logs of the previous boot with: journalctl -b -1. I guess there should be an error message near the end. If you don't see any relevant error message, try the same command with sudo to get more blah-blah.

Hmmm...I have the Nextcloud desktop client running. Other than that I have an SSD and two HDDs.

Next time I'll time the duration the machine takes to shut off and I'll print the logs. Thanks.

In my case I had no external drives nor network drive, just my internal HDD with personal files, as usual. I have a separated drive for music and photos.