Fedora logs out after Super + L

Ask Fedora
1

I’m using fedora for quite some time and recently it’s started to just randomly log me out and stop all of the process of my user when I use super + L to lock the pc.

2

Can you provide some additional information, including which version of Fedora you are using and which edition or spin? Thanks!

1 Like
3

Might be good to relevant capture logs from journalctl around the time. It smells like a crash on lock/suspend, which is often a video card driver/memory issue.

4

Yes, of course.

inxi -b

System:
  Host: fedora-40-workstation Kernel: 6.13.9-100.fc40.x86_64 arch: x86_64
    bits: 64
  Desktop: GNOME v: 46.9 Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Dash F15 FX516PE_FX516PE
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FX516PE v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: FX516PE.330 date: 05/15/2023
Battery:
  ID-1: BAT0 charge: 56.7 Wh (100.0%) condition: 56.7/76.0 Wh (74.6%)
    volts: 15.8 min: 15.8
CPU:
  Info: quad core 11th Gen Intel Core i7-11370H [MT MCP] speed (MHz):
    avg: 3143 min/max: 400/4800
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] driver: nvidia
    v: 570.133.07
  Display: wayland server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
    compositor: gnome-shell driver: X: loaded: modesetting failed: nvidia
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.133.07 renderer: NVIDIA
    GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2
  Info: Tools: api: glxinfo,vulkaninfo gpu: nvidia-settings,nvidia-smi
    x11: xdriinfo, xdpyinfo, xprop, xrandr
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi
  Device-2: Realtek driver: r8169
Drives:
  Local Storage: total: 953.87 GiB used: 230.22 GiB (24.1%)
Info:
  Memory: total: 16 GiB note: est. available: 15.31 GiB
    used: 11.53 GiB (75.4%)
  Processes: 514 Uptime: 1d 1h 23m Shell: Bash inxi: 3.3.37

This is the journalctl of logging out in the last day.
Using journalctl -u systemd-logind --since "1 day ago".

5

Does Super-L always log you out or only sometimes?
If it is all the time then check what Super-L is current bound to.

6

By default, it locks the screen, but it can also trigger a suspend, depending on your idle settings. I say “by default” but Gnome now disables this by default for some reason, but if the dconf flag is enabled, then it’s locks the screen like other DEs.

7

I’m running Fedora 41 and your post feels curiously familiar enough to reply, there’s been a couple times in the last month or so when I’ve locked my machine (Super +L) at the end of the day only to login in the morning and have ALL my apps which I know I left open, not running, as if my user had strangely been logged out. I’d think to myself Huh, that was weird, but simply go about my day…I will now pay closer attention. :thinking: :thinking: :thinking:

1 Like
8

Maybe the OOM killer ran?
If so it will be in the system journal. Worth looking for.

9

maybe yours was just electric shortage

10

It happens sometimes.
Most of the time it makes the pc to go to sleep.
And although the title said it’s only after super + L sometimes after the pc goes to sleep the ‘sleep time’ it logs me off.
At first I thought it was an OOM kill but then it happened to me when only I had my browser and vscode open and I have a 16GB RAM laptop.

11

I added my journalctl logs.

12

Check to see if gnome-shell is crashing. I had gnome-shell crash yesterday when I hit super + L to lock screen and my session exited and dropped me at the login screen. Others are seeing similar issues. Refer to 2316352 – [abrt] gnome-shell: st_theme_node_lookup_shadow(): gnome-shell killed by SIGSEGV.

13

Well, I just upgraded to 42 and will inform this thread if I experience such again.

1 Like