[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 --- Comment #11 from Bug Janitor Service --- 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

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 Nate Graham changed: What|Removed |Added CC||n...@kde.org See Also|

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 Martin Klapetek changed: What|Removed |Added CC|mklape...@kde.org | -- You are receiving this mail because:

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 --- Comment #9 from soredake --- Any progress on this? -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 Oskar Roesler changed: What|Removed |Added CC||o.roes...@oscloud.info --- Comment #8 from

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 OlafLostViking changed: What|Removed |Added CC|

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 mp3.1...@o2.pl changed: What|Removed |Added CC||mp3.1...@o2.pl --- Comment #7 from

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 William Becker changed: What|Removed |Added CC||wbec...@gmail.com ---

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 slartibar...@gmail.com changed: What|Removed |Added CC||slartibar...@gmail.com --- Comment #5

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 --- Comment #4 from Johannes --- 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

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 --- Comment #3 from Martin Gräßlin --- next time try to kill kglobalaccel. Maybe then xorg usage goes down. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 --- Comment #2 from Johannes --- 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

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 --- Comment #1 from Martin Gräßlin --- 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: *

[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

https://bugs.kde.org/show_bug.cgi?id=360421 Martin Klapetek changed: What|Removed |Added Target Milestone|1.0 |---