On Sun, May 11, 2014 at 12:18:39AM +0200, Stefano Karapetsas wrote:
> >>Notification daemons arent running every time, they are just started
> >>by dbus when needed
> >...the problem is notification-daemon is not handling notifications
> >of mate-power-manager (only mate-notification-daemon is), and instead
> >a weird fallback happens.
> In this case the problem is notification-daemon, because it must be
> started by dbus when libnotify is used
You are right that this seems to be the case. I tried uninstalling
mate-notification-daemon again and starting notification-daemon manually
and it sort of works... But the theme doesn't fit Mate at all, so
I still hope mate-notification-daemon will be pulled in (and used in
preference to notification-daemon when Mate is running) by the
metapackages.
Note that I don't think notification-daemon works well outside of
GNOME3 - after showing a single notification, it crashed for me with:
(notification-daemon:8381): GLib-CRITICAL **: Source ID 15 was not
found when attempting to remove it
Trace/breakpoint trap
Of course this is a bug of notification-daemon but I'm not sure how
eager to fix it GNOME developers will be, so I don't know if we should
really depend on it as drop-in replacement for mate-notification-daemon.
Not sure what to do about this bug - close it and create another for
notification-daemon or move it to that package... I'm not too
experienced with the BTS so I'll appreciate if someone takes an action.
Petr "Pasky" Baudis
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
