| Summary: | Numlock key not turning on under Wayland | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Andrius Štikonas <andrius> |
| Component: | input | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.9.4 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Andrius Štikonas
2017-04-06 17:07:25 UTC
Do you have an led? If yes, does it represent the state correctly? (In reply to Martin Gräßlin from comment #1) > Do you have an led? If yes, does it represent the state correctly? Yes, I have led and it didn't represent state correctly. I was going to write that I can't reproduce this anymore after reboot but now I managed to trigger it again after opening poedit. I guess something to do with XWayland. I.e. Kate as wayland client works fine now but Kate running under xcb does not work. Which Xwayland version are you using? (In reply to Martin Gräßlin from comment #3) > Which Xwayland version are you using? 1.19.2 hmm XWayland 1.19 really improved in getting the state updates right. Looks like not in all cases. As I don't have a keyboard with numlock: could you please test whether the same problem happens with Weston? I can't reproduce it from either Weston or Gnome session. Only in Plasma session. Hm, I wonder if this bug is caused by the same thing as #375708. After investigating bug #377155 I think it's that one. If you could test whether https://phabricator.kde.org/D5452 also works for this bug report, that would be appreciated. *** This bug has been marked as a duplicate of bug 377155 *** |