Bug 496362

Created attachment 175870 [details]
log files outputted after forced to log out.

SUMMARY
Randomly my system will force log me out and then when I try to log back in, I will get nothing but black screens and eventually my monitors will turn off, almost like they're not receiving any GPU output.

STEPS TO REPRODUCE
1. Log in to computer
2. Do literally anything
3. I get logged out automatically after 30 seconds - 4 minutes
4. I try logging back in, I get a black screen with nothing and my monitor(s) stop detecting output and turn off, but my computer remains on. Can't do anything. Forced to restart computer with button.

OBSERVED RESULT
KDE seemingly crashes/force-logs-me-out and stops my GPU output

EXPECTED RESULT
To not be forced to log out, and even if I was, be able to log back in without my GPU just not outputting anything.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.7.2
Kernel Version: 6.11.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4060/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650M C V2-Y1
System Version: -CF

ADDITIONAL INFORMATION

So this was not an issue when I first installed Fedora 40 KDE Spin, it just randomly started one day and I've been trying to figure this out forever, with zero luck.

I found some other people who are having the same bug (or appear to be), however:
https://www.reddit.com/r/Fedora/comments/1g9nyh4/fedora_kde_spin_logoutlogin_issue/

https://discussion.fedoraproject.org/t/new-user-problems-with-fedora-kde-spin-when-logging-in/132669


It is super annoying, the only "fix" I've found is restarting my computer and hoping it doesn't do it. It doesn't do this every time which I do not understand why. Someone in a discord recommended me to look at the logs after going into CLI at the log in screen, which I did get a log.txt file but I'm not able to find anything that I understand that would cause the issue. I also can't do the command startplasma-wayland in the CLI, it just doesn't do anything.

I know it is not a hardware issue because I tried installing a different OS and it worked just fine.

I'm going to attach the logs that I have when I opened the command line in the log in screen after being forced to log out, I used the following command: journalctl -b > logs.txt