Xpra: Ticket #2276: xpra cannot start connection

I updated both the server and the client with the latest versions:

Server: Xenial 16.04.5 / r22432 (switched from python2-xpra to python3-xpra, since it was forcefully pulled, and I didn't want the disambiguation :/ )

Xpra-Python3-x86_64_3.0-r22432\xpra_cmd" start ssh://user@ip/2  --opengl=no --start-new-commands=yes --microphone=off --speaker=off --webcam=no --start=gnome-terminal
2019-04-17 14:14:02,244 Xpra GTK3 client version 3.0-r22432 64-bit
2019-04-17 14:14:02,246  running on Microsoft Windows 10
2019-04-17 14:14:02,840 GStreamer version 1.14.4 for Python 3.7.2 64-bit
xpra initialization error:
 connection failed: name 'ssh_target_string' is not defined
Press any key to continue . . .

ssh-password-prompt is coming, but xpra has died already (probably?)



Wed, 17 Apr 2019 11:26:29 GMT - stdedos:

Not sure if that helps, but, downgrading the client, gives this:

Xpra-Python3-x86_64_3.0-r22261\xpra_cmd" shadow ssh://user@ip/0  --clipboard=no --opengl=no --desktop-scaling=0.75 --webcam=no --speaker=off --microphone=off --exit-with-client=no
2019-04-17 14:24:22,082 Xpra GTK3 client version 3.0-r22261 64-bit
2019-04-17 14:24:22,085  running on Microsoft Windows 10
2019-04-17 14:24:23,703 GStreamer version 1.14.4 for Python 3.7.2 64-bit
2019-04-17 14:24:24,351  keyboard settings: layout=us
2019-04-17 14:24:24,356  desktop size is 1600x900 with 1 screen:
2019-04-17 14:24:24,357   Default (423x238 mm - DPI: 96x96) workarea: 1600x860
2019-04-17 14:24:24,358     (Standard monitor types) Generic PnP Monitor (309x174 mm - DPI: 131x131)
2019-04-17 14:24:24,359  downscaled to 75%, virtual screen size: 2133x1200
2019-04-17 14:24:24,359   Default (423x238 mm - DPI: 128x128) workarea: 2133x1147
2019-04-17 14:24:24,360     (Standard monitor types) Generic PnP Monitor (309x174 mm - DPI: 175x175)
2019-04-17 14:24:30,123 Error: failed to receive anything, not an xpra server?
2019-04-17 14:24:30,125   could also be the wrong protocol, username, password or port
2019-04-17 14:24:30,125   or the session was not found
2019-04-17 14:24:30,128 Connection lost

Manual execution gave me this:

$ 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' '/usr/bin/xpra' 'shadow' ':0' '--systemd-run=no'
Running scope as unit run-rf0e5d8a553e8452d8df5ee3876fbcb2e.scope.
xpra for python 2.7 is not installed
$

and then I decided to bring python2-xpra in again; now it's working


Wed, 17 Apr 2019 11:53:00 GMT - Antoine Martin: status changed

This was caused by r22412. r22445 should fix that, will test when I get a chance.

@stdedos: how come you are not using the paramiko backend?


Wed, 17 Apr 2019 12:02:58 GMT - stdedos:

Replying to Antoine Martin:

@stdedos: how come you are not using the paramiko backend?

No idea:

$ grep -Trin ssh /etc/xpra/conf.d/
/etc/xpra/conf.d/40_client.conf:  23   :# Client ssh command:
/etc/xpra/conf.d/40_client.conf:  24   :#ssh = "C:\Program Files\Plink.exe" -ssh -noagent
/etc/xpra/conf.d/40_client.conf:  25   :#ssh = /usr/bin/ssh
/etc/xpra/conf.d/40_client.conf:  26   :#ssh = ssh -o ControlMaster=no -o ConnectTimeout=20
/etc/xpra/conf.d/40_client.conf:  27   :#ssh = ssh -x
/etc/xpra/conf.d/40_client.conf:  28   :#ssh = paramiko
/etc/xpra/conf.d/40_client.conf:  29   :ssh = auto
$ locate $HOME*xpra*
$

Thu, 18 Apr 2019 02:54:16 GMT - Antoine Martin:

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' '/usr/bin/xpra' 'shadow' ':0' '--systemd-run=no'
Running scope as unit run-rf0e5d8a553e8452d8df5ee3876fbcb2e.scope.
xpra for python 2.7 is not installed

Good catch, r22449 fixes this: when wrapping with systemd-run, we have to do extra work to preserve the python interpreter version.


I still don't understand how you end up using plink instead of the paramiko backend so r22448 adds some debugging (new beta builds posted). Try:

xpra_cmd.exe -d ssh ssh://......

It should print which backend is chosen and why.

Maybe you have an old config laying around? This should show ssh = auto:

xpra_cmd.exe showconfig

Thu, 18 Apr 2019 05:28:18 GMT - stdedos:

You might want to change the comment at browser/xpra/trunk/src/xpra/scripts/main.py

#ie: "xpra start ssh://HOST/DISPLAY --start-child=xterm"

Maybe you have an old config laying around? This should show ssh = auto:

xpra_cmd.exe showconfig

Yep, should've remembered to do xpra_cmd.exe showconfig that. I'll check later today and update the comment.


Thu, 18 Apr 2019 05:44:27 GMT - Antoine Martin:

Comment updated in r22455.


Thu, 16 May 2019 12:02:05 GMT - Antoine Martin:

Bump


Thu, 16 May 2019 12:38:20 GMT - stdedos:

I know I am not behaving nicely with tickets, apologies :/

xpra_cmd showconf shows:

[...]
ssh                   (used)   = 'plink -ssh -agent'               <class 'str'>
ssh                  (default) = 'auto'                            <class 'str'>
[...]

After a lot of fiddling with paths etc C:\ProgramData\Xpra\conf.d\40_client.conf:29 is the culprit:

[...]
ssh = plink -ssh -agent
[...]

Unfortunately, nothing seems to come with -d ssh :/

C:\Users\user\Documents\xpra-clients\Xpra-Python3_2.5.2-r22633>Xpra_cmd.exe  -d ssh shadow ssh://user@ip/0 --opengl=no --desktop-scaling=0.75 --webcam=no --speaker=off --microphone=off --exit-with-client=no
2019-05-16 15:27:23,013 Xpra GTK3 client version 2.5.2-r22633 32-bit
2019-05-16 15:27:23,017  running on Microsoft Windows 10
2019-05-16 15:27:23,828 GStreamer version 1.14.4 for Python 3.7.3 32-bit
2019-05-16 15:27:25,630  keyboard settings: layout=us
2019-05-16 15:27:25,640  desktop size is 1600x900 with 1 screen:
2019-05-16 15:27:25,643   Default (423x238 mm - DPI: 96x96) workarea: 1600x860
2019-05-16 15:27:25,647     (Standard monitor types) Generic PnP Monitor (309x174 mm - DPI: 131x131)
2019-05-16 15:27:25,649  downscaled to 75%, virtual screen size: 2133x1200
2019-05-16 15:27:25,651   Default (423x238 mm - DPI: 128x128) workarea: 2133x1147
2019-05-16 15:27:25,652     (Standard monitor types) Generic PnP Monitor (309x174 mm - DPI: 175x175)
2019-05-16 15:27:33,883 enabled remote logging
2019-05-16 15:27:33,890 Xpra GTK2 shadow server version 3.0-r22647 64-bit
2019-05-16 15:27:33,892  running on Linux Ubuntu 16.04 xenial
(Xpra_cmd.exe:4732): Pango-WARNING **: 15:27:34.728: couldn't load font "Bitstream Vera Sans Not-Rotated 11.7294921875", falling back to "Sans Not-Rotated 11.7294921875", expect ugly output.
2019-05-16 15:27:41,566 window-close event on desktop or shadow window, disconnecting

I haven't touched the file in question myself C:\ProgramData\Xpra\conf.d\40_client.conf:29, so, what do I do?

Should I wipe the directory clean for good measure?


Can the showconf show "who" has applied a setting?

In Unix it's not a problem, but, until e.g. windows has a proper terminal, it's not that easy to "grep" a list of directories to find "something" in them.


Thu, 30 May 2019 15:12:32 GMT - Antoine Martin: owner, status changed

Can the showconf show "who" has applied a setting?

Sadly, no. By the time we get the data in a useful format, we don't know where each setting came from.

until e.g. windows has a proper terminal, it's not that easy to "grep" a list of directories to find "something" in them

Try [‚Äčhttps://www.msys2.org/ msys2.org].

I think we can close this ticket.


Thu, 30 May 2019 19:01:33 GMT - stdedos: status changed; resolution set

Replying to Antoine Martin:

I think we can close this ticket.

Yes

I haven't touched the file in question myself C:\ProgramData\Xpra\conf.d\40_client.conf:29, so, what do I do? Should I wipe the directory clean for good measure?

I didn't apply this setting, but it was there


Mon, 17 Jun 2019 10:37:33 GMT - Antoine Martin:

r22969 + r22970 add the xpra showsetting subcommand which can be used to see where a specific setting is coming from:

$ python2 /usr/bin/xpra showsetting postscript-printer
* default config:
postscript-printer  : 'drv:///sample.drv/generic.ppd'          (<type 'str'>)
* '/etc/xpra':
postscript-printer  : ''                                       (<type 'str'>)
* '/home/antoine/.xpra':
postscript-printer  :                                          (<type 'NoneType'>)
* '/home/antoine/.config/xpra':
postscript-printer  :                                          (<type 'NoneType'>)

So you should be able to figure out where the setting comes from. (also works on ms windows obviously)


Sat, 23 Jan 2021 05:46:53 GMT - migration script:

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