Talk:Desktop notifications

From ArchWiki
Revision as of 23:34, 1 January 2018 by Grawity (talk | contribs) (Clarification on setting up standalone environment)
Jump to navigation Jump to search

Clarification on setting up standalone environment

I just went through this for the first time and found this bit confusing:

""" In other desktop environments, the notification server needs to be launched using your WM's/DE's "autostart" option.

It can also be launched on the first call via D-Bus, adding the following configuration to its services directory /usr/share/dbus-1/services respectively $XDG_DATA_HOME/dbus-1/services, e.g.

[D-BUS Service]


I expected /usr/lib/notification-daemon-1.0 to exist, but it didn't. I also didn't see any systemd units containing "notif." In the end, I was able to install dusnt and things just worked when issuing notify-sent "test", which would indicate that that section might be either/or? If so, that would be awesome to clarify. Maybe dbus setup is one way, *or* you can install one of the other packages. Since dunst mentions it takes dbus notifications, I assumed I needed to do something to get it to work. To my knowledge, I haven't. If there is such a step, perhaps that check could be cited as well (e.g. "To ensure things are setup properly, issue this command and check for this output."). There's surprisingly little out there about notifications and openbox, so it would be great for this to be a comprehensive source for others! Jwhendy (talk) 23:23, 1 January 2018 (UTC)

D-Bus .service files are not systemd units. (Secondly, in both DBus and systemd, user services are fully separate from system services.) grawity (talk) 23:34, 1 January 2018 (UTC)