Edit: Fixed by this comment: https://lemm.ee/comment/8626267 Thanks!

Hi all, please help me figure out this weird issue I’ve been having. Any time I leave my laptop idle for a long time, when I come back to it, it’s back to the log in screen as in the laptop rebooted.

I am not sure which logs I should be looking for to figure out the source of the problem.

Here’s my system info:

             .',;::::;,'.                verde@verde-xps 
         .';:cccccccccccc:;,.            --------------- 
      .;cccccccccccccccccccccc;.         OS: Fedora release 39 (Thirty Nine) x86_64 
    .:cccccccccccccccccccccccccc:.       Host: XPS 15 9520 
  .;ccccccccccccc;.:dddl:.;ccccccc;.     Kernel: 6.6.11-200.fc39.x86_64 
 .:ccccccccccccc;OWMKOOXMWd;ccccccc:.    Uptime: 22 mins 
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:.   Packages: 2754 (rpm), 56 (flatpak) 
,cccccccccccccc;MMM.;cc;;WW::cccccccc,   Shell: bash 5.2.21 
:cccccccccccccc;MMM.;cccccccccccccccc:   Resolution: 2560x1440 
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc:   DE: GNOME 45.3 
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc;   WM: Mutter 
ccccc:XM0';cccc;MMM.;cccccccccccccccc'   WM Theme: Yaru-purple-dark 
ccccc;MMo;ccccc;MMW.;ccccccccccccccc;    Theme: Yaru-purple-dark [GTK2/3] 
ccccc;0MNc.ccc.xMMd:ccccccccccccccc;     Icons: Yaru-purple-dark [GTK2/3] 
cccccc;dNMWXXXWM0::cccccccccccccc:,      Terminal: gnome-terminal 
cccccccc;.:odl:.;cccccccccccccc:,.       CPU: 12th Gen Intel i9-12900HK (20) @ 4.900GHz 
:cccccccccccccccccccccccccccc:'.         GPU: NVIDIA GeForce RTX 3050 Ti Mobile 
.:cccccccccccccccccccccc:;,..            GPU: Intel Alder Lake-P GT2 [Iris Xe Graphics] 
  '::cccccccccccccc::;,.                 Memory: 7683MiB / 63971MiB
    • Bruno Finger@lemm.eeOP
      1·
      11 months ago

      not rude. yeah it’s a login screen as when I input my password all apps that I was using are closed, blank new session.

      • allywilson@sopuli.xyz
        2·
        11 months ago

        OK, thanks.

        I guess it’s worth confirming if it’s been a logout or a reboot as well. If you open a terminal and type “uptime” does the time match when you booted up or after you left it alone for a while?

        Check the output of: dmesg -T and have a look through: /var/log/messages

        I would be focussing on errors, warnings and/or terms like “reboot, shutdown, logout, timeout, idle, etc.” to try to narrow it down what is happening and when.

  • 1984@lemmy.today
    4·
    11 months ago

    If it really has rebooted, it could be some graphics driver issue causing it to freeze up. I had stuff like that on Nvidia graphics back in the day. Linux will reboot itself after a while if it freezes.

  • reyemxela@lemmy.worldEnglish
    4·
    11 months ago

    Ooh, I might actually be able to help here. Try disabling screen sleep in your power options and see if that fixes it. It took me a long time to narrow my issues down to that. I still don’t know why it happens.

    And definitely let me know if that fixes the issue for you. I’d love to know it’s not just me and my laptop.

    • Bruno Finger@lemm.eeOP
      3·
      11 months ago

      Thanks, I had screen sleep set to 10 minutes. Hibernation has been off since a long time. I will let you know by tomorrow if this fixed it.

  • 🧟‍♂️ Cadaver@lemmy.world
    4·
    11 months ago

    I have had the same issue in the past.

    It might come from going into hibernation. Since you have an nvidia card it’s where the error is most likely.

    • carcus@lemmy.mlEnglish
      2·
      11 months ago

      Without more info this is a good best guess. However, Instead of the graphics card I would suspect an undersized swap space to support hibernation.

  • lemmyreader@lemmy.ml
    3·
    11 months ago

    Yes, agreed with the other comment. Did you check uptime command ? In your system info it shows Uptime : 22 mins. In a terminal you can also type uptime or w

  • FooBarrington@lemmy.world
    1·
    11 months ago

    Is it possible that you’re on a different TTY? The login screen used in Fedora has some problems with using the correct TTY if you don’t use auto-login. If this happens again, try cycling through them, maybe your old session is still there.