Building a trunk machine from source causes /usr/bin/xpra
to start with the line:
#!/usr/bin/python3
And, when a user tries to launch a server, it says that operation is not supported.
For some odd reasons, the trunk build scripts (the ones that Smo helped me set up) spit out that line, which caused almost two days worth of a headache for me until Smo spotted it. I thought this was an issue with just my machines until someone else had it happen to them on a completely fresh machine, so I figured it would be best to report this as an issue.
Here's the shell script I'm building with (ran in the src/ folder):
#clean up build info rm xpra/build_info.py rm xpra/src_info.py #clean up old build ./setup.py clean #LDFLAGS=-Wl,-rpath=/usr/lib64/xpra \ #PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/lib64/xpra/pkgconfig \ # ./setup.py install #no longer needed python2 ./setup.py build \ --rpath=/usr/lib64/xpra --pkg-config-path=/usr/lib64/xpra/pkgconfig sudo python3 ./setup.py install \ --rpath=/usr/lib64/xpra --pkg-config-path=/usr/lib64/xpra/pkgconfig --without-html5 --without-printing sudo python2 ./setup.py install \ --rpath=/usr/lib64/xpra --pkg-config-path=/usr/lib64/xpra/pkgconfig
Oh, I should mention that changing the python3
to python2
allows the trunk servers to launch and run as expected.
Just run the python2 build last, or delete "/usr/bin/xpra" before you run it.
This is not new, both builds claim the same file.
Note: there is a workaround for this, you can run:
python2 /usr/bin/xpra (...) --systemd-run=no
Running Python2 before Python3 doesn't change anything, but leaving the Python3 one first and deleting /usr/bin/xpra
before running the Python2 one did it.
Note: The wiki page on building from source didn't mention this and needs to be updated. Especially considering all the build system changes that 2.X brings.
Feel free to edit the wiki, I don't see what needs adding.
Okay, I see now.
Weird that it EDIT: swapping the Python2 and Python3 lines didn't fix it, but it's working for now so I don't really want to poke it, lest I make it worse.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1439