Notifications pixmaps are broken sometimes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Polly |
New
|
Undecided
|
Unassigned |
Bug Description
Apparently, sometimes there is a problem with the pixmaps in notifications. I have enabled notifications for every tweet and message, and with about 75% of the displayed notifications, awesome (which implements the org.freedesktop
Oops, an error happened!
/usr/
Some notifications will be rendered as expected though. I have the feeling that it is related to the user avatars, as all the error messages are tweets from the same group of users, and the notifications which are displayed correctly are all messages from a disjoint set of users.
(I have not tested it with notify-osd or any other libnotify server implementation, so this could also be related to awesome. Maybe someone could say if the bug also occurs with other implementations.)
awesome:
Installed: 3.4.12-2
Candidate: 3.4.12-2
Version table:
*** 3.4.12-2 0
500 http://
1 http://
100 /var/lib/
polly:
Installed: 0.93.4-
Candidate: 0.93.4-
Version table:
*** 0.93.4-
500 http://
100 /var/lib/
python-notify:
Installed: 0.1.1-3
Candidate: 0.1.1-3
Version table:
*** 0.1.1-3 0
500 http://
1 http://
100 /var/lib/
Marking as incomplete until someone can confirm the problem is not on awesome. I have never heard about this from users of other notification services.
Roland, maybe you could contact the awesome developers to learn what that line means?