NoExtract /usr/bin/dunst (and the service files) will prevent that and you can still have dunstify, whether that's perfectly compatible w/ other notification daemons is a different matter.
]]>any reason why my notifications were using dunst? I installed it to try dunstify, and running it manually never gave me the notifications I was experiencing recently. they all looked like Plasma-themed notify-send in the past.
edit: here is what you asked for
qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications
996
cat /proc/$(qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications)/cmdline
/usr/bin/plasmashell%
qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications cat /proc/$(qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications)/cmdline
The issue has returned after the latest upgrade to 5.27.3.
qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications
1231
cat /proc/$(qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications)/cmdline
/usr/bin/dunst%
The difference this time is previously, this bug was only in my notify-send cron notifications. Now, it is all native plasma notifications that are affected.
Edit: uninstalling dunst does not correct this.
]]>qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications
cat /proc/$(qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.freedesktop.Notifications)/cmdline
]]>After upgrading to 5.27.2, the notifications appear at the top right of the screen and have no theming. Instead, they have a very basic (almost ncurses) looking blue block with white text inside.
Has anyone else experienced or can replicate this?
Since the upgrade, I've had to make a different tweak to my i3 config. Is this a Plasma issue or do I need something new in my i3 config? Here are the relevant Plasma lines:
# Plasma compatibility improvements
for_window [window_role="pop-up"] floating enable
for_window [window_role="task_dialog"] floating enable
for_window [class="yakuake"] floating enable
for_window [class="systemsettings"] fullscreen enable
for_window [class="plasmashell"] floating enable
for_window [class="Plasma"] floating enable; border none
for_window [title="plasma-desktop"] floating enable; border none
#for_window [title="win7"] floating enable; border none
for_window [class="krunner"] floating enable; border none
for_window [class="Kmix"] floating enable; border none
for_window [class="Klipper"] floating enable; border none
for_window [class="Plasmoidviewer"] floating enable; border none
for_window [class="(?i)*nextcloud*"] floating disable
for_window [class="plasmashell" window_type="notification"] border none; move postiion 1450px 20px
#for_window [class="plasmashell" window_type="notification"] border none; move right 700px; move down 450px
no_focus [class="plasmashell" window_type="notification"]
for_window [title="Desktop — Plasma"] kill; floating enable; border none
for_window [title="Save File — KDialog"] floating disable
for_window [class="kinfocenter"] floating enable
for_window [instance="_scratchpad"] floating enable
for_window [window_type="menu"] floating enable
for_window [window_type="dialog"] floating enable
for_window [window_role="Preferences"] floating enable
for_window [window_role="About"] floating enable
for_window [window_role="bubble"] floating enable
for_window [class="plasmashell" window_type="applet"] move up 30 px
# Kill KDE desktop windows opened from version 5.27.2
for_window [title="Desktop @ QRect"] kill; floating enable; border none