Discussion:
[kwin] [Bug 365255] New: inconsistent behavior with alt+7
Add Reply
Eric Forgeot via KDE Bugzilla
2016-07-08 21:11:37 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

Bug ID: 365255
Summary: inconsistent behavior with alt+7
Product: kwin
Version: unspecified
Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: core
Assignee: kwin-bugs-***@kde.org
Reporter: ***@yahoo.fr

(using KDE 4.14.2)

I couldn't use an alt+7 shortcut in an application. I discovered KDE was
intercepting it and modified the output. I thought it was a shortcut already
used in the KDE system, but couldn't find anything relevant in the shortcut
settings.

Reproducible: Always

Steps to Reproduce:
1. launch xev
2. test alt+6
3. test alt+7

Actual Results:
xev returns this for alt+6:

KeyPress event, serial 42, synthetic NO, window 0x5a00001,
root 0x28f, subw 0x0, time 323174779, (-206,579), root:(2110,608),
state 0x18, keycode 15 (keysym 0x36, 6), same_screen YES,
XLookupString gives 1 bytes: (36) "6"
XmbLookupString gives 1 bytes: (36) "6"
XFilterEvent returns: False

and for alt+7:


KeymapNotify event, serial 42, synthetic NO, window 0x0,
keys: 2 0 1 0 0 0 0 0 1 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 42, synthetic NO, window 0x5a00001,
root 0x28f, subw 0x0, time 323178411, (-206,579), root:(2110,608),
state 0x18, keycode 16 (keysym 0x37, 7), same_screen YES,
XLookupString gives 1 bytes: (37) "7"
XFilterEvent returns: False


Expected Results:
this part shouldn't be there:

KeymapNotify event, serial 42, synthetic NO, window 0x0,
keys: 2 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

I've encountered this on two different computers running linux mint 17.3 and
KDE.
It doesn't happen with the xfce desktop for example.
--
You are receiving this mail because:
You are watching all bug changes.
Eric Forgeot via KDE Bugzilla
2016-07-08 21:14:40 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #1 from Eric Forgeot <***@yahoo.fr> ---
just a precision: I'm generally using an azerty keyboard. In the application I
need alt+7, so I remapped my keyboard with "setxkbmap us" to be able to use the
correct keys (it does the same if I use "setxkbmap de" for example). When in
qwerty mode, alt+shift+7 is working correctly btw.
--
You are receiving this mail because:
You are watching all bug changes.
Thomas Lübking via KDE Bugzilla
2016-07-09 06:24:57 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

Thomas Lübking <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|kwin-bugs-***@kde.org |***@kde.org
CC| |kdelibs-***@kde.org
Product|kwin |frameworks-kglobalaccel
Component|core |general

--- Comment #2 from Thomas Lübking <***@gmail.com> ---
Try to kill and restart kglobalacceld after altering the layout, the event is
probably still being sucked by Qt. (KWin doesn't do shortcuts)
--
You are receiving this mail because:
You are watching all bug changes.
Martin Gräßlin via KDE Bugzilla
2016-07-11 06:57:41 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #3 from Martin Gräßlin <***@kde.org> ---
I don't understand where the KeymapNotify event comes from and doubt that
KGlobalacceld has anything to do with it.
--
You are receiving this mail because:
You are watching all bug changes.
Eric Forgeot via KDE Bugzilla
2016-07-12 17:33:32 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #4 from Eric Forgeot <***@yahoo.fr> ---
I can confirm that killing kglobalaccel solves the problem. But if I start it
again, the problem comes again, as if there was a shortcut assigned to this key
combination. I can live without the shortcuts system so killing kglobalaccel is
a good solution for my case.

I couldn't find any shortcut related to alt+7, and since there are several
programs in the "configuration of keybindings" it's quite tedious to check them
all. Which I did, but maybe not correctly.

Yet, I tried to assign alt+7 to a random command, and the system didn't
complain it was already assigned. Then I deleted the shortcut. And the problem
is still present, so I suppose there is a bug somewhere. Why only alt+7 and not
the other keys?
--
You are receiving this mail because:
You are watching all bug changes.
Martin Gräßlin via KDE Bugzilla
2016-07-12 18:02:37 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #5 from Martin Gräßlin <***@kde.org> ---
could you please attach your ~/.config/kglobalshortcutsrc? It should contain
the offending key.
--
You are receiving this mail because:
You are watching all bug changes.
Eric Forgeot via KDE Bugzilla
2016-07-12 19:46:57 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #6 from Eric Forgeot <***@yahoo.fr> ---
Created attachment 100041
--> https://bugs.kde.org/attachment.cgi?id=100041&action=edit
kglobalshortcutsrc

here it is. I've renamed it so it won't be used, but it's the same (but maybe
it need to log out and in again).
--
You are receiving this mail because:
You are watching all bug changes.
Eric Forgeot via KDE Bugzilla
2016-07-12 20:03:07 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #7 from Eric Forgeot <***@yahoo.fr> ---
I've also an installation of KDE on a different system, PC-BSD, under a virtual
machine. I've logged out of KDE on my linux system, and logged in xfce instead
(I don't have the alt+7 bug there). I've launched the PC-BSD machine, switched
to US keyboard, and with xev I got the same extra data sent by the alt+7
combination:

KeymapNotify event, serial 42, synthetic NO, window 0x0, keys: 2 0 1 0 0 0 0 0
1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

(and only with this alt+7 combination, alt+1 to 6 are correct, alt+8, 9 and 0
too).
--
You are receiving this mail because:
You are watching all bug changes.
Martin Gräßlin via KDE Bugzilla
2016-07-13 06:17:23 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #8 from Martin Gräßlin <***@kde.org> ---
I don't think that this is related to global shortcuts. Might it be that your
keymap has a layout switch on alt+7?
--
You are receiving this mail because:
You are watching all bug changes.
Eric Forgeot via KDE Bugzilla
2016-07-13 21:34:46 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #9 from Eric Forgeot <***@yahoo.fr> ---
I don't know but the keymap is working correctly with other desktop manager
(such as xfce). Don't you get those extra "KeymapNotify event..." with alt+7 on
your computer as well?
--
You are receiving this mail because:
You are watching all bug changes.
Jurica Vukadin
2018-12-06 12:42:39 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=365255

Jurica Vukadin <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #10 from Jurica Vukadin <***@gmail.com> ---
I've been poking at this in my spare time. It seems Alt+7 (and Alt+1 as well,
I'm using Croatian layout), gets intercepted by
KGlobalAccelImpl::nativeEventFilter(), while the others do not. I've added some
debug prints to KGlobalAccelImpl::nativeEventFilter() and get this when I hit
Alt+7:
responseType: 2
Got XKeyPress event
keyQt= "8000037" (this is Qt::AltModifier | Qt::Key_7)

For others I only get "responseType: 85" when I hit the Alt key.

Any clues how I can chase this down further?
--
You are receiving this mail because:
You are watching all bug changes.
Loading...