This seems quite intrusive. So now we connect to the snapd unix socket.
Does this happen everytime a window is drawn? Or an app is launched (any
app, not just snaps)? Or once per login?
What if snapd is restarted in the backgroud (a snapd update, dep or
snap, happens), what effect will that have on the desktop? What if the
event that triggers a connection to this socket, or sending/reading data
to/from it, happens exactly when snapd is down?
Does this affect launching non-snap applications?
Does this fully make ubuntu desktop dependent on snapd being installed
and running, if that wasn't already the case?
As a side note, this patch (debian/patches/ubuntu/window-Use-snapd-
socket-to-get-the-application-ID.patch) is lacking DEP3 headers. There
is nothing in it, its name, or in d/changelog, tying it to this bug.
This doesn't block SRU review (just makes it a tiny bit harder to find
the patch amongst the 10 other patches included in the upload), but
would have blocked sponsoring.
** Changed in: mutter (Ubuntu Resolute)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2147501
Title:
Broken popup menus and clipboard interaction in multiple Snaps on
Ubuntu 26.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2147501/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
