Bug 370920

Summary:	Meta key sometimes stops working after suspend phase
Product:	[Plasma] kwin	Reporter:	Roman Gilg <subdiff>
Component:	input	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugs.kde.org, d.misdanitis, dev, lalochcz
Priority:	NOR	Flags:	mgraesslin: X11+
Version:	git master
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Roman Gilg 2016-10-15 15:57:59 UTC

I can't tell if the problem was also present prior to 5.8.1 e.g. prior to https://phabricator.kde.org/D2945
but now sometimes I can't open the start menu anymore after a suspend phase.

At the moment I don't have more precise information. I have to monitor the situation a bit more.

Reproducible: Sometimes

Comment 1 Bastian Köcher 2016-10-31 08:20:30 UTC

I can not confirm that it is triggered by suspend/resume. However, I have the bug on my laptop and there I only use suspend.

Comment 2 David Strobach 2016-10-31 22:52:56 UTC

For me it gets reliably triggered by switching virtual terminals. I'm currently on 5.8.2, but IIRC it happens since 5.8.0.

Comment 3 Martin Flöser 2016-11-01 07:49:46 UTC

Good theory with the vt switch. Though I just tried and was not able to reproduce. But it might be a good idea to reset the state on vt switch.

Comment 4 David Strobach 2016-11-01 08:21:10 UTC

I just realized that it only happens to me with evdev driver. xf86-input-libinput survives the VT switch just fine.

Comment 5 Bastian Köcher 2016-11-01 08:46:08 UTC

I will try xf86-input-libinput and will report back the results.

Comment 6 Roman Gilg 2016-11-03 12:28:21 UTC

You're right David. It stops working on VT switch. Maybe this is what happened to me and not the suspend phase (or maybe is there an implicit VT switch when suspending?).

Comment 7 Martin Flöser 2016-11-16 10:27:31 UTC

Once https://phabricator.kde.org/D3379 is merged I would like you to open the debug console check whether any modifiers are considered active. If not, I'll extend it further to also inspect the mod-only-trigger-state.

Comment 8 David Strobach 2016-11-17 15:43:26 UTC

(In reply to Martin Gräßlin from comment #7)
> Once https://phabricator.kde.org/D3379 is merged I would like you to open
> the debug console check whether any modifiers are considered active. If not,
> I'll extend it further to also inspect the mod-only-trigger-state.

I did. No active modifiers, sorry.

Comment 9 Martin Flöser 2016-11-18 06:34:39 UTC

ok, I'll add more features to it.

Comment 10 Bastian Köcher 2016-11-18 19:38:40 UTC

Sorry for late reply, but at the moment the meta key seems to work always. I switched libinput. I can suspend/resume and switch to virtual terminals, the meta key continues to work. Maybe the last KDE applications update fixed it?

Comment 11 Roman Gilg 2016-11-19 14:20:06 UTC

I just tested it also on git master (Wayland session) and I can confirm there seem to be no problems at the moment.

Comment 12 Martin Flöser 2016-12-28 08:05:04 UTC

*** Bug 373798 has been marked as a duplicate of this bug. ***

Comment 13 silentz0r 2016-12-28 12:16:24 UTC

I also noticed something else: occasionally my laptop screen stays black after suspend and I need to switch to another vterm (e.g. ctrl+alt+F2) and then switch back, in which case the screen shows me output. If I suspend a few more times after that the screen will eventually not come on at all. Yesterday I noticed that as soon as this happened, the meta key also didn't work.

Comment 14 Christoph Feck 2017-01-19 17:05:46 UTC

*** Bug 375228 has been marked as a duplicate of this bug. ***

Comment 15 Martin Flöser 2017-03-19 12:44:48 UTC

We added some more hardening to the mod-only shortcuts like e.g. 4a976d58ec50d6acd22e5cdbff0ca7fbda1367d0. I think we fixed it for good now in 5.10. In case it still happens with current git master of 5.10 please reopen.