Issues arising from #1806 testing.
Can you tell from the logs where the connection originated from, or break down the file into connection attempts? I will try to comment your statements and also "draw a timeline" (mentioning connection attempt # and location from where I attach).
Warning: more than 30 clipboard requests per second!:
I would assume this happened when I first attached. I attached from localhost - so xpra shadow :0 on the server and xpra attach on the server.
This was working perfectly. ... except for the fact that there was a major shadowing loop since xpra shadow and xpra attach happened on the same computer. I did have a perfomance hit, but nothing major. I "fixed" it by scaling the windows to 25%. Fuctionality seemed okay.
I closed this client
Warning: delayed region timeout region is 15 seconds old, will retry - bad connection?:
This is connection attempt 2 and 3. Connection was made remotely - so that means, from the Windows 10 2.2.6 latest setup. I never actually got to see the windows. I got the red disconnected message (no response, it could mean no credentials - thing).
(removing cut&paste from #1806 - linking to it is enough, also changed the title: only one issue at a time, there's only one issue unresolved in this ticket AFAICT anyway)
Can you tell from the logs where the connection originated from
Each new connection will log a message like this one:
New tcp connection received from 127.0.0.1:60624 on 0.0.0.0:10000
I never actually got to see the windows. I got the red disconnected message
What exact message?
Try connecting to a regular "start" session instead of a "shadow" session - this shouldn't make any difference, but who knows what is going on with your setup. This is also known to work reliably and is being used by thousands of people every day. Also try connecting from another client, ie: html5 client or Linux client, so at least we know which end is having problems, client or server.
Replying to Antoine Martin:
Can you tell from the logs where the connection originated from
Each new connection will log a message like this one:
New tcp connection received from 127.0.0.1:60624 on 0.0.0.0:10000
I cannot see "new tcp connection" when I am doing "C:\Program Files\Xpra\xpra_cmd" attach ssh:sntentos@172.16.57.108:0 --desktop-scaling=0.25. I splitted the logfiles regardless for more clarity.
Server is on Ubuntu 16.04.3
xpra attach :0 --desktop-scaling=0.25 --clipboard=no
"C:\Program Files\Xpra\xpra_cmd" attach ssh:sntentos@172.16.57.108:0 --desktop-scaling=0.25
ws://***/. It seems to work correctly. Server does not close after giving Ctrl+D on the terminal - should/shouldn't it?
I never actually got to see the windows. I got the red disconnected message
What exact message?
C:\>"C:\Program Files\Xpra\xpra_cmd" shadow ssh://sntentos@172.16.57.108//:0 2018-04-20 11:19:23,001 Xpra gtk2 client version 2.2.6-r18959 64-bit 2018-04-20 11:19:23,017 running on Microsoft Windows 10 2018-04-20 11:19:24,048 GStreamer version 1.12.4 for Python 2.7.14 64-bit 2018-04-20 11:19:24,282 OpenGL_accelerate module loaded 2018-04-20 11:19:24,361 Using accelerated ArrayDatatype 2018-04-20 11:19:25,236 Warning: vendor 'Intel' is greylisted, 2018-04-20 11:19:25,236 you may want to turn off OpenGL if you encounter bugs 2018-04-20 11:19:33,892 OpenGL enabled with Intel(R) HD Graphics 4000 2018-04-20 11:19:34,064 keyboard settings: layout=us 2018-04-20 11:19:34,064 desktop size is 1600x900 with 1 screen: 2018-04-20 11:19:34,064 2\WinSta-Default (423x238 mm - DPI: 96x96) workarea: 1600x860 2018-04-20 11:19:34,064 DISPLAY1 (310x174 mm - DPI: 131x131) 2018-04-20 11:19:34,111 keyboard layouts: us,gr 2018-04-20 11:19:34,220 Error: failed to receive anything, not an xpra server? 2018-04-20 11:19:34,236 could also be the wrong protocol, username, password or port 2018-04-20 11:19:34,236 Connection lost
But I figured this has to do with the command line. For me, it is not shadow ssh://sntentos@172.16.57.108//:0 but shadow ssh:sntentos@172.16.57.108:0
Try connecting to a regular "start" session instead of a "shadow" session - this shouldn't make any difference, but who knows what is going on with your setup.
After fixing the command line, "all things appear to work".
This is also known to work reliably and is being used by thousands of people every day.
I know, and I value the effort, professionalism and the time you spend to keep xpra active, up-to-date, and bulletproof. This is why I decided to put in a feature request and all the "issues" that arose from it. I am sorry if that is not coming out.
Also try connecting from another client, ie: html5 client or Linux client, so at least we know which end is having problems, client or server.
Mentinoned HTML5 client already
Server does not close after giving Ctrl+D on the terminal - should/shouldn't it?
That depends on a number of things:
Works for me, though the browser will display a "cannot connect" page since the server is now dead.
I cannot see "new tcp connection" when I am doing .. attach via ssh
SSH connections will show up as "unix-domain" (same as local socket connections), ie:
New unix-domain connection received on /run/user/1000/xpra/desktop-3
ssh://sntentos@172.16.57.108//:0
Remove the double slash at the end, I have edited ticket:1806#comment:8 which wrongly contained it. Also remove the ":", so that becomes: ssh://sntentos@172.16.57.108/0
I know, and I value the effort,...
Thanks
As I managed to solve #1815, I'd say that this is invalid and/or affected by clipboard.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1813