According to the stack trace, this seems to happen when signond is quitting -- which it never does, unless it receives a TERM signal. So it looks like that this bug might occur when the session is terminating (and then reported on the next login).
So far I had no luck in reproducing it, but I'll keep trying.
According to the stack trace, this seems to happen when signond is quitting -- which it never does, unless it receives a TERM signal. So it looks like that this bug might occur when the session is terminating (and then reported on the next login).
So far I had no luck in reproducing it, but I'll keep trying.