[SOLVED] Can no longer type "dead_acute" and "dead_caron"

MightyPork · 2015-07-27 19:08:25

The characters are mapped properly:

xmodmap -pk

     21    	0xfe51 (dead_acute)	0xfe5a (dead_caron)	0xfe51 (dead_acute)	0xfe5a (dead_caron)	0xfe54 (dead_macron)	0xfe5b (dead_cedilla)	0xfe54 (dead_macron)

"xev" also (I think) confirms they are there:

KeyPress event, serial 103, synthetic NO, window 0x4c00001,
    root 0xaa, subw 0x0, time 223317, (-44,128), root:(897,652),
    state 0x10, keycode 21 (keysym 0xfe51, dead_acute), same_screen YES,
    XLookupString gives 1 bytes: (b4) ""
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: True

KeyPress event, serial 235, synthetic NO, window 0x4c00001,
    root 0xaa, subw 0x0, time 280261, (-7,-129), root:(934,395),
    state 0x1, keycode 21 (keysym 0xfe5a, dead_caron), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

However, when used in a text field (I tested - "works" this way for all apps) - the key has no effect, as if I didn't even press it.
Other characters that are mapped directly, such as ěščýáíĚŠČÝÁÍ can be typed just fine.

I was able to type dead_caron & dead_actute perfectly fine until a few days back (noticed it today, it's not needed that often).

Any pointers?

Last edited by MightyPork (2015-07-28 10:16:47)

MightyPork · 2015-07-28 10:14:51

The problem was borked locale in .bashrc and .pam_environment.

To verify, check some GTK apps terminal output - eg. gedit.

Last edited by MightyPork (2015-07-28 10:16:37)

Arch Linux

#1 2015-07-27 19:08:25

[SOLVED] Can no longer type "dead_acute" and "dead_caron"

#2 2015-07-28 10:14:51

Re: [SOLVED] Can no longer type "dead_acute" and "dead_caron"

Board footer