I had tried installing unstable directly, but at the time, perl was broken (I do not remember the exact offending package), which prevented me from trying to install it directly. So I resorted to installing testing and subsequently safe-upgrading to Sid. Right now, I have an empty /run directory, presumably recreated on some upgrade. It does seem like I was caught in a transitional phase with /run being introduced halfway, as this was an install not too long after Squeeze was released. I have installed Testing this way a few months before, but this issue did not exist then.
> reassign 628870 udev > thanks > > Quoting Manjul Apratim ([email protected]): >> Package: installation-reports >> Severity: important >> >> >> After performing a fresh install of Debian Testing (using debootstrap), >> udev is unable to detect input devices. After installing the X-server as >> well as the gnome suite, issuing a `startx' at TTY1 resulted in a >> graphical X session starting, but without the functioning of the >> mouse/touchpad/keyboard. As such, a hard reboot is the only option. The >> user may think that configuring Xorg is the solution, but the solution >> that works is to remove the /run directory. This is a bug in either udev >> or the installer itself. This also seems to be related to the following >> bug: >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620995 > > > I reassign this to udev so that the udev maintainer takes appropriate > action (merging bugs, closing the bug report as "already known", > etc.). > > Please note, however, that /run introduction triggers several actions > on several packages, and the "chance" that you went into a bad > combination of packages versions (some supporting /run; some not), is > quite high.... > > Try installing unstable: there are chances that it wold behave better > in that regard. > > > > -- Manjul Apratim
