Created attachment 164503 [details] journalctl from that time period SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After waking up from StandBy my two monitor setup sometimes(!) shows a strange behaviour. One Monitor shows sddm-greeter with login, the other shows the Desktop that was active before StandBy. Both Monitors are unresponsive. Only way to solve this issue is either reboot or change into another virtualterminal, login and kill sddm, or kill plasma and startplasma from terminal. STEPS TO REPRODUCE 1. Let Linux get into StandBy ( on its own), let it rest there for a while 2. wake up by pressing button/mouse 3. see that it has crashed OBSERVED RESULT sometimes it crashes, sometimes it doesnt. when it does it is annoying as hell EXPECTED RESULT should not crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.13-7-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION its annoying that i cannot reproduce it all the time. Issue keeps on happening for almost a year now.
Sorry this is happening. A few questions: - Youu said SDDM; you mean the screen locker, right? Because SDDM is used for logging in, while kscreenlocker is used for screen locking. So are you talking about the lock screen, or have you configured the system to log out on sleep or something? - Are you using X11 or Wayland? - Does it ever happen when you have only one screen connected? - Do you have an NVIDIA GPU? - If you log into a VT and run `top` is kscreenlocker_greet using 100% CPU?
Hi, so i'm not sure, i guess it's sddm, i'll attach a foto from when this happens, for meit looks like sddm. All this is happening on x11. i haven't tried this with only one Monitor to be honest. >If you log into a VT and run `top` is kscreenlocker_greet using 100% CPU? nope, all seems normal, nothing running on high cpu, the easiest way for me to login on to the desktop is killing /usr/lib/sddm/sddm-helper when i do this everything loads normally and i can log in, (that's where my feeling that it's sddm stems from) So this is it how it looks like when my issue happens: https://s20.directupload.net/images/240216/gtzstkvn.jpg
(In reply to Nate Graham from comment #1) > Sorry this is happening. A few questions: > - Youu said SDDM; you mean the screen locker, right? Because SDDM is used > for logging in, while kscreenlocker is used for screen locking. So are you > talking about the lock screen, or have you configured the system to log out > on sleep or something? > - Are you using X11 or Wayland? > - Does it ever happen when you have only one screen connected? > - Do you have an NVIDIA GPU? > - If you log into a VT and run `top` is kscreenlocker_greet using 100% CPU? Hi, so i'm not sure, i guess it's sddm, i'll attach a foto from when this happens, for meit looks like sddm. All this is happening on x11. i haven't tried this with only one Monitor to be honest. >If you log into a VT and run `top` is kscreenlocker_greet using 100% CPU? nope, all seems normal, nothing running on high cpu, the easiest way for me to login on to the desktop is killing /usr/lib/sddm/sddm-helper when i do this everything loads normally and i can log in, (that's where my feeling that it's sddm stems from) So this is it how it looks like when my issue happens: https://s20.directupload.net/images/240216/gtzstkvn.jpg i do not own a nvidia card, its team red over here, amd gpu and amd cpu
> the easiest way for me to login on to the desktop is killing /usr/lib/sddm/sddm-helper This is confusing to me, because what you're looking at is clearly the lock screen, and SDDM isn't involved at all. If killing sddm-helper fixes the issue, that means that something on your system is misconfigured. Are you able to reproduce the issue in a new clean user account? If not, can you describe any customizations you've done on of this system?
(In reply to Nate Graham from comment #4) > > the easiest way for me to login on to the desktop is killing /usr/lib/sddm/sddm-helper > This is confusing to me, because what you're looking at is clearly the lock > screen, and SDDM isn't involved at all. If killing sddm-helper fixes the > issue, that means that something on your system is misconfigured. > > Are you able to reproduce the issue in a new clean user account? > > If not, can you describe any customizations you've done on of this system? So what i've tried is switching to wayland, which apparently fixes my issue with this. customizations i've done: "plain" manjaro out of the box, i have dual boot win 10 for my wife i tried a couple of sddm themes but am stuck with 'breath' installed intellij/vscode/qt had to delete couple of old kernels from hand but to be honest nothing comes to my mind that i have done besides trying out sddm themes that could have messed up sth there Is there anything concrete that you're thinking of that can mess up my configuration like that? i havn't tried creating a clean user and reproducing that since it appears to me switching to wayland resolves my issue. I'll try that when i can find the time.
Cool, thanks. Can you try again with X11 in Plasma 6, which is being released in one week? I think there's a chance it's fixed there.
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!