The crashes that failed to retrace all seem to have the following stacktrace:
?? ()
g_io_channel_shutdown () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Which suggests they are a bug in PackageKit. A quick look at the PackageKit source shows this is done in a callback that may still be running after an object has been unreferenced. So I don't think they're related to the Snap changes.
The crash with the backtrace seems to be related to the network monitor changing state (network disconnected/connected?). So I don't think it's related to the Snap plugin.
The crashes that failed to retrace all seem to have the following stacktrace: shutdown () from /lib/x86_ 64-linux- gnu/libglib- 2.0.so. 0 x86_64- linux-gnu/ libpackagekit- glib2.so. 18 context_ dispatch () from /lib/x86_ 64-linux- gnu/libglib- 2.0.so. 0 64-linux- gnu/libglib- 2.0.so. 0
?? ()
g_io_channel_
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
Which suggests they are a bug in PackageKit. A quick look at the PackageKit source shows this is done in a callback that may still be running after an object has been unreferenced. So I don't think they're related to the Snap changes.
The crash with the backtrace seems to be related to the network monitor changing state (network disconnected/ connected? ). So I don't think it's related to the Snap plugin.