Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #160000 > unrolled thread

Keyboard and Mouse not Working after Upgrade

Back to article view | Back to linux.debian.user

Contents

  Keyboard and Mouse not Working after Upgrade Flo <debianflo@gmx.at> - 2015-10-30 14:20 +0100
    Re: Keyboard and Mouse not Working after Upgrade <tomas@tuxteam.de> - 2015-10-30 15:10 +0100
      Re: Keyboard and Mouse not Working after Upgrade Flo <debianflo@gmx.at> - 2015-10-30 15:50 +0100
        Re: Keyboard and Mouse not Working after Upgrade <tomas@tuxteam.de> - 2015-10-30 16:20 +0100
          Re: Keyboard and Mouse not Working after Upgrade Sven Joachim <svenjoac@gmx.de> - 2015-10-30 17:10 +0100
            Re: Keyboard and Mouse not Working after Upgrade Flo <debianflo@gmx.at> - 2015-10-30 18:30 +0100
          Re: Keyboard and Mouse not Working after Upgrade Flo <debianflo@gmx.at> - 2015-10-30 18:30 +0100
        Re: Keyboard and Mouse not Working after Upgrade Brian <ad44@cityscape.co.uk> - 2015-10-30 17:20 +0100
          Re: Keyboard and Mouse not Working after Upgrade Brian <ad44@cityscape.co.uk> - 2015-10-30 17:40 +0100
          Re: Keyboard and Mouse not Working after Upgrade Flo <debianflo@gmx.at> - 2015-10-30 18:40 +0100

#160000 — Keyboard and Mouse not Working after Upgrade

Hi all,

I upgraded my Debian testing system.

The keyboard is working at the console. But when I enter startx and X is
running neither the keyboard nor the mouse works.

I found out that when I startx as root keyboard&mouse is working.

The Xorg.0.log is only updated when I run X as root.

On the web there are plenty of articles and messages about
keyboard&mouse&X issues but nothing was a big help for me.

My current version of xorg is: 1:7.7+12 .

Thank you.
Flo.

[toc] | [next] | [standalone]

#160001

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Oct 30, 2015 at 01:57:41PM +0100, Flo wrote:
> Hi all,
> 
> I upgraded my Debian testing system.
> 
> The keyboard is working at the console. But when I enter startx and X is
> running neither the keyboard nor the mouse works.

Hm. Are they USB devices? If yes: what happens when you unplug and re-plug
them (while X is up, as non-root user)?

> I found out that when I startx as root keyboard&mouse is working.
> 
> The Xorg.0.log is only updated when I run X as root.

Sysvinit or systemd? As which user is X running?

(under systemd it reportedly doesn't run as root, under sysvinit it has
to).

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlYzcbIACgkQBcgs9XrR2kbSfgCeNpDvc7WJ6wBK/wdRbXadKDhf
RlcAn0OTlqg+xSiiukbjisl2wFjsYqAC
=uLhQ
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#160002

On 10/30/2015 02:33 PM, tomas@tuxteam.de wrote:
> On Fri, Oct 30, 2015 at 01:57:41PM +0100, Flo wrote:
>> Hi all,
> 
>> I upgraded my Debian testing system.
> 
>> The keyboard is working at the console. But when I enter startx and X is
>> running neither the keyboard nor the mouse works.
> 
> Hm. Are they USB devices? If yes: what happens when you unplug and re-plug
> them (while X is up, as non-root user)?
> 

For me the log looks normal (/var/log/syslog):
Oct 30 15:31:39 arvak kernel: [ 7191.742296] usb 3-1.6: USB disconnect,
device number 3
Oct 30 15:31:39 arvak acpid: input device has been disconnected, fd 4
Oct 30 15:31:39 arvak acpid: input device has been disconnected, fd 5
Oct 30 15:31:43 arvak kernel: [ 7196.481955] usb 3-1.6: new low-speed
USB device number 4 using ehci-pci
Oct 30 15:31:43 arvak kernel: [ 7196.583898] usb 3-1.6: New USB device
found, idVendor=0a81, idProduct=0205
Oct 30 15:31:43 arvak kernel: [ 7196.583903] usb 3-1.6: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Oct 30 15:31:43 arvak kernel: [ 7196.583905] usb 3-1.6: Product: PS2 to
USB Converter
Oct 30 15:31:43 arvak kernel: [ 7196.583908] usb 3-1.6: Manufacturer: CHESEN
Oct 30 15:31:43 arvak kernel: [ 7196.591103] input: CHESEN PS2 to USB
Converter as
/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.0/0003:0A81:0205.0003/input/input17
Oct 30 15:31:44 arvak kernel: [ 7196.646343] hid-generic
0003:0A81:0205.0003: input,hidraw0: USB HID v1.10 Keyboard [CHESEN PS2
to USB Converter] on usb-0000:00:1a.0-1.6/input0
Oct 30 15:31:44 arvak kernel: [ 7196.654294] input: CHESEN PS2 to USB
Converter as
/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:0A81:0205.0004/input/input18
Oct 30 15:31:44 arvak kernel: [ 7196.710339] hid-generic
0003:0A81:0205.0004: input,hidraw1: USB HID v1.10 Mouse [CHESEN PS2 to
USB Converter] on usb-0000:00:1a.0-1.6/input1

I am using the old PS2 keyboard&mouse and the converter as you can see.
But, of course, I tried a native USB keyboard as well.

>> I found out that when I startx as root keyboard&mouse is working.
> 
>> The Xorg.0.log is only updated when I run X as root.
> 
> Sysvinit or systemd? As which user is X running?
> 
> (under systemd it reportedly doesn't run as root, under sysvinit it has
> to).
> 

The process with PID 1 is called init, therefore, I think I am still
using sysvinit. I thought there was already a migration to systemd but
appearently it wasn't.

User: I log in at the console as regular user. And this regular user
invokes 'startx'.

$ ps auxw | grep Xorg
username       8566  0.0  0.3 245992 25544 tty1     Sl   15:19   0:00
/usr/lib/xorg/Xorg -nolisten tcp :0 vt1 -keeptty -auth
/tmp/serverauth.Gi5TPbXzpf

Thank you very much.

Regards,
Flo.

[toc] | [prev] | [next] | [standalone]

#160004

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Oct 30, 2015 at 03:46:47PM +0100, Flo wrote:
> 
> 
> On 10/30/2015 02:33 PM, tomas@tuxteam.de wrote:
> > On Fri, Oct 30, 2015 at 01:57:41PM +0100, Flo wrote:
> >> Hi all,
> > 
> >> I upgraded my Debian testing system.
> > 
> >> The keyboard is working at the console. But when I enter startx and X is
> >> running neither the keyboard nor the mouse works.
> > 
> > Hm. Are they USB devices? If yes: what happens when you unplug and re-plug
> > them (while X is up, as non-root user)?
> > 
> 
> For me the log looks normal (/var/log/syslog):

[...]

> The process with PID 1 is called init, therefore, I think I am still
> using sysvinit. I thought there was already a migration to systemd but
> appearently it wasn't.
> 
> User: I log in at the console as regular user. And this regular user
> invokes 'startx'.
> 
> $ ps auxw | grep Xorg
> username       8566  0.0  0.3 245992 25544 tty1     Sl   15:19   0:00
> /usr/lib/xorg/Xorg -nolisten tcp :0 vt1 -keeptty -auth
> /tmp/serverauth.Gi5TPbXzpf

OK, I *think* that's the problem: Once upon a time, X was setuid root.
So "startx" as a user used to do the right thing. In the brave new
systemd world, X is run as a regular user and systemd-whatever (sorry,
I'm not versed on systemd's innards) does whatever root magic is
needed.

Assuming my hunch above is right, you might try to

 - start X from a display manager (this one runs as root and can inherit
   that to the X server)
 - afaik there is an X "setuid wrapper", but I forgot how it's called,
   perhaps something like "xorg-legacy" or thereabouts. This should make
   startx work again for "mortals".

Or you go the systemd way.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlYzgUMACgkQBcgs9XrR2kYqvgCbB4uqkCOTizFAzwkBVhRWR5O9
X4MAn3Ru3jmVtyEgr8R/2kV2S9t1SbeD
=Neli
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#160005

On 2015-10-30 15:40 +0100, tomas@tuxteam.de wrote:

> OK, I *think* that's the problem: Once upon a time, X was setuid root.
> So "startx" as a user used to do the right thing. In the brave new
> systemd world, X is run as a regular user and systemd-whatever (sorry,
> I'm not versed on systemd's innards) does whatever root magic is
> needed.

It is systemd-logind which controls access rights to input devices. 

> Assuming my hunch above is right, you might try to
>
>  - start X from a display manager (this one runs as root and can inherit
>    that to the X server)
>  - afaik there is an X "setuid wrapper", but I forgot how it's called,
>    perhaps something like "xorg-legacy" or thereabouts. This should make
>    startx work again for "mortals".
>
> Or you go the systemd way.

That means installing libpam-systemd (the latest xserver-xorg-core
package in unstable recommends it, BTW).

Cheers,
       Sven

[toc] | [prev] | [next] | [standalone]

#160008

On 10/30/15 17:02, Sven Joachim wrote:
> On 2015-10-30 15:40 +0100, tomas@tuxteam.de wrote:
> 
>> OK, I *think* that's the problem: Once upon a time, X was setuid root.
>> So "startx" as a user used to do the right thing. In the brave new
>> systemd world, X is run as a regular user and systemd-whatever (sorry,
>> I'm not versed on systemd's innards) does whatever root magic is
>> needed.
> 
> It is systemd-logind which controls access rights to input devices. 
> 
>> Assuming my hunch above is right, you might try to
>>
>>  - start X from a display manager (this one runs as root and can inherit
>>    that to the X server)
>>  - afaik there is an X "setuid wrapper", but I forgot how it's called,
>>    perhaps something like "xorg-legacy" or thereabouts. This should make
>>    startx work again for "mortals".
>>
>> Or you go the systemd way.
> 
> That means installing libpam-systemd (the latest xserver-xorg-core
> package in unstable recommends it, BTW).
> 

Thank you for your hints, I will need them when I migrate.

Regards,
Flo.

[toc] | [prev] | [next] | [standalone]

#160009

> 
>> $ ps auxw | grep Xorg
>> username       8566  0.0  0.3 245992 25544 tty1     Sl   15:19   0:00
>> /usr/lib/xorg/Xorg -nolisten tcp :0 vt1 -keeptty -auth
>> /tmp/serverauth.Gi5TPbXzpf
> 
> OK, I *think* that's the problem: Once upon a time, X was setuid root.
> So "startx" as a user used to do the right thing. In the brave new
> systemd world, X is run as a regular user and systemd-whatever (sorry,
> I'm not versed on systemd's innards) does whatever root magic is
> needed.
> 
> Assuming my hunch above is right, you might try to
> 
>  - start X from a display manager (this one runs as root and can inherit
>    that to the X server)
>  - afaik there is an X "setuid wrapper", but I forgot how it's called,
>    perhaps something like "xorg-legacy" or thereabouts. This should make
>    startx work again for "mortals".
> 

That was the right thought: I installed xserver-xorg-legacy. No effect.
But then I had a closer look at /etc/X11/Xwrapper.config. This file is
from 2012 and was there before installation of xserver-xorg-legacy
(maybe from x11-common). And I had to set needs_root_rights to yes. Now
it's working. Thanks a lot.

> Or you go the systemd way.
> 

Yes, this would have been better way but I am afraid that my init
scripts don't work anymore. I need to take some time to get into it.

Thank you again,
best Regards,
Flo.

[toc] | [prev] | [next] | [standalone]

#160006

On Fri 30 Oct 2015 at 15:46:47 +0100, Flo wrote:

> On 10/30/2015 02:33 PM, tomas@tuxteam.de wrote:
> > On Fri, Oct 30, 2015 at 01:57:41PM +0100, Flo wrote:
> >> Hi all,
> > 
> >> I upgraded my Debian testing system.
> > 
> >> The keyboard is working at the console. But when I enter startx and X is
> >> running neither the keyboard nor the mouse works.
> > 
> > Hm. Are they USB devices? If yes: what happens when you unplug and re-plug
> > them (while X is up, as non-root user)?

[...]
 
> >> The Xorg.0.log is only updated when I run X as root.

Very strange. Did you look in ~/.local?

> > Sysvinit or systemd? As which user is X running?
> > 
> > (under systemd it reportedly doesn't run as root, under sysvinit it has
> > to).
> 
> The process with PID 1 is called init, therefore, I think I am still
> using sysvinit. I thought there was already a migration to systemd but
> appearently it wasn't.

What does 'cat /proc/1/comm' give you? (Not that systemd is necessarily
the culprit).
 
> User: I log in at the console as regular user. And this regular user
> invokes 'startx'.
> 
> $ ps auxw | grep Xorg
> username       8566  0.0  0.3 245992 25544 tty1     Sl   15:19   0:00
> /usr/lib/xorg/Xorg -nolisten tcp :0 vt1 -keeptty -auth
> /tmp/serverauth.Gi5TPbXzpf

On two systems here 'ls /usr/lib/xorg/Xorg' gives

  ls: cannot access /usr/lib/xorg/Xorg: No such file or directory

'cat /etc/X11/xinit/xserverrc' shows the command to start X as

  exec /usr/bin/X -nolisten tcp "$@"

[toc] | [prev] | [next] | [standalone]

#160007

On Fri 30 Oct 2015 at 16:19:13 +0000, Brian wrote:

> On two systems here 'ls /usr/lib/xorg/Xorg' gives
> 
>   ls: cannot access /usr/lib/xorg/Xorg: No such file or directory

Not very helpful of me. Unstable has this file; stable doesn't. 
> 
> 'cat /etc/X11/xinit/xserverrc' shows the command to start X as
> 
>   exec /usr/bin/X -nolisten tcp "$@"
> 

[toc] | [prev] | [next] | [standalone]

#160010

On 10/30/15 17:19, Brian wrote:
> On Fri 30 Oct 2015 at 15:46:47 +0100, Flo wrote:
> 
>> On 10/30/2015 02:33 PM, tomas@tuxteam.de wrote:
>>> On Fri, Oct 30, 2015 at 01:57:41PM +0100, Flo wrote:
>>>> Hi all,
>>>
>>>> I upgraded my Debian testing system.
>>>
>>>> The keyboard is working at the console. But when I enter startx and X is
>>>> running neither the keyboard nor the mouse works.
>>>
>>> Hm. Are they USB devices? If yes: what happens when you unplug and re-plug
>>> them (while X is up, as non-root user)?
> 
> [...]
>  
>>>> The Xorg.0.log is only updated when I run X as root.
> 
> Very strange. Did you look in ~/.local?
> 

No, I wasn't aware that there are log files, too. I will consider that
next time.

>>> Sysvinit or systemd? As which user is X running?
>>>
>>> (under systemd it reportedly doesn't run as root, under sysvinit it has
>>> to).
>>
>> The process with PID 1 is called init, therefore, I think I am still
>> using sysvinit. I thought there was already a migration to systemd but
>> appearently it wasn't.
> 
> What does 'cat /proc/1/comm' give you? (Not that systemd is necessarily
> the culprit).
>  

init

>> User: I log in at the console as regular user. And this regular user
>> invokes 'startx'.
>>
>> $ ps auxw | grep Xorg
>> username       8566  0.0  0.3 245992 25544 tty1     Sl   15:19   0:00
>> /usr/lib/xorg/Xorg -nolisten tcp :0 vt1 -keeptty -auth
>> /tmp/serverauth.Gi5TPbXzpf
> 
> On two systems here 'ls /usr/lib/xorg/Xorg' gives
> 
>   ls: cannot access /usr/lib/xorg/Xorg: No such file or directory
> 
> 'cat /etc/X11/xinit/xserverrc' shows the command to start X as
> 
>   exec /usr/bin/X -nolisten tcp "$@"
> 
> 

Same at my system.

Thanks,
Flo.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web