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 upgrade issues: signal problems, sockets not responding #485

Closed
totaam opened this issue Jan 4, 2014 · 7 comments
Closed

xpra upgrade issues: signal problems, sockets not responding #485

totaam opened this issue Jan 4, 2014 · 7 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Jan 4, 2014

Issue migrated from trac ticket # 485

component: server | priority: blocker | resolution: fixed

2014-01-04 11:00:55: totaam created the issue


Start a server as usual:

xpra start --bind-tcp=0.0.0.0:10000 :10 --no-daemon

Then upgrade it from another terminal:

xpra upgrade --bind-tcp=0.0.0.0:10001 :10 --no-daemon

The upgrade happens, but the new server does not respond to ^C and its sockets are unreachable!

@totaam
Copy link
Collaborator Author

totaam commented Jan 4, 2014

2014-01-04 11:01:44: totaam changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented Jan 4, 2014

2014-01-04 11:01:44: totaam changed owner from antoine to totaam

@totaam
Copy link
Collaborator Author

totaam commented Jan 4, 2014

2014-01-04 11:01:44: totaam edited the issue description

@totaam
Copy link
Collaborator Author

totaam commented Jan 4, 2014

2014-01-04 12:12:14: totaam commented


here comes the bisection:

So r4790 is bad, a seemingly innocuous change (see #420)... sigh.

@totaam
Copy link
Collaborator Author

totaam commented Jan 4, 2014

2014-01-04 14:07:40: totaam changed status from assigned to closed

@totaam
Copy link
Collaborator Author

totaam commented Jan 4, 2014

2014-01-04 14:07:40: totaam changed resolution from ** to fixed

@totaam
Copy link
Collaborator Author

totaam commented Jan 4, 2014

2014-01-04 14:07:40: totaam commented


r5115 fixes this and will need to be backported

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