dunstctl close #ID does not work

[SpancerNow]

Good morning,
I need your help.
Dunst - notification-daemon v1.12.2-58-g896f788

"Dunstify close by ID" does not work if I configure the urgency level.

The working part
dunstify "Internet switched off-1" -t 0 -r 4713
dunstify "Internet switched off-2" -t 0 -r 4714
dunstctl close #4713

The non working part
dunstify "Internet switched off-1" --urgency low -t 0 -r 4713
dunstify "Internet switched off-2" --urgency low -t 0 -r 4714
dunstctl close 4713

Do you have any idea why this is not working?

[bynect]

You shouldn't use the hashbang, it gets interpreted as a comment. Just do

dunst close 4137

[bynect]

Did you update dunstctl alongside dunst? Old version of dunstctl did not support close [id]

What does dunstctl help print?

[SpancerNow]

My new installed version of dunst is (Dunst - notification-daemon v1.12.2-58-g896f788; dunst version: 1.9.2 ).
I only kept the dunstrc from the previous version.

[bynect]

dunst version: 1.9.2

This is a problem

[SpancerNow]

Sorry, this is the current version
"Dunst - A customizable and lightweight notification-daemon v1.12.2-58-g896f788"

[bynect]

dunstctl help
Usage: dunstctl <command> [parameters]
Commands:
  action                            Perform the default action, or open the
                                    context menu of the notification at the
                                    given position
  close [ID]                        Close the last notification or the   <-------------
                                    notification with given ID
  close-all                         Close all the notifications
  context                           Open context menu
  count [displayed|history|waiting] Show the number of notifications
  history                           Display notification history (in JSON)
  history-clear                     Delete all notifications from history
  history-pop [ID]                  Pop the latest notification from
                                    history or optionally the
                                    notification with given ID
  history-rm ID                     Remove the notification from
                                    history with given ID.
  is-paused [-e|--exit-code]        Check if pause level is greater than 0, optionally with exit code instead of text output
  set-paused true|false|toggle      Set the pause status
  get-pause-level                   Get the current pause level
  set-pause-level level             Set the pause level
  rule name enable|disable|toggle   Enable or disable a rule by its name
  rules [--json]                    Displays configured rules (optionally
                                    in JSON)
  reload [dunstrc ...]              Reload the settings of the running
                                    instance, optionally with specific
                                    config files (space/comma-separated)
  debug                             Print debugging information
  help                              Show help

does this show up?

[SpancerNow]

Yes it does. Exact the same.

[bynect]

this is really strange.
if you do dunstify -p test
and immediately
dunstctl close ID
with the id you just got.
does anything happen?

also try to put dunst in logging
killall dunst; dunst -verbosity debug
and send logs

[SpancerNow]

I made the test:
dunstify -p test & dunstctl close ID > It was not working
dunstify -p test & dunstctl close #ID > It was working

Your second suggestions put dunst in logging. I Hope that's what you mean. Here is the output of the command. The log itself was empty. The dunst debug log I attached.

dunst-debug.log
dunst -print > dunst.log &
[2] 237322
[1] Exit 1 dunst -print > dunst.log
theo@prv-pc:~$ WARNING: Setting hight in section global doesn't exist
WARNING: Setting notification_height in section global doesn't exist
WARNING: Setting startup_notification in section global doesn't exist
WARNING: Setting verbosity in section global doesn't exist
WARNING: Section shortcuts is deprecated.
Settings in the shortcuts sections have been moved to the global section.
Alternatively you can bind shortcuts in your window manager to dunstctl commands. For that, see the manual for dunstctl.
Ignoring this section.
WARNING: Cannot set empty value for setting frame_color
CRITICAL: [dbus_cb_name_lost:1401] Cannot acquire 'org.freedesktop.Notifications': Name is acquired by 'dunst' with PID '139993'.
dunstify -p test
24
[2]+ Exit 1 dunst -print > dunst.log

[bynect]

CRITICAL: [dbus_cb_name_lost:1401] Cannot acquire 'org.freedesktop.Notifications': Name is acquired by 'dunst' with PID '139993'

first you have to kill the current dunst. otherwise this won't start a new process.

dunstify -p test & dunstctl close ID > It was not working
dunstify -p test & dunstctl close #ID > It was working

using #ID is never correct. this is just a comment for shells. it means the command executed is
dunstctl close
This closes the last notifiication, disregarding id

please try again getting a debug log

[SpancerNow]

I would like to know whether you tried the following code on your configuration and what is your result?

The working part
dunstify "Internet switched off-1" -t 0 -r 4713
dunstify "Internet switched off-2" -t 0 -r 4714
dunstctl close #4713

The non working part
dunstify "Internet switched off-1" --urgency low -t 0 -r 4713
dunstify "Internet switched off-2" --urgency low -t 0 -r 4714
dunstctl close 4713

[bynect]

I would like to know whether you tried the following code on your configuration and what is your result?

The working part
dunstify "Internet switched off-1" -t 0 -r 4713
dunstify "Internet switched off-2" -t 0 -r 4714
dunstctl close #4713

The non working part
dunstify "Internet switched off-1" --urgency low -t 0 -r 4713
dunstify "Internet switched off-2" --urgency low -t 0 -r 4714
dunstctl close 4713

If you do -- then the arguments after that will not be interpreted as custom arguments for the command but just as string, hence they will not set the custom id. So closing that id will not work.

Anyway any shell will interpret # as a comment, meaning they will always ignore what comes after. So when you add #number it will not be considered at all. All the commands I provided for dunstify and dunstctl work on a default build of dunst

[SpancerNow]

Did you try it on your system?
Why is (dunstctl close #4713) it working on my system?
I know, the system interpreted the # as a comment. Nevertheless, the question arises, why does it work with the # ???

[bynect]

Did you try it on your system?
Why is (dunstctl close #4713) it working on my system?
I know, the system interpreted the # as a comment. Nevertheless, the question arises, why does it work with the # ???

The id is optional for dunstctl close. Meaning if you don't supply any id it will still do something. And that something is close the most recent notification. So if you do

dunstctl close #id

Which is the same as

dunstctl close #abcdef

Which is the same as

dunstctl close

Only the most recent notification will be closed