Julien Cristau on 2015/10/21 +0200 @20:48:56: > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > > > This upgrade has broken X startup for me. Here is how > > I start X (as ordinary user): > > > > exec setsid env -i \ > > ... > > X :0 vt63 \ > > So one solution is to install xserver-xorg-legacy and > tell it to not drop privileges > (needs_root_rights=yes). But that leaves X running > as root, which we're trying to move away from.
That would surely be a regression. Debian went from a working X that dropped privileges, to a non-working X that can only be run as root. Huh?? And the suggested solution is: > to change your setup to run X on the VT it's started > from, inside a logind session, so it doesn't need > extra privileges. There's more than the tty problem, there's also the IOPL issue (I don't know what that is... all I know is I didn't get it before the wrapper changed, started it as ordinary user and it worked fine). I fail to see why I should be forced to run some whizbang login daemon. I have a very simple setup that has worked forever. I run an X server, with kernel modesetting, and a simple window manager. I have no need for desktop environments, login daemons, or to run "kitchensinkd" or anything else. This change is clearly a regression. This has taken a perfectly working setup that does NOT run the X server with root privileges, and forces me to either run additional things I don't need and which cause invasive changes to my system, or to run my X server insecurely with root privileges. Why did the wrapper even need to change? I get that it's desired in a '-legacy' package, fine, I can deal with a moved program. But why was a perfectly working wrapper *broken* and functionality removed?
