Bug#807015: xinit: startx freezes, mouse and keyboard don't work

[Laurent Bigonville]

On Sat, 5 Dec 2015 07:55:54 +1100 Craig Sanders  wrote:
> On Fri, Dec 04, 2015 at 01:57:53PM +0100, Laurent Bigonville wrote:
> > Are you using systemd?
>
> Nope, this particular machine is still sysvinit.
>
> It also has over 20 years worth of cruft on it, as i first built it in
> 1994 and have continuously upgraded it (with debian unstable) ever since.
>
> > is libpam-systemd installed on your machine?
>
> Yes, because without it several important packages would be uninstalled,
> including libvirt packages for some unfathomable reason - it's 
impossible to
> have a completely non-systemd machine in debian, you can either have 
systemd

> or you can have a hybrid of systemd + whatever else. systemd, or at least
> parts of it, is mandatory.
>
>
> It is not enabled in /etc/pam.d/ though. None of the files in there use
> it.
>
> and, yes, I have tried it with libpam_systemd enabled. Makes no 
difference.

>
>
> > If it's not the case, try to install xserver-xorg-legacy and look at
> > Xwrapper.config man page
>
> What good would that do? What would it fix, and how? I am running
> neither legacy drivers nor non-linux kernels.
>
> startx worked without this until recently, i'd rather not digress into
> installing and configuring random packages unless there's a good and
> clearly defined reason for it.

Since version 2:1.17.2-2, the xserver is trying running as non-root, but 
you need systemd  for this.


If you don't have systemd installed on your machine, you need a setuid 
wrapper so the server is still started as root. This wrapper is 
installed by the xserver-xorg-legacy package.


I don't think it's a good idea to add your user into the input group.

Laurent Bigonville

Bug#807015: xinit: startx freezes, mouse and keyboard don't work

[Craig Sanders]

Package: xinit
Version: 1.3.4-3
Severity: grave
Justification: renders package unusable

sometime in the last ~70 days (since I last started X or rebooted),
something has changed in X that prevents startx from working as an
ordinary user.

startx *was* working perfectly.  Now when I run startx, I can see the
xfce desktop but neither keyboard nor mouse work at all, can't even
switch VT with Ctrl-Alt-F1 to kill X.  I have to login from another
machine on the network to kill X and get back to a text console.

seems to be something to do with the error message:

  xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)


here's the entire log from 'startx > startx.log 2>&1':

X.Org X Server 1.17.3
Release Date: 2015-10-26
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux ganesh 3.19-5.dmz.1-liquorix-amd64 #1 ZEN SMP 
PREEMPT Debian 3.19-5 (2015-04-19) x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.19-5.dmz.1-liquorix-amd64 
root=/dev/md1 ro iommu=noagp iommu=noagp
Build Date: 27 October 2015  11:41:02PM
xorg-server 2:1.17.3-2 (http://www.debian.org/support) 
Current version of pixman: 0.33.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/cas/.local/share/xorg/Xorg.1.log", Time: Fri Dec  4 
18:47:52 2015
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19-5.dmz.1-liquorix-amd64 (SMP w/6 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages xinit depends on:
ii  coreutils   8.23-4
ii  libc6   2.21-1
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  lxde-common [x-session-manager]   0.99.0-2
ii  lxsession [x-session-manager] 0.5.1-2
ii  metacity [x-window-manager]   1:3.18.1-1
ii  openbox [x-window-manager]3.6.1-2
ii  roxterm [x-terminal-emulator] 3.2.1-1
ii  terminator [x-terminal-emulator]  0.97-4
ii  xfce4-session [x-session-manager] 4.12.1-3
ii  xfce4-terminal [x-terminal-emulator]  0.6.3-2
ii  xfwm4 [x-window-manager]  4.12.3-1
ii  xserver-xorg [xserver]1:7.7+12
ii  xterm [x-terminal-emulator]   320-1

xinit suggests no packages.

-- no debconf information

Bug#807015: xinit: startx freezes, mouse and keyboard don't work

[Laurent Bigonville]

On Fri, 04 Dec 2015 19:03:05 +1100 Craig Sanders  wrote:
Hi,

>
> sometime in the last ~70 days (since I last started X or rebooted),
> something has changed in X that prevents startx from working as an
> ordinary user.
>
> startx *was* working perfectly. Now when I run startx, I can see the
> xfce desktop but neither keyboard nor mouse work at all, can't even
> switch VT with Ctrl-Alt-F1 to kill X. I have to login from another
> machine on the network to kill X and get back to a text console.
>
> seems to be something to do with the error message:
>
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>

Are you using systemd? is libpam-systemd installed on your machine?

If it's not the case, try to install xserver-xorg-legacy and look at 
Xwrapper.config man page


Cheers,

Laurent Bigonville

Bug#807015: xinit: startx freezes, mouse and keyboard don't work

[Craig Sanders]

On Fri, Dec 04, 2015 at 01:57:53PM +0100, Laurent Bigonville wrote:
> Are you using systemd? 

Nope, this particular machine is still sysvinit.

It also has over 20 years worth of cruft on it, as i first built it in
1994 and have continuously upgraded it (with debian unstable) ever since.

> is libpam-systemd installed on your machine?

Yes, because without it several important packages would be uninstalled,
including libvirt packages for some unfathomable reason - it's impossible to
have a completely non-systemd machine in debian, you can either have systemd
or you can have a hybrid of systemd + whatever else.  systemd, or at least
parts of it, is mandatory.


It is not enabled in /etc/pam.d/ though.  None of the files in there use
it.

and, yes, I have tried it with libpam_systemd enabled.  Makes no difference.


> If it's not the case, try to install xserver-xorg-legacy and look at
> Xwrapper.config man page

What good would that do?  What would it fix, and how? I am running
neither legacy drivers nor non-linux kernels.

startx worked without this until recently, i'd rather not digress into
installing and configuring random packages unless there's a good and
clearly defined reason for it.


craig

-- 
craig sanders 

Bug#807015: xinit: startx freezes, mouse and keyboard don't work

[Craig Sanders]

I have managed to get startx working again, but I'm not sure if it's the
correct way.  I added my user to the 'input' group after noticing the
following in /home/cas/.local/share/xorg/Xorg.1.log

[ 24633.131] (**) evdev: Dell Dell USB Keyboard: Device: "/dev/input/event1"
[ 24633.131] (EE) evdev: Dell Dell USB Keyboard: Unable to open evdev device 
"/dev/input/event1".

$ ls -l /dev/input/event1
crw-rw 1 root input 13, 65 Dec  4 11:57 /dev/input/event1

and similar for the mouse.


Doing this allows the mouse and keyboard to work with startx but it
seems a rather hackish and possibly completely incorrect solution.  I'm
going to have to do some research on where this input group came from
and whether it's appropriate for ordinary user accounts to be members.
I suspect it's a bad idea to do that.

I'm still getting the "xf86EnableIOPorts: failed to set IOPL for
I/O (Operation not permitted)" error message in startx.log - and
so far google has been absolutely useless in revealing what that's
about...several people have complained about it but no-one has come up
with a definitive reason for it.


craig

-- 
craig sanders