retitle 588205 client throws exception with libnotify 0.5.0 severity 588205 important thanks
On Tue, 06 Jul 2010 13:06:48 +0200, Yves-Alexis Perez wrote: > On 06/07/2010 09:11, David Paleino wrote: > > Another path of investigation, the most probable one, is some issue in > > python-notify/libnotify. > > I currently don't have a stable DSL connection -- I'm on dialup -- this is > > why I haven't upgraded my sid (yet), and I still have libnotify 0.4.5. I > > see that sid has 0.5.0, so that's why it still works here, but not for you. > > > > Just to be sure, what happens if you downgrade libnotify? snapshot.d.o has > > 0.4.5-1, just to check. :) > > It seems to fix the problem yes, so it might need porting. Should the > severity be raised? I believe so, but I'm not raising that to RC yet. This is because I believe it could be pynotify's fault (source package notify-python). However, I need to make a small example showing the bug, before claiming that. And, maybe, just wrap the notification code inside a try..except, to handle it more gracefully (notifications aren't essential for the functioning of the client). Have a nice day, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
