Post #3236937

@jimsalter@fosstodon.org That confirms it's only gnome asking for the inhibit, but it's absolutely mindnumbingly stupid that gnome is supposedly inhibiting just because there's a foreground process... For reference, my gnome-session-inhibit -l on debian Trixie only shows org.gnome.gedit: There are unsaved documents (logout) which is what I mentioned above: I have unsaved documents open in gedit (Which is perfectly reasonable to inhibit on, if somewhat annoying when trying to do a remote reboot of my desktop. It's the exact thing that triggers the "please save or discard your changes" popup)