Package: dunst Version: 1.9.2-1 Severity: normal X-Debbugs-Cc: Daniel Kahn Gillmor <d...@fifthhorseman.net>
the dunst system --user service works well whenever i'm in a graphical
environment, but it produces a lot of noisy warnings, errors, and
complaints, especially when i log in from a tty instead of a graphical
display manager. It would be great if unimportant warnings and errors
were minimized so that i could focus
When i log in from a tty, systemd's user session manager tries to start
dunst, and dunst fails because there is no graphical environment
(it actually gives warnings and errors about a missing X11).
after i've started a graphical environment (Wayland, not X11), if some
tool sends a desktop notification, dunst will succeed in starting up.
But in the meantime, "systemctl --user status" will show that the
session is "degraded" because dunst failed to launch.
This "degraded" state masks when other user services have failed -- if i
just assume that my user session will always be degraded until i've
started a graphical environment and a desktop notification was sent,
then i won't notice if other user services are broken.
The logs created by dunst are pretty noisy too, even when it's working:
$ journalctl -b --user-unit dunst
Apr 05 14:26:09 alice systemd[2598]: Starting dunst.service - Dunst
notification daemon...
Apr 05 14:26:09 alice dunst[2615]: WARNING: Cannot open X11 display.
Apr 05 14:26:09 alice dunst[2615]: ERROR: [ get_x11_output:0065] Couldn't
initialize X11 output. Aborting...
Apr 05 14:26:09 alice systemd[2598]: dunst.service: Main process exited,
code=killed, status=5/TRAP
Apr 05 14:26:09 alice systemd[2598]: dunst.service: Failed with result 'signal'.
Apr 05 14:26:09 alice systemd[2598]: Failed to start dunst.service - Dunst
notification daemon.
Apr 05 14:32:13 alice systemd[2915]: Starting dunst.service - Dunst
notification daemon...
Apr 05 14:32:13 alice dunst[2934]: WARNING: Cannot open X11 display.
Apr 05 14:32:13 alice dunst[2934]: ERROR: [ get_x11_output:0065] Couldn't
initialize X11 output. Aborting...
Apr 05 14:32:13 alice systemd[2915]: dunst.service: Main process exited,
code=killed, status=5/TRAP
Apr 05 14:32:13 alice systemd[2915]: dunst.service: Failed with result 'signal'.
Apr 05 14:32:13 alice systemd[2915]: Failed to start dunst.service - Dunst
notification daemon.
Apr 05 15:13:49 alice systemd[2915]: Starting dunst.service - Dunst
notification daemon...
Apr 05 15:13:49 alice dunst[166154]: CRITICAL:
g_water_wayland_source_get_display: assertion 'self != NULL' failed
Apr 05 15:13:49 alice dunst[166154]: CRITICAL:
g_water_wayland_source_set_error_callback: assertion 'self != NULL' failed
Apr 05 15:13:49 alice dunst[166154]: WARNING: failed to create display
Apr 05 15:13:49 alice dunst[166154]: WARNING: Couldn't initialize wayland
output. Falling back to X11 output.
Apr 05 15:13:49 alice dunst[166154]: CRITICAL: g_water_wayland_source_free:
assertion 'self != NULL' failed
Apr 05 15:13:49 alice systemd[2915]: Started dunst.service - Dunst notification
daemon.
Apr 05 15:14:24 alice dunst[166154]: X connection to :0 broken (explicit kill
or server shutdown).
Apr 05 15:14:24 alice systemd[2915]: dunst.service: Main process exited,
code=exited, status=1/FAILURE
Apr 05 15:14:24 alice systemd[2915]: dunst.service: Failed with result
'exit-code'.
Apr 05 16:09:18 alice systemd[398192]: Starting dunst.service - Dunst
notification daemon...
Apr 05 16:09:18 alice dunst[398211]: WARNING: Cannot open X11 display.
Apr 05 16:09:18 alice dunst[398211]: ERROR: [ get_x11_output:0065] Couldn't
initialize X11 output. Aborting...
Apr 05 16:09:18 alice systemd[398192]: dunst.service: Main process exited,
code=killed, status=5/TRAP
Apr 05 16:09:18 alice systemd[398192]: dunst.service: Failed with result
'signal'.
Apr 05 16:09:18 alice systemd[398192]: Failed to start dunst.service - Dunst
notification daemon.
Apr 05 16:25:42 alice systemd[398192]: Starting dunst.service - Dunst
notification daemon...
Apr 05 16:25:42 alice systemd[398192]: Started dunst.service - Dunst
notification daemon.
Apr 05 16:26:00 alice dunst[399160]: CRITICAL: Source ID 16 was not found when
attempting to remove it
Apr 05 16:26:48 alice dunst[399160]: CRITICAL: Source ID 23 was not found when
attempting to remove it
$
It could be that the answer is "don't use dunst if you log in from the
tty and are bothered by spurious errors and warnings", but i quite like
dunst's minimalism otherwise, and would prefer to keep using it.
--dkg
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dunst depends on:
ii dbus-user-session [default-dbus-session-bus] 1.14.10-4
ii dbus-x11 [dbus-session-bus] 1.14.10-4
ii libc6 2.37-15
ii libcairo2 1.18.0-3
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b2
ii libglib2.0-0t64 [libglib2.0-0] 2.78.4-6
ii libnotify4 0.8.3-1
ii libpango-1.0-0 1.52.1+ds-1
ii libpangocairo-1.0-0 1.52.1+ds-1
ii libwayland-client0 1.22.0-2.1+b1
ii libwayland-cursor0 1.22.0-2.1+b1
ii libx11-6 2:1.8.7-1
ii libxext6 2:1.3.4-1+b1
ii libxinerama1 2:1.1.4-3
ii libxrandr2 2:1.5.4-1
ii libxss1 1:1.2.3-1
ii xdg-utils 1.1.3-4.1
dunst recommends no packages.
dunst suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
