Bug#981544: mate-notification-daemon hardcodes mate-screensaver

["Andrej Shadura" <andrew@shadura.me>]

On Mon, 1 Feb 2021, at 09:37, Andrej Shadura wrote:
> I’m trying to use mate-notification-daemon without mate-screensaver, and
> it doesn’t work. If I keep mate-screensaver installed but not running,
> it starts on its own from time to time — turns out it’s mate-notification-daemon
> which prods it. Apparently, mate-notification-daemon checks whether a
> screensaver is running before showing a notification, and it hardcodes
> the mate-screensaver’s D-Bus interface org.mate.ScreenSaver instead of
> using some other cross-DE method.

I’d also like to add that failing to talk to mate-screensaver, it ends up not showing a notification at all, making itself unusable for its primary purpose.

The hard dependency on mate-screensaver is also not declared in the dependencies.

-- 
Cheers,
  Andrej