You are not logged in.
Bug since a few days back, my compose key stopped working.
I have it mapped to right CTRL.
Here's output of a command I found on the Wiki, seems to be correctly set up
~ $ setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc104
layout: cz
variant: qwerty
options: compose:rctrl
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwertz)
types: complete
compat: complete
symbols: pc+cz(qwerty)+inet(evdev)+compose(rctrl)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwertz)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+cz(qwerty)+inet(evdev)+compose(rctrl)" };
xkb_geometry { include "pc(pc104)" };
};It used to work like "t m" -> trade symbol, ", c" -> the french C with tail below, "~ n" -> n with tilde, "--" -> long dash
Now it sometimes consumes the characters as if it worked, but no composed character is entered in their place.
What config should I check to debug this?
If it ain't broke, pacman -Syyu and it will be
Offline
Where do you define the compose key?
What did you change 'since a few days back'?
For testing, if you change to another key, does it still not work?
I have this in '/etc/X11/xorg.conf.d/30-keyboard.conf':
Section "InputClass"
Identifier "Keyboard French layout"
MatchIsKeyboard "yes"
Option "XkbLayout" "fr"
Option "XkbOptions" "compose:rwin"
EndSectionThis still works on my machine.
Offline
Where do you define the compose key?
What did you change 'since a few days back'?For testing, if you change to another key, does it still not work?
I have this in '/etc/X11/xorg.conf.d/30-keyboard.conf':
Section "InputClass" Identifier "Keyboard French layout" MatchIsKeyboard "yes" Option "XkbLayout" "fr" Option "XkbOptions" "compose:rwin" EndSectionThis still works on my machine.
What changed: Nothing. I just updated from official repos a few times, as usual.
One issue - messed up Qt windows - is now fixed, another: crashing audio system - still investigating, and this is the third issue I got from the updates.
I'm starting to think I'd be best off just not updating at all once it's working.
Tried your proposed fix now - no change.
Actually, I discovered the compose key is sort of enabled, but doesn't work as it used to (eg. I can't type ellipsis, because two dots produce this-> ·, can't type "tm" at all, can't type long dash... but can do eg. ñ)
Also, it works only in a few programs now - it used to work system-wide.
Works in Kwrite, Dolphin, Krusader, not eg. in Chrome, Pluma, PhpStorm, Terminator.
Should I try downgrading x-server perhaps?
Last edited by MightyPork (2015-07-27 16:01:08)
If it ain't broke, pacman -Syyu and it will be
Offline
This might sound obvious but could it be that your desktop environment is overriding your settings in /etc/X11/xorg.conf.d/30-keyboard.conf ? It looks like you are using KDE, try to disable all keyboard options in the system settings gui, this worked for me a while back.
Offline
This might sound obvious but could it be that your desktop environment is overriding your settings in /etc/X11/xorg.conf.d/30-keyboard.conf ? It looks like you are using KDE, try to disable all keyboard options in the system settings gui, this worked for me a while back.
I'm using xfce, in fact. No I don't think that's the case, the compose key *is* configured. It's just not working (in some apps not at all, in some it's making *some* characters - not all it should, though...).
If it ain't broke, pacman -Syyu and it will be
Offline
I've now also discovered that some keys don't work anymore, but that's for it's own thread. Might be related though.
Something that updated recently messed up the keyboard input, apparently. I tried downgrading some stuff but with no luck.
Last edited by MightyPork (2015-07-27 19:11:05)
If it ain't broke, pacman -Syyu and it will be
Offline