/usr/lib/snapd-glib/snapd-login-service:11:read_data:read_from_snapd:read_cb:socket_source_dispatch:g_main_dispatch
Bug #1646784 reported by
errors.ubuntu.com bug bridge
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd-glib |
Fix Released
|
Medium
|
Unassigned | ||
snapd-glib (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Yakkety |
Triaged
|
Medium
|
Unassigned |
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding snapd-glib. This problem was most recently seen with package version 1.3-0ubuntu1, the problem page at https:/
If you do not have access to the Ubuntu Error Tracker you can request it at http://
Changed in snapd-glib (Ubuntu): | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
Changed in snapd-glib: | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
Changed in snapd-glib: | |
milestone: | none → 1.4 |
status: | Fix Committed → Fix Released |
Changed in snapd-glib (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in snapd-glib (Ubuntu Yakkety): | |
importance: | Undecided → Medium |
Changed in snapd-glib (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in snapd-glib (Ubuntu Yakkety): | |
status: | New → Triaged |
Changed in snapd-glib (Ubuntu): | |
assignee: | nobody → Giovanni (aresclaw) |
assignee: | Giovanni (aresclaw) → nobody |
Changed in snapd-glib (Ubuntu Xenial): | |
status: | Incomplete → Fix Released |
Changed in snapd-glib (Ubuntu Xenial): | |
status: | Fix Released → Triaged |
Changed in snapd-glib (Ubuntu Yakkety): | |
status: | Incomplete → Triaged |
To post a comment you must log in.
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 snapd
Step 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.