xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 4 years ago

Closed 4 years ago

Last modified 6 months ago

#1439 closed defect (wontfix)

Trunk servers built from source try to launch with Python 3

Reported by: J. Max Mena Owned by: Antoine Martin
Priority: major Milestone:
Component: server Version: trunk
Keywords: Cc:


Building a trunk machine from source causes /usr/bin/xpra to start with the line:


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

Change History (7)

comment:1 Changed 4 years ago by J. Max Mena

Oh, I should mention that changing the python3 to python2 allows the trunk servers to launch and run as expected.

comment:2 Changed 4 years ago by Antoine Martin

Resolution: wontfix
Status: newclosed

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.

Last edited 4 years ago by Antoine Martin (previous) (diff)

comment:3 Changed 4 years ago by Antoine Martin

Note: there is a workaround for this, you can run:

python2 /usr/bin/xpra (...) --systemd-run=no

comment:4 Changed 4 years ago by J. Max Mena

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.

comment:5 Changed 4 years ago by Antoine Martin

  • you do not need to delete the file, whatever you run last will be what sticks (edited comment:2 which said "first" instead of "last")
  • there are no "build system changes" in 2.x relating to this AFAIK - the "systemd-run" option which makes this more apparent was already in 1.0

Feel free to edit the wiki, I don't see what needs adding.

comment:6 Changed 4 years ago by J. Max Mena

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.

Last edited 4 years ago by J. Max Mena (previous) (diff)

comment:7 Changed 6 months ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1439

Note: See TracTickets for help on using tickets.