Solus not sleeping?
Open, Needs More InfoPublic
Actions

Assigned To

None

Authored By

	samteezy
	Feb 5 2021, 2:03 AM

Description

I'm having an issue getting Solus to sleep on command. When I use the "user indicator" applet in the Budgie panel to try to get my desktop to sleep, the monitors go dark, the computer continues to stay awake, and then I'm presented at the login screen again.

Pulling the logs from the relevant time, this is what I'm getting:

Feb 04 20:56:01 tributo gvfsd[1502]: Error calling org.gtk.vfs.MonitorClient.Changed(): Timeout was reached (g-io-error-quark, 24)
Feb 04 20:56:01 tributo gvfsd[1502]: Error calling org.gtk.vfs.MonitorClient.Changed(): Timeout was reached (g-io-error-quark, 24)
Feb 04 20:56:01 tributo gvfsd[1502]: Error calling org.gtk.vfs.MonitorClient.Changed(): Timeout was reached (g-io-error-quark, 24)
Feb 04 20:56:01 tributo budgie-panel[1411]: UserIndicatorWindow.vala:370: Cannot lock screen: Timeout was reached
Feb 04 20:56:02 tributo gsd-usb-protect[1302]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
Feb 04 20:56:09 tributo gnome-screensaver-dialog[97148]: gkr-pam: unlocked login keyring
Feb 04 20:56:09 tributo gnome-screensaver-dialog[97148]: pam_warn(gnome-screensaver:account): function=[pam_sm_acct_mgmt] flags=0 service=[gnome-screensaver] terminal=[:0.0] user=[sam] ruser=[<unknown>] rhost=[<unknown>]
Feb 04 20:56:09 tributo gsd-usb-protect[1302]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
Feb 04 20:56:12 tributo gnome-control-c[97194]: gtk_style_context_add_provider_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

Event Timeline

samteezy created this task.Feb 5 2021, 2:03 AM

Herald added a project: Lacks Project. · View Herald TranscriptFeb 5 2021, 2:03 AM

Is this still an issue?

Yes, it is. Not near the PC right now but I can get you the specific error I’m seeing when attempting to sleep.

@samteezy Thanks!

Ok, so this is annoying. I literally had the issue last night and this morning, but after a forced power off and fresh boot, I'm able to to sleep and shutdown properly. Argh.

Again, still saw the same issue this morning where attempting to sleep. When logging back in and attempting to shutdown, I got:

systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
systemd-shutdown[1]: Failed to finalized DM devices, ignoring.

I've been getting this message consistently as well for the past several MONTHS. At that point, my only option (I think) is to hold the power button to force the machine off, and then boot normally. Only difference this morning is after booting up now everything is working as normal - I've been able to suspend and resume properly, as well as shut down.

If it's ok with you I'd like to keep this open a little bit. Maybe it's an app in particular I frequently use that's causing the hangup? I could try to pull log files from last night when I last saw the sleep issue or this morning when I saw the shutdown issue. Just tell me what to look for.

Update: I am indeed seeing the sleeping issue again. Try to go to sleep, the monitors turn off, but the computer doesn't change power state and after a few seconds the monitors are on and I'm presented at the login screen.

Let me know what logs to pull to help see what's going on.

TClark77 added a subscriber: TClark77.Jun 12 2022, 4:24 PM

Solus not sleeping?Open, Needs More InfoPublicActions

Description

Event Timeline

Solus not sleeping?
Open, Needs More InfoPublic
Actions