Package: dunst
Version: 1.5.0-1
Severity: normal
Hi,
I have experienced the following minor problem for a long time:
Every time after booting up my system (Debian Testing with i3 as desktop)
dunst.service is resolved to failed state:
$ systemctl --user status dunst.service
● dunst.service - Dunst notification daemon
Loaded: loaded (/usr/lib/systemd/user/dunst.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-04-05 11:52:53 EEST;
1min 31s ago
Docs: man:dunst(1)
Process: 1534 ExecStart=/usr/bin/dunst (code=exited, status=1/FAILURE)
Main PID: 1534 (code=exited, status=1/FAILURE)
CPU: 28ms
Apr 05 11:52:53 hecate systemd[1514]: Starting Dunst notification daemon...
Apr 05 11:52:53 hecate dunst[1534]: CRITICAL: Cannot open X11 display.
Apr 05 11:52:53 hecate systemd[1514]: dunst.service: Main process exited,
code=exited, status=1/FAILURE
Apr 05 11:52:53 hecate systemd[1514]: dunst.service: Failed with result
'exit-code'.
Apr 05 11:52:53 hecate systemd[1514]: Failed to start Dunst notification daemon.
Upon issuing a notification (the notification is shown in the desktop correctly)
dunst.service is again resolved active:
$ notify-send "foobar"
$ systemctl --user status dunst.service
● dunst.service - Dunst notification daemon
Loaded: loaded (/usr/lib/systemd/user/dunst.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2021-04-05 11:59:37 EEST; 2s ago
Docs: man:dunst(1)
Main PID: 6750 (dunst)
Tasks: 4 (limit: 18703)
Memory: 4.4M
CPU: 32ms
CGroup:
/user.slice/user-1000.slice/user@1000.service/app.slice/dunst.service
└─6750 /usr/bin/dunst
Apr 05 11:59:37 hecate systemd[1514]: Starting Dunst notification daemon...
Apr 05 11:59:37 hecate dunst[6750]: WARNING: Unknown keyboard shortcut:
'ctrl+grave'
Apr 05 11:59:37 hecate systemd[1514]: Started Dunst notification daemon.
Apr 05 11:59:37 hecate dunst[6750]: WARNING: No icon found in path:
'dialog-information'
I expected the service to be active after boot.
My dunst.service:
$ systemctl --user cat dunst.service
# /usr/lib/systemd/user/dunst.service
[Unit]
Description=Dunst notification daemon
Documentation=man:dunst(1)
PartOf=graphical-session.target
[Service]
Type=dbus
BusName=org.freedesktop.Notifications
ExecStart=/usr/bin/dunst
For completeness, this bug was reported upstream (by myself):
https://github.com/dunst-project/dunst/issues/314#issuecomment-601228703
I file it here as the problem has not been solved and is pointed to be
elsewhere.
Quote Github user smcv:
> [...] The service was enabled system-wide by the Debian packaging,
> because at the time it was installed, it had WantedBy=default.target
> (which I think is a bug - it shouldn't be started before the GUI,
> and in any case shouldn't be started for users of other Notifications
> implementations, like GNOME Shell) [...]
-Manuel
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dunst depends on:
ii dbus-user-session [default-dbus-session-bus] 1.12.20-2
ii libc6 2.31-10
ii libcairo2 1.16.0-5
ii libgdk-pixbuf2.0-0 2.40.2-2
ii libglib2.0-0 2.66.8-1
ii libnotify4 0.7.9-3
ii libpango-1.0-0 1.46.2-3
ii libpangocairo-1.0-0 1.46.2-3
ii libx11-6 2:1.7.0-2
ii libxext6 2:1.3.3-1.1
ii libxinerama1 2:1.1.4-2
ii libxrandr2 2:1.5.1-1
ii libxss1 1:1.2.3-1
Versions of packages dunst recommends:
ii sensible-utils 0.0.14
dunst suggests no packages.
-- no debconf information
