xmodmap setup is missing (general startup is wrong?)
Bug #27839 reported by
ViktorNagy
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| meta-kde (Ubuntu) |
Fix Released
|
Medium
|
Jonathan Riddell | ||
Bug Description
KDE at startup should load the ~/xmodmap (some sources say ~/.Xmodmap) file.
This does not happen. Without this "feature" it is impossible to redefine the
special keys (the Win/Tux key for example) to use them as F13, F14, etc.
As a workaround some sites say that scripts put in ~/.kde/env should have run at
KDE startup. So I wrote a simple script to run xmodmap ~/.Xmodmap at startup,
but it is not run neither.
A possible solution was to put this script to ~/.kde/Autostart
The real solution would be to run the .xmodmap file automatically. (As under GNOME.)
Bug #27003 is one manifestation of this bug.
Revision history for this message
| Andreas Simon (andreas-w-simon) wrote | #1 |
| Changed in meta-kde: | |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Jonathan Riddell (jr) wrote | #2 |
| Changed in meta-kde: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
It would be really nice to get this into dapper.
The question how kde starts automatically a user's ~/.Xmodmap file is a common one from people who need to setup their keyboard's special keys.
Just adding the following lines from gdm's /etc/X11/
usermodmap=
userxkbmap=
if [ -f "$userxkbmap" ]; then
setxkbmap `cat "$userxkbmap"`
XKB_IN_USE=yes
fi
# xkb and xmodmap don't play nice together
if [ -z "$XKB_IN_USE" ]; then
if [ -f "$usermodmap" ]; then
xmodmap "$usermodmap"
fi
fi
unset XKB_IN_USE