Created attachment 135537 [details] dmesg from failed relogin attempts SUMMARY When I "re-login" into plasma "quickly", it freezes after correctly entering the password. I can still move the cursor, but I cant really do anything. Restarting sddm via a second tty brings my login screen back, but when I enter the PW, I get the same situation. I have to reboot to fix it. STEPS TO REPRODUCE 1. Boot and sign in (works without problems) 2. Sign out (I.e. via KDE Menu) 3. Sign in "quickly", by quickly I don't mean: "Try as hard as you can", but just like when you simply want to sign out and back in again. (Some settings and installations require that) This does not happen if I let a minute pass between signing out and back in! OBSERVED RESULT After typing in my PW and hitting enter, plasma freezes. I can still move the cursor and use ctrl+alt+f2 to get a different tty, but the original shell is unusable. I tried `systemctl restart display-manager` and `sddm` and `pkill X`. That allows me to type in my password again, but it also freezes up again. I have to reboot the system to get a plasma session working again. The first time the freeze happens, I am seeing ACPI errors in dmesg. I then systemctl restart sddm, try signing in again and get supressed callbacks in dmesg. After some more time, while I am saving the dmesg outputs, sddm apparently restarts itself: acc. to dmesg it experienced a segfault. I try signing in again, no luck. Dmesg shows "suppressed callbacks". I am attaching the annoted dmesg. EXPECTED RESULT Just wanna sign back in. :) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.10.14-arch1-1 plasmashell 5.20.5 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: Not applicable I guess Qt Version: Not applicable I guess ADDITIONAL INFORMATION Not seeing a ~/.xsession-errors
I might have tracked this down to "xembedsniproxy". I was actually investigating a different issue: Sometimes my CPU would start ramping up and refuse to come down. System Activity Monitor would show Xorg constantly consuming 12% cpu (one core). This occurred randomly but ALWAYS when plugging in an additional screen. Using sudo htop I could see that "xembednisproxy" was wreaking the havoc, which led me to this forum post: https://forum.kde.org/viewtopic.php?f=289&t=168880 And indeed, I had recently switched to the "Flatery" Icon pack. Switching back to the "breeze Icons" made the ramp-up and my re-login issue disappear so far. (Only tested for a few hours but I am pretty positive). I really don't think this falls within expected behavior. Please let me now what I can do to help fix this.
Another thing that seems to trigger "xembedsniproxy" seems to be blueman. I noticed because the only noticeable effect killing xembedsniproxy had, was that the blueman icon disappeared from my system tray. I am gonna switch to bluedevil for now, tho its a bit of a bummer since it does not allow me to switch audio profiles on my bluetooth headset. :/ .
Are you still able to reproduce this issue today in Plasma 5.27.5 or later? I suspect the systemd-enabled Plasma boot process may have fixed it.
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!