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 1 of Ticket #1892


Ignore:
Timestamp:
06/30/18 08:00:21 (3 years ago)
Author:
Antoine Martin
Comment:

In my case, this is plink from TortoiseSVN which is broken for normal usage (it returns immideately after calling).

That's odd, because the plink.exe we ship comes from tortoisesvn! (they patch it with a GUI, which the upstream plink lacks)

Please try the latest beta builds I have uploaded:

  • r19779: missing env settings - probably not essential since this had been broken for a while, maybe this could even be removed
  • r19780: make sure our installation path comes first, so the shell should be finding our copy of plink.exe ahead of any other found on the %PATH%

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1892

    • Property Owner changed from Antoine Martin to Lukas Haase
    • Property Milestone changed from to 2.4
  • Ticket #1892 – Description

    initial v1  
    1 This bug report is based on the findings from https://xpra.org/trac/ticket/1853.
     1This bug report is based on the findings from  #1853.
    22
    33Previously, xpra in Windows used plink.exe that is shipped with Xpra and is in the same directory as Xpra_cmd.exe.
    44
    5 With the newest version (in my case 2.3.2, Rev 19729), it seems that this is not the case and the plink.exe is used that is found in the path.
     5With the newest version (in my case 2.3.2-r19729), it seems that this is not the case and the plink.exe is used that is found in the path.
    66
    7 In my case, this is plink from TortoiseSVN which is broken for normal usage (it returns immideately after calling).
     7In my case, this is plink from TortoiseSVN which is broken for normal usage (it returns immidiately after calling).
    88
    9 This is strange behavior because it even appears when I call Xpra_cmd.exe from wihin the same directory (c:\Program Files\Xpra).
     9This is strange behavior because it even appears when I call Xpra_cmd.exe from within the same directory (c:\Program Files\Xpra).
    1010
    11 When I use xpra files, I can circumvent this bug by explicitely setting the path:
    12 
     11When I use xpra files, I can circumvent this bug by explicitly setting the path:
    1312
    1413{{{
     
    1817However, when I use the GUI, after some time I get the error:
    1918
    20 "TortoisePlink Fatal Error: Network error: Connection timed out" - again hinting that the wrong plink.exe is being used.
     19{{{
     20TortoisePlink Fatal Error: Network error: Connection timed out
     21}}}
     22again hinting that the wrong plink.exe is being used.
    2123
    22 Another important remark: Xpra is started from the start menu link which has "C:\Program Files\Xpra" set as "Start in".
    23 
     24Another important remark: Xpra is started from the start menu link which has {{{C:\Program Files\Xpra}}} set as "Start in".