Currently, the number of minutes exceeds '59' if delta is more than one hour.
I've fixed it locally with the following modifications.

diff -u a/dunst.c b/dunst.c
--- a/dunst.c   2012-08-02 19:19:32.000000000 +0400
+++ b/dunst.c   2012-08-10 11:21:42.434974194 +0400
@@ -411,8 +411,8 @@
                                 continue;

                         hours = t_delta / 3600;
-                        minutes = (t_delta / 60);
-                        seconds = (t_delta % 60);
+                        minutes = t_delta / 60 % 60;
+                        seconds = t_delta % 60;

                         for (end = n_buf[i].txt; *end != '\0'; end++) ;
                         if (hours > 0) {

It would be nice if there was an option to show messages on all monitors.

When using synergy if a notification time reaches the "idle_threshold" time when the mouse cursor is on another computer
dbus-daemon starts leaking memory at a rate of about 100MiB/5s and programs that send dbus messages (in my case evolution and nm-applet) start using 100% of a processing thread.

After moving the mouse cursor back to the computer running dunst the dunst window does not respond.
The only way to stop the cpu use is to kill the dunst process and reboot the computer to free the memory used by dbus-daemon.

This does not happen with "idle_threshold = 0".

Currently, it's necessary to start dunst manually, e.g. in ~/.xsession.

Putting the following snippet as /usr/share/dbus-1/services/dunst.service results in dunst getting launched via DBus as soon as needed.

[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/bin/dunst

When using NetworkManager, I get disconnect messages multiple times. Filtering identical messages would be a good feature, IMO.

Hey,

I’d like to package dunst for Debian so that people don’t have to follow a strange tutorial and can enjoy apt-get install dunst instead.

However, your licensing is a bit problematic :-/. As you might know, beerware is not exactly a license which Debian considers free. Would it be an option for you to provide a clear LICENSE file and use one of the licenses which are already present in your code? For example MIT/X11 from dmenu, or the BSD license from inih.

That’d be great!
Thanks,
Best regards,
Michael

This is just an idea, I'm not sure if it's better, it's just how I envisioned the feature when I originally requested it and I thought I'd throw it out there. I expected redisplaying previous messages to be sticky and to have to manually clear them. I guess I'll have to use it how it is now for a bit to see how I like it.

Add a option to change the format of the message. Example:

%a --> appname
%s --> summary
%b --> body
%i -->icon name

As part of a rule you could specify the path to a shell script that would be run when a matching notification is received. Maybe script path could include format string characters designating what data is passed to the script.

I haven't actually thought of a use for this one, but thought I'd mention it in case you don't have enough work already :)

Maybe you do something when a torrent is complete. Or when you lose wireless access. Granted in an ideal world you'd do these things through the applications that send the notifications themselves, but I imagine in some cases using dunst would actually be easier.

This is something that twmn does that I actually like. It's not a common thing for me to have icons in my notifications (for the most part I don't have any) but in the cases that I do, the icons are what make it.

I'm really digging dunst and will probably use it over twmn (stacking notifications, cool! Nice, easy config? GREAT!), and if this doesn't make it in it's not really a game changer but definitely something I think a lot of people would want.

dunst seems to be receiving them from dbus just fine (dunst -v prints them to command line like a champ!), but they're never actually getting drawn to the screen.

Did it from a "git clone https://github.com/knopwob/dunst.git && make"

Make spits out a few errors:

pod2man README.pod > dunst.1
dunst build options:
CFLAGS   = -g -ansi -pedantic -Wall -Os -I/usr/X11R6/include -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include   -I/usr/include/freetype2 -D_BSD_SOURCE -DVERSION="" -DXINERAMA -DINI_ALLOW_MULTILINE=0
LDFLAGS  = -L/usr/X11R6/lib -lX11 -lXss -lXft -lXinerama -ldbus-1 -lxdg-basedir  
CC       = cc
CC -c draw.c
CC -c dunst.c
dunst.c: In function ‘update_lists’:
dunst.c:271:17: warning: passing argument 2 of ‘l_sort’ from incompatible pointer type [enabled by default]
list.h:54:6: note: expected ‘int (*)(void *, void *)’ but argument is of type ‘int (*)(struct notification *, struct notification *)’
CC -c list.c
CC -c dunst_dbus.c
dunst_dbus.c:78:5: warning: string length ‘1627’ is greater than the length ‘509’ ISO C90 compilers are required to support [-Woverlength-strings]
CC -c ini.c
CC -o dunst

I noticed that Dunst eats my designated modifier key; even if there's no notification showing thus rendering that key useless in any other app.

I'm using DWM and Tmux (had the dunst modifier set to ctrl, making tmux useless)

Using the latest master (commit VERSION="pre-0.4.0") monitor specification is broken in dunstrc and the using the -mon command line option.

I have

monitor = 1

in my dunstrc but the notification shows up in monitor 0.
Invalid options like

monitor =  2 

do not produce error messages.

dunst -mon 1

produces this error.

dunst: unrecognized option '-mon'
usage: dunst [-h/--help] [-v] [-geometry geom] [-fn font] [-format fmt]
[-nb color] [-nf color] [-lb color] [-lf color] [-cb color] [ -cf color]
[-to secs] [-lto secs] [-cto secs] [-nto secs] [-key key] [-history_key key] [-all_key key] [-mon n]  [-follow none/mouse/keyboard] [-config dunstrc]

Hello,

can you please somewhere publish latest release tarball (and future ones)? Github downloads page should be ok.

I am going to create package for Fedora now. Thanks.

I'd love it if there was a way to have a single line mode. I set geometry to one line, which works great! But would there be a way to have "single_mode = true" and that notification, if enabled, would be pushed to the right (or left?) of the notification?

Hello,

review is good, I only need to add Fedora specific CFLAGs, would you mind including EXTRACFLAGS on the CFLAGS line, so I would be able to send them there?

It should be in the very end of the line:

CFLAGS=.... ${EXTRACFLAGS}

Thanks

it would be cool if dunst decided that the user was inactive (e.g. no key presses within a certain time) it could make all new alerts sticky so they'd still be there when you come back.

Not sure if X has a library for easily detecting inactivity.

Make it possible to have the window fit to the length of the notification until len > max_with and start wordwrapping then..

There is no package for libiniparser in Debian so the config file version of dunst cannot be built without first building libiniparser.

The build error looks like this for reference.

make
dunst build options:
CFLAGS   = -g -ansi -pedantic -Wall -Os -I/usr/X11R6/include -I/usr/lib/dbus-1.0/include -I/usr/include/dbus-1.0 -I/usr/include/freetype2 -D_BSD_SOURCE -DVERSION="" -DXINERAMA
LDFLAGS  = -L/usr/X11R6/lib -lX11 -lXext -lXss -ldbus-1 -lXft -lXrender -lfreetype -lz -lfontconfig -lpthread -liniparser -lrt -lXinerama
CC       = cc
CC -c dunst.c
dunst.c:18:23: fatal error: iniparser.h: No such file or directory
compilation terminated.
make: *** [dunst.o] Error 1

The libiniparser source can be found here for anyone who wants to build it themselves.
http://ndevilla.free.fr/iniparser/

dmenu with the height patch allows for you to set a height in pixels.

Hey Knopwob,

I recently started using dunst-light and I have two remarks:

1. The licensing isn't on par with the licensing you use on Master
2. Can you implement the Dropbox notifications on this branch as well? It requires an updated dunst_dbus.c. To be precise, this one: https://github.com/Unia/dunst-xft/blob/master/dunst_dbus.c

Hey,

There was a reaction to my ITP-bug in Debian: somebody wondered what parts of the notification spec dunst implements. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678445#10 — you can download the conversation in mbox format and directly reply via email. In case that’s not practical for you, I can also forward any answer you give in this github issue.

Thanks!
Best regards,
Michael

I use http://neo-layout.org which has 'grave' bound to the third level of the z key.

xmodmap says:

xmodmap -pke | grep 'z Z'
keycode  56 = z Z grave Greek_zeta Undo Redo U2124

When dunst is running, ctrl+z is not available anymore. This is because you resolve the Keysym to a Keycode using XKeysymToKeycode without taking care about the level on which the Keysym is found. I’m not familiar enough with Xlib to provide any more hints.

The correct way to handle it would be to check only the first level, unless shift is specified as a modifier, in which case you should check the second level. In i3, the relevant function is http://code.stapelberg.de/git/i3/tree/src/config.c?h=next#n108

And this is the fix:

pod2man --name=%{name} -c "Katello Reference" --section=1 --release=%{version} - man/katello-configure.man1

(replace name and version with real name and VERSION as well as "Katello" strings)

http://i.imgur.com/d9pOQ.png I have a script that notifies on song change, and I use little note blocks from unicode (that work fine elsewhere).

This is with the changes I had made, but I don't think that bit should make a difference.

[global]
    font = -*-terminus-medium-r-*-*-12-*-*-*-*-*-*-*

    # The format of the message. Possible variables are:
    #   %a  appname
    #   %s  summary
    #   %b  body
    #   %i  iconname (including its path)
    #   %I  iconname (without its path)
    format = "%I %s %b"

    # Sort messages by urgency
    sort = yes

    # Show how many messages are currently hidden (because of geometry)
    indicate_hidden = yes

    # If indicate_hidden is set to yes, this will show the (x more) on
    # the same line as the notification, and will force only notification
    # to be shown at a time.
    single_line = yes

    # keybindings to remove notification
    # available modifiers are 'ctrl', 'mod1' (the alt-key), 'mod2', 'mod3'
    # and 'mod4' (windows-key)
    modifier = mod4

    # use xev to find the names for keys
    key = c
    # key to redisplay last message(s)
    history_key = grave


    # the geometry of the window
    # geometry [{width}]x{height}][+/-{x}+/-{y}]
    # The geometry of the message window.
    # The height is measured in lines everything else in pixels. If the width
    # is omitted but the height is given ("-geometry x2"), the message window
    # expands over the whole screen (dmenu-like). If width is 0,
    # the window expands to the longest message displayed.
    # A positive x is measured from the left, a negative from the
    # right side of the screen.  Y is measured from the top and down respectevly.
    geometry = "0x3"

    # 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 = 120

[urgency_low]
    # IMPORTANT: colors have to be defined in quotation marks.
    # Otherwise the '#' and following  would be interpreted as a comment.
    background = "#222222"
    foreground = "#ababab"
    timeout = 3

[urgency_normal]
    background = "#222222"
    foreground = "#ababab"
    timeout = 3

[urgency_critical]
    background = "#ababab"
    foreground = "#222222"
    timeout = 5

Did some reading and apparently utf-8 + c isn't always nice. Hope to see it in the future. Again, will try to mess with the code some to get it to work if I can.

Perhaps this is possible outside of Dunst using xrandr to set the primary monitor but at the moment, Dunst always displays on my left-hand monitor which I am not normally focused on.

Is it possible to change the monitor?

Dropbox is unable to send notifications, because it relies on org.freedesktop.DBus.Introspectable.Introspect.

This should be fixed in Master; Waiting for confirmation.

http://www.galago-project.org/specs/notification/0.9/x408.html#signal-notification-closed

I've compiled Dunst on my own on Ubuntu 12.04 with development libraries found in official repository. After starting it (either by command or automatically from my i3 window manager config file) program works fine for random period of time, usually more than few hours, and then just crashes with the following message:

X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  53 (X_CreatePixmap)
  Value in failed request:  0x0
  Serial number of failed request:  3767
  Current serial number in output stream:  3773

Some notifications would include how long it has been since they were originally sent. I'd expect this to be useful in several situations, such as when you have been idle and have sticky messages remaining and also perhaps when you redisplay historical messages.

"Torrent Complete (5 min)"
"Battery Low (30 sec)"
"john: coming over (1 hour)"

This is inspired by new Mac OS notification center thing.

Sometimes you miss a message and it could be nice to have one of the following:

1- a keybinding to redisplay last message

2- a command to communicate with the running dunst and tell it to redisplay the last n messages. "dunst --last 5" or something would redisplay them. dunst would have a setting of how many messages to remember.

The easiest solution is probably just for me to log everything to a temp file and check there. Thought I'd share the idea anyway though.

you must find better way to bind your keys. if my modifier is ctrl then i can not do ctrl+c or any other ctrl+ hotkeys..
i use many programs that works with keybinding so i don't want to lose a key..

as a quick workstation i disabled all dunst's keybindings..

I'm not sure if I'm supposed to type modifier = super or modifier = win or modifier = Mod4Mask, so might be nice to have the various popular ones in a comment above this line in the example config.

Btw, since you've implemented all my suggestions I'm probably going to be creating several new issues here :)

Display the notifications on the monitor that currently has the focus. This may either be the monitor that contains the mouse cursor or the monitor containing the window with the keyboard focus (configurable).

The implementation of this feature depends on wether there is a nice way to get the needed information.

Hi,

is it possible to filter out messages that match a pattern? E.g. never showing messages that matches in the summary filed
:irssi: &bitlbee: root.

I know you can make rules based on matching but I don't know how to then take the action of filtering the message out. Setting the timeout to 0 will not have that effect.

Without digging into src yet, I think it calculates its width at start and then keeps it through lifespan. It probably should recalculate things at some RandR or other applicable event.

I'm using:

geometry = "x10-0+25"

currently:

-lb/nb/cg

should be cb not cg

Very minor, great util, thanks!

Hey,

I looked at your code to use $XDG_CONFIG_HOME, and unfortunately it is missing a lot of things:

• There is no fallback for $XDG_CONFIG_HOME to ~/.config, as described by the spec
• There is no fallback to $XDG_DATA_DIRS
• There is no fallback to sysconfdir (/etc)
• You don’t distribute your example config file in /etc

In case you want to fix this yourself, have a look at http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html and http://code.stapelberg.de/git/i3/tree/src/config.c#n175 (which is slightly more complex since it has override_config_path, which you can ignore).

I could also submit a patch in case you’re ok with it.

Best regards,
Michael

see: http://www.galago-project.org/specs/notification/0.9/x161.html

dunst keeps crashing on me with a Segmentation fault.

I am not sure how to build a debug version of dunst to get a backtrace but if you walk me through it I can get one for you.

If incoming notifications were a map it would be cool if they passed through a series of middleware functions that could return a possibly changed map. With C not sure how this would work, perhaps the middleware would have to be added at compile time.

Here are a few examples of things that could be middleware:

• Change critical level messages from some app or containing some text to normal level
• Increase duration on notifications from some app
• Change sticky notifications (-t 0?) from some app to non-sticky
• Set colors for notifications from some app
• Determine if user is active and optionally set notification to be sticky
• Rewrite the text of a notification from some app to be more succinct/better formatted.