How do I disable Dunst and go back to notify-osd?
up vote
1
down vote
favorite
I installed i3, which recommends dunst, but I'm not using i3 at the moment, and the dunst notifications don't really fit with Unity. I'd rather not uninstall dunst totally, since I might want to start using it at some point in the future; is there a way to switch back to notify-osd without uninstalling dunst?
notification dbus
asked Nov 12 at 20:10
Josh
5061419
add a comment |
up vote
1
down vote
favorite
I installed i3, which recommends dunst, but I'm not using i3 at the moment, and the dunst notifications don't really fit with Unity. I'd rather not uninstall dunst totally, since I might want to start using it at some point in the future; is there a way to switch back to notify-osd without uninstalling dunst?
notification dbus
asked Nov 12 at 20:10
Josh
5061419
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I installed i3, which recommends dunst, but I'm not using i3 at the moment, and the dunst notifications don't really fit with Unity. I'd rather not uninstall dunst totally, since I might want to start using it at some point in the future; is there a way to switch back to notify-osd without uninstalling dunst?
notification dbus
asked Nov 12 at 20:10
Josh
5061419
I installed i3, which recommends dunst, but I'm not using i3 at the moment, and the dunst notifications don't really fit with Unity. I'd rather not uninstall dunst totally, since I might want to start using it at some point in the future; is there a way to switch back to notify-osd without uninstalling dunst?
notification dbus
notification dbus
asked Nov 12 at 20:10
Josh
5061419
asked Nov 12 at 20:10
Josh
5061419
asked Nov 12 at 20:10
Josh
5061419
asked Nov 12 at 20:10
Josh
5061419
asked Nov 12 at 20:10
Josh
5061419
5061419
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
The notification daemon is started by dbus-daemon when a notification is sent. You can see the currently-active notification daemon (assuming there is one) by searching for the org.freedesktop.Notifications bus name on the session bus in D-Feet; you can also examine journalctl output to see what dbus-daemon thinks it's doing, and why (including e.g. which application sent a notification).
dbus-daemon looks at the service files in /usr/share/dbus-1/services/ to find the service to run for each bus name. The file org.freedesktop.Notifications.service is the file for notify-osd (on default Ubuntu 18.04), and dunst installs a new service at org.knopwob.dunst.service. Both files have a Name of org.freedesktop.Notifications, meaning that they're both capable of handling notifications.
Unfortunately, dbus-daemon isn't very clever when it comes to working out which service to start when there are multiple possible services for a given bus name. As of 2018, it just picks the first one it finds; there's been a feature request in Red Hat Bugzilla about this for almost a decade. The only real solutions appear to be:
- write your own service that picks whether to start notify-osd or dunst based on some factor (covered in this answer), or
- move or delete all but one of the conflicting service files.
Moving the conflicting service files is much easier in this case: just run sudo mv /usr/share/dbus-1/services/org.knopwob.dunst.service{,.disabled}. If you want to start using dunst again, it's easy enough to rename the file back to what it was originally.
answered Nov 12 at 20:10
Josh
5061419
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The notification daemon is started by dbus-daemon when a notification is sent. You can see the currently-active notification daemon (assuming there is one) by searching for the org.freedesktop.Notifications bus name on the session bus in D-Feet; you can also examine journalctl output to see what dbus-daemon thinks it's doing, and why (including e.g. which application sent a notification).
dbus-daemon looks at the service files in /usr/share/dbus-1/services/ to find the service to run for each bus name. The file org.freedesktop.Notifications.service is the file for notify-osd (on default Ubuntu 18.04), and dunst installs a new service at org.knopwob.dunst.service. Both files have a Name of org.freedesktop.Notifications, meaning that they're both capable of handling notifications.
Unfortunately, dbus-daemon isn't very clever when it comes to working out which service to start when there are multiple possible services for a given bus name. As of 2018, it just picks the first one it finds; there's been a feature request in Red Hat Bugzilla about this for almost a decade. The only real solutions appear to be:
- write your own service that picks whether to start notify-osd or dunst based on some factor (covered in this answer), or
- move or delete all but one of the conflicting service files.
Moving the conflicting service files is much easier in this case: just run sudo mv /usr/share/dbus-1/services/org.knopwob.dunst.service{,.disabled}. If you want to start using dunst again, it's easy enough to rename the file back to what it was originally.
answered Nov 12 at 20:10
Josh
5061419
add a comment |
up vote
1
down vote
The notification daemon is started by dbus-daemon when a notification is sent. You can see the currently-active notification daemon (assuming there is one) by searching for the org.freedesktop.Notifications bus name on the session bus in D-Feet; you can also examine journalctl output to see what dbus-daemon thinks it's doing, and why (including e.g. which application sent a notification).
dbus-daemon looks at the service files in /usr/share/dbus-1/services/ to find the service to run for each bus name. The file org.freedesktop.Notifications.service is the file for notify-osd (on default Ubuntu 18.04), and dunst installs a new service at org.knopwob.dunst.service. Both files have a Name of org.freedesktop.Notifications, meaning that they're both capable of handling notifications.
Unfortunately, dbus-daemon isn't very clever when it comes to working out which service to start when there are multiple possible services for a given bus name. As of 2018, it just picks the first one it finds; there's been a feature request in Red Hat Bugzilla about this for almost a decade. The only real solutions appear to be:
- write your own service that picks whether to start notify-osd or dunst based on some factor (covered in this answer), or
- move or delete all but one of the conflicting service files.
Moving the conflicting service files is much easier in this case: just run sudo mv /usr/share/dbus-1/services/org.knopwob.dunst.service{,.disabled}. If you want to start using dunst again, it's easy enough to rename the file back to what it was originally.
answered Nov 12 at 20:10
Josh
5061419
add a comment |
up vote
1
down vote
up vote
1
down vote
The notification daemon is started by dbus-daemon when a notification is sent. You can see the currently-active notification daemon (assuming there is one) by searching for the org.freedesktop.Notifications bus name on the session bus in D-Feet; you can also examine journalctl output to see what dbus-daemon thinks it's doing, and why (including e.g. which application sent a notification).
dbus-daemon looks at the service files in /usr/share/dbus-1/services/ to find the service to run for each bus name. The file org.freedesktop.Notifications.service is the file for notify-osd (on default Ubuntu 18.04), and dunst installs a new service at org.knopwob.dunst.service. Both files have a Name of org.freedesktop.Notifications, meaning that they're both capable of handling notifications.
Unfortunately, dbus-daemon isn't very clever when it comes to working out which service to start when there are multiple possible services for a given bus name. As of 2018, it just picks the first one it finds; there's been a feature request in Red Hat Bugzilla about this for almost a decade. The only real solutions appear to be:
- write your own service that picks whether to start notify-osd or dunst based on some factor (covered in this answer), or
- move or delete all but one of the conflicting service files.
Moving the conflicting service files is much easier in this case: just run sudo mv /usr/share/dbus-1/services/org.knopwob.dunst.service{,.disabled}. If you want to start using dunst again, it's easy enough to rename the file back to what it was originally.
answered Nov 12 at 20:10
Josh
5061419
The notification daemon is started by dbus-daemon when a notification is sent. You can see the currently-active notification daemon (assuming there is one) by searching for the org.freedesktop.Notifications bus name on the session bus in D-Feet; you can also examine journalctl output to see what dbus-daemon thinks it's doing, and why (including e.g. which application sent a notification).
dbus-daemon looks at the service files in /usr/share/dbus-1/services/ to find the service to run for each bus name. The file org.freedesktop.Notifications.service is the file for notify-osd (on default Ubuntu 18.04), and dunst installs a new service at org.knopwob.dunst.service. Both files have a Name of org.freedesktop.Notifications, meaning that they're both capable of handling notifications.
Unfortunately, dbus-daemon isn't very clever when it comes to working out which service to start when there are multiple possible services for a given bus name. As of 2018, it just picks the first one it finds; there's been a feature request in Red Hat Bugzilla about this for almost a decade. The only real solutions appear to be:
- write your own service that picks whether to start notify-osd or dunst based on some factor (covered in this answer), or
- move or delete all but one of the conflicting service files.
Moving the conflicting service files is much easier in this case: just run sudo mv /usr/share/dbus-1/services/org.knopwob.dunst.service{,.disabled}. If you want to start using dunst again, it's easy enough to rename the file back to what it was originally.
answered Nov 12 at 20:10
Josh
5061419
answered Nov 12 at 20:10
Josh
5061419
answered Nov 12 at 20:10
Josh
5061419
answered Nov 12 at 20:10
Josh
5061419
5061419
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1092323%2fhow-do-i-disable-dunst-and-go-back-to-notify-osd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
