Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
totaam opened this issue Jan 15, 2014 · 8 comments
Closed

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

totaam opened this issue Jan 15, 2014 · 8 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Jan 15, 2014

Issue migrated from trac ticket # 497

component: client | priority: major | resolution: fixed

2014-01-15 14:29:14: drag0on created the issue


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?

@totaam
Copy link
Collaborator Author

totaam commented Jan 15, 2014

2014-01-15 15:10:15: totaam changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented Jan 15, 2014

2014-01-15 15:10:15: totaam changed owner from antoine to totaam

@totaam
Copy link
Collaborator Author

totaam commented Jan 15, 2014

2014-01-15 15:10:15: totaam commented


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.

@totaam
Copy link
Collaborator Author

totaam commented Jan 15, 2014

2014-01-15 15:25:49: totaam commented


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-3326 good
  • 0.9.8-4003 good
  • 0.10.0-3326 (beta) good
  • 0.10.0-r3961 (beta) good (with log file error on exit though)
  • 0.10.1-r4191 good
  • 0.10.4-4315 good
  • 0.10.9-4669 good
  • 0.10.10-5001 bad
  • 0.10.10-4905 bad
  • 0.10.10-4827 bad

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

@totaam
Copy link
Collaborator Author

totaam commented Jan 15, 2014

2014-01-15 16:26:41: totaam changed status from assigned to closed

@totaam
Copy link
Collaborator Author

totaam commented Jan 15, 2014

2014-01-15 16:26:41: totaam changed resolution from ** to fixed

@totaam
Copy link
Collaborator Author

totaam commented Jan 15, 2014

2014-01-15 16:26:41: totaam commented


Bisecting:

This is yet another bug caused by FreeBSD compatibility (see #420).
The fix is in r5196 for trunk and 5199 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-5199.exe]

Closing - let me know if you still have problems.

@totaam totaam closed this as completed Jan 15, 2014
@totaam
Copy link
Collaborator Author

totaam commented Jan 16, 2014

2014-01-16 21:36:25: drag0on commented


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-5199.exe) is also working fine, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant