Description of problem:
The use of the "void" input driver in xpra is obsolete. This driver existed to provide empty input devices back when the server required at least one pair of input devices to exist. That hasn't been true since server 1.6 (in 2007).
The only use of it seems to be in the xorg.conf where it can be safely removed i.e. both InputDevice sections and the references in the ServerLayout. The server will initialize a default device for both.
Sorry, I only noticed this after retiring xorg-x11-drv-void. It's only retired in git so far though.
OK, xorg.conf is autogenerated by xpra, so this will require some patching. I'll report upstream, but for now please don't remove it from the repos.
xpra-0.14.21-5.fc22 has been submitted as an update for Fedora 22.
xpra-0.14.21-5.fc21 has been submitted as an update for Fedora 21.
xpra-0.14.21-5.fc20 has been submitted as an update for Fedora 20.
Note the 0.14.21-5 packages still Require the void driver - I'll fix that in the next update I push.
(In reply to Jonathan Underwood from comment #5)
> Note the 0.14.21-5 packages still Require the void driver - I'll fix that in
> the next update I push.
no worries, thanks. Let me know when you're done with that please so I can finish the retirement of the driver.
xpra-0.14.22-4.fc20 has been submitted as an update for Fedora 20.
xpra-0.14.22-4.fc21 has been submitted as an update for Fedora 21.
xpra-0.14.22-4.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xpra-0.14.21-5.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
xpra-0.14.22-4.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
xpra-0.14.22-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.