You are not logged in.
I finally got my keyboard configured using hal. But then, xmodmap stopped working during xinit. When I run it from xterm, everything is fine, but as I want to make a switch to tiling (musca that is) I need to remap caps lock to mod4, or else I can't lauch anything...
Now to the point, when I remove the /etc/hal/fdi/policy/10-keymap.fdi file, xmodmap works from startx again... As soon as the file is back there, no xmodmap from start.
Is this a bug, or am I missing something?
.xinitrc
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
# load .xmodmap if it exists
if [ -f $HOME/.xmodmap ]; then
/usr/bin/xmodmap $HOME/.xmodmap
fi
pypanel &
xbindkeys &
# exec scrotwm >> /dev/null
# exec musca >> /dev/null
# exec enlightenment_start
exec openbox-session
# exec musca
# exec gnome-session
# exec startkde
# exec startxfce4
# exec icewm
# exec openbox-session
# exec blackbox
# exec fluxbox
# exec ratpoison
# exec dwm
# ... or any other WM of your choosing ...
10-keymap.fdi
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">us,de,cz</merge>
<merge key="input.xkb.variant" type="string">,qwerty,qwerty</merge>
<merge key="input.xkb.options" type="string">grp:alt_shift_toggle,terminate:ctrl_alt_bksp</merge>
</match>
</device>
</deviceinfo>
Offline
so after further looking into this, I figured it must be something in that my 10-keymap.fdi is different from the default one and I've found it:
it is the parameter grp:alt_shift_toggle, if the fdi is identical, except not containing this, xmodmap loads.
futhermore, changing alt_shift_toggle to ctrl_shift_toggle, xmodmap loads!!!!!
there is nothing in the logs. I suspect this might be a bug, what do you think?
could please someone try and reproduce this?
Last edited by jarda-wien (2009-11-07 17:06:11)
Offline
Well, the last post was over a month ago, but I am trying to get my .xmodmaprc to work from startx/xinitrc, as I can't seem to do it anymore.
I moved /etc/hal/fdi/policy/10-keymap.fdi, restarted hal, xmodmaprc loads ok, like jarda-wien states, although my 10-keymap.fdi looks like this:
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">pt</merge>
<merge key="input.xkb.variant" type="string" />
</match>
</device>
</deviceinfo>
I don't have that last "merge key". I'll try adding it and restarting xorg.
Edit: Doesn't work, editing, adding or removing /etc/fdi/hal/policy/10-keymap.fdi. Back to running xmodmap manually. No big deal.
Last edited by s3kt0r (2010-01-07 21:03:24)
box1: Arch (linux-3.17-rc5)
box2: Gentoo (linux-3.17-rc5)
wm: subtle
Offline