-----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, to...@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-----
