#485 closed defect (fixed)
xpra upgrade issues: signal problems, sockets not responding
| Reported by: | Antoine Martin | Owned by: | Antoine Martin |
|---|---|---|---|
| Priority: | blocker | Milestone: | 0.11 |
| Component: | server | Version: | |
| Keywords: | Cc: |
Description (last modified by )
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!
Change History (4)
comment:1 Changed 7 years ago by
| Description: | modified (diff) |
|---|---|
| Owner: | changed from Antoine Martin to Antoine Martin |
| Status: | new → assigned |
comment:2 Changed 7 years ago by
comment:3 Changed 7 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
r5115 fixes this and will need to be backported
comment:4 Changed 3 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/485
Note: See
TracTickets for help on using
tickets.
copyleft 2010 - 2021
here comes the bisection:
So r4790 is bad, a seemingly innocuous change (see #420)... sigh.