Xpra: Ticket #141: PYTHONPATH in xpra 0.3.2 in ubuntu (packaging problem)

Don't know if this bug should be reported here, being it likely a packaging problem.

Xpra_launcher aborts on ubuntu 12.04 since import of pra modules from python code fail. Explicitly setting the PYTHONPATH fixes the issue.



Tue, 05 Jun 2012 05:56:55 GMT - Antoine Martin: status changed

Are you saying that simply running:

xpra_launcher

From the command line fails?

Does it work if you just run:

xpra

?

Thanks Antoine


Tue, 05 Jun 2012 12:26:39 GMT - sergio:

xpra --version
xpra v0.3.2

xpra works just fine

xpra_launcher
Traceback (most recent call last):
  File "/usr/bin/xpra_launcher", line 3, in <module>
    from xpra.scripts.client_launcher import main
ImportError: No module named xpra.scripts.client_launcher

xpra launcher cannot find its pieces. Easy to see why: the xpra script starts with

import sys
sys.path.append("/usr/lib/xpra")

the xpra_launcher script does not. Obviously, adding the two liner on top of xpra_launcher fixes the issue.


Tue, 05 Jun 2012 13:02:32 GMT - Antoine Martin: status changed; resolution set

sigh, yet another packaging hoop I have to jump through, this time Debian specific patches for placing the python libraries in an unusual place...

Done in r900 + r901 (oops), I will push an update to debian shortly.


Sat, 23 Jan 2021 04:46:39 GMT - migration script:

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