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, 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)? > > [...] > >>>> 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.
