Bjørn Lie writes:
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.
We could add a 'recommends:' or 'suggests:' to the affected driver packages. Since these packages are only installed if the hardware is found, the user will not get the wrapper normally.
This will hopefully "encourage" upstreams to port their drivers, or switch to other ones.
This will not happen. Most of the hardware supported by the UMS drivers is of marginal relevance today. Therefore the drivers are not really supported. Upstream just makes sure they still build. Some community users (openSUSE) complain if they don't work as expected in which case I often reply, that it is a free software project where everybody can contribute - if someone is interested in such hardware (s)he should expect to have to fix issues her/himself.
From what I understood from a virtualbox bug I was cc'ed on, Oracle is already underway with theirs.
Yeah, this driver is an exception. VMWare and QXL are there already. (Well, VMWare isn't quite: there is still xf86-input-vmware). Cheers, Egbert.
Input: ======
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)
Yeah, you can. Just not configure them from Gnome.
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=66c211ff2 4bec6a938d6a6a0dd8730f4689ef383
https://bugzilla.gnome.org/show_bug.cgi?id=759595
This will kinda force us to Require xf86-input-libinput for the next release, so I guess that more or less "taken care off"
Yeah, possibly. I'm not even sure - have we done this on TW already? Last time I've checked we hadn't. IHMO we should do this there ASAP to have a good test coverage. Cheers, Egbert.-- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org