Hi Nikos,
> So sadly it's either a race over which daemon gets the address first, or up
> to dbus to
> decide which daemon to start.
Indeed.
> from `~/.local/share/dbus-1/services` and neutralize it that way, but I'm not
Tried it, but didn't work :-(
> [1]
Sorry for the delay,
On 03/03, Norbert Preining wrote:
> Is there a way to claim that interface/service somehow? I am thinking of
> other cinnamon users (since I am one of the maintainers of Cinnamon in
> Debian), and how Cinnamon could stop dbus from starting another
> notification daemon, when
Hi Nikos,
sorry for the late reply, and thanks for the detailed explanations. I
just rebooted my system, and realized that dunst is back there ;-)
> The autostart part of dunst is managed by dbus, specifically the
> auto-activation
> feature. Unfortunately dbus is not as powerful of a service
Hello,
On 25/02, Norbert Preining wrote:
> How am I supposed to disable this program?
> And no, I do *not* want to remove it, nor mask the service, because
> other uses are using i3 and are using dunst here.
The autostart part of dunst is managed by dbus, specifically the auto-activation
Package: dunst
Version: 1.4.1-1
Severity: important
Hi,
I am running cinnamon, which uses its own notification daemon.
But when dunst is installed it suddenly takes over all notifications.
I tried to disable it, but it comes back again and again.
systemctl even reports it as disabled but
5 matches
Mail list logo
