[arch-dev-public] Dangerous dbus update for testing
Jan de Groot
jan at jgc.homeip.net
Wed Mar 12 19:26:42 EDT 2008
On Wed, 2008-03-12 at 16:09 -0700, Jason Chu wrote:
> On Wed, Mar 12, 2008 at 10:30:19PM +0100, Jan de Groot wrote:
> > On Wed, 2008-03-12 at 16:12 -0500, Dan McGee wrote:
> > > Is there any better way to handle this? When this gets moved to extra,
> > > people -Syu first, read front page news later.
> > >
> > > I ask because I can't really think of a better way. Dang this is
> > > stupid.
> > The crashing xorg-server is in testing and will never make it to extra:
> > we're against the input hotplugging as it breaks too many things,
> > including a dbus restart. This warning is for testing users who also
> > have xorg-server from testing installed.
> I'm not against input hotplugging. I am against input hotplugging that
> dies when it loses the connection to dbus.
> What other things does it break?
Crosspaste from other thread. Note that point 4 will take until next
year to finish... something xorg-server-1.6'ish:
1. The dbus code is shit
2. Configuration of keyboard maps is shit
3. Suspend/resume is shit (probably related to 1.)
4. XInput itself is in very bad state already
Point 1 can be triggered by /etc/rc.d/dbus restart.
Point 2 can be triggered by wanting something else than a US keymap,
combined with some nice non-standard variant
Point 3 has been reported in combination with synaptics, but I haven't
investigated on it further because I know 1 and 2 are valid.
Point 4 was told to me at FOSDEM by Daniel Stone, the only maintainer I
know that has the guts to mess with code that nobody wants to get his
hands dirty on.
More information about the arch-dev-public