This can be reproduced by:
1. Attempting a login, e.g. using Python:
$ python
>>> from gi.repository import Snapd
>>> Snapd.login_sync ("", "", "")
2. Entering your password in the PolicyKit dialog
3. Killing snapd, i.e:
$ sudo killall snapdStep 1 causes snapd-login-service to start, 2 to make a connection to snapd and 3 to cause the socket to be closed. Because snapd-glib wasn't correctly disabling the socket callback it would be called on a destroyed object. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646784 Title: /usr/lib/snapd-glib/snapd-login- service:11:read_data:read_from_snapd:read_cb:socket_source_dispatch:g_main_dispatch To manage notifications about this bug go to: https://bugs.launchpad.net/snapd-glib/+bug/1646784/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
