Arch Linux

Unaipg

Member

Registered: 2014-07-04

Posts: 3

Cant use "m" key after updating to Gnome 3.18

Hi!

I just updated to gnome shell 3.18, then I restarted and my "m" is gone, it does nothing when I press it. I've tried to use it and works when I search an app or I'm typing in the Alt+F2 command box but I cant use it in the console, browser or any other place. Here is the xev output for the m key

FocusOut event, serial 36, synthetic NO, window 0x2800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 36, synthetic NO, window 0x2800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 36, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   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   0   

KeyRelease event, serial 36, synthetic NO, window 0x2800001,
    root 0xd4, subw 0x0, time 635522, (301,-434), root:(808,373),
    state 0x10, keycode 58 (keysym 0x6d, m), same_screen YES,
    XLookupString gives 1 bytes: (6d) "m"
    XFilterEvent returns: False

and here for any other key. I must say that (shift + m) works fine.

KeyPress event, serial 36, synthetic NO, window 0x2800001,
    root 0xd4, subw 0x0, time 724970, (425,97), root:(932,904),
    state 0x10, keycode 57 (keysym 0x6e, n), same_screen YES,
    XLookupString gives 1 bytes: (6e) "n"
    XmbLookupString gives 1 bytes: (6e) "n"
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x2800001,
    root 0xd4, subw 0x0, time 725051, (425,97), root:(932,904),
    state 0x10, keycode 57 (keysym 0x6e, n), same_screen YES,
    XLookupString gives 1 bytes: (6e) "n"
    XFilterEvent returns: False

I think there may be some keyboard shortcut binded to the character m but I've searched all the dconf and I haven't found anything.

Sorry for the English it's not my first language.

PD: I can write m by setting caps lock and using shift+m but this is painfull.

Edit:
localectl status output:

   System Locale: LANG=es_ES.UTF-8
       VC Keymap: es
      X11 Layout: es,us
     X11 Variant: ,

Last edited by Unaipg (2016-01-14 17:32:28)

drcouzelis

Member

From: Connecticut, USA

Registered: 2009-11-09

Posts: 4,092

Website

Re: Cant use "m" key after updating to Gnome 3.18

I think problems like that are usually due to either incorrectly mapped shortcuts or incorrect locale settings, as seen here: https://bbs.archlinux.org/viewtopic.php?id=199438

Did you change any other settings when you updated? What is the output of "localectl status"?

...Or maybe there is a bug in GNOME Shell...

EDIT: Oops, I think I accidentally confused your problem with another problem. I'm sorry if my comment isn't very useful.

Last edited by drcouzelis (2016-01-14 16:05:49)

Unaipg

Member

Registered: 2014-07-04

Posts: 3

Re: Cant use "m" key after updating to Gnome 3.18

I think problems like that are usually due to either incorrectly mapped shortcuts or incorrect locale settings, as seen here: https://bbs.archlinux.org/viewtopic.php?id=199438

Did you change any other settings when you updated? What is the output of "localectl status"?

...Or maybe there is a bug in GNOME Shell...

EDIT: Oops, I think I accidentally confused your problem with another problem. I'm sorry if my comment isn't very useful.

Dont worry, thanks for the answer, I've edited the first post with the output of "localectl status". I added the us one to check if it was the locale config for spanish but dont look like that.

I dont think there is a bug in GNOME,  more like I have something maped to that key but I cannot find what it is or where is the config. There is any way to trace what is happening when I press the key?