On Thu, Apr 16, 2009 at 07:15:03PM +0200, Julien Cristau wrote:
> > Yes, that works (at least lshal now returns the correct values; I have
> > long-running jobs so I can't log out to test if X receives them). From
> > what little I understand from HAL, the call to debian-setup-keyboard
> > happens _after_ procesing the .fdi files, so it will always overwrite
> > any custom configuration unconditionally.
> >
> that still sounds like a hal bug to me.
I don't think so. You specify in a config file that it should run a
script that updates the configuration, but you expect that script to run
_before_ parsing the config files?
>
> > You should probably not only check for the existence of the input.xkb.*
> > keys, but also that all keys still have the default value. Probably you
> > should remove the xkb-specific part from
> > /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi, and
>
> that's shipped by hal, so xserver-xorg can't do anything about that.
Yes you can. You can request the HAL maintainers to disable that script
(IMHO the directory is called "OS vendor" for a reason), and then depend
on the corrected HAL version.
> > debian-setup-keyboard should only set the input.xkb.* properties if they
> > are _all_ empty (otherwise it would be difficult to distinguish the
> > "layout is US by default" and the "layout has been explicitely set to
> > US" cases).
> >
> i don't think debian-setup-keyboard can distinguish between 'layout set
> by hal's 10-keymap.fdi' and 'layout set by the user's config' currently.
I've just described how you can do it in my previous mail.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
