-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
notifications fail after a certain number have been shown #1
Comments
From googling around, it looks like you can send a maximum of 20 notifications. A user has to acknowledge them before you can send more. Two thoughts on how to get past this
|
If those options don't work, could we automate an acknowledgement? By
|
I suppose we could use something like PyUserInput, but at that point we're piling hacks on notify2/libnotify. Instead, we could display/control our notifications using pygame or something. A SimpleCV rewrite would also fix this. |
Agreed, I hope one of your first suggestions work for the time being.
|
What notification daemon are you using? It appears there's varying support for timeouts and closing across notification daemons. xfce4-notifyd seems to support it, while notify-osd and notification-daemon don't (not supporting it is a "feature"). I was able to spawn 40 notifications by manually closing them after a second using xfce4-notifyd:
|
I'll check when I get home, whatever was preinstalled though
|
looks like: notify-osd dpkg --list|grep notify James On Fri, Aug 30, 2013 at 7:39 PM, James Hice jameshice@gmail.com wrote:
|
Try uninstalling that and installing xfce4-notifyd |
Just committed a simplecv-based photobooth; it draws its own notifications to get around this issue. |
Sweet. Does this need the camera to show up as /dev/video0 ?
|
Yes, I think so. I don't have a raspberry pi, so I had to test it with my
|
Ok I think I already did what is needed to get that to work and may need to
|
The drivers needed are with uv4l-raspicam or something like that I do like this way of notifications a lot better though
|
from google'ing around it looks like a known issue, i didn't see any solutions so far but if there is a way to close or clear the queue that might work?? not really sure
Traceback (most recent call last):
File "/home/pi/projects/pibooth/master/notify_screen.py", line 3, in
countdown_notify()
File "/home/pi/projects/pibooth/master/pibooth_notifications.py", line 26, in countdown_notify
notify2.Notification(str(x),cdtext).show()
File "/usr/lib/python2.7/dist-packages/notify2.py", line 188, in show
self.timeout, # expire_timeout
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in call
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications
^CTraceback (most recent call last):
File "./buttonboothtest.py", line 52, in
time.sleep(0.05)
KeyboardInterrup
possible helpful links include but aren't limited to:
https://notify2.readthedocs.org/en/latest/ <--docs for the notify2 library
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648378
http://dbus.freedesktop.org/doc/dbus-daemon.1.html
http://forums.debian.net/viewtopic.php?f=6&t=67703
The text was updated successfully, but these errors were encountered: