Summary: | After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary | ||
---|---|---|---|
Product: | [Plasma] kscreenlocker | Reporter: | Johannes <kdebugs.spam> |
Component: | greeter | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | critical | CC: | bhush94, katyaberezyaka, mgraesslin, mp3.1415, nate, o.roesler, olaf.the.lost.viking, plasma-bugs, slartibart70, wbecker |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=419142 https://bugs.kde.org/show_bug.cgi?id=370676 |
||
Latest Commit: | Version Fixed In: |
Description
Johannes
2016-03-11 18:25:25 UTC
next time it happens, please try: * login in to a tty (e.g. ctrl+Alt+F2) * run loginctl unlock-sessions * switch back to graphical tty if unlocked, win, otherwise go back to the tty and: * killall -9 kscreenlocker_greet * switch back to graphical tty. Did that, it helped (the screen was unlocked and usable again), but the problems about high CPU load after TTY switching remained. "Unfortunately" the error only occurred once since your comment, which is odd since before it happened 50% of the time or so. So I couldn't check out what happens if I wake up with screen locker deactivated. next time try to kill kglobalaccel. Maybe then xorg usage goes down. Killing kglobalaccel didn't help. The Xorg usage went up to 100% and other applicatoins (plasmashell, kwalletd5, kwin_x11, ksmserver, yakuake, and krunner) went up to ~22% cpu usage. Also afterwards the complete screen froze (mouse was movable but nothing reacted, killing the konsole that was in foreground from another TTY didn't make it disappear as well). Same here with fedora25/kde on lenovo laptop t420(intel graphics) Sleep/resume goes well if the laptop is sleeping for a short period of time. But if you let it sleep overnight, kscreenlocker just won't accept any keystrokes (nor is the cursor flashing in the input fields) Alternative shell (Alt-F2) is coming up slowly, meaning the keyboard inputs go to the system, the reaction does take a while. So, keyboard is working properly, but switching back to graphical input and we are still stuck (no mouse, no keyboard response) This is very annyoing!!! Same issues re login after sleep on up-to-date arch/kde on a Lenovo X220. In addition, the 60/40 xorg/kglobalaccel thing just started happening out of the blue in the middle of a session which took me to this bug report - however it did stop happening after about 30 seconds. I'm also affected on kubuntu 17.04. I can cause this problem either by switching to tty or by plugging in new usb device (suspending works at the moment). After enabling everything in kdebugdialog I noticed, that every time this problem occurs my .xsession-erros contains several repetitions of Initializing "kcm_input" : "kcminit_mouse" QXcbConnection: XCB error: 3 (BadWindow), sequence: 25627, resource id: 113246216, major code: 18 (ChangeProperty), minor code: 0 kdeinit5: Got SETENV 'KDE_MULTIHEAD=false' from launcher where 'resource id' is identical for all massages of all errorous events in whole kde session. I have a definitely related bug: https://bugs.kde.org/show_bug.cgi?id=405355 Any progress on this? The kglobalaccel 100% CPU bug was fixed in Plasma 5.21. Is anyone able to reproduce this in 5.21 or 5.22? 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! |