ti., 12.01.2016 kl. 13.56 +0100, skrev Egbert Eich:
The bigger challange will be UMS devices. For these the only option I see would be to start them as root or to use a wrapper script to do this (this seems to be the present solution at Debian). The question which remains is, how does GDM know that a wrapper script is required? It would be easy to test for the presence of KMS, however, this will often include cases where fbdev can be used. I'm open to suggestions here ;) - after all, this decision needs to be made in GDM.
For openSUSE I'd be fine with this not being automatic, as in we provide a suid-wrapper-"compat" package, but do not install it by default. Those who need it have to install it, and since that will lead to only users in need, always apply it when installed.
This will hopefully "encourage" upstreams to port their drivers, or switch to other ones.
From what I understood from a virtualbox bug I was cc'ed on, Oracle is
already underway with theirs.
For input drivers upstream have already dropped all mouse support for non-libinput drivers (at least for configuration, I've not verified if one can still use synaptic/foo but not configure them via gnome-tools)
This will kinda force us to Require xf86-input-libinput for the next release, so I guess that more or less "taken care off"