Bug#669949: sysvinit: Break X11: no more mouse and keyboard
Definitely caused by /run - /var/run symlink here. After getting rid of that and creating /run dir in /, I have my keyboard, mouse and sound back. Extremely weird bug, also only got this recently, been running unstable for quite a while on LMDE. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Thu, Jun 07, 2012 at 10:45:44PM +0200, Jakub Moc wrote: Definitely caused by /run - /var/run symlink here. After getting rid of that and creating /run dir in /, I have my keyboard, mouse and sound back. Extremely weird bug, also only got this recently, been running unstable for quite a while on LMDE. Thanks all for investigating. It looks like we need to cater for the directory and symlink being the wrong way around, and to rectify that if possible. Other than for chroots, where we don't have a choice, and no means to effectively upgrade to the correct configuration, this has never been an officially supported configuration. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Sun, Apr 22, 2012 at 11:57:07AM +0100, Roger Leigh wrote: On Sun, Apr 22, 2012 at 11:15:29AM +0200, valette wrote: After upgrade, X11 does not report any keybord or mouse on my laptop. If I plug a USB mouse its detected. If the USB mouse is plugged before X starts its not detected either. Probably related to hal/udev but... I'm not sure. I'm seeing the same thing; but it's fine until the start of X. However, in my case the mouse and keyboard are plugged into a USB hub on my monitor, and unplugging and reconnecting the hub to the main system results in them working again. NB: I modified the /etc/defalt/tmpfs to get /tmp as a normal fs. Does this alter the behaviour at all? I can't see what has changed here that could affect this, so a bit more information would be appreciated if possible. I'm not sure how USB device availability is related to /tmp, but hopefully some more investigation will help here. This is due to /lib/init/bootclean.sh cleaning (I think) /run and removing some udev stuff early on. I've added .clean flag files to prevent the cleaning of tmpfses, but haven't quite yet got it to stop. However, we now know what the cause is, so should have this fixed tonight. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
Package: sysvinit Version: 2.88dsf-23 Severity: important After upgrade, X11 does not report any keybord or mouse on my laptop. If I plug a USB mouse its detected. If the USB mouse is plugged before X starts its not detected either. Probably related to hal/udev but... NB: I modified the /etc/defalt/tmpfs to get /tmp as a normal fs. # mount /tmp as a tmpfs. Defaults to yes; set to no to disable (/tmp # will then be part of the root filesystem). /tmp may also be # configured to be a separate mount in /etc/fstab. RAMTMP=no My xorg.conf is pretty slim: Section InputClass Identifier touchpad catchall Driver evdev MatchIsTouchpad on MatchDevicePath /dev/input/event* OptionEmulate3Buttonstrue EndSection -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.2 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysvinit depends on: ii debianutils 4.3 ii initscripts 2.88dsf-23 ii libc6 2.13-30 ii libselinux1 2.1.9-4 ii libsepol1 2.1.4-3 ii sysv-rc 2.88dsf-23 ii sysvinit-utils 2.88dsf-22.1 sysvinit recommends no packages. sysvinit suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Sun, Apr 22, 2012 at 11:15:29AM +0200, valette wrote: After upgrade, X11 does not report any keybord or mouse on my laptop. If I plug a USB mouse its detected. If the USB mouse is plugged before X starts its not detected either. Probably related to hal/udev but... I'm not sure. I'm seeing the same thing; but it's fine until the start of X. However, in my case the mouse and keyboard are plugged into a USB hub on my monitor, and unplugging and reconnecting the hub to the main system results in them working again. NB: I modified the /etc/defalt/tmpfs to get /tmp as a normal fs. Does this alter the behaviour at all? I can't see what has changed here that could affect this, so a bit more information would be appreciated if possible. I'm not sure how USB device availability is related to /tmp, but hopefully some more investigation will help here. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: [Pkg-sysvinit-devel] Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Sun, 22 Apr 2012, Roger Leigh wrote: On Sun, Apr 22, 2012 at 11:15:29AM +0200, valette wrote: After upgrade, X11 does not report any keybord or mouse on my laptop. If I plug a USB mouse its detected. If the USB mouse is plugged before X starts its not detected either. Probably related to hal/udev but... I'm not sure. I'm seeing the same thing; but it's fine until the start of X. However, in my case the mouse and keyboard are plugged into a USB hub on my monitor, and unplugging and reconnecting the hub to the main system results in them working again. NB: I modified the /etc/defalt/tmpfs to get /tmp as a normal fs. Does this alter the behaviour at all? I can't see what has changed here that could affect this, so a bit more information would be appreciated if possible. I'm not sure how USB device availability is related to /tmp, but hopefully some more investigation will help here. It is related to /dev, which is a tmpfs. If anything messes with /dev, the device node will be lost (and X won't find it), but a hotplug will recreate it. So, is /dev alright? -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
I can confirm this bug, and I did not touch /etc/default/tmpfs. I am also experiencing other bugs that might be related to the initscripts upgrade, for example systemd has stopped working and I had to go back using sysvinit. With systemd, /run/lock was not created, as well as /run/dbus (dbus not starting, but working if creating /run/dbus and launching the daemon manually from the cmdline after booting in single-user mode). Does dbus / systemd require something special from /dev? Can it be related to problems in /run missing some directories and files? I don't have hal installed, nor any entry in fstab besides the normal physical hard-disk partitions + proc. To me, it looks as if something strange was changed early in the boot process, but there's nothing relevant in the logfiles. Cheers, -- Matteo Settenvini FSF Associated Member Email : mat...@member.fsf.org -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/E d--(-) s+: a- C+++ UL+++ P+ L$ E+ W+++ N+ o? w--- O M- V- PS++ PE- Y+++ PGP+++ t++ 5 X- R+ !tv b+++ DI++ D++ G++ e++ h+ r++ y+ --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On 22/04/2012 12:57, Roger Leigh wrote: Does this alter the behaviour at all? probably not as from what I read the /tmp fs will be correctly mounted afterward. --eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Sun, Apr 22, 2012 at 05:04:28PM +0200, Eric Valette wrote: On 22/04/2012 12:57, Roger Leigh wrote: Does this alter the behaviour at all? probably not as from what I read the /tmp fs will be correctly mounted afterward. I'm not sure that this is definitely a sysvinit issue. The mouse and keyboard are entirely functional right up until X11 starts up. I've tested this in single user mode, running the init scripts by hand. It's all working perfectly up until kdm/gdm starts, and it can be triggered by hand with xinit. All of the tmpfses, including /dev, are mounted and functional. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On 22/04/2012 19:49, Roger Leigh wrote: On Sun, Apr 22, 2012 at 05:04:28PM +0200, Eric Valette wrote: On 22/04/2012 12:57, Roger Leigh wrote: Does this alter the behaviour at all? probably not as from what I read the /tmp fs will be correctly mounted afterward. I'm not sure that this is definitely a sysvinit issue. The mouse and keyboard are entirely functional right up until X11 starts up. I've tested this in single user mode, running the init scripts by hand. It's all working perfectly up until kdm/gdm starts, and it can be triggered by hand with xinit. I'm sure it is beause reverting *only* sysvinit (and all related packages) makes the problem vanish. --eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: [Pkg-sysvinit-devel] Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Sun, 22 Apr 2012, Roger Leigh wrote: I'm not sure that this is definitely a sysvinit issue. The mouse and keyboard are entirely functional right up until X11 starts up. This may well be a red herring, but you're all using the latest 3.2 kernel, aren't you? A Debian user went straight to LKML with an udev issue related to the later 3.2 kernels (which was a _lot_ worse than just input devices disappearing, I think. I will have to hunt down that message). It is not impossible that an interaction of the latest sysvinit with the later 3.2 kernels is causing problems if we changed _anything_ that has direct interaction with the kernel (such as an ioctl, signal masks...) in the latest sysvinit that could trigger a kernel issue. Did we? Can anyone that is reproducing this bug try an older kernel (preferably not the latest 3.0, as all longterm kernels are somewhat sync'd and if something caused a regression in 3.2-stable, changes are high it is already in 3.0-stable too). I've tested this in single user mode, running the init scripts by hand. It's all working perfectly up until kdm/gdm starts, and it can be triggered by hand with xinit. All of the tmpfses, including /dev, are mounted and functional. X.org makes use of several input-layer features/ioctls/etc that very few/no other programs would during boot. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: [Pkg-sysvinit-devel] Bug#669949: sysvinit: Break X11: no more mouse and keyboard
On Mon, 23 Apr 2012, Henrique de Moraes Holschuh wrote: On Sun, 22 Apr 2012, Roger Leigh wrote: I'm not sure that this is definitely a sysvinit issue. The mouse and keyboard are entirely functional right up until X11 starts up. This may well be a red herring, but you're all using the latest 3.2 kernel, aren't you? A Debian user went straight to LKML with an udev issue related to the later 3.2 kernels (which was a _lot_ worse than just input devices disappearing, I think. I will have to hunt down that message). Hmm, found it and it is a very different issue, related to udevadm settle and event filtering. It is unlikely to be related to this problem. It is not impossible that an interaction of the latest sysvinit with the later 3.2 kernels is causing problems if we changed _anything_ that has direct interaction with the kernel (such as an ioctl, signal masks...) in the latest sysvinit that could trigger a kernel issue. Did we? That's still a question worth considering. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
