Xpra: Ticket #18: error in logging when ^C the client

 Exception in thread Thread-2 (most likely raised during interpreter shutdown):
 Traceback (most recent call last):
   File "/usr/lib/python2.6/threading.py", line 532, in __bootstrap_inner
   File "/usr/lib/python2.6/threading.py", line 484, in run
   File "v0.0.7.22-75-gb933db8/lib/python/xpra/protocol.py", line 144, in _read_thread_loop
   File "v0.0.7.22-75-gb933db8/lib/python/wimpiggy/log.py", line 43, in <lambda>
   File "v0.0.7.22-75-gb933db8/lib/python/wimpiggy/log.py", line 39, in log
   File "v0.0.7.22-75-gb933db8/lib/python/wimpiggy/log.py", line 30, in getLogger
   File "/usr/lib/python2.6/logging/__init__.py", line 1427, in getLogger
   File "/usr/lib/python2.6/logging/__init__.py", line 956, in getLogger
 <type 'exceptions.TypeError'>: 'NoneType' object is not callable

Fri, 23 Sep 2011 14:39:42 GMT - Antoine Martin: status, milestone changed

• status changed from new to accepted
• milestone changed from v0.8 to future

when the python interpreter shuts down, errors like this one can occur anywhere - it's not pretty but these are harmless and fixing this would be quite hard.

Tue, 29 Nov 2011 18:23:37 GMT - Antoine Martin: status changed; resolution set

• status changed from accepted to closed
• resolution set to fixed

r293 shuts down cleanly by catching the SIGINT signal and ensuring we close all files/threads properly

Mon, 20 Feb 2012 20:14:29 GMT - Antoine Martin: milestone changed; version set

• version set to 0.0.7.32
• milestone changed from future to 0.0.7.x

Sat, 23 Jan 2021 04:43:20 GMT - migration script:

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