Bug#802618: xinit: no keyboard/mouse support after yesterdays's upgrade
Package: xinit Version: 1.3.4-3 Severity: important Hello, yesterday's X11 upgrade broke my setup, both keyboard and mouse are dead under X. I am starting X with startx, and am ataching the X log file. Comparing old (X as root) ad new logfile, these seem to be the interesting lines: [ 406.871] (II) LoadModule: "evdev" [ 406.871] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [ 406.898] (II) Module evdev: vendor="X.Org Foundation" [ 406.898]compiled for 1.16.4, module version = 2.9.2 [ 406.898]Module class: X.Org XInput Driver [ 406.898]ABI class: X.Org XInput driver, version 21.0 [...] [ 406.899] (II) config/udev: Adding input device HID 046a:0023 (/dev/input/event0) [ 406.899] (**) HID 046a:0023: Applying InputClass "evdev keyboard catchall" [ 406.899] (II) Using input driver 'evdev' for 'HID 046a:0023' [ 406.899] (**) HID 046a:0023: always reports core events [ 406.899] (**) evdev: HID 046a:0023: Device: "/dev/input/event0" [ 406.899] (EE) evdev: HID 046a:0023: Unable to open evdev device "/dev/input/event0". [ 406.899] (EE) PreInit returned 2 for "HID 046a:0023" [ 406.899] (II) UnloadModule: "evdev" [ 406.900] (II) config/udev: Adding input device HID 046a:0023 (/dev/input/event1) [ 406.900] (**) HID 046a:0023: Applying InputClass "evdev keyboard catchall" [ 406.900] (II) Using input driver 'evdev' for 'HID 046a:0023' [ 406.900] (**) HID 046a:0023: always reports core events [ 406.900] (**) evdev: HID 046a:0023: Device: "/dev/input/event1" [ 406.900] (EE) evdev: HID 046a:0023: Unable to open evdev device "/dev/input/event1". [ 406.900] (EE) PreInit returned 2 for "HID 046a:0023" [ 406.900] (II) UnloadModule: "evdev" [ 406.901] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event2) [ 406.901] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall" [ 406.901] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse' [ 406.901] (**) Logitech USB-PS/2 Optical Mouse: always reports core events [ 406.901] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event2" [ 406.901] (EE) evdev: Logitech USB-PS/2 Optical Mouse: Unable to open evdev device "/dev/input/event2". [ 406.901] (EE) PreInit returned 2 for "Logitech USB-PS/2 Optical Mouse" [ 406.901] (II) UnloadModule: "evdev" [ 406.901] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0) [ 406.901] (II) No input driver specified, ignoring this device. ls l /dev/input insgesamt 0 drwxr-xr-x 2 root root 120 Okt 21 19:23 by-id drwxr-xr-x 2 root root 140 Okt 21 19:23 by-path crw-rw 1 root input 13, 64 Okt 21 19:23 event0 crw-rw 1 root input 13, 65 Okt 21 19:23 event1 crw-rw 1 root input 13, 74 Okt 21 19:23 event10 crw-rw 1 root input 13, 75 Okt 21 19:23 event11 crw-rw 1 root input 13, 76 Okt 21 19:23 event12 crw-rw 1 root input 13, 77 Okt 21 19:23 event13 crw-rw 1 root input 13, 66 Okt 21 19:23 event2 crw-rw 1 root input 13, 67 Okt 21 19:23 event3 crw-rw 1 root input 13, 68 Okt 21 19:23 event4 crw-rw 1 root input 13, 69 Okt 21 19:23 event5 crw-rw 1 root input 13, 70 Okt 21 19:23 event6 crw-rw 1 root input 13, 71 Okt 21 19:23 event7 crw-rw 1 root input 13, 72 Okt 21 19:23 event8 crw-rw 1 root input 13, 73 Okt 21 19:23 event9 crw-rw 1 root input 13, 63 Okt 21 19:23 mice crw-rw 1 root input 13, 32 Okt 21 19:23 mouse0 I am not a member of the input group. I am not sure against which package I should report this, wich is basically the only reason I have importanr severity. ;-) I would be grateful for a quick fix. cu Andreas -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xinit depends on: ii coreutils 8.23-4 ii libc6 2.19-22 ii libx11-62:1.6.3-1 ii x11-common 1:7.7+12 ii xauth 1:1.0.9-1 Versions of packages xinit recommends: ii mlterm [x-terminal-emulator] 3.5.0-1+b1 ii wmaker [x-window-manager] 0.95.6-1.1 ii xserver-xorg [xserver]1:7.7+12 ii xterm [x-terminal-emulator] 320-1 xinit suggests no packages. -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' [ 352.975] X.Org X Server 1.17.2 Release Date: 2015-06-16 [ 352.975] X Protocol Version 11, Revision 0 [ 352.975] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 352.975] Current Operating System: Linux argenau 3.16.0-4-amd64 #1 SMP
Bug#802618: xinit: no keyboard/mouse support after yesterdays's upgrade
Control: reassign 802618 xserver-xorg-core 2:1.17.2-2 Control: severity 802618 serious Control: retitle 802618 keyboard/mouse support broken - mising dep on libpam-systemd? On 2015-10-21 Andreas Metzler wrote: > Package: xinit > Version: 1.3.4-3 > Severity: important > Hello, > yesterday's X11 upgrade broke my setup, both keyboard and mouse are > dead under X. > I am starting X with startx, and am attaching the X log file. Comparing > old (X as root) ad new logfile, these seem to be the interesting > lines: > [...] > [ 406.900] (**) evdev: HID 046a:0023: Device: "/dev/input/event1" > [ 406.900] (EE) evdev: HID 046a:0023: Unable to open evdev device > "/dev/input/event1". > [...] > I am not sure against which package I should report this, wich is > basically the only reason I have important severity. ;-) I would be > grateful for a quick fix. Hello, reassiging, there seems to be a missig/incorrect dependency. Manually installing libpam-systemd:i386 lets X work again. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Processed: Re: Bug#802618: xinit: no keyboard/mouse support after yesterdays's upgrade
Processing control commands: > reassign 802618 xserver-xorg-core 2:1.17.2-2 Bug #802618 [xinit] xinit: no keyboard/mouse support after yesterdays's upgrade Bug reassigned from package 'xinit' to 'xserver-xorg-core'. No longer marked as found in versions xinit/1.3.4-3. Ignoring request to alter fixed versions of bug #802618 to the same values previously set Bug #802618 [xserver-xorg-core] xinit: no keyboard/mouse support after yesterdays's upgrade Marked as found in versions xorg-server/2:1.17.2-2. > severity 802618 serious Bug #802618 [xserver-xorg-core] xinit: no keyboard/mouse support after yesterdays's upgrade Severity set to 'serious' from 'important' > retitle 802618 keyboard/mouse support broken - mising dep on libpam-systemd? Bug #802618 [xserver-xorg-core] xinit: no keyboard/mouse support after yesterdays's upgrade Changed Bug title to 'keyboard/mouse support broken - mising dep on libpam-systemd?' from 'xinit: no keyboard/mouse support after yesterdays's upgrade' -- 802618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#802618: xinit: no keyboard/mouse support after yesterdays's upgrade
On Wed, Oct 21, 2015 at 20:12:01 +0200, Andreas Metzler wrote: > Control: reassign 802618 xserver-xorg-core 2:1.17.2-2 > Control: severity 802618 serious > Control: retitle 802618 keyboard/mouse support broken - mising dep on > libpam-systemd? > > On 2015-10-21 Andreas Metzler wrote: > > Package: xinit > > Version: 1.3.4-3 > > Severity: important > > > Hello, > > > yesterday's X11 upgrade broke my setup, both keyboard and mouse are > > dead under X. > > > I am starting X with startx, and am attaching the X log file. Comparing > > old (X as root) ad new logfile, these seem to be the interesting > > lines: > > > > [...] > > [ 406.900] (**) evdev: HID 046a:0023: Device: "/dev/input/event1" > > [ 406.900] (EE) evdev: HID 046a:0023: Unable to open evdev device > > "/dev/input/event1". > > > [...] > > I am not sure against which package I should report this, wich is > > basically the only reason I have important severity. ;-) I would be > > grateful for a quick fix. > > Hello, > > reassiging, there seems to be a missig/incorrect dependency. Manually > installing libpam-systemd:i386 lets X work again. > Yep, we should add a dependency (or at the very least Recommends) on libpam-systemd. Cheers, Julien signature.asc Description: PGP signature
Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)
On Tue, Oct 20, 2015 at 14:46:44 -0700, Scott Mcdermott wrote: > Package: xserver-xorg-legacy > Version: 2:1.17.2-3 > Severity: grave > > I recently did an upgrade of X, which broke it on my machine. > Here are old (working) and new (broken) versions that apt-get > installed, as shown in /var/log/apt/history.log: > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > This upgrade has broken X startup for me. Here is how > I start X (as ordinary user): > > exec setsid env -i \ > LOGNAME=$LOGNAME \ > USER=$USER \ > HOME=$HOME \ > PATH=$PATH \ > EDITOR=$EDITOR \ > DISPLAY=$DISPLAY \ > SHELL=$SHELL \ > TERM=$TERM \ > LANG=$LANG \ > X :0 vt63 \ > -dpi 106 \ > -nolisten tcp \ > -noreset \ > -keeptty \ > -novtswitch > So one solution is to install xserver-xorg-legacy and tell it to not drop privileges (needs_root_rights=yes). But that leaves X running as root, which we're trying to move away from. The better solution is to change your setup to run X on the VT it's started from, inside a logind session, so it doesn't need extra privileges. Cheers, Julien signature.asc Description: PGP signature
Bug#802327: xserver-xorg-core: (EE) Server terminated with error (1). Closing log file.
Thanks for the additional info. In that case, the fbdev driver ought to Recommends xserver-xorg-legacy (Depends seems too strong of a dependency, since it's mostly GDM3 that wants to launch X as non-root; lightdm doesn't). Martin-Éric 2015-10-20 9:32 GMT+03:00 Julien Cristau : > On Mon, Oct 19, 2015 at 20:24:36 +0300, Martin-Éric Racine wrote: > >> That's what I assumed too, except that X also fails to launch via gdm3 >> without the legacy wrapper if I remove the Geode driver and let the >> Xserver use its own choice of fbdev or its built-in modeline driver. >> > The modesetting driver requires a kernel driver, which there isn't for > geode; the fbdev driver requires root. > > Cheers, > Julien
Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)
Julien Cristau on 2015/10/21 +0200 @20:48:56: > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > > > This upgrade has broken X startup for me. Here is how > > I start X (as ordinary user): > > > > exec setsid env -i \ > > ... > > X :0 vt63 \ > > So one solution is to install xserver-xorg-legacy and > tell it to not drop privileges > (needs_root_rights=yes). But that leaves X running > as root, which we're trying to move away from. That would surely be a regression. Debian went from a working X that dropped privileges, to a non-working X that can only be run as root. Huh?? And the suggested solution is: > to change your setup to run X on the VT it's started > from, inside a logind session, so it doesn't need > extra privileges. There's more than the tty problem, there's also the IOPL issue (I don't know what that is... all I know is I didn't get it before the wrapper changed, started it as ordinary user and it worked fine). I fail to see why I should be forced to run some whizbang login daemon. I have a very simple setup that has worked forever. I run an X server, with kernel modesetting, and a simple window manager. I have no need for desktop environments, login daemons, or to run "kitchensinkd" or anything else. This change is clearly a regression. This has taken a perfectly working setup that does NOT run the X server with root privileges, and forces me to either run additional things I don't need and which cause invasive changes to my system, or to run my X server insecurely with root privileges. Why did the wrapper even need to change? I get that it's desired in a '-legacy' package, fine, I can deal with a moved program. But why was a perfectly working wrapper *broken* and functionality removed?
Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)
On Wed, Oct 21, 2015 at 16:10:50 -0700, Scott Mcdermott wrote: > Julien Cristau on 2015/10/21 +0200 @20:48:56: > > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > > > > > This upgrade has broken X startup for me. Here is how > > > I start X (as ordinary user): > > > > > > exec setsid env -i \ > > > ... > > > X :0 vt63 \ > > > > So one solution is to install xserver-xorg-legacy and > > tell it to not drop privileges > > (needs_root_rights=yes). But that leaves X running > > as root, which we're trying to move away from. > > That would surely be a regression. Debian went from a > working X that dropped privileges, to a non-working X > that can only be run as root. Huh?? > No, Debian is going from an X server that always runs as root to one that can run as unprivileged user in most cases. There was previously no dropping privileges. Cheers, Julien signature.asc Description: PGP signature
