[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

replacing plasma notifications by another notification daemon



Hi!

I would like to use "cleanly" another notification daemon in my KDE
environment (dunst to be precise, because I like the small size of its
boxes and the possibility to replay notifications).

However, I haven't found any clean way to do that yet. dunst is started
early in my X session, but as I understand from the code in 
plasma-workspace
https://sources.debian.net/src/plasma-workspace/4:5.6.4-2/dataengines/notifications/notificationsengine.cpp/?hl=91#L43
any existing notification daemon is killed and replaced by the plasma
one.

Is there a way to tell KDE to not deal with nofications at all and let
another program do it? I haven't found any, and for the moment, the only
solution I found is to comment (most of) the source code in the
NotificationsEngine constructor and NotificationsEngine::registerDBusService()
in that file and rebuild the package.
Is there a hidden option I missed, or a magic dbus invocation command I
could use?

I take the opportunity to thank a lot the KDE team for their wonderful
work, and for making me happy to use my computer.

Cheers,

Cédric

P.S. : note that it worked most of the time with one of my machines
without manual intervention, but it was maybe a bug :)

Attachment: signature.asc
Description: PGP signature


Reply to: