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

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=360421

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #12 from Bug Janitor Service  ---
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!

-- 
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

[Bug Janitor Service]

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 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!

-- 
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

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=360421

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=370676
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #10 from Nate Graham  ---
The kglobalaccel 100% CPU bug was fixed in Plasma 5.21. Is anyone able to
reproduce this in 5.21 or 5.22?

-- 
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

[Martin Klapetek]

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:
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

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=360421

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=419142

-- 
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

[soredake]

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

[soredake]

https://bugs.kde.org/show_bug.cgi?id=360421

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

-- 
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

[Oskar Roesler]

https://bugs.kde.org/show_bug.cgi?id=360421

Oskar Roesler  changed:

   What|Removed |Added

 CC||o.roes...@oscloud.info

--- Comment #8 from Oskar Roesler  ---
I have a definitely related bug: https://bugs.kde.org/show_bug.cgi?id=405355

-- 
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

[OlafLostViking]

https://bugs.kde.org/show_bug.cgi?id=360421

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

-- 
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

[bugzilla_noreply]

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 mp3.1...@o2.pl ---
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.

-- 
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

[William Becker]

https://bugs.kde.org/show_bug.cgi?id=360421

William Becker  changed:

   What|Removed |Added

 CC||wbec...@gmail.com

--- Comment #6 from William Becker  ---
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.

-- 
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

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=360421

slartibar...@gmail.com changed:

   What|Removed |Added

 CC||slartibar...@gmail.com

--- Comment #5 from slartibar...@gmail.com ---
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!!!

-- 
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

[Johannes via KDE Bugzilla]

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 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).

-- 
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

[Martin Gräßlin via KDE Bugzilla]

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

[Johannes via KDE Bugzilla]

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 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.

-- 
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

[Martin Gräßlin via KDE Bugzilla]

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:
* killall -9 kscreenlocker_greet
* switch back to graphical tty.

-- 
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

[Martin Klapetek via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360421

Martin Klapetek  changed:

   What|Removed |Added

   Target Milestone|1.0 |---
Version|5.5.5   |unspecified
Product|plasmashell |kscreenlocker
   Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org
 CC||mgraess...@kde.org,
   ||mklape...@kde.org
  Component|general |greeter

-- 
You are receiving this mail because:
You are watching all bug changes.