dunst icon indicating copy to clipboard operation
dunst copied to clipboard

Dunst fails to load after booting from time to time

Open harishnkr opened this issue 1 year ago • 1 comments

Issue description

Dunst fails to output messages during certain boots. When it works, it works normally.

Installation info

  • Version: Dunst - A customizable and lightweight notification-daemon 1.9.2 (2023-04-20)
  • Install type: arch package manager
  • Window manager / Desktop environment: bspwm
  • Distro: Arch Linux
Minimal dunstrc
[colors]
	background = "#222b3e"
	foreground = "#ffffef"

[global]
    ### Display ###

    monitor = 0
    follow = mouse

    indicate_hidden = yes
    shrink = yes
    transparency = 0
    separator_height = 3
    padding = 12
    horizontal_padding = 12
    frame_width = 3

    frame_color = "#6e9a6a"
    separator_color = auto
    sort = yes
    idle_threshold = 120

    ### Text ###
    # font = inter 10
    line_height = 0

    markup = full

    # The format of the message.  Possible variables are:
    #   %a  appname
    #   %s  summary
    #   %b  body
    #   %i  iconname (including its path)
    #   %I  iconname (without its path)
    #   %p  progress value if set ([  0%] to [100%]) or nothing
    #   %n  progress value if set without any extra characters
    #   %%  Literal %
    # Markup is allowed
    format = "<b>%s</b>\n%b"
    alignment = left
    show_age_threshold = 60
    word_wrap = yes
    ellipsize = middle
    ignore_newline = no
    stack_duplicates = true
    hide_duplicate_count = false
    show_indicators = yes

    ### Icons ###
    icon_position = left
    max_icon_size = 64
    icon_theme = "rose-pine-moon-icons"
    enable_recursive_icon_lookup = true

    ### History ###
    sticky_history = yes
    history_length = 20

    ### Misc/Advanced ###
    dmenu = /usr/bin/rofi -show run -p dunst:
    browser = /usr/bin/firefox
    always_run_script = true
    title = Dunst
    class = Dunst
    force_xinerama = false

[experimental]
    per_monitor_dpi = false

[urgency_low]
    timeout = 10

[urgency_normal]
    timeout = 10

[urgency_critical]
    frame_color = "#c09d68"
    timeout = 0

Systemd info

OUTPUT OF systemctl --user status dunst

● dunst.service - Dunst notification daemon
     Loaded: loaded (/usr/lib/systemd/user/dunst.service; static)
     Active: active (running) since Thu 2024-01-18 13:29:08 IST; 9min ago
       Docs: man:dunst(1)
   Main PID: 690 (dunst)
      Tasks: 4 (limit: 9271)
     Memory: 19.6M (peak: 22.4M)
        CPU: 235ms
     CGroup: /user.slice/user-1001.slice/[email protected]/app.slice/dunst.service
             └─690 /usr/bin/dunst

Jan 18 13:29:09 archlinux dunst[690]: WARNING: Could not find theme breeze
Jan 18 13:29:07 archlinux systemd[657]: Starting Dunst notification daemon...
Jan 18 13:29:07 archlinux systemd-coredump[678]: [🡕] Process 671 (dunst) of user 1001 dumped core.

                                                 Stack trace of thread 671:
                                                 #0  0x00007591c9071485 g_logv (libglib-2.0.so.0 + 0x62485)
                                                 #1  0x00007591c9071724 g_log (libglib-2.0.so.0 + 0x62724)
                                                 #2  0x00005e7d2070939d n/a (dunst + 0x1439d)
                                                 #3  0x00005e7d207028c1 n/a (dunst + 0xd8c1)
                                                 #4  0x00007591c8e38cd0 n/a (libc.so.6 + 0x27cd0)
                                                 #5  0x00007591c8e38d8a __libc_start_main (libc.so.6 + 0x27d8a)
                                                 #6  0x00005e7d20702ce5 n/a (dunst + 0xdce5)

                                                 Stack trace of thread 673:
                                                 #0  0x00007591c8f1f73d syscall (libc.so.6 + 0x10e73d)
                                                 #1  0x00007591c90c22f7 g_cond_wait (libglib-2.0.so.0 + 0xb32f7)
                                                 #2  0x00007591c90341b4 n/a (libglib-2.0.so.0 + 0x251b4)
                                                 #3  0x00007591c909ca8e n/a (libglib-2.0.so.0 + 0x8da8e)
                                                 #4  0x00007591c909aa05 n/a (libglib-2.0.so.0 + 0x8ba05)
                                                 #5  0x00007591c8e9d9eb n/a (libc.so.6 + 0x8c9eb)
                                                 #6  0x00007591c8f217cc n/a (libc.so.6 + 0x1107cc)

...skipping...
                                                 Stack trace of thread 676:
                                                 #0  0x00007591c8f13f6f __poll (libc.so.6 + 0x102f6f)
                                                 #1  0x00007591c90c72b6 n/a (libglib-2.0.so.0 + 0xb82b6)
                                                 #2  0x00007591c9069b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
                                                 #3  0x00007591c92d119c n/a (libgio-2.0.so.0 + 0x11219c)
                                                 #4  0x00007591c909aa05 n/a (libglib-2.0.so.0 + 0x8ba05)
                                                 #5  0x00007591c8e9d9eb n/a (libc.so.6 + 0x8c9eb)
                                                 #6  0x00007591c8f217cc n/a (libc.so.6 + 0x1107cc)

                                                 Stack trace of thread 675:
                                                 #0  0x00007591c8f1f73d syscall (libc.so.6 + 0x10e73d)
                                                 #1  0x00007591c90c2cd3 g_cond_wait_until (libglib-2.0.so.0 + 0xb3cd3)
                                                 #2  0x00007591c9034185 n/a (libglib-2.0.so.0 + 0x25185)
                                                 #3  0x00007591c909d53b n/a (libglib-2.0.so.0 + 0x8e53b)
                                                 #4  0x00007591c909aa05 n/a (libglib-2.0.so.0 + 0x8ba05)
                                                 #5  0x00007591c8e9d9eb n/a (libc.so.6 + 0x8c9eb)
                                                 #6  0x00007591c8f217cc n/a (libc.so.6 + 0x1107cc)

                                                 Stack trace of thread 674:
                                                 #0  0x00007591c8f13f6f __poll (libc.so.6 + 0x102f6f)
                                                 #1  0x00007591c90c72b6 n/a (libglib-2.0.so.0 + 0xb82b6)
                                                 #2  0x00007591c9067162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
                                                 #3  0x00007591c90671b2 n/a (libglib-2.0.so.0 + 0x581b2)
                                                 #4  0x00007591c909aa05 n/a (libglib-2.0.so.0 + 0x8ba05)
                                                 #5  0x00007591c8e9d9eb n/a (libc.so.6 + 0x8c9eb)
                                                 #6  0x00007591c8f217cc n/a (libc.so.6 + 0x1107cc)
                                                 ELF object binary architecture: AMD x86-64
Jan 18 13:29:07 archlinux systemd[657]: dunst.service: Main process exited, code=dumped, status=5/TRAP
Jan 18 13:29:07 archlinux systemd[657]: dunst.service: Failed with result 'core-dump'.
Jan 18 13:29:07 archlinux systemd[657]: Failed to start Dunst notification daemon.
Jan 18 13:29:07 archlinux systemd[657]: Starting Dunst notification daemon...
Jan 18 13:29:08 archlinux systemd[657]: Started Dunst notification daemon.
Jan 18 13:34:08 archlinux dunst[690]: CRITICAL: Source ID 16 was not found when attempting to remove it

The theme breeze output comes up because the rose-pine-theme inherits theme breeze, and is probably not the cause of error

harishnkr avatar Jan 18 '24 08:01 harishnkr

Could you check if dunst is started before the X server and wm are initialized?

bynect avatar Feb 28 '24 21:02 bynect

same problem as #1340

bynect avatar Apr 20 '24 09:04 bynect

I am terribly sorry for the late response but somehow it started working again. I started it as a daemon and it works fine. I'll close the issue since it's a duplicate and I can't reproduce the problem. I'll reopen if I have the same problem again.

harishnkr avatar Apr 25 '24 19:04 harishnkr

I am terribly sorry for the late response but somehow it started working again. I started it as a daemon and it works fine. I'll close the issue since it's a duplicate and I can't reproduce the problem. I'll reopen if I have the same problem again.

It may be related to systemd. Maybe if you disable the dunst.service and just start in the xinitrc it worn't happen again. But if you already fixed it is also good

bynect avatar Apr 25 '24 20:04 bynect

No. It works from time to time. Since I can't exactly describe the situation perfectly, I'll create a new issue if I can figure out the problem. Thanks anyway.

harishnkr avatar May 04 '24 05:05 harishnkr