xpra icon
Bug tracker and wiki

Opened 2 months ago

Closed 4 weeks ago

#2296 closed defect (fixed)

Cannot start xpra shadow with 226**

Reported by: stdedos Owned by: stdedos
Priority: minor Milestone: 3.0
Component: server Version: 2.5.x
Keywords: Cc:

Description

py3-x64-r22647 on Ubuntu 16.04.5 LTS Server and
Xpra-Python3_2.5.2-r22633 on Win10 client

From the Windows 10 client:

\xpra-clients\Xpra-Python3_2.5.2-r22633\xpra_cmd" shadow ssh://[email protected]/0  --opengl=no --desktop-scaling=0.75 --webcam=no --speaker=off --microphone=off --exit-with-client=no

2019-05-13 12:36:32,206 Xpra GTK3 client version 2.5.2-r22633 32-bit
2019-05-13 12:36:32,209  running on Microsoft Windows 10
2019-05-13 12:36:32,749 GStreamer version 1.14.4 for Python 3.7.3 32-bit
2019-05-13 12:36:33,110  keyboard settings: layout=us
2019-05-13 12:36:33,112  desktop size is 1600x900 with 1 screen:
2019-05-13 12:36:33,112   Default (423x238 mm - DPI: 96x96) workarea: 1600x860
2019-05-13 12:36:33,112     (Standard monitor types) Generic PnP Monitor (309x174 mm - DPI: 131x131)
2019-05-13 12:36:33,112  downscaled to 75%, virtual screen size: 2133x1200
2019-05-13 12:36:33,113   Default (423x238 mm - DPI: 128x128) workarea: 2133x1147
2019-05-13 12:36:33,113     (Standard monitor types) Generic PnP Monitor (309x174 mm - DPI: 175x175)
2019-05-13 12:36:42,230 Error: failed to receive anything, not an xpra server?
2019-05-13 12:36:42,232   could also be the wrong protocol, username, password or port
2019-05-13 12:36:42,233   or the session was not found
2019-05-13 12:36:42,233 Connection lost

From an existing xpra-start-gnome-terminal (:2):

[email protected] [2019-05-13 12:24:45]:/run/user/1000/xpra$ env -i bash -c ' . /run/user/1000/dbus-session; xpra shadow :0'
xpra for python 2.7 is not installed
 retrying with python3
using systemd-run to wrap 'shadow' server command
'systemd-run' '--description' 'xpra-shadow' '--scope' '--user' 'python3' '/usr/bin/xpra' 'shadow' ':0' '--systemd-run=no'
Failed to create bus connection: No such file or directory
[email protected] [2019-05-13 12:25:07]:/run/user/1000/xpra$ xpra shadow :0
xpra for python 2.7 is not installed
 retrying with python3
using systemd-run to wrap 'shadow' server command
'systemd-run' '--description' 'xpra-shadow' '--scope' '--user' 'python3' '/usr/bin/xpra' 'shadow' ':0' '--systemd-run=no'
Failed to create bus connection: No such file or directory

No logs get generated on the server to attach.

Change History (10)

comment:1 Changed 2 months ago by stdedos

(Basic xpra start :10 works)

comment:2 Changed 2 months ago by Antoine Martin

Owner: changed from Antoine Martin to stdedos

Have you tried with the python2 builds?

Last edited 2 months ago by Antoine Martin (previous) (diff)

comment:3 Changed 2 months ago by stdedos

python2-xpra seems to work okay (just pulled it)

comment:4 Changed 2 months ago by Antoine Martin

Owner: changed from stdedos to Antoine Martin
Priority: majorminor
Status: newassigned

The ssh command ends up running:

$XDG_RUNTIME_DIR/xpra/run-xpra _proxy_shadow_start

And since the default python2 version is not installed, it re-execs the script with python3 via os.execvpe.

Strangely, this fails with: failed to indentify the new server display.

comment:5 Changed 2 months ago by Antoine Martin

Owner: changed from Antoine Martin to stdedos
Status: assignednew

This should be fixed in r22716, but unfortunately we cannot fix a script that has already been generated: an ssh connection will just use it as it is.
So this may not fix things until you wipe $XDG_RUNTIME_DIR (on some platforms, a reboot might do this)
Or you could edit $XDG_RUNTIME_DIR/xpra/run-xpra by hand and just remove XPRA_ALT_PYTHON_RETRY from there.

comment:6 in reply to:  5 Changed 2 months ago by stdedos

Replying to Antoine Martin:

This should be fixed in r22716, but unfortunately we cannot fix a script that has already been generated: an ssh connection will just use it as it is.
So this may not fix things until you wipe $XDG_RUNTIME_DIR (on some platforms, a reboot might do this)
Or you could edit $XDG_RUNTIME_DIR/xpra/run-xpra by hand and just remove XPRA_ALT_PYTHON_RETRY from there.

I did that:

[email protected] [2019-05-16 15:18:27]:/run/user/1000/xpra$ grep XPRA_ALT_PYTHON_RETRY /run/user/1000/xpra/run-xpra
[email protected] [2019-05-16 15:18:58]:/run/user/1000/xpra$ 

Still not working (haven't updated either).

I needed to re-install python2-xpra for it to work

comment:7 Changed 6 weeks ago by Antoine Martin

Not sure how I had missed that, but running run-xpra _proxy_shadow_start was erroring out with python3, r22926 fixes that.

(there's still a segfault on server exit - but that's a different thing)

@stdedos: does that fix things for you? (the trivial patch can be applied by hand to the server)

comment:8 Changed 6 weeks ago by Antoine Martin

new ticket for the shadow segfault with python3 on Ubuntu 16.04: #2328

comment:9 in reply to:  7 Changed 5 weeks ago by stdedos

Replying to Antoine Martin:

Not sure how I had missed that, but running run-xpra _proxy_shadow_start was erroring out with python3, r22926 fixes that.

(there's still a segfault on server exit - but that's a different thing)

@stdedos: does that fix things for you? (the trivial patch can be applied by hand to the server)

I have had applied the patch, and I have installed the latest xenial beta (as of Wed morning) for #2338. So, I guess things are working.

I don't remember, though, if I have removed the py2 package; I need to check that tomorrow --> No, I haven't. Need to try again on Monday. :/

Last edited 5 weeks ago by stdedos (previous) (diff)

comment:10 Changed 4 weeks ago by stdedos

Resolution: fixed
Status: newclosed

The proposed solution does not work:

~$  grep -i 'XPRA_ALT_PYTHON_RETRY' $XDG_RUNTIME_DIR/xpra/run-xpra
~$ 

but just removing the file seems to be fine

Note: See TracTickets for help on using tickets.