Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#986405: dunst: After system boot, dunst.service is resolved to failed state until first notification is issued

164 views
Skip to first unread message

manuel

unread,
Apr 5, 2021, 7:00:04 AM4/5/21
to
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/us...@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

Jose Lombera

unread,
Sep 26, 2022, 2:10:03 AM9/26/22
to
Any update on this? As of dunst 1.8.1-1 (Debian testing/bookworm) this
is still an issue. However, in my case, a coredump is also generated
when it fails due to a SIGTRAP.


$ systemctl --user status dunst.service
× dunst.service - Dunst notification daemon
Loaded: loaded (/usr/lib/systemd/user/dunst.service; enabled; preset: enabled)
Active: failed (Result: core-dump) since Mon 2022-09-26 05:38:17 UTC; 20min ago
Docs: man:dunst(1)
Process: 1296 ExecStart=/usr/bin/dunst (code=dumped, signal=TRAP)
Main PID: 1296 (code=dumped, signal=TRAP)
CPU: 22ms

Sep 26 05:38:17 debian dunst[1296]: Invalid MIT-MAGIC-COOKIE-1 key
Sep 26 05:38:17 debian dunst[1296]: WARNING: Cannot open X11 display.
Sep 26 05:38:17 debian dunst[1296]: ERROR: [ get_x11_output:0065] Couldn't initialize X11 output. Aborting...
Sep 26 05:38:17 debian systemd[1279]: Starting Dunst notification daemon...
Sep 26 05:38:17 debian systemd-coredump[1306]: Process 1296 (dunst) of user 1000 dumped core.

Module linux-vdso.so.1 with build-id c35c947b072ff69b395cd326b83b24630f2c5065
Module libmd.so.0 with build-id bfcdab3e6fabdc0d6f3e3e7d562330e80601a5af
Module libbsd.so.0 with build-id 974e49045a7855a26d47583928fa20dbbfd4f530
Module libbrotlicommon.so.1 with build-id 3c671f721b58fd96b70ba426a215b3c43847bbf5
Module libblkid.so.1 with build-id d3e947026c74ed40701063d17ae59a2f6e51abcb
Module libXdmcp.so.6 with build-id 1d12a8566670c95b1b02e341400060d2d825aade
Module libXau.so.6 with build-id 84ffa90fee1b716cdc7d8349be47ed6ca4761b75
Module libbrotlidec.so.1 with build-id 1160b28572b6a6fc5674f5db1333716d4ba9e55f
Module libdatrie.so.1 with build-id 57f62fe2ce6d6db200f0f8cfee3cc987b25a9e2f
Module libuuid.so.1 with build-id 6b0f1c26b65771068f1daa425dae3f769ce41a6c
Module libexpat.so.1 with build-id 0fa805792649d58f26fa59d23e9f5355ba67cca2
Module libgraphite2.so.3 with build-id 5b00ca1eda239ea043d7eae3b0fd4481560a907e
Module libpcre2-8.so.0 with build-id 5aa43e3778622f4b95261331e97a45be5b87481d
Module libffi.so.8 with build-id bb0fa5371874ba431e7cd9dc2df93922de436fa9
Module libselinux.so.1 with build-id 827b23e6391a3374fa79e36bca36c41c8e6d29e4
Module libmount.so.1 with build-id e29bc51dddfc4e370eb7eac9ff29df81efdbf22c
Module libjpeg.so.62 with build-id 12da81e724cd81f4c71e54182d94d21f2bab27df
Module libgmodule-2.0.so.0 with build-id 9f28f23ebfa524093fe5a2d1a8d086eaf3824645
Module libdl.so.2 with build-id 7a460055e0485a14f1d19cd8f8b8a0e77319fa44
Module libz.so.1 with build-id 19168f84642e8fe27700f92388598565e59048ee
Module libXrender.so.1 with build-id 23dd581f5d93297dc5c508f03e224f9860af8217
Module libxcb-render.so.0 with build-id ca78dfc48f5a2593d9dc3b1d439740c6abad3f1c
Module libxcb.so.1 with build-id 81156ba79b0ca3ca8d015453e333d16c3fcdc277
Module libxcb-shm.so.0 with build-id 77958cefc38a0b1edb4d0f4b76817b05ac6ec605
Module libpng16.so.16 with build-id 24720328fb61293ea32d8283c030fc0431082f65
Module libfreetype.so.6 with build-id 5d03f612aa76f7a175f1f23e5275809b0db692a4
Module libpixman-1.so.0 with build-id 2ba0d88f718a0fef93d759cfc90bc650cdee38ba
Module libthai.so.0 with build-id 11b774e6b958fa6734f1a721527e1596e34ecd00
Module libfribidi.so.0 with build-id df6a1c7bc544c74c18a8635e3e65965a1fb529c3
Module libfontconfig.so.1 with build-id 3209e243ebaf08c058f6a17b9037cbdfecc3e72c
Module libharfbuzz.so.0 with build-id d4a75db68352b8ea150e830e6720dc7f241b6c6c
Module libpangoft2-1.0.so.0 with build-id 7665226d35e490413282233bb338a8ad7fa67343
Module ld-linux-x86-64.so.2 with build-id 677c6b03c07000faccc863eaf95e426b1d419430
Module libc.so.6 with build-id ef3afb43092687d7fcc8167fabdee73f4a3287f1
Module libpthread.so.0 with build-id fba10b5687be23f32ae49c9ca70f036e4156e61d
Module libwayland-cursor.so.0 with build-id 67f712e24c0ebf8ea5be5410c32a34d5b5271b2b
Module libwayland-client.so.0 with build-id 296271640039da17030592ae7c798e4d785d3835
Module libglib-2.0.so.0 with build-id be501444301099c646ec77871ca83c5d6a530313
Module libgobject-2.0.so.0 with build-id bb1321e36df16e444469e4e2fb57323bf2c2c584
Module libgio-2.0.so.0 with build-id ade73737ec816f7ec61ccd7fbf554bf613977034
Module libgdk_pixbuf-2.0.so.0 with build-id 2c2c8cf1085b910a682d0ac9078dce999e2a875f
Module libXss.so.1 with build-id afbbf09d10ee939272bda7d6783cd69b6138f74c
Module libXrandr.so.2 with build-id 0372dfb32a5c0d113819e1167f75c81c751373a8
Module libXext.so.6 with build-id d3ac3e1515190245564a30a611f4a2a4eb94a617
Module libXinerama.so.1 with build-id 5a76407b56b10810711c5345defbdf4e2dad3897
Module libX11.so.6 with build-id 692ceb08bd361ef2ea7caaa0926de19466d6f3ad
Module libcairo.so.2 with build-id 48feebcd296c6d353cf5f6e385180362219f166a
Module libpango-1.0.so.0 with build-id 56468d1b5210773cf31bb8be42a16ef199a38b86
Module libpangocairo-1.0.so.0 with build-id d625ce8d575bda90b74d2a3a89120405e3202d27
Module librt.so.1 with build-id 3a53a3002be35bd46ef7c1ce5b6c6a7aaa57b0d9
Module libm.so.6 with build-id 989a409fe23136438f2ce34b685dd738dc20c6d9
Module dunst with build-id 092a779cafdda56c03726c61f8e912689e756cf8
Stack trace of thread 1296:
#0 0x00007f88f9e36d82 g_logv (libglib-2.0.so.0 + 0x5bd82)
#1 0x00007f88f9e36fef g_log (libglib-2.0.so.0 + 0x5bfef)
#2 0x000055999df0302a n/a (dunst + 0x1a02a)
#3 0x000055999def9d70 n/a (dunst + 0x10d70)
#4 0x000055999defbdb2 n/a (dunst + 0x12db2)
#5 0x00007f88f9a2920a __libc_start_call_main (libc.so.6 + 0x2920a)
#6 0x00007f88f9a292bc __libc_start_main_impl (libc.so.6 + 0x292bc)
#7 0x000055999def75ca n/a (dunst + 0xe5ca)

Stack trace of thread 1301:
#0 0x00007f88f9afda3f __GI___poll (libc.so.6 + 0xfda3f)
#1 0x00007f88fa0192c5 g_socket_condition_timed_wait (libgio-2.0.so.0 + 0xa62c5)
#2 0x00007f88fa01a266 n/a (libgio-2.0.so.0 + 0xa7266)
#3 0x00007f88f9ff3b45 g_input_stream_read (libgio-2.0.so.0 + 0x80b45)
#4 0x00007f88f9fc2d1e n/a (libgio-2.0.so.0 + 0x4fd1e)
#5 0x00007f88f9fc3ea4 g_buffered_input_stream_fill (libgio-2.0.so.0 + 0x50ea4)
#6 0x00007f88f9fcc019 g_data_input_stream_read_line (libgio-2.0.so.0 + 0x59019)
#7 0x00007f88fa0777f5 n/a (libgio-2.0.so.0 + 0x1047f5)
#8 0x00007f88fa078099 n/a (libgio-2.0.so.0 + 0x105099)
#9 0x00007f88fa088c85 n/a (libgio-2.0.so.0 + 0x115c85)
#10 0x00007f88f9fc2027 n/a (libgio-2.0.so.0 + 0x4f027)
#11 0x00007f88fa02a323 n/a (libgio-2.0.so.0 + 0xb7323)
#12 0x00007f88f9e5a4ba n/a (libglib-2.0.so.0 + 0x7f4ba)
#13 0x00007f88f9e59aed n/a (libglib-2.0.so.0 + 0x7eaed)
#14 0x00007f88f9a87b27 start_thread (libc.so.6 + 0x87b27)
#15 0x00007f88f9b0a78c __clone3 (libc.so.6 + 0x10a78c)

Stack trace of thread 1300:
#0 0x00007f88f9afda3f __GI___poll (libc.so.6 + 0xfda3f)
#1 0x00007f88f9e2f92e n/a (libglib-2.0.so.0 + 0x5492e)
#2 0x00007f88f9e2fa4c g_main_context_iteration (libglib-2.0.so.0 + 0x54a4c)
#3 0x00007f88f9e2fa91 n/a (libglib-2.0.so.0 + 0x54a91)
#4 0x00007f88f9e59aed n/a (libglib-2.0.so.0 + 0x7eaed)
#5 0x00007f88f9a87b27 start_thread (libc.so.6 + 0x87b27)
#6 0x00007f88f9b0a78c __clone3 (libc.so.6 + 0x10a78c)
ELF object binary architecture: AMD x86-64
Sep 26 05:38:17 debian systemd[1279]: dunst.service: Main process exited, code=dumped, status=5/TRAP
Sep 26 05:38:17 debian systemd[1279]: dunst.service: Failed with result 'core-dump'.
Sep 26 05:38:17 debian systemd[1279]: Failed to start Dunst notification daemon.


$ coredumpctl -S "$(uptime -s)" list dunst
TIME PID UID GID SIG COREFILE EXE SIZE
Mon 2022-09-26 05:38:08 UTC 922 106 111 SIGTRAP inaccessible /usr/bin/dunst n/a
Mon 2022-09-26 05:38:17 UTC 1296 1000 1000 SIGTRAP present /usr/bin/dunst 241.6K
0 new messages