xpra icon
Bug tracker and wiki

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


Changes between Initial Version and Version 2 of Ticket #1813


Ignore:
Timestamp:
04/20/18 03:28:03 (3 years ago)
Author:
Antoine Martin
Comment:

(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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1813

    • Property Owner changed from Antoine Martin to stdedos
    • Property Summary changed from Issues arising from #1806 testing to cannot attach from win10 client
  • Ticket #1813 – Description

    initial v2  
    11Issues arising from #1806 testing.
    2 
    3 ----
    4 
    5 
    6 From the log file:
    7 
    8 {{{
    9 C:\>"C:\Program Files\Xpra\xpra_cmd" shadow ssh:user@SERVERIP
    10 }}}
    11 
    12 So you're starting a remote shadow without specifying the display to shadow, this may fail if there is more than one display active, which may be the case if you have started other xpra sessions for example.
    13 Try starting the shadow server in advance, which will give you a log file you can inspect (directly on the server):
    14 
    15 {{{
    16 xpra shadow :THEDISPLAY
    17 }}}
    18 
    19 or specify the display to shadow (from the client):
    20 
    21 {{{
    22 xpra_cmd.exe shadow ssh://user@SERVERIP/THESERVERDISPLAY
    23 }}}
    24 
    25 ''I am getting confused by this ticket now, because this has little to do with 3 monitors?''
    26 
    27 ----
    28 I never actually specified a monitor on the commandline :/
    29 Running
    30 
    31 {{{
    32 C:\>"C:\Program Files\Xpra\xpra_cmd" shadow ssh:user@SERVERIP:THESERVERDISPLAY
    33 }}}
    34 
    35 Didn't change anything.
    36 Running
    37 
    38 {{{
    39 C:\>"C:\Program Files\Xpra\xpra_cmd" shadow ssh://user@SERVERIP//THESERVERDISPLAY
    40 }}}
    41 
    42 Does not even give me a password prompt.
    43 
    44 ----
    45 
    46 From your log output:
    47 
    48 {{{
    49 makeRootWindowModels()=[GTKX11RootWindowModel(0x29f - (0, 30, 1680, 1050)), GTKX11RootWindowModel(0x29f - (1680, 0, 1920, 1080)), GTKX11RootWindowModel(0x29f - (3600, 0, 1920, 1080))]
    50 }}}
    51 
    52 So the 3 monitors are detected just fine. The client should show them as 3 separate windows.
    53 Note: if you started your server with "`xpra shadow`", you should "`xpra attach`" from the client - no need to ask it to start a new shadow.
    54 ----
    55 I mistakenly attached from local computer. Suprisingly, it worked correctly. (on the attached log)
    56 No combination of
    57 
    58 {{{
    59 attach ssh://user@SERVERIP
    60 attach ssh://user@SERVERIP//THESERVERDISPLAY
    61 }}}
    62 
    63 worked (on the attached log)
    64 
    65 ----
    66 Failures to attach are unrelated to this ticket, so please file a separate ticket for that. Looking at your log, I've already found:
    67 * a minor harmless bug, fixed in r19020
    68 * `Warning: more than 30 clipboard requests per second!` - you have a clipboard loop, you should disable the clipboard if it doesn't get disabled automatically
    69 *this warning is usually a sign that things are very bad indeed, could be related to the clipboard:
    70 
    71 {{{
    72 Warning: delayed region timeout
    73 region is 15 seconds old, will retry - bad connection?
    74 }}}
    75