On Sun, May 1, 2011 at 16:26:20 +0200, Michael Biebl wrote: > Am 01.05.2011 15:58, schrieb Julien Cristau: > > On Sun, May 1, 2011 at 15:53:17 +0200, Michael Biebl wrote: > > > >> Am 01.05.2011 15:34, schrieb Julien Cristau: > >>> Does this mean for example that if X is running, and I kill hal, it will > >>> be restarted automatically so it can tell the already running X server > >>> about possible new input devices? > >> > >> That should be possible. But then, that depends on how Xorg is setting up > >> and > >> using the Hal D-Bus interface, e.g. if it uses > >> dbus_bus_start_service_by_name() > >> or a Ping() to auto-start hal. > >> I don't know the Xorg code, so I can't tell. > >> > > http://cgit.freedesktop.org/xorg/xserver/tree/config/hal.c > > Xorg seems to use libhal_ctx_init() in connect_and_register() and we > ship > http://patch-tracker.debian.org/patch/series/view/hal/0.5.14-5/02_libhal_dont_check_running.patch > > So it *should* work. > AIUI that just helps when X starts up. When hal goes down, we'll just get the NameOwnerChanged event with null new_owner, and wait forever for it to come back up? I might just be misunderstanding how dbus activation works though, I have no idea if anything keeps track of active connections to hal when it goes down to restart it. Or if we get disconnected from the bus somehow when that happens?
Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110501144113.gq2...@radis.liafa.jussieu.fr
