dunstctl close <id> does not dismiss notification window

[conor-naranjo]

I am using a script running in dunst config that contains (roughly) the following to log the emitting application and the dunst notification id:
script = ~/bin/dunst_log_filter

NOTIF_APPNAME="$1"

if [ -n "$DUNST_ID" ]; then
	echo "$DUNST_ID $NOTIF_APPNAME" >> "$LOG_FILE"
fi

If I run dunstctl close with no additional parameters, the window is removed and the notification is moved into history as expected.

Is this expected behavior or is there another way to invoke close_current for a single id using dunstctl?

[fedang]

I don't understand what is the problem. dunstctl close closes the last notification, while dunstctl close ID closes that specific notification.

[conor-naranjo]

Oh, I'm sorry, when I edited my issue body to cleanup unnecessary info I removed necessary context.

The issue is that dunstctl close ID is not removing the notification window that is drawn on the screen, whereas dunstctl close will successfully remove the notification.

It appears that dunstctl close ID is just doing nothing and I have no way to confirm whether it is working or not. Even when I invoke the CloseNotification to dbus directly, I'm not certain it's behaving as expected

Given the format of the log file noted in the bash snippet above if I have, e.g.:

12 notify-send
13 dunstify
14 dunstify

where all 3 of those are actively rendered on screen, running dunstctl close 12 will not remove the notification, but dunstctl close will remove the newest

 $ dbus-send --print-reply --dest="org.freedesktop.Notifications" /org/freedesktop/Notifications 
org.freedesktop.Notifications.CloseNotification "uint32:14"
method return time=1772735723.539893 sender=:1.305660 -> destination=:1.311724 serial=175 reply_serial=2

is the dbus-send command I was invoking directly as well to try to get better info

[fedang]

If you do notify-send -p hello does the printed id match the ones logged? If you do dunstctl close id with the ones printed by that does it work?

[conor-naranjo]

Yes, the printed id matches what gets logged.
dunstctl close $id does not close the notification

Attached is a screenshot that (sort of) illustrates

[fedang]

That is indeed a problem. But I can't seem to replicate it on my machine. Could you include a log dunst -verbosity debug and more info about your setup?

[conor-naranjo]

My setup is i3 and arch (kernel 6.19.6-arch1-1)

dunstrc:

[global]
    monitor = 1
    follow = none
    origin = bottom-right
    width = (100, 800)
    height = (0, 1000)
    offset = (0, 10) # 0 from right, 10 from top 
    font = "Hack 10"
    format = "%a - %s (%b)"
    idle_threshold = 0
    history_length = 20
    sticky_history = true
    stack_duplicates = false
    ignore_dbusclose = true

    separator_color = frame
    highlight = "#8aadf4"

    script = ~/bin/dunst_log_filter

dunst_log_filter:

#!/bin/bash
NOTIF_APPNAME="$1"
LOG_FILE="/tmp/dunst_active_ids"

FOCUSED_WINDOW=$(i3-msg -t get_tree | jq -r '.. | select(.focused? == true).window_properties.class')

if [[ "${NOTIF_APPNAME,,}" == "${FOCUSED_WINDOW,,}" ]]; then
	dunstctl close

	exit 0
fi

if [ -n "$DUNST_ID" ]; then
	echo "$DUNST_ID $NOTIF_APPNAME" >> "$LOG_FILE"
fi

My intention is to have a script subscribed to i3 window events that will close a particular dunst notification when the application that emitted the event is the currently selected window

dunst -verbosity debug log is attached

dunst_debug.log

[conor-naranjo]

Oh jeez - I'm now realizing this is a self-own because I forgot I enabled ignore_dbusclose and dunst is behaving as expected

So my question is maybe rephrased as: is is possible to keep notifications open indefinitely (or until explicitly dismissed) without having to enable ignore_dbusclose

My other thought was possibly adding a new custom dbus signal similar to NotificationCloseLast that accepts a dunst id in a fork to meet my specific use-case

[fedang]

My other thought was possibly adding a new custom dbus signal similar to NotificationCloseLast that accepts a dunst id in a fork to meet my specific use-case

I am not sure what you mean but there is CloseNotification that takes the id