You are not logged in.
- Topics: Active | Unanswered
#1 2026-02-13 15:30:22
- trippycamper
- Member
- Registered: 2025-09-22
- Posts: 11
[solved] Dunst core dump - can't find the supposed issue
Trying to configure dunst, modified a few values in the dunstrc template and saved it to ~/.config/dunst.
Launching via terminal gives the output:
WARNING: Invalid config file at line 1: Key value pair without a section.
Segmentation fault (core dumped) dunstSystem journal:
Feb 13 10:27:37 cthulhu kernel: dunst[18323]: segfault at 0 ip 00007f6ae0cad7a4 sp 00007ffea1d89db0 error 4 in libc.so.6[4f7a4,7f6ae0c82000+171000] likely on CPU 2 (core 2, socket 0)
Feb 13 10:27:37 cthulhu kernel: Code: 72 75 19 00 64 c7 00 16 00 00 00 31 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d c3 66 2e 0f 1f 84 00 00 00 00 00 4d 8b 61 68 <49> 0f be 0b 4d 89
d9 48 89 ca 41 f6 44 4c 01 20 74 1e 66 2e 0f 1f
Feb 13 10:27:37 cthulhu systemd-coredump[18328]: Process 18323 (dunst) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Feb 13 10:27:37 cthulhu systemd[1]: Started Process Core Dump (PID 18328/UID 0).
Feb 13 10:27:37 cthulhu systemd-coredump[18329]: [?] Process 18323 (dunst) of user 1000 dumped core.
Stack trace of thread 18323:
#0 0x00007f6ae0cad7a4 n/a (libc.so.6 + 0x4f7a4)
#1 0x00005655036744b5 n/a (/usr/bin/dunst + 0x1f4b5)
#2 0x00005655036656d7 n/a (/usr/bin/dunst + 0x106d7)
#3 0x00005655036660c8 n/a (/usr/bin/dunst + 0x110c8)
#4 0x000056550365d6b1 n/a (/usr/bin/dunst + 0x86b1)
#5 0x00007f6ae0c85635 n/a (libc.so.6 + 0x27635)
#6 0x00007f6ae0c856e9 __libc_start_main (libc.so.6 + 0x276e9)
#7 0x000056550365db55 n/a (/usr/bin/dunst + 0x8b55)
Stack trace of thread 18325:
#0 0x00007f6ae0cfcfe2 n/a (libc.so.6 + 0x9efe2)
#1 0x00007f6ae0cf116c n/a (libc.so.6 + 0x9316c)
#2 0x00007f6ae0cf11b4 n/a (libc.so.6 + 0x931b4)
#3 0x00007f6ae0d6ba36 ppoll (libc.so.6 + 0x10da36)
#4 0x00007f6ae1038784 n/a (libglib-2.0.so.0 + 0x60784)
#5 0x00007f6ae1038865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865)
#6 0x00007f6ae10388b2 n/a (libglib-2.0.so.0 + 0x608b2)
#7 0x00007f6ae106f8bc n/a (libglib-2.0.so.0 + 0x978bc)
#8 0x00007f6ae0cf498b n/a (libc.so.6 + 0x9698b)
#9 0x00007f6ae0d78a0c n/a (libc.so.6 + 0x11aa0c)
Stack trace of thread 18326:
#0 0x00007f6ae0d7676d syscall (libc.so.6 + 0x11876d)
#1 0x00007f6ae10687be g_cond_wait_until (libglib-2.0.so.0 + 0x907be)
#2 0x00007f6ae0ffe197 n/a (libglib-2.0.so.0 + 0x26197)
#3 0x00007f6ae10712db n/a (libglib-2.0.so.0 + 0x992db)
#4 0x00007f6ae106f8bc n/a (libglib-2.0.so.0 + 0x978bc)
#5 0x00007f6ae0cf498b n/a (libc.so.6 + 0x9698b)
#6 0x00007f6ae0d78a0c n/a (libc.so.6 + 0x11aa0c)
Stack trace of thread 18327:
#0 0x00007f6ae0cfcfe2 n/a (libc.so.6 + 0x9efe2)
#1 0x00007f6ae0cf116c n/a (libc.so.6 + 0x9316c)
#2 0x00007f6ae0cf11b4 n/a (libc.so.6 + 0x931b4)
#3 0x00007f6ae0d6ba36 ppoll (libc.so.6 + 0x10da36)
#4 0x00007f6ae1038784 n/a (libglib-2.0.so.0 + 0x60784)
#5 0x00007f6ae1038a17 g_main_loop_run (libglib-2.0.so.0 + 0x60a17)
#6 0x00007f6ae12ab2e4 n/a (libgio-2.0.so.0 + 0x11a2e4)
#7 0x00007f6ae106f8bc n/a (libglib-2.0.so.0 + 0x978bc)
#8 0x00007f6ae0cf498b n/a (libc.so.6 + 0x9698b)
#9 0x00007f6ae0d78a0c n/a (libc.so.6 + 0x11aa0c)
Stack trace of thread 18324:
#0 0x00007f6ae0d7676d syscall (libc.so.6 + 0x11876d)
#1 0x00007f6ae106782e g_cond_wait (libglib-2.0.so.0 + 0x8f82e)
#2 0x00007f6ae0ffe1cd n/a (libglib-2.0.so.0 + 0x261cd)
#3 0x00007f6ae1070487 n/a (libglib-2.0.so.0 + 0x98487)
#4 0x00007f6ae106f8bc n/a (libglib-2.0.so.0 + 0x978bc)
#5 0x00007f6ae0cf498b n/a (libc.so.6 + 0x9698b)
#6 0x00007f6ae0d78a0c n/a (libc.so.6 + 0x11aa0c)
ELF object binary architecture: AMD x86-64
Feb 13 10:27:37 cthulhu systemd[1]: systemd-coredump@34-28675-18328_18329-0.service: Deactivated successfully.dunstrc file: https://pastes.io/config-18403
Seeing as line 1 is quite literally the section, I don't see how a setting could be without one. TIA for help.
Last edited by trippycamper (2026-02-13 18:40:25)
Offline
#2 2026-02-13 16:04:35
- twelveeighty
- Member
- Registered: 2011-09-04
- Posts: 1,429
Re: [solved] Dunst core dump - can't find the supposed issue
What happens if you copy /etc/dunst/dunstrc to ~/.config/dunst? Back up your custom config first, of course.
If that original file works from your ~/config location, then my total guesses are 1) *maybe* line-endings - did CRLF instead of LF perhaps make it into your edited file? or 2) Add the original's "# See dunst(5) for all configuration options" followed by an empty line at the top of your edited file. Both of these are long shots.
Offline
#3 2026-02-13 17:33:55
- trippycamper
- Member
- Registered: 2025-09-22
- Posts: 11
Re: [solved] Dunst core dump - can't find the supposed issue
What happens if you copy /etc/dunst/dunstrc to ~/.config/dunst? Back up your custom config first, of course.
This does work, which is confusing since I just modified a few numbers and saved.
If that original file works from your ~/config location, then my total guesses are 1) *maybe* line-endings - did CRLF instead of LF perhaps make it into your edited file? or 2) Add the original's "# See dunst(5) for all configuration options" followed by an empty line at the top of your edited file. Both of these are long shots.
Not sure what 1) means if you could clarify it would be appreciated, but 2) doesn't change anything - I had those lines in and removed them to check if that was the issue.
Offline
#4 2026-02-13 17:38:03
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 13,560
Re: [solved] Dunst core dump - can't find the supposed issue
Online
#5 2026-02-13 18:39:56
- trippycamper
- Member
- Registered: 2025-09-22
- Posts: 11
Re: [solved] Dunst core dump - can't find the supposed issue
Ok it seems I had set both icon_theme and icon_path, only one of which can be used. Setting only the path and commenting out the theme fixed my issue. Thank you!
Offline