dunst-project / dunst

Lightweight and customizable notification daemon
https://dunst-project.org
Other
4.52k stars 338 forks source link

unable to edit dunst using config file #1161

Closed 1stepback closed 1 year ago

1stepback commented 1 year ago

I've tried editing 2 different config files.

  1. /~/dunst/dunstrc
  2. /etc/xdg/dunst/dunstrc

I tried changing all urgency level notifications to the critical urgency red colour, & changing timeout settings. Neither did anything.

I'm a complete noob at Linux, so i'm just trying to find out which file will allow me to customise my Dunst notification daemon. I checked: config.mk
And it lists /etc/xdg/ as the SYSCONFDIR. Should that not be the location of the config file being read by Dunst? I tried editing the dunstrc at that location using sudo -e, and nothing.

I'm on Raspberry Pi OS (Debian based), and I installed Dunst from the repository, if that makes a difference.

If anyone can point me in a direction, I would greatly appreciate it. Sorry for posting twice in 24 hours, but I've been reading so much and i'm only sinking deeper into terms and commands I don't understand.

1stepback commented 1 year ago

After many hours of throwing myself at a wall (usually what happens with me and programming), I finally found the correct dunstrc file. I did not think to look for a hidden .config directory, and believed I didnt have one. In the end it was there.

ClassickTech commented 4 months ago

Hello, I have been having the same EXACT PROBLEM. Where exactly did you find it?

Edit: for anyone who comes across this in the future: The config is located at: /etc/xdg/dunst/dunstrc

Make a directory in home .config: mkdir ~/.config/dunst/

Then copy: cp /etc/xdg/dunst/dunstrc ~/.config/dunst/

Then point to your config when running dunst: dunst -config ~/.config/dunst/dunstrc

It will be owned by root so edit in nano, vim, etc: sudo nano duntsrc

bynect commented 4 months ago

It will be owned by root so edit in nano, vim, etc: sudo nano duntsrc

You should chown the file to yourself

sudo chown user:user dunstrc

ClassickTech commented 4 months ago

I just did that. Thanks!