My initial conclusion about go-udev being the culprit was premature, the
socket closing & quit channel code looks fine after all, the problem
lies somewhere else and may be something in the go runtime stack and
it's very unclear for the time being.
** Changed in: snapd (Ubuntu)
Importance: Critical => Undecided
** Changed in: snapd
Importance: Critical => Undecided
** Changed in: snapd (Ubuntu)
Status: In Progress => Confirmed
** Changed in: snapd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824162
Title:
/usr/lib/snapd/snapd:11:runtime:runtime:runtime:runtime:runtime
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1824162/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
