I'm referred to the change happened here https://github.com/canonical/snapd/commit/95f1e3c414c3294d9c18fbd6f0331156e1eddc7a
I did not notice this until the problem raised on some app. ** Description changed: Recent updates of snapd use a more complex cgroup name (such as snap.firefox.firefox-24fad744-4555-4b48-846c-28d3a8ecbe9c.scope), however that breaks the libnotify (and portals) assumptions. Since we use this value to figure out the application full name, as at the time SNAP_INSTANCE_NAME was not exposed. This code: https://gitlab.gnome.org/GNOME/libnotify/-/blob/0.8.6/libnotify/notify.c?ref_type=tags#L223-306 Is working since 2022, and it's now used by many applications relying on libnotify, the new syntax breaks it, causing matching problems for applications (the app name is used by the shell to figure out what application sent the notification) While in libnotify we are switching to use the instance name, this change should be adjusted in snapd not to break old packaged applications. Using snap.firefox.firefox.24fad744-4555-4b48-846c-28d3a8ecbe9c.scope - (so a dot to divide the snap with UUID) would be enough to fix it. + (so a dot to separate the snap with UUID) would be enough to fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2125222 Title: cgroups name changes breaks the assumptions in libnotify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2125222/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
