SUMMARY Since the upgrade to Plasma 6, I find many times, at least once per day, when I left my computer with the desktop idle during a while, when I come back, the session has been closed. Uptime command shows my computer hasn't been restarted, but when I enter the credentials, the desktop loads as if the session were closed. STEPS TO REPRODUCE 1. Open plasma session 2. Do some stuff 3. Leave the computer, go for a walk, to lunch, etc OBSERVED RESULT Sometimes when I come back, the session is locked (as expected), some other times the session is still unlocked (even if it has been idle for two or three hours, which is not normal, but I think it's not related to this issue and is not so fatidic as at least I don't lose any job, or close any ssh), and sometimes, the session has been closed, which in my opinion is the worst case scenario, because in this case, I've lost all the unsaved work. EXPECTED RESULT Session should be locked and monitors in saving energy mode. (if it's configured like this) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I'm on X11, as Wayland is buggy with my nvidia card.
Hi - I've not seen this problem myself on a clean Neon install. We're going to need to try to narrow it down but I suspect this is something in the underlying OS rather than Plasma. Could you please try to provide more details, or if the problem goes away please close the bug? Thanks, Nick
Sure, what else can I provide? Is there any log where I can see if something has closed the session? When I start plasma again, there is no crash report, so it seems it closed "properly". I'm running arhc linux in this computer since my last computer died 3 years ago. So I've been upgrading everything to the latest version since then. This issue is hard to reproduce, I turn on the computer at 7am and power it off around 2am, I work from home, so I leave it with my session open always, and sometimes I need to go AFK for a while. It does not happens every time, just one time or so each day. If I could take a look somewhere in those moments, it would be of great help.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
The issue is present after the upgrade to plasma 6, so while it could be due to my OS, the only change is the version of plasma. As I said, I would be eager to help if someone tell me how can I see the plasma logs and have a look when this happens, which happens in a daily basis
It happened again. I went to lunch, and I when I came back, session was closed. I opened a terminal and execute the command uptime. > uptime > 15:40:33 up 7:27, 1 user, load average: 3,45, 0,93, 0,32 I've took a look into journalctl and I saw a core dump, but I don't know if it was related to KDE... https://hastebin.com/share/kozoqefiji.yaml
It happened again. This time, I was in a videocall in the company's Mac, and my computer was going idle, and everytime the screen went off, I pressed quickly one key before the desktop were locked. One time, though, even I pressed the key, the sddm screen appeared, and yes, the session started once again. I paste the logs, they are pretty similar than the last I posted: X11 seems to die just when the screen lock starts. Here is the pastebin of the sudden crash and this time, I'm including the login as well https://hastebin.com/share/rifegefisi.sql
Just to mention I disabled nvidia_modeset because, IIRC, I activated it to make hyprland working with nvidia, but as we can see, plasma hangs even with this change, and I had installed hypranland and the nvidia_modeset module activated for more than a year, and all this stuff began with the plasma 6 upgrade.
This generally happens when kwin_wayland has crashed. Can you get a backtrace of the crash (see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl) and attach it here? If you already did at https://hastebin.com/share/rifegefisi.sql, then sorry for not getting to this sooner, because the link appears to have expired, unfortunately.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.