Xpra-Launcher not starting (Code 255), xpra_cmd.exe works.

[drag0on]

System:
Windows 8.1 no special configuration (ie Windows Firewall, Windows Defender and Drivers)
Lenovo Touch U430

I have nothing else to report as I tried to add the debugger but only got info that the process does exit with exit code 255.
This problem seems to be there on all versions I tested from ​https://www.xpra.org/dists/windows/

What is going on? What else should I do? Is there a debugging binary I can try to use?

[Antoine Martin]

Confirmed, you can help us by figuring out when this regression occurred, it certainly used to work before. This only affects Vista onwards, and is probably related to file write access somewhere.

[Antoine Martin]

Note to drag0on: you can't have tried that many versions, I went far back based on the assumption that you had:

• 0.9.1-r3326 good
• 0.9.8-r4003 good
• 0.10.0-r3326 (beta) good
• 0.10.0-r3961 (beta) good (with log file error on exit though)
• 0.10.1-r4191 good
• 0.10.4-r4315 good
• 0.10.9-r4669 good
• 0.10.10-r5001 bad
• 0.10.10-r4905 bad
• 0.10.10-r4827 bad

So the problem appeared between in the 0.10.x branch between r4669 and r4827 (not many changesets in that branch)

[Antoine Martin]

Bisecting:

• r4750 good
• r4790 good
• r4808 bad
• r4798 good
• r4799 bad

This is yet another bug caused by FreeBSD compatibility (see #420).
The fix is in r5196 for trunk and r5199 for v0.10.x branch.

I have rebuilt 0.10.12 with this patch on top and uploaded it:
​http://xpra.org/dists/windows/Xpra_Setup_0.10.12-r5199.exe

Closing - let me know if you still have problems.

[drag0on]

Wow I was pretty sure that I tried Xpra_Setup_0.10.0-r4168.exe as it is in my Downloads folder, but after trying again you are right and this version is working. The given installer (Xpra_Setup_0.10.12-r5199.exe) is also working fine, thank you

[migration script]

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