ActionInvoked and NotificationClosed signals alwas have zero ID
Bug #410870 reported by
Oben Sonne
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
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
NonfreeKernelMo
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
Changed in notify-osd (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Incomplete |
To post a comment you must log in.
Just recognized that already the return value of org.freedesktop .Notifications. Notify( ), the notification's ID, is always zero.