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-n...@kde.org
          Reporter: eforg...@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.

Reply via email to