Without sounding rude, are you sure it's at the login screen and not the unlock screen?
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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.
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.
Could also be going to sleep for power saving.
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.
Seems to have fixed the issue, it didn't reboot overnight. Thanks!
I'd look if there's an updated BIOS version for your system, ACPI issues like that are usually a non-compliant subsytem in the firmware.
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.
lol I love that you unironically copypasted neofetch output
I just thought it was the easiest way to show relevant system information :p
totally irrelevant and irrespectfully hard to read for ppl volunteering to helpdesk you
What's so hard to read about that?
...
Huh, I guess must be something dependent on the client. On the web I can scroll horizontally in the code box instead:
Code blocks got updated in 0.19, lemmy.world is still on a 0.18 version
I get horizontal scroll even if I view the post on lemmy.world though
still not the point. Is it my own damn fault if I think it's stupid to pass this bolus of text? :D
I'm glad you can scroll horizontally, but the point I was making is that the action of posting that bolus of rubbish remains stupid 🤷🏼
oh, sorry about that, I didn't realize this could be bad for mobile users. All I needed was a command that could display all system info like distro name and version, kernel version, DE version, etc, I didn't necessarily need the distro logo and some other useless info in there.
no need to be sorry
the little effort involves taking the piss, just taking ourselves less seriously, we're only messing around online. And btw no info in neofetch is relevant :P
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.
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.
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.
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
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.