Bug#980071: gnome-shell: Using suspend in the gnome-shell power off/log out menu does log out and suspend in the wrong order

[A Ozbay]

I havent encountered this bug since upgrading to GNOME 41 on Debian testing. You can close it, if you wish.



Sent with ProtonMail secure email.
------- Original Message -------
On Sunday, January 31st, 2021 at 3:51 PM, Simon McVittie <smcv at debian.org> wrote:


> On Thu, 14 Jan 2021 at 20:03:37 +0000, A Ozbay wrote:
>
> > I looked through journalctl output and saw this which looked out of ordinary:
> > Jan 13 22:59:29 snorlax gnome-shell[2475]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running
> > _promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:435:45
> > ### Promise created here: ###
> > inhibit at resource:///org/gnome/shell/misc/loginManager.js:196:35
> > _syncInhibitor at resource:///org/gnome/shell/ui/screenShield.js:203:32
> > _setActive at resource:///org/gnome/shell/ui/screenShield.js:157:14
> > _completeDeactivate at resource:///org/gnome/shell/ui/screenShield.js:565:14
> > onComplete at resource:///org/gnome/shell/ui/screenShield.js:542:36
> > _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:84:13
> > _easeActor/<@resource:///org/gnome/shell/ui/environment.js:167:64
>
>
> That looks likely to be part of the problem you are reporting. GNOME
> Shell and systemd-logind are having this conversation:
>
> <shell> Please don't suspend until I tell you I'm ready, because I need to
>
> lock the screen first
> <logind> Sorry, you're too late - suspend is already in progress
>
>
> However, that is probably not the whole story. I'd need to see more of
> the log to say more.
>
> Would you be able to share a log with this bug's address, starting from
> around the time you started the process of suspending? You can censor
> parts that you consider to be private as long as you make it obvious
> where you have done so (e.g. replacing details with REDACTED).
>
> Or you could send a log to me privately, but I'm dealing with several
> high-priority things at the moment and my time is limited, so I can't
> guarantee to get to this any time soon, and it might be better to put the
> information where other GNOME team members have an opportunity to help.
>
> > I am not sure if this would crash the shell.
>
>
> Probably not, but I can't tell from just this one message. If the shell
> crashes, you should see other messages, for instance gnome-session
> reporting that a required component (the shell) has failed.
>
> > Other than that, I also noticed that this happens only on Xorg, and
> > not on Wayland.
>
>
> That's probably significant information, and will make it more likely
> that a GNOME team member can reproduce the bug - I suspect we're all
> using GNOME in its recommended Wayland mode.
>
> Thanks,
> smcv