Dear Maintainer,

   * What led up to the situation?
   I leave the computer with some apps running without doing anything so
that the blank
   screen/screen lock kicks in after 15 minutes.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   Nothing.
   * What was the outcome of this action?
   The screen blanks as expected, but when I move the mouse or press a
   key I am presented with the initial log-in screen.
   Once logged in, I am in a new session with none of my previous running
apps.
   * What outcome did you expect instead?
   I expected to see the lock screen to input my password and getting
   back to my previous session with all my running apps still there.

*** End of the template - remove these template lines ***

Control: reassign 974985 gnome-shell 3.38.1-2
lock", rather than to #974987 "gnome-control-center: blank screen option
in two menu entries"? It looks more appropriate for #974985.

Is #974985 something that happened once but not reliably, or does it happen
every time you let the time-based screen lock happen?

Are you using Wayland or Xorg?

Please try disabling all GNOME Shell extensions. If that resolves this,
then it's a bug in one of the extensions, most likely the window list,
and we should reassign #974985 to that package.

Another thing to try would be to upgrade gnome-shell and libmutter to
the versions from experimental, which contain most of the changes that
will be released as 3.38.2 later.

As far as I can tell from your log, either GNOME Shell, Xwayland or
Xorg crashed after this point - although I would have expected more
messages to be logged. Please try looking at the corresponding time in
the systemd journal or /var/log/syslog, which might provide more detail
(not all messages go into /var/log/messages).

    smcv

Summary of the bug report: After leaving the computer idle and logged in
to GNOME in Wayland mode, when the screen locks based on a timer,
waking the screen back up results in the gdm login screen; the session
seems to have ended. This happens consistently.

From the symptoms described, GNOME Shell appears to have crashed,
resulting in the session terminating.

The bug reporter confirmed in private email that disabling the "window
list" extension is a workaround for this, therefore this is probably a
bug in that extension.

This would probably still be useful information for whoever investigates
this bug next.

    smcv