On Sat, 5 Dec 2015 07:55:54 +1100 Craig Sanders <c...@taz.net.au> 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
