I verified the fix on resolute (amd64, MATE session) with mate-
notification-daemon 1.26.1-1ubuntu0.26.04.1 from resolute-proposed.
Before the test, the system had a local build with the same patch; I
replaced it with the -proposed binaries (mate-notification-daemon and
mate-notification-daemon-common, checksums matched the signed resolute-
proposed index).
Test plan results:
1. CloseNotification 0 returned "0 is not a valid notification ID".
GetServerInformation then returned ('Notification Daemon', 'MATE',
'1.26.1', '1.1') from the same daemon process. journalctl -k showed no
segfault.
2. 22 x notify-send -t 30000: the daemon process stayed the same; the
calls over the limit got "Exceeded maximum number of notifications". The
journal showed no "g_object_unref: assertion 'G_IS_OBJECT (object)'
failed" message.
3. notify-send "hello" displayed a notification, and it closed on expiry
(NotificationClosed reason 1).
For comparison: the unpatched 1.26.1-1build6 binary crashed on step 1 in
3 of 3 runs when I tested it on 2026-09-27.
** Tags removed: verification-needed-resolute
** Tags added: verification-done-resolute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2165836
Title:
mate-notification-daemon segfaults in libgobject at session start
(glib 2.88 regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/2165836/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
