https://bugs.kde.org/show_bug.cgi?id=364361
Bug ID: 364361
Summary: impossible to replace plasma notifications by another
notification daemon
Product: frameworks-knotifications
Version: unspecified
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mklape...@kde.org
Reporter: cedric.boutill...@gmail.com
CC: kdelibs-b...@kde.org
I use an up to date Debian unstable, which has plasma-workspace 5.6.4.
I would like in my KDE environment to have notifications displayed by the
notification daemon 'dunst' http://www.knopwob.org/dunst/
Disabling notifications from the systray is not enough to stop KDE notification
daemon, Notifications are not displayed any more, but seem still caught by the
KDE notification daemon.
Trying to run dunst from the command line gives then:
$dunst
Name Lost. Is Another notification daemon running?
I try to run dunst early, but when the desktop opens, there is no 'dunst'
process anymore.
I have a similar output when I try to use notify-osd:
$ /usr/lib/x86_64-linux-gnu/notify-osd
** (notify-osd:2893): WARNING **: Another instance has already registered
org.freedesktop.Notifications
** (notify-osd:2893): WARNING **: Could not register instance
For the moment, the only way I found to make work another notification daemon
is to comment out (most of) the source code in the
NotificationsEngine constructor and NotificationsEngine::registerDBusService()
in the file dataengines/notifications/notificationsengine.cpp of
plasma-workspace and rebuild the package.
Reproducible: Always
Actual Results:
either notifications are displayed as plasma popups, or not displayed at all.
Expected Results:
I would like an option to disable completely KDE notification daemon (and
unregister it from dbus).
Maybe there is a dbus magic invokation to do that? An option in the
notification dialog from systray would be great.
--
You are receiving this mail because:
You are watching all bug changes.
