I’ve just put out libnotify 0.4.4 and notification-daemon 0.3.7 releases. I highly advise that everybody upgrades, as several memory leaks, rendering glitches and other bugs have been fixed.
Along with these releases is some basic support for accessibility in the notifications and a nice, subtle transparent effect on the notifications when running on a system using a compositing manager. Don’t worry, it’s not bad at all, and it doesn’t make the notifications any harder to read. I’ve been running this for some time at this point 🙂 I would show a screenshot, but it’s probably best to see it on your own setup.
The downloads are available on the downloads page, and full release notes are below:
libnotify 0.4.4 changes
- Fixed a bug where a notification’s ID could be reset when a different notification was closed. Patch by jylefort. (Bug #94)
- Fixed a crash when the D-BUS proxy was not being freed on notify_uninit, which was problematic when used in a loadable module. (Bug #92)
- Fixed a crash when a signal handler for the notification’s closed signal caused the notification to be destroyed. (Bug #116)
- Fixed memory leaks when creating notifications. (Bug #112)
- Fixed potential memory leaks where the function passed to notify_notification_add_action to free the user data was not being called. (Bug #119)
notification-daemon 0.3.7 changes
- Fixed a compatibility issue with dbus-glib 0.72. Patch by Pawel Worach. (Bug #95)
- The background of the window in the standard theme is now just slightly transparent when compiled against GTK+ 2.10 and when using a composite manager. Patch by Matt Walton. (Ticket #110)
- Fix several rendering glitches with the borders in the standard theme.
- Fix a memory leak when removing a notification. Patch by Sven Wegener. (Bug #105).
- Added initial accessibility support with the standard theme engine.
- Clicking anywhere in a notification should now close the notification. This was happening only on the body text sometimes.