Comment 14 for bug 1243642
Revision history for this message
| Uriel Tunn (u2n) wrote Re: [Bug 1243642] Re: .Xmodmap not automatically loaded on start | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
Yes, different. Editing those system-level files affects keyboard
mapping for ALL users. But this bug is about .Xmodmap, which is
per-user. My post noted that even xkb maps are lost on suspend/sleep.
Converting .Xmodmap files to xkb is straightforward. After manually
loading the desired .Xmodmap file, then:
[[ -d "$HOME/.xkb" ]] || mkdir $HOME/.xkb
xkbcomp $DISPLAY $HOME/.xkb/xkb-map
Then edit $HOME/.xkb/xkb-map, which is fairly intuitive, if needed.
Next, since the file won't load automatically no matter what, I did:
echo 'xkbcomp $HOME/.xkb/xkb-map $DISPLAY' >> ~/.bashrc
This way, at least the map can be loaded by just popping open a
terminal. (Remove the 'xmodmap .Xmodmap' line in .bashrc, if it was there.)
On single-head, multi-user systems where everyone doesn't use the same
keyboard map, instead of just being able to switch users, it would be
necessary to change configuration and restart (if control is only
system-wide). Completely unacceptable. This bug really needs fixing.
On 03/01/2015 12:03 AM, Rafael Nonato wrote:
> I don't think we are talking about the same thing when we talk of XKB. To
> clarify what I am talking about, I meant editing the files under
> /usr/share/X11/xkb/
>