Mastodawn

My #Debian 13 desktop keeps refusing (is "inhibited") from suspending.

I think I've worked out why.

When someone calls me, the left-hand monitor often gets turned off momentarilly by the phone signal. It comes back on, but Debian somehow thinks that this is a new monitor and then inhibits suspend.

It seems that the daft thing thinks it might be a laptop, though I have none of the Debian laptop stuff installed.

Not looking for a solution, just (I know about systemctl suspend -i), I'm just ...

Show thread

ROTOPE~1 ⭐️Feb 22

@ecadre i saw this somewhere ..
dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitors
to get a list of Inhibitor####, and then turn those into something meaningful with

dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager/InhibitorXXX org.gnome.SessionManager.Inhibitor.GetAppId

Show thread

ROTOPE~1 ⭐️Feb 22

@ecadre the most common inhibitor that I get is "Nautilus was doing a copy, it completed hours ago, but it forgot to remove the inhibitor". I do a "killall nautilus" whenever that comes up.

Show thread

Andrew Wigglesworth

@rotopenguin Honestly, I'm more amused by it than annoyed. My desktop is very reliable (there, I wrote it, now reap the whirlwind!!!), it's just that all these complex pieces of modern technology find new ways of going wrong.

It didn't do this when the phone turned my old monitor off and on :-D

Maybe my phone should be sent to live somewhere else? But, really, I'm perfectly happy suspending from the cli.