state of notification
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Hi, there is no working way to get state of notification. Signal 'closed' does not work. For my app, I need to know if my notification is being displayed, so I do not display other notifications
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: notify-osd 0.9.35daily12.
ProcVersionSign
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Fri Feb 22 19:48:48 2013
DesktopSession: 'ubuntu'
EcryptfsInUse: Yes
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2012-12-07 (77 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121207)
MachineType: LENOVO 208253G
MarkForUpload: True
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=sk_SK.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu4
libgl1-mesa-glx 9.0.2-0ubuntu1
libdrm2 2.4.42-0ubuntu1
xserver-
xserver-
SourcePackage: notify-osd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET71WW (3.01 )
dmi.board.name: 208253G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 208253G
dmi.product.
dmi.sys.vendor: LENOVO
Changed in notify-osd (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!