<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet href="/rss.xsl" type="text/xsl" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dunst | Bacardi55&#39;s Web Cave</title>
    <link>https://bacardi55.io/tags/dunst/</link>
    <description>Recent content in Dunst on Bacardi55&#39;s Web Cave</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>bac@rdi55.pl (bacardi55)</managingEditor>
    <webMaster>bac@rdi55.pl (bacardi55)</webMaster>
    <copyright>2010-2025 bacardi55</copyright>
    <lastBuildDate>Fri, 21 Mar 2025 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://bacardi55.io/tags/dunst/index.xml" rel="self" type="application/rss+xml" />
    <item>
      
      <title>Fix desktop notifications conflict between kde plasma and dunst</title><link>https://bacardi55.io/2025/03/21/fix-desktop-notifications-conflict-between-kde-plasma-and-dunst/</link><pubDate>Fri, 21 Mar 2025 00:00:00 +0100</pubDate><author>bac@rdi55.pl (bacardi55)</author><guid>https://bacardi55.io/2025/03/21/fix-desktop-notifications-conflict-between-kde-plasma-and-dunst/</guid><description>&lt;p&gt;Today, a short blog post mostly for myself so that I can remember in the future if that issue happen again.&lt;/p&gt;&#xA;&lt;h2 id=&#34;context&#34;&gt;Context&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;m currently using &lt;a href=&#34;https://endeavouros.com/&#34;&gt;Endeavour OS&lt;/a&gt; with &lt;a href=&#34;https://i3wm.org/&#34;&gt;i3wm&lt;/a&gt; as my window manager. I say &amp;ldquo;currently&amp;rdquo;, but I have been using i3wm for more years than I can remember. On my desktop computer, even though I never use it, &lt;a href=&#34;https://kde.org/plasma-desktop/&#34;&gt;KDE Plasma Desktop&lt;/a&gt; is also installed. Main reason being that I installed it for potentially allow someone else to use this computer with a more &amp;ldquo;traditional&amp;rdquo;  (understand: usable with a mouse) complete desktop environment. I thought it would maybe be useful a few time, even though it didn&amp;rsquo;t happen yet.&lt;/p&gt;&#xA;&lt;p&gt;What I didn&amp;rsquo;t know is that it may cause issue between kde built-in notification system and &lt;a href=&#34;https://github.com/dunst-project/dunst&#34;&gt;dunst&lt;/a&gt;. Dunst is a standalone notification daemon, very useful when you use a window manager and not a desktop environment (DE). Most DE have their own implementation of a notification deamon. Kde plasma, Gnome, Cinnamon and others all do. So the solution should also apply in case of conflict with others.&lt;/p&gt;&#xA;&lt;h2 id=&#34;symptoms-and-debugging&#34;&gt;Symptoms and debugging&lt;/h2&gt;&#xA;&lt;p&gt;Symptoms are easily found: when a notification is due to happen, the application that sent the notification will freeze for one minute.&lt;/p&gt;&#xA;&lt;p&gt;An easy to confirm if the freeze is due to that particular problem is to send a test notification, eg:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;notify-send &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;Test notification&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If it the prompt just stall and fail after a minute, you may check if you don&amp;rsquo;t have multiple desktop notification program.&lt;/p&gt;&#xA;&lt;p&gt;You can run this command to find out:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;find /usr/share/dbus-1/services/ -name &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#39;*Notif*&amp;#39;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Which returned:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code class=&#34;language-nil&#34; data-lang=&#34;nil&#34;&gt;/usr/share/dbus-1/services/org.kde.plasma.Notifications.service&#xA;/usr/share/dbus-1/services/org.x.StatusNotifierWatcher.service&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;And here we find the culprit!&lt;/p&gt;&#xA;&lt;h2 id=&#34;solution&#34;&gt;Solution&lt;/h2&gt;&#xA;&lt;p&gt;To fix this, as explained in the &lt;a href=&#34;https://wiki.archlinux.org/title/Desktop_notifications#Multiple_notification_servers_with_D-Bus_services&#34;&gt;Archlinux documentation&lt;/a&gt;, we need to override the service used and point to the service we want.&lt;/p&gt;&#xA;&lt;p&gt;To do so, we need to create the file:&#xA;&lt;code&gt;~/.local/share/dbus-1/services/org.freedesktop.Notifications.service&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;With the following content&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code class=&#34;language-nil&#34; data-lang=&#34;nil&#34;&gt;[D-BUS Service]&#xA;Name=org.freedesktop.Notifications&#xA;Exec=/usr/bin/dunst&#xA;SystemdService=dunst.service&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Of course, adapt if you are using another standalone tool than Dunst.&lt;/p&gt;&#xA;&lt;p&gt;The session has to be restarted to make it work, so exit and login again and it should be fixed (and we can test using &lt;code&gt;notify-send&lt;/code&gt; again).&lt;/p&gt;&#xA;&lt;h2 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h2&gt;&#xA;&lt;p&gt;Was a tad annoying as at first I found a workaround that involved modifying the &lt;code&gt;org.kde.plasma.Notifications.service&lt;/code&gt; at each reboot (granted it does not happen that often, but still). So very happy to have finally fixed it correctly :-).&lt;/p&gt;&#xA;</description></item>
  </channel>
</rss>
