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.
** Changed in: online-accounts-signond
Importance: Undecided => High
** Changed in: online-accounts-signond
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040667
Title:
signond crashed with SIGABRT in __libc_message()
To manage notifications about this bug go to:
https://bugs.launchpad.net/online-accounts-signond/+bug/1040667/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs