Arch Linux

barnd3

Member

Registered: 2023-02-07

Posts: 165

[SOLVED] "dunst" WARNING: Unable to parse

I get the error message from dunst

WARNING: Unable to parse markup: Unknown tag 'p' on line 3 char 5

Unfortunately, I don't know where the error comes from and where I have to look...
Can anyone help me?

Last edited by barnd3 (2025-01-29 18:05:13)

cryptearth

Member

Registered: 2024-02-03

Posts: 2,013

Re: [SOLVED] "dunst" WARNING: Unable to parse

as so often the wiki is your friend: https://wiki.archlinux.org/title/Dunst
as the error complains about "p" I guess its missing an & in front

btw: please post FULL error messages - as it likely hints the file it tries to parse

barnd3

Member

Registered: 2023-02-07

Posts: 165

Re: [SOLVED] "dunst" WARNING: Unable to parse

Unfortunately, I only have this message.
It doesn't appear with every message.
What I don't know is which file the error refers to!

cryptearth

Member

Registered: 2024-02-03

Posts: 2,013

Re: [SOLVED] "dunst" WARNING: Unable to parse

again - please post the FULL console output from the prompt you start the session to you end up at the prompt again - like so:

[main@main ~]> ls -alFh
... directory listing
[main@main]>

barnd3

Member

Registered: 2023-02-07

Posts: 165

Re: [SOLVED] "dunst" WARNING: Unable to parse

ls -alFh
insgesamt 468K
drwx------ 40 andre users 4,0K 27. Jan 17:13  ./
drwxr-xr-x  4 root  root  4,0K 16. Nov 14:51  ../
drwxr-xr-x  3 andre users 4,0K  5. Jan 20:49 '~'/
-rw-r--r--  1 andre users 2,4K  2. Dez 14:59 'ax | grep dnsq'
-rw-------  1 andre users  636 16. Nov 16:16  .bash_history
-rw-r--r--  1 andre users   21 24. Sep 21:46  .bash_logout
-rw-r--r--  1 andre users   57 24. Sep 21:46  .bash_profile
-rw-r--r--  1 andre users  172 24. Sep 21:46  .bashrc
drwxr-xr-x  4 andre users 4,0K  6. Jan 16:14  Bilder/
drwxr-xr-x 35 andre users 4,0K 27. Jan 17:13  .cache/
drwxr-xr-x  3 andre users 4,0K 15. Jan 08:21  .cargo/
drwx------ 65 andre users 4,0K 27. Jan 14:50  .config/
drwxr-xr-x  3 andre users 4,0K 16. Nov 16:01  .conky/
-rw-------  1 andre users   75 19. Dez 21:44  dead.letter
-rw-r--r--  1 andre users   23 16. Nov 15:13  .dmrc
drwxr-xr-x  3 andre users 4,0K 27. Jan 16:43  Dokumente/
drwxr-xr-x 25 andre users 4,0K 26. Jan 19:16  Downloads/
drwx------  3 andre users 4,0K 16. Nov 18:10  .fltk/
drwx------  4 andre users 4,0K 17. Jan 20:14  .gnupg/
drwxr-xr-x  3 andre users 4,0K 13. Jan 17:02  go/
-rw-------  1 andre users    0 16. Nov 15:13  .ICEauthority
drwxr-xr-x  3 andre users 4,0K 18. Nov 13:43  .installjammerinfo/
-rw-r--r--  1 andre users   48 22. Jan 22:52  .jackdrc
drwxr-xr-x  4 andre users 4,0K 18. Nov 08:05  .java/
drwx------  2 andre users 4,0K 20. Nov 18:27  .links/
drwxr-xr-x  5 andre users 4,0K  5. Jan 21:28  .local/
drwx------  3 andre users 4,0K 24. Nov 17:49  .log/
drwx------  3 andre users 4,0K 23. Dez 21:44  mail/
-rw-------  1 andre users 6,2K 19. Dez 21:55  Mailbox
drwxr-xr-x  2 andre users 4,0K 26. Jan 22:46  .mediathek3/
drwx------  9 andre users 4,0K 23. Nov 15:56  moneyplex/
drwx------  4 andre users 4,0K 16. Nov 15:18  .mozilla/
drwxr-xr-x  2 andre users 4,0K 29. Nov 18:03  .mplayer/
drwxr-xr-x  2 andre users 4,0K 16. Nov 15:13  Musik/
drwxr-xr-x  4 andre users 4,0K 14. Jan 20:50  .npm/
drwx------  3 andre users 4,0K 16. Nov 16:28  .nv/
-rw-r--r--  1 andre users 2,3K 24. Jan 23:22  .nvidia-settings-rc
drwxr-xr-x  2 andre users 4,0K 16. Nov 15:13  Öffentlich/
drwxr-xr-x  3 andre users 4,0K 18. Nov 08:05  .openjfx/
drwx------  3 andre users 4,0K 16. Nov 16:58  .pki/
-rw-r--r--  1 andre users    0 22. Nov 14:44  run.py
drwxrwx---  3 andre users 4,0K 16. Nov 18:33  .sane/
drwxr-xr-x  2 andre users 4,0K 18. Nov 13:43  Schreibtisch/
drwxr-xr-x  2 andre users 4,0K 26. Jan 22:15  .scripts/
drwx------  2 andre users 4,0K 12. Jan 20:36  .ssh/
drwxr-xr-x  2 andre users 4,0K  1. Jan 18:08  .steam/
lrwxrwxrwx  1 andre users   30  1. Jan 16:58  .steampath -> /home/andre/.steam/sdk32/steam
lrwxrwxrwx  1 andre users   28  1. Jan 16:58  .steampid -> /home/andre/.steam/steam.pid
-rw-r--r--  1 andre users 150K  8. Jan 19:01  System.html
drwx------  4 andre users 4,0K  3. Dez 17:03  .thunderbird/
drwxr-xr-x  3 andre users 4,0K  4. Dez 22:28  .var/
drwxr-xr-x  2 andre users 4,0K 18. Jan 20:47  Videos/
drwxr-xr-x  2 andre users 4,0K 16. Nov 15:13  Vorlagen/
-rw-r--r--  1 andre users  165 29. Nov 18:49  .wget-hsts
-rw-------  1 andre users   50 27. Jan 16:56  .Xauthority
-rw-------  1 andre users  13K 27. Jan 17:10  .xsession-errors
-rw-------  1 andre users 2,7K 27. Jan 16:56  .xsession-errors.old
drwxr-xr-x  3 andre users 4,0K 14. Jan 18:00  .yarn/
-rw-r--r--  1 andre users  50K 27. Jan 16:56  .zcompdump
-rw-------  1 andre users  27K 27. Jan 17:13  .zhistory
drwx------  3 andre users 4,0K 16. Nov 17:14  .zsh/
-rw-r--r--  1 andre users  382 25. Jul 2023   .zshrc

If that's what you mean?

Last edited by barnd3 (2025-01-27 16:52:37)

cryptearth

Member

Registered: 2024-02-03

Posts: 2,013

Re: [SOLVED] "dunst" WARNING: Unable to parse

well - don't take my command - but YOUR command

also: please stick to english - if you request support in german please use the report link and ask a mod to move the topic

barnd3

Member

Registered: 2023-02-07

Posts: 165

Re: [SOLVED] "dunst" WARNING: Unable to parse

I don't know what kind of command you mean...?
I log in via lightdm and XFCE starts. I don't enter a console command...

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,439

Re: [SOLVED] "dunst" WARNING: Unable to parse

Post your ~/.config/dunst/dunstrc.

As a side-note, probably nothing to do with your dunst problem: be aware that you have some phantom files in your $HOME: 'ax | grep dnsq' is probably a redirection gone wrong some time last month. I am also puzzled why you have an actual folder called ~ inside your home folder, is that some kind of zsh tomfoolery?

barnd3

Member

Registered: 2023-02-07

Posts: 165

Re: [SOLVED] "dunst" WARNING: Unable to parse

# See dunst(5) for all configuration options

[global]
    ### Display ###

    # Which monitor should the notifications be displayed on.
    monitor = 0

    # Display notification on focused monitor.  Possible modes are:
    #   mouse: follow mouse pointer
    #   keyboard: follow window with keyboard focus
    #   none: don't follow anything
    #
    # "keyboard" needs a window manager that exports the
    # _NET_ACTIVE_WINDOW property.
    # This should be the case for almost all modern window managers.
    #
    # If this option is set to mouse or keyboard, the monitor option
    # will be ignored.
    follow = none

    ### Geometry ###

    # The width of the window, excluding the frame.
    # dynamic width from 0 to 300
    # width = (0, 300)
    # constant width of 300
    width = (0, 500)

    # The height of a single notification, excluding the frame.
    # dynamic height from 0 to 300
    height = (0, 300)
    # constant height of 300
    # height = 300
    # NOTE: Dunst from version 1.11 and older don't support dynamic height
    #       and the given value is treated as the maximum height

    # Position the notification in the top right corner
    origin = top-right

    # Offset from the origin
    # NOTE: Dunst from version 1.11 and older use this alternative notation
    # offset = 10x50
    offset = (10, 50)

    # Scale factor. It is auto-detected if value is 0.
    scale = 0

    # Maximum number of notification (0 means no limit)
    notification_limit = 20

    ### Progress bar ###

    # Turn on the progress bar. It appears when a progress hint is passed with
    # for example dunstify -h int:value:12
    progress_bar = true

    # Set the progress bar height. This includes the frame, so make sure
    # it's at least twice as big as the frame width.
    progress_bar_height = 10

    # Set the frame width of the progress bar
    progress_bar_frame_width = 1

    # Set the minimum width for the progress bar
    progress_bar_min_width = 150

    # Set the maximum width for the progress bar
    progress_bar_max_width = 300

    # Corner radius for the progress bar. 0 disables rounded corners.
    progress_bar_corner_radius = 0

    # Define which corners to round when drawing the progress bar. If progress_bar_corner_radius
    # is set to 0 this option will be ignored.
    progress_bar_corners = all

    # Corner radius for the icon image.
    icon_corner_radius = 0

    # Define which corners to round when drawing the icon image. If icon_corner_radius
    # is set to 0 this option will be ignored.
    icon_corners = all

    # Show how many messages are currently hidden (because of
    # notification_limit).
    indicate_hidden = yes

    # The transparency of the window.  Range: [0; 100].
    # This option will only work if a compositing window manager is
    # present (e.g. xcompmgr, compiz, etc.). (X11 only)
    transparency = 10

    # Draw a line of "separator_height" pixel height between two
    # notifications.
    # Set to 0 to disable.
    # If gap_size is greater than 0, this setting will be ignored.
    separator_height = 2

    # Padding between text and separator.
    padding = 8

    # Horizontal padding.
    horizontal_padding = 8

    # Padding between text and icon.
    text_icon_padding = 0

    # Defines width in pixels of frame around the notification window.
    # Set to 0 to disable.
    frame_width = 0

    # Defines color of the frame around the notification window.
    frame_color = "#aaaaaa"

    # Size of gap to display between notifications - requires a compositor.
    # If value is greater than 0, separator_height will be ignored and a border
    # of size frame_width will be drawn around each notification instead.
    # Click events on gaps do not currently propagate to applications below.
    gap_size = 0

    # Define a color for the separator.
    # possible values are:
    #  * auto: dunst tries to find a color fitting to the background;
    #  * foreground: use the same color as the foreground;
    #  * frame: use the same color as the frame;
    #  * anything else will be interpreted as a X color.
    separator_color = frame

    # Sort type.
    # possible values are:
    #  * id: sort by id
    #  * urgency_ascending: sort by urgency (low then normal then critical)
    #  * urgency_descending: sort by urgency (critical then normal then low)
    #  * update: sort by update (most recent always at the top)
    sort = yes

    # Don't remove messages, if the user is idle (no mouse or keyboard input)
    # for longer than idle_threshold seconds.
    # Set to 0 to disable.
    # A client can set the 'transient' hint to bypass this. See the rules
    # section for how to disable this if necessary
    # idle_threshold = 120

    ### Text ###

    font = Noto Sans Mono Regular 9

    # The spacing between lines.  If the height is smaller than the
    # font height, it will get raised to the font height.
    line_height = 0

    # Possible values are:
    # full: Allow a small subset of html markup in notifications:
    #        <b>bold</b>
    #        <i>italic</i>
    #        <s>strikethrough</s>
    #        <u>underline</u>
    #
    #        For a complete reference see
    #        <https://docs.gtk.org/Pango/pango_markup.html>.
    #
    # strip: This setting is provided for compatibility with some broken
    #        clients that send markup even though it's not enabled on the
    #        server. Dunst will try to strip the markup but the parsing is
    #        simplistic so using this option outside of matching rules for
    #        specific applications *IS GREATLY DISCOURAGED*.
    #
    # no:    Disable markup parsing, incoming notifications will be treated as
    #        plain text. Dunst will not advertise that it has the body-markup
    #        capability if this is set as a global setting.
    #
    # It's important to note that markup inside the format option will be parsed
    # regardless of what this is set to.
    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 of message text.
    # Possible values are "left", "center" and "right".
    alignment = left

    # Vertical alignment of message text and icon.
    # Possible values are "top", "center" and "bottom".
    vertical_alignment = center

    # Show age of message if message is older than show_age_threshold
    # seconds.
    # Set to -1 to disable.
    show_age_threshold = 60

    # Specify where to make an ellipsis in long lines.
    # Possible values are "start", "middle" and "end".
    ellipsize = middle

    # Ignore newlines '\n' in notifications.
    ignore_newline = no

    # Stack together notifications with the same content
    stack_duplicates = true

    # Hide the count of stacked notifications with the same content
    hide_duplicate_count = false

    # Display indicators for URLs (U) and actions (A).
    show_indicators = yes

    ### Icons ###

    # Recursive icon lookup. You can set a single theme, instead of having to
    # define all lookup paths.
    enable_recursive_icon_lookup = false

    # Set icon theme (only used for recursive icon lookup)
    icon_theme = Colloid-Light
    # You can also set multiple icon themes, with the leftmost one being used first.
    # icon_theme = "Adwaita, breeze"

    # Align icons left/right/top/off
    icon_position = left

    # Scale small icons up to this size, set to 0 to disable. Helpful
    # for e.g. small files or high-dpi screens. In case of conflict,
    # max_icon_size takes precedence over this.
    min_icon_size = 32

    # Scale larger icons down to this size, set to 0 to disable
    max_icon_size = 128

    # Paths to default icons (only necessary when not using recursive icon lookup)
    icon_path = /usr/share/icons/Colloid-Light/status/16/:/usr/share/icons/Colloid-Light/devices/16/:/usr/share/icons/Colloid-Light/status/symbolic/

    ### History ###

    # Should a notification popped up from history be sticky or timeout
    # as if it would normally do.
    sticky_history = yes

    # Maximum amount of notifications kept in history
    history_length = 20

    ### Misc/Advanced ###

    # dmenu path.
    dmenu = /usr/bin/dmenu -p dunst:

    # Browser for opening urls in context menu.
    browser = /usr/bin/xdg-open

    # Always run rule-defined scripts, even if the notification is suppressed
    always_run_script = true

    # Define the title of the windows spawned by dunst (X11 only)
    title = Dunst

    # Define the class of the windows spawned by dunst (X11 only)
    class = Dunst

    # Define the corner radius of the notification window
    # in pixel size. If the radius is 0, you have no rounded
    # corners.
    # The radius will be automatically lowered if it exceeds half of the
    # notification height to avoid clipping text and/or icons.
    corner_radius = 10

    # Define which corners to round when drawing the window. If the corner radius
    # is set to 0 this option will be ignored.
    #
    # Comma-separated list of the corners. The accepted corner values are bottom-right,
    # bottom-left, top-right, top-left, top, bottom, left, right or all.
    corners = all

    # Ignore the dbus closeNotification message.
    # Useful to enforce the timeout set by dunst configuration. Without this
    # parameter, an application may close the notification sent before the
    # user defined timeout.
    ignore_dbusclose = false

    ### Wayland ###
    # These settings are Wayland-specific. They have no effect when using X11

    # Uncomment this if you want to let notifications appear under fullscreen
    # applications (default: overlay)
    # layer = top

    # Set this to true to use X11 output on Wayland.
    force_xwayland = false

    ### Legacy

    # Use the Xinerama extension instead of RandR for multi-monitor support.
    # This setting is provided for compatibility with older nVidia drivers that
    # do not support RandR and using it on systems that support RandR is highly
    # discouraged.
    #
    # By enabling this setting dunst will not be able to detect when a monitor
    # is connected or disconnected which might break follow mode if the screen
    # layout changes.
    force_xinerama = false

    ### mouse

    # Defines list of actions for each mouse event
    # Possible values are:
    # * none: Don't do anything.
    # * do_action: Invoke the action determined by the action_name rule. If there is no
    #              such action, open the context menu.
    # * open_url: If the notification has exactly one url, open it. If there are multiple
    #             ones, open the context menu.
    # * close_current: Close current notification.
    # * close_all: Close all notifications.
    # * context: Open context menu for the notification.
    # * context_all: Open context menu for all notifications.
    # These values can be strung together for each mouse event, and
    # will be executed in sequence.
    mouse_left_click = close_current
    mouse_middle_click = do_action, close_current
    mouse_right_click = close_all

# Experimental features that may or may not work correctly. Do not expect them
# to have a consistent behaviour across releases.
[experimental]
    # Calculate the dpi to use on a per-monitor basis.
    # If this setting is enabled the Xft.dpi value will be ignored and instead
    # dunst will attempt to calculate an appropriate dpi value for each monitor
    # using the resolution and physical size. This might be useful in setups
    # where there are multiple screens with very different dpi values.
    per_monitor_dpi = false


[urgency_low]
    # IMPORTANT: colors have to be defined in quotation marks.
    # Otherwise the "#" and following would be interpreted as a comment.
    background = "#222222"
    foreground = "#888888"
    timeout = 10
    # Icon for notifications with low urgency
    default_icon = dialog-information

[urgency_normal]
    background = "#cccccc"
    foreground = "#333333"
    timeout = 5
    override_pause_level = 30
    # Icon for notifications with normal urgency
    default_icon = dialog-information

[urgency_critical]
    background = "#900000"
    foreground = "#ffffff"
    frame_color = "#ff0000"
    timeout = 0
    override_pause_level = 60
    # Icon for notifications with critical urgency
    default_icon = dialog-warning

# Every section that isn't one of the above is interpreted as a rules to
# override settings for certain messages.
#
# Messages can be matched by
#    appname (discouraged, see desktop_entry)
#    body
#    category
#    desktop_entry
#    icon
#    match_transient
#    msg_urgency
#    stack_tag
#    summary
#
# and you can override the
#    background
#    foreground
#    format
#    frame_color
#    fullscreen
#    new_icon
#    set_stack_tag
#    set_transient
#    set_category
#    timeout
#    urgency
#    icon_position
#    skip_display
#    history_ignore
#    action_name
#    word_wrap
#    ellipsize
#    alignment
#    hide_text
#    override_pause_level
#
# Shell-like globbing will get expanded.
#
# Instead of the appname filter, it's recommended to use the desktop_entry filter.
# GLib based applications export their desktop-entry name. In comparison to the appname,
# the desktop-entry won't get localized.
#
# You can also allow a notification to appear even when paused. Notification will appear whenever notification's override_pause_level >= dunst's paused level.
# This can be used to set partial pause modes, where more urgent notifications get through, but less urgent stay paused. To do that, you can override the following in the rules:
# override_pause_level = X

# SCRIPTING
# You can specify a script that gets run when the rule matches by
# setting the "script" option.
# The script will be called as follows:
#   script appname summary body icon urgency
# where urgency can be "LOW", "NORMAL" or "CRITICAL".
#
# NOTE: It might be helpful to run dunst -print in a terminal in order
# to find fitting options for rules.

# Disable the transient hint so that idle_threshold cannot be bypassed from the
# client
#[transient_disable]
#    match_transient = yes
#    set_transient = no
#
# Make the handling of transient notifications more strict by making them not
# be placed in history.
#[transient_history_ignore]
#    match_transient = yes
#    history_ignore = yes

# fullscreen values
# show: show the notifications, regardless if there is a fullscreen window opened
# delay: displays the new notification, if there is no fullscreen window active
#        If the notification is already drawn, it won't get undrawn.
# pushback: same as delay, but when switching into fullscreen, the notification will get
#           withdrawn from screen again and will get delayed like a new notification
#[fullscreen_delay_everything]
#    fullscreen = delay
#[fullscreen_show_critical]
#    msg_urgency = critical
#    fullscreen = show

#[espeak]
#    summary = "*"
#    script = dunst_espeak.sh

#[dunst_gleiten]
#    summary = "*"
#    script = /home/andre/.scripts/dunst_gleiten.sh

#[ignore]
#    # This notification will not be displayed
#    summary = "foobar"
#    skip_display = true

#[history-ignore]
#    # This notification will not be saved in history
#    summary = "foobar"
#    history_ignore = yes

#[skip-display]
#    # This notification will not be displayed, but will be included in the history
#    summary = "foobar"
#    skip_display = yes

#[signed_on]
#    appname = Pidgin
#    summary = "*signed on*"
#    urgency = low
#
#[signed_off]
#    appname = Pidgin
#    summary = *signed off*
#    urgency = low
#
#[says]
#    appname = Pidgin
#    summary = *says*
#    urgency = critical
#
#[twitter]
#    appname = Pidgin
#    summary = *twitter.com*
#    urgency = normal
#
#[stack-volumes]
#    appname = "some_volume_notifiers"
#    set_stack_tag = "volume"
#
[play_sound]
summary = "*"
script = /home/andre/.scripts/alert.sh
# vim: ft=cfg

The error only occurs in connection with an email in which I receive a message via dunst. Now I suspect that the message has a format that dunst cannot handle!?

The folder '~' was created by "vlcskineditor", it has no meaning, I can also delete it.

cryptearth

Member

Registered: 2024-02-03

Posts: 2,013

Re: [SOLVED] "dunst" WARNING: Unable to parse

I don't know what kind of command you mean...?
I log in via lightdm and XFCE starts. I don't enter a console command...

I somewhat struggle to call that trolling - but given your output and what a mess that is I just take it you just don't it any better

so - to recap

you posted some console log - an error
and to get there you had to run some command - like an "ls"
my snippet was to show you how you're supposed to post your actual session including the command you ran to end up with the error you posted along with any additional line you cut out - which likely give some more hints about your initial problem
as you either don't know or fail to comprehend let me point you here: https://bbs.archlinux.org/viewtopic.php … 95#p440695
or to put it in simple easy to translate plain english: we're happy to help you to help yourself - but for that you have to provide us what we ask you - otherwise we just can't - and I mean: CAN NOT - help you

yes, this may sound harsh - but your action was about me asking you "what's your problem" and you just replying with "some problem" - I guess you see issue with that approach

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,439

Re: [SOLVED] "dunst" WARNING: Unable to parse

The error only occurs in connection with an email in which I receive a message via dunst.

What email client are you using? How did you configure its notifications? Are you reading email with a web client like Firefox / Chromium?

barnd3

Member

Registered: 2023-02-07

Posts: 165

Re: [SOLVED] "dunst" WARNING: Unable to parse

I use Thunderbird to read and send emails. In Thunderbird, I have only selected system notifications, the rest is done by Dunst.
Here is the email in question, probably Dunst can't handle the <p> tags, there's nothing you can do about it, right?

Last edited by barnd3 (2025-01-28 14:56:46)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,789

Re: [SOLVED] "dunst" WARNING: Unable to parse

"allow_markup = yes", http://developer.gnome.org/pango/stable … ormat.html

Edit: "no, the <p> tag isn't supported by the pango subset"

Last edited by seth (2025-01-28 15:18:31)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

barnd3

Member

Registered: 2023-02-07

Posts: 165

Re: [SOLVED] "dunst" WARNING: Unable to parse

I have now adjusted the dunstrc and used "markup = strip", that seems to work...
Thank you

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,439

Re: [SOLVED] "dunst" WARNING: Unable to parse

Please mark your post as SOLVED by editing your original post and prepending SOLVED to the title.