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
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.
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.
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.
I just realized that it only happens to me with evdev driver. xf86-input-libinput survives the VT switch just fine.
I will try xf86-input-libinput and will report back the results.
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?).
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.
(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.
ok, I'll add more features to it.
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?
I just tested it also on git master (Wayland session) and I can confirm there seem to be no problems at the moment.
*** Bug 373798 has been marked as a duplicate of this bug. ***
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.
*** Bug 375228 has been marked as a duplicate of this bug. ***
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.