Xpra: Ticket #1779: Traceback when running Xpra Stop

My client and server are Fedora 26 machines running trunk r18658.

Server is started normally with xpra start :13 --bind-tcp= --start-new-commands=yes --start-child=xterm --start-via-proxy=no --systemd-run=no --no-daemon. Attempting to stop the server with xpra stop both from inside the session's Xterm and in a separate terminal window SSHd into the server, it fails with this traceback:

error in hello packet
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/xpra/client/client_base.py", line 730, in _process_hello
    if not self.server_connection_established():
  File "/usr/lib64/python2.7/site-packages/xpra/client/gobject_client_base.py", line 158, in server_connection_established
    return CommandConnectClient.server_connection_established(self)
  File "/usr/lib64/python2.7/site-packages/xpra/client/gobject_client_base.py", line 141, in server_connection_established
  File "/usr/lib64/python2.7/site-packages/xpra/client/gobject_client_base.py", line 476, in do_command
    if not self.server_client_shutdown:
AttributeError: 'StopXpraClient' object has no attribute 'server_client_shutdown'
error processing hello packet from server: 'StopXpraClient' object has no attribute 'server_client_shutdown'

Assuming one started the server with --no-daemon then one could use a ctrl + c and that'll stop the server. Otherwise one has to manually kill the process.

Thu, 01 Mar 2018 18:12:44 GMT - Antoine Martin: status changed; resolution set

Caused by one of the huge refactorings from #1761, fixed in r18659.

Thu, 01 Mar 2018 18:19:02 GMT - J. Max Mena:

Unfortunately r18659 has a traceback when attempting to connect.

Thu, 01 Mar 2018 18:19:17 GMT - J. Max Mena:

Followed up in #1780

Sat, 23 Jan 2021 05:33:34 GMT - migration script:

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