Bug 508663 - Forceful logout after about 30 seconds, desktop freeze on relogin
Summary: Forceful logout after about 30 seconds, desktop freeze on relogin
Status: REPORTED
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.4.4
Platform: CachyOS Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-23 21:56 UTC by Martin Häusler
Modified: 2025-09-02 07:23 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Häusler 2025-08-23 21:56:19 UTC
SUMMARY

I've had this issue before on Fedora (KDE), now I have it again on CachyOS... The procedure is always the same.


STEPS TO REPRODUCE

1. I start my PC, log in regularly

2. After about 30 seconds, the plasma desktop forcefully logs me out (no matter what I do, including doing nothing at all)

3. Attempting to log in again causes the desktop to freeze completely

This does not always happen (I suspect some form of race condition), but it's a severe impact on the reliability of the system.

Does anybody have any idea why this happens and what I can do to fix this? I realize now that this is very likely a KDE issue since it's the only common denominator between my previous Fedora installation and my current CachyOS installation.


OBSERVED RESULT

Forced logout, plasma shell freeze on relogin


EXPECTED RESULT

No forced logout to begin with, also relogin shouldn't freeze the plasma shell


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Verified separately on Fedora 42 and latest CachyOS
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version:  6.9.1

ADDITIONAL INFORMATION

I am running an Nvidia RTX 3080 graphics card with the proprietary drivers if that makes any difference.
Comment 1 Martin Häusler 2025-08-24 00:40:41 UTC
Here are the journalctl logs for the plasmashell between the initial boot, the freeze, and the subsequent (manually triggered) hard reset:

https://pastebin.com/s9ftDFGS
Comment 2 Nate Graham 2025-08-26 20:56:27 UTC
Unfortunately there's no information in the journal log that indicates an issue. If you're getting logged out, it sounds like KWin is either crashing or exiting. Can you look for kwin_wayland crash logd with `coredumpctl --reverse`?

See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 3 Martin Häusler 2025-08-26 21:46:38 UTC
H Nate,

thank you very much for taking the time to look into this. 

The issue just occurred right now since I've started my system to find the information you've requested. Same as described in the opening post. However, I have been able to do the following:

- I got forcefully logged out
- Instead of logging back in, I pressed `CTRL + ALT + F3` to open a terminal
- logged into the terminal session
- executed `killall plasmashell`
- switched back to the plasma session with `CTRL + ALT + F2`
- I was greeted by the chrome browser window I had open. Curiously, I was logged into the system and wasn' tasked for the password again.
- I executed `plasmashell` command and the syte


Does that help in the analysis?

So I ran the following command:

coredumpctl --reverse

... and piped the output in a text file. The system installation is only about a week old, so there's not too much going on in there. There are no logs in there that relate to wayland, kwin, kde, plasma, or any other related technology. Here's the entire resulting file:

https://pastebin.com/raw/NZGZaVnG

The `osqueryd` is very likely unrelated. I suspect it's coming from a device management software I had to install for my employer. There's a chrome crash in there once but that's about it.

So... did no process crash, or did one crash and just doesn't show up in that log either? Somehow my entire desktop is having a stroke and leaves no traces about it anywhere it seems.
Comment 4 Nate Graham 2025-08-26 22:06:25 UTC
Hmm, no KWin crash. It's possible KWin is *exiting* which is worse. Let's see if we can get more logs. Can you run:

> journalctl -xb 0 > ~/Desktop/boot.log

And then go through it and remove any personal information, and then attach it here?

Thanks!
Comment 5 Martin Häusler 2025-08-27 16:46:39 UTC
Hello again,

sorry for the delay. Here's the requested boot.log:

https://pastebin.com/raw/8YkETcEu

I hope this helps.
Comment 6 Nate Graham 2025-08-28 15:15:59 UTC
Thanks. Unfortunately I don't see anything incriminating in there. Moving to KWin (since that's most likely what's dying and kicking you out) so the folks there can investigate.
Comment 7 Martin Häusler 2025-09-02 07:23:06 UTC
Hi,

I just wanted to ask if someone from the KWin team has looked into the matter in the meantime. I'm happy to provide additional diagnostic information as necessary. This bug is the bane of my existence at the moment.