ActionInvoked and NotificationClosed signals alwas have zero ID

[Oben Sonne]

Binary package hint: notify-osd

The ID parameter of DBus ActionInvoked and NotificationClosed signals is always zero. This way it is not possible to detect by which notification the signals have been caused.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: fglrx
Package: notify-osd 0.9.11-0ubuntu3
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: notify-osd
Uname: Linux 2.6.28-14-generic i686

[Oben Sonne (obensonne)]

Just recognized that already the return value of org.freedesktop.Notifications.Notify(), the notification's ID, is always zero.

[Mirco Müller (macslow)]

Oben, do you have example-code which exposes this failure? I've looked at notify-osd trunk and mined it with printf()s just to be sure and the notification IDs are valid (not 0). Have you tried it with notify-osd 0.9.16 or trunk? What's the result?

[Mirco Müller (macslow)]

It is a deliberate design-feature of notify-osd to not have close-buttons. See https://wiki.ubuntu.com/NotifyOSD#Bubble%20behavior

[Mirco Müller (macslow)]

Ignore my last comment... I had the wrong window focused when typing.

[Oben Sonne (obensonne)]

I'm using notify-osd 0.9.11 from Jaunty, so maybe this bug is outdated? I'll try again with the trunk version.

[Oben Sonne (obensonne)]

Just did a test with 0.9.23 from Karmic - there it works.