Using dunst to send notifications to HDMI display monitor

[westrock2000]

I want to use something like notify-send in a script to pop up on the HDMI screen.

The command is installed, but when you run it remotely it does not do anything. I assume this is because it doesn't know what display to send to (since I'm remote logged in).

what is the DISPLAY:x syntax to get the HDMI display?

I tried a couple common ones but no go

[root@runeaudio ~]# export DISPLAY=0.0
[root@runeaudio ~]# notify-send Test "Hello World"
[root@runeaudio ~]# export DISPLAY=0
[root@runeaudio ~]# export DISPLAY=:0
[root@runeaudio ~]# notify-send Test "Hello World"
[root@runeaudio ~]# export DISPLAY=:0.0
[root@runeaudio ~]# notify-send Test "Hello World"
[root@runeaudio ~]# export DISPLAY=:1
[root@runeaudio ~]# notify-send Test "Hello World"

[westrock2000]

Or is the HDMI display not a compatible "desktop" for this command?

[hondagx35]

Hi,

Or is the HDMI display not a compatible "desktop" for this command?

Yes, because we use matchbox-window-manager and not a full desktop.

You can try to install the package "dunst"

Code: Select all

pacman -Sy dunst

Code: Select all

export DISPLAY=":0"
dunst &
notify-send "Test" "Hello World"

Frank

[westrock2000]

Thanks Frank, thats what I thought about the desktop not being traditional. Dunst did work. But it sends very small text. I tried editing the font size and other stuff like colors in /usr/share/dunst/dunstrc , but it does not appear to have any effect..

I had to update pacman first before it would install dunst, kept getting a 404 on the archlinux repository. Then try installing again after that.

[root@runeaudio]# pacman -Syy
[root@runeaudio]# pacman -Sy dunst

[westrock2000]

Does the desktop run as root or some other user?

[westrock2000]

I figured it out (not much documentation on either Matchbox or Dunst). If I explicitly tell dunst what config to source, it works.

So set the display. Kill dunst. Restart telling what config to source. You have to kill and then immediatly restart because there is a daemon that will restart the dunst service automatically. Further research might figure out how to have the daemon start it with the config argument automatically.


[root@runeaudio dunst]# export DISPLAY=":0"
[root@runeaudio dunst]# killall dunst;/usr/bin/dunst -config /usr/share/dunst/dunstrc&
[root@runeaudio dunst]# notify-send "Track 3/12 Ripped"



Setting the display and config only need to be done once in the script (or terminal session).

Some of the config things I changed

# 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.
idle_threshold = 0

### Text ###

font = LiberationSans Mono 20

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

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

[urgency_normal]
background = "#e6dc4e"
foreground = "#000000"
timeout = 10
# Icon for notifications with normal urgency, uncomment to enable
#icon = /path/to/icon

[westrock2000]

I updated the thread title to better reflect the topic for those searching later.