[kwin] [Bug 410181] when using an xmodmap, some key-combinations never reach the active application
https://bugs.kde.org/show_bug.cgi?id=410181 --- Comment #5 from Arne Babenhauserheide --- This works in recent versions of Gnome, but it is still broken in KDE. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410181] when using an xmodmap, some key-combinations never reach the active application
https://bugs.kde.org/show_bug.cgi?id=410181 --- Comment #4 from Arne Babenhauserheide --- Do you mean "is not responsible"? Where is the appropriate place? I filed it here because I now have a secondary workspace with Gnome and I do not see this happening there — with the same applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410181] when using an xmodmap, some key-combinations never reach the active application
https://bugs.kde.org/show_bug.cgi?id=410181 --- Comment #2 from Arne Babenhauserheide --- xev info: CTRL-c (which works): KeyPress event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399383802, (116,-374), root:(3655,648), state 0x0, keycode 66 (keysym 0xffe3, Control_L), same_screen YES, XKeysymToKeycode returns keycode: 37 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399384026, (116,-374), root:(3655,648), state 0x4, keycode 38 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: (03) "" XmbLookupString gives 1 bytes: (03) "" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399384146, (116,-374), root:(3655,648), state 0x4, keycode 38 (keysym 0x63, c), same_screen YES, XLookupString gives 1 bytes: (03) "" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399386210, (116,-374), root:(3655,648), state 0x4, keycode 66 (keysym 0xffe3, Control_L), same_screen YES, XKeysymToKeycode returns keycode: 37 XLookupString gives 0 bytes: XFilterEvent returns: False CTRL-x (which does not work) KeyPress event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399386883, (116,-374), root:(3655,648), state 0x0, keycode 66 (keysym 0xffe3, Control_L), same_screen YES, XKeysymToKeycode returns keycode: 37 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False FocusOut event, serial 40, synthetic NO, window 0x861, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 40, synthetic NO, window 0x861, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 40, synthetic NO, window 0x0, keys: 54 0 0 0 0 0 16 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399387532, (116,-374), root:(3655,648), state 0x4, keycode 52 (keysym 0x78, x), same_screen YES, XLookupString gives 1 bytes: (18) "▒" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399388844, (116,-374), root:(3655,648), state 0x4, keycode 66 (keysym 0xffe3, Control_L), same_screen YES, XKeysymToKeycode returns keycode: 37 XLookupString gives 0 bytes: XFilterEvent returns: False CTRL-SHIFT-x (which does work): KeyPress event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399489172, (-913,-277), root:(2626,745), state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399489172, (-913,-277), root:(2626,745), state 0x1, keycode 66 (keysym 0xffe3, Control_L), same_screen YES, XKeysymToKeycode returns keycode: 37 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399490068, (-913,-277), root:(2626,745), state 0x5, keycode 52 (keysym 0x58, X), same_screen YES, XLookupString gives 1 bytes: (18) "▒" XmbLookupString gives 1 bytes: (18) "▒" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399490212, (-913,-277), root:(2626,745), state 0x5, keycode 52 (keysym 0x58, X), same_screen YES, XLookupString gives 1 bytes: (18) "▒" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399491852, (-913,-277), root:(2626,745), state 0x5, keycode 50 (keysym 0xffe6, Shift_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x861, root 0x236, subw 0x0, time 2399491876, (-913,-277), root:(2626,745), state 0x4, keycode 66 (keysym 0xffe3, Control_L), same_screen YES, XKeysymToKeycode returns keycode: 37 XLookupString gives 0 bytes: XFilterEvent returns: False -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410181] when using an xmodmap, some key-combinations never reach the active application
https://bugs.kde.org/show_bug.cgi?id=410181 Arne Babenhauserheide changed: What|Removed |Added OS|Android 9.x |Linux --- Comment #1 from Arne Babenhauserheide --- This might be connected to https://bugs.kde.org/show_bug.cgi?id=310881 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410181] New: when using an xmodmap, some key-combinations never reach the active application
https://bugs.kde.org/show_bug.cgi?id=410181 Bug ID: 410181 Summary: when using an xmodmap, some key-combinations never reach the active application Product: kwin Version: 5.12.8 Platform: Ubuntu Packages OS: Android 9.x Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: arne_...@web.de Target Milestone: --- Created attachment 121712 --> https://bugs.kde.org/attachment.cgi?id=121712=edit crie.xmodmap SUMMARY When I switch to a different keyboard layout with xmodmap, the CTRL-x key combination does not reach the applications. Curiously the blinking cursor reacts to the keystroke by restarting the blinking. STEPS TO REPRODUCE 1. switch to alternate keyboard layout with `setxkbmap de -option ctrl:nocaps; xmodmap path/to/crie.xmodmap` — take the xmodmap from the attachment. 2. Select some text. 3. On a German keyboard type CTRL-y, on a US keyboard type CTRL-z (this is mapped to CTRL-x in the xmodmap) 4. Observe that the text is not cut. 5. Switch back to your regular keyboard layout with `setxkbmap de -option ctrl:nocaps` (replace de by your locale) OBSERVED RESULT CTRL-x does not reach the text field, the text is not cut, but the cursor restarts blinking. EXPECTED RESULT CTRL-x reaches the text field and cuts the text. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.04, Kernel: 4.15.0-52-generic (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION This is a long-standing bug and I’ve been using a workaround for years in Emacs (use CTRL-SHIFT-x — this does not work in the browser, though). I also observed this in Gentoo GNU/Linux with a customized setup, so this is not from the distribution. It might be connected to the switch to XCB with Qt5 (yes, the bug already exists for that long). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 319972] When I use a gesture while xmodmap is running, gestures stop working
https://bugs.kde.org/show_bug.cgi?id=319972 Arne Babenhauserheide changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Arne Babenhauserheide --- This no longer happens in Plasma 5. Thank you for re-asking! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 218447] SystemSettings crashed when trying to apply changes to keyboard shortcuts [QList, KHotKeys::ActionDataGroup::children, KHotkeysModel::parent]
https://bugs.kde.org/show_bug.cgi?id=218447 Arne Babenhauserheide changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #8 from Arne Babenhauserheide --- no longer happens in KDE 5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 268278] telling KDE to always activate numlock lead to strange effects (including broken global shortcuts) with a custom xmodmap
https://bugs.kde.org/show_bug.cgi?id=268278 --- Comment #6 from Arne Babenhauserheide --- (In reply to Arne Babenhauserheide from comment #5) > This still happens, but I missed the request for more info — sorry about > that :-( > > IT also happens when the numlock is activated manually. With bare X11 and emacs on top, it all works. Different display managers have different kinds of problems, though (i.e. in dwm and xmonad some keys are completely ignored). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 268278] telling KDE to always activate numlock lead to strange effects (including broken global shortcuts) with a custom xmodmap
https://bugs.kde.org/show_bug.cgi?id=268278 --- Comment #5 from Arne Babenhauserheide --- This still happens, but I missed the request for more info — sorry about that :-( IT also happens when the numlock is activated manually. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 266959] missing ~/.config/menus/applications.menu leads to empty menus and failing kbuildsycoca4 --menutest
https://bugs.kde.org/show_bug.cgi?id=266959 Arne Babenhauserheide changed: What|Removed |Added Resolution|REMIND |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 326672] selecting encrypt all in the unencrypted warning does not work and causes a crash
https://bugs.kde.org/show_bug.cgi?id=326672 Arne Babenhauserheide changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Arne Babenhauserheide --- I no longer see this. Thank you for curating the bugs! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 285142] KWin crashed when switching windows via alt-tab
https://bugs.kde.org/show_bug.cgi?id=285142 Arne Babenhauserheide changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 342600] gnupg: Answer to encrypted mail should by default be encrypted
https://bugs.kde.org/show_bug.cgi?id=342600 --- Comment #2 from Arne Babenhauserheide <arne_...@web.de> --- I still didn’t manage to get all of KDE 5 to build, so I cannot check that yet (I’ve been working for month to fix cruft which accumulated on my system, but I rarely have enough uninterrupted computer time to let large re-emerges finish). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 327986] when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password
https://bugs.kde.org/show_bug.cgi?id=327986 --- Comment #8 from Arne Babenhauserheide <arne_...@web.de> --- (In reply to Sandro Knauß from comment #7) > Please - still awnser my question: Are the recipients are hidden in the > mail? This is a feature of gpg and than gpg has to test every private key ( > in worst case scenario), because I can be that only the last key is the one > that decrypts the email. If gpg can see the keyIds it should only ask for > these keys to enter the passphrase. There are hidden recipients, yes. That might explain the issue… Sorry for being so slow to answer - and thank you for persisting! A possibility to improve this might be to first try the key for the email address with which I received the email. I cannot currently test this with a kmail based on kde5, because akonadi currently does not work at all for me (fails to start and the error logs says that all old accounts are missing). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 347964] Shortcuts mixup and falling through mouse clicks with non-standard keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=347964 --- Comment #27 from Arne Babenhauserheide <arne_...@web.de> --- (In reply to Arne Babenhauserheide from comment #26) > Might be related: With plasma kde-plasma/kwin 5.6.5-r1 CTRL-X does not reach > the application when setting a lithauian keyboard (lv), but the copied text > appears in klipper. This makes it pretty hard to use Emacs. I now found that I can trigger CTRL-x in emacs with CTRL-SHIFT-x. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 347964] Shortcuts mixup and falling through mouse clicks with non-standard keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=347964 Arne Babenhauserheide <arne_...@web.de> changed: What|Removed |Added CC||arne_...@web.de --- Comment #26 from Arne Babenhauserheide <arne_...@web.de> --- Might be related: With plasma kde-plasma/kwin 5.6.5-r1 CTRL-X does not reach the application when setting a lithauian keyboard (lv), but the copied text appears in klipper. This makes it pretty hard to use Emacs. -- You are receiving this mail because: You are watching all bug changes.
