Probable silent error while notifying hampers further notification capabilities
I was toying around with BorgBackup and borgmatic, and I thought it would be fun to display a notification with a sound on the event of an error. I may have over-specified some command-line options and I may have caused an error for libnotify (although I was not notified of this). However, the behavior of notifications after this incident resulted in only silent notifications being logged.
Steps to reproduce
notify-send --urgency=normal --app-name=borg --icon=error --category=transfer.error --hint=string:sound-file:~/Downloads/audio/borg_computer_beep.wav "Summary" "Body"
notify-send --urgency=critical --icon=error "Critical Error" "This should not be silent"
Note: Perhaps my usage of app-name
is erroneous, as there is no existing borg.desktop
Work-around for sound notifications
Using a wav file
notify-send --urgency=normal --app-name=borg --icon=error --category=transfer.error "Summary" "Body" && aplay ~/Downloads/audio/borg_computer_beep.wav
Possibly related issues
- Missing documentation about category and hints in manpage (external; I found some info in this StackExchange answer... somewhat related to #8 (closed)).
- #6 (closed) because further notifications are only shown when clicking the displayed time to show the notifications and calendar.
- #10 (closed) because it's possible that
Update: Forgot one step to show further notifications go unnoticed
Edited by Rolando Garza