xpra icon
Bug tracker and wiki

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


Opened 3 years ago

Last modified 4 months ago

#1892 closed defect

Xpra uses plink from path first instead from program directory — at Initial Version

Reported by: Lukas Haase Owned by: Antoine Martin
Priority: major Milestone: 2.4
Component: client Version: 2.3.x
Keywords: Cc:

Description

This bug report is based on the findings from https://xpra.org/trac/ticket/1853.

Previously, xpra in Windows used plink.exe that is shipped with Xpra and is in the same directory as Xpra_cmd.exe.

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.

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

This is strange behavior because it even appears when I call Xpra_cmd.exe from wihin the same directory (c:\Program Files\Xpra).

When I use xpra files, I can circumvent this bug by explicitely setting the path:

ssh=c:\\Program Files\\Xpra\\plink.exe -noagent -T

However, when I use the GUI, after some time I get the error:

"TortoisePlink? Fatal Error: Network error: Connection timed out" - again hinting that the wrong plink.exe is being used.

Another important remark: Xpra is started from the start menu link which has "C:\Program Files\Xpra" set as "Start in".

Change History (0)

Note: See TracTickets for help on using tickets.