Your message dated Fri, 16 Apr 2010 20:07:31 +0200 with message-id <20100416180731.GA29662@radis.liafa.jussieu.fr> and subject line Re: Bug#524185: xserver-xorg - No keyboard/mouse after upgrade has caused the Debian Bug report #524185, regarding xserver-xorg - No keyboard/mouse after upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 524185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524185 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: xserver-xorg - No keyboard/mouse after upgrade
- From: Bastian Blank <waldi@debian.org>
- Date: Wed, 15 Apr 2009 13:07:41 +0200
- Message-id: <20090415110741.GA28350@wavehammer.waldi.eu.org>
Package: xserver-xorg-core Version: 2:1.4.2-11 Severity: grave After the upgrade to xorg 1.4, the x server wants to use hal to detect input devices regardless of the old config. This leads to unusable systems because there is no way out of an x server which does not find any keyboard. And the reasons for this seems to be not uncommon. Nothing about that and the environmental requirements of this changes are documented at the usual location (NEWS.Debian). On my old notebook it just writes log messages that it wants to disable all kdb and mouse device entries and starts without input devices. Bastian -- Only a fool fights in a burning house. -- Kank the Klingon, "Day of the Dove", stardate unknown
--- End Message ---
--- Begin Message ---
- To: Bastian Blank <waldi@debian.org>, 524185-done@bugs.debian.org
- Subject: Re: Bug#524185: xserver-xorg - No keyboard/mouse after upgrade
- From: Julien Cristau <jcristau@debian.org>
- Date: Fri, 16 Apr 2010 20:07:31 +0200
- Message-id: <20100416180731.GA29662@radis.liafa.jussieu.fr>
- In-reply-to: <20090415122439.GA29857@wavehammer.waldi.eu.org>
- References: <20090415110741.GA28350@wavehammer.waldi.eu.org> <1239795468.25727.2.camel@radis.liafa.jussieu.fr> <20090415122439.GA29857@wavehammer.waldi.eu.org>
On Wed, Apr 15, 2009 at 14:24:39 +0200, Bastian Blank wrote: > severity 524185 important > thanks > > On Wed, Apr 15, 2009 at 01:37:48PM +0200, Julien Cristau wrote: > > please send > > 1) full X config > > 2) full X log > > 3) output of lshal > > 4) contents of /proc/bus/input/devices > > I'm not longer able to reproduce the problem after a reboot. Also the old > log is gone because of my tests. Part of the problem was a > missinterpretation of the output; earlier versions provided some optical > feedback like a moving cursor and the ability to zap the xserver, both > things are gone with this version by default. > > So the documentation problem remains. From my point of view it will not > longer be able to get any input devices on a kernel without event > devices in the default config. > We switched off hal since then, and the requirement for CONFIG_INPUT_EVDEV is documented in NEWS.Debian, so closing this bug. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---