This basically means that code that would have created an abstract namespace socket in glib 2.74.x now creates a regular unix domain socket in 2.75.x. We have AppArmor rules in snapd's desktop-legacy interface granting access to the abstract namespace socket in $XDG_CACHE_HOME, but nothing for the equivalent regular socket:
I still need to verify this is the actual cause, but if so it should be relatively simple to update snapd's AppArmor rules to allow access to this socket.
This seems like the most likely culprit:
https:/ /gitlab. gnome.org/ GNOME/glib/ -/merge_ requests/ 3005
This basically means that code that would have created an abstract namespace socket in glib 2.74.x now creates a regular unix domain socket in 2.75.x. We have AppArmor rules in snapd's desktop-legacy interface granting access to the abstract namespace socket in $XDG_CACHE_HOME, but nothing for the equivalent regular socket:
https:/ /github. com/snapcore/ snapd/blob/ d5f47ca71fcd8a8 84072e75391a7e5 5d9ec9d145/ interfaces/ builtin/ desktop_ legacy. go#L142- L149
I still need to verify this is the actual cause, but if so it should be relatively simple to update snapd's AppArmor rules to allow access to this socket.