So, the way Xorg is started has changed yet again for the Fedora 22 release.
On F22 XORG_BIN gets set to /usr/bin/Xorg which is a shell script that execs /usr/libexec/Xorg.wrap which is then supposed to exec /usr/libexec/Xorg after doing it's stuff, instead of /usr/libexec/Xorg.bin in F21.
So, that's the first problem - XORG_BIN should be being set to /usr/libexec/Xorg, rather than /usr/libexec/Xorg.bin. So, the logic in setup.py needs enhancing.
The second issue is then that, even when XORG_BIN is correctly set to /usr/libexec/Xorg in xpra_Xdummy, the X server fails to start with this:
(++) Log file: "/home/tom/.xpra/Xorg.:100.log", Time: Mon May 25 12:30:08 2015 (++) Using config file: "/etc/xpra/xorg.conf" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory) (EE) (EE)
Downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1224678
"So, the logic in setup.py needs enhancing." should read "So, the logic in xpra_Xdummy needs enhancing."
Patch to find the Xorg binary on Fedora 22
OK, there's a suggested patch to xpra_Xdummy wrapper to fix the logic for finding the Xorg binary.
The second problem, i.e. the failure of Xorg to start with the xdummy driver looks likely to be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1203780
which is a bug with the xserver, fixed in a later package - we'll test with that and report back. In the meantime, see what you think to the simple patch.
Applied in r9525 for all maintained branches.
It should be safe I think, there should not be any other distributions out there that use libexec and have an executable Xorg in there. (centos7 does not)
As for the other issue, I guess we can only wait for the fix to get pushed? (will try it in a VM tomorrow)
Replying to totaam:
Applied in r9525 for all maintained branches.
It should be safe I think, there should not be any other distributions out there that use libexec and have an executable Xorg in there. (centos7 does not)
OK, great.
As for the other issue, I guess we can only wait for the fix to get pushed? (will try it in a VM tomorrow)
Yes; I actually think that xorg-x11-server-1.17.1-12 will fix the issue, which is making its way to the updates repos.
Confirmed, with the patch in this bug, and xorg-x11-server-1.17.1-12, xpra now starts successfully on F22. I'll close this. Thanks for applying the patch.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/872