Bug#515214: Xorg / HAL

[Julien Cristau <jcristau@debian.org>]

On Thu, May 14, 2009 at 20:56:47 +0200, Michael Biebl wrote:

> Julien Cristau wrote:
>   Assuming NoAutoAddDevices if hal isn't there
> > when we start up means getting duplicated events whenever it shows up.
> 
> I thought, if NoAutoAddDevices is used, that Xorg ignores devices reported via
> hal? Or maybe I'm just misunderstanding what you mean with duplicated events.
> 
Hrm yes you're right.  But since at the point where xorg.conf is
processed, we don't know whether hal will report anything, this is not
an easy plan.  We could start up with the default xorg.conf devices,
then if any hal device shows up, disable the default ones.  But that
sounds very fragile, and gets us back into the evdev vs kbd keycodes
mix, which we had so much fun with when input hotplug got first enabled
(clients not refreshing keymaps correctly, or not refreshing their grabs.
I'd rather not go back there.
Going back to look at the xorg.conf devices if nothing shows up on the
hal connection after a timeout also sounds like it'd bring its amount of
pain too.
I'm more interested in trying to figure out why people's session die on
dbus restart, which so far look like client bugs leading to X restarts
in the middle of an upgrade, and which probably need to be fixed
regardless.

Cheers,
Julien