GNOME Bugzilla – Bug 622021
Closed signal is not emitted when the screensaver si active
Last modified: 2010-06-24 04:32:18 UTC
I'm connecting to closed signal to do some operations but if I have the screensaver active it is not emitted
The problem is: I show the notification (pynotify) but it is not shown because the screensaver is active then the closed signal is never emitted. Perhaps libnotify should tell me that the notification cannot be shown...
libnotify has no concept of the screensaver being on or not. All the "do not disturb" code lives in notification-daemon. There are multiple ways we could handle this: - return an error from notify_notification_show(), but this would usually imply a severe failure - send a close signal as soon as done dealing with the "Show" call In any case, barring a change in the spec, this should be done in the notification-daemon.
Created attachment 164464 [details] [review] Send Close when notification isn't shown When a notification comes in and we have the screensaver or a fullscreen application showing, we never actually show the popup, and the application will not receive a "Close" notification. Change this so that the close notification is the first thing we send out after being done dealing with the requested notification.
Note that bug 608068 requests for the popups to be deferred, but that's not really possible without a change in the spec.
Probably should keep track of that idle source but probably isn't a huge deal. Pushed thanks.