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

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

Hi,

On Mon, 1 Feb 2021, at 15:51, Mike Gabriel wrote:
> On  Mo 01 Feb 2021 09:41:34 CET, Andrej Shadura wrote:
> > 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.

> we won't get this changed for bullseye, but long term... do you have a  
> patch to propose to upstream?

I wish I had, but unfortunately I do not :(

-- 
Cheers,
  Andrej