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

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!

Sat, 04 Jan 2014 11:01:43 GMT - Antoine Martin: owner, status, description changed

owner changed from Antoine Martin to Antoine Martin
status changed from new to assigned
description modified (diff)

Sat, 04 Jan 2014 12:12:13 GMT - Antoine Martin:

here comes the bisection:

r3143 good
r3900 good
r4300 good
r4700 good
r5000 bad
r4850 bad
r4775 good
r4812 bad
r4783 good
r4798 bad
r4790 bad
r4787 good
r4789 good

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

Sat, 04 Jan 2014 14:07:39 GMT - Antoine Martin: status changed; resolution set

status changed from assigned to closed
resolution set to fixed

r5115 fixes this and will need to be backported

Sat, 23 Jan 2021 04:57:01 GMT - migration script:

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