On 06/07/2010 09:11, David Paleino wrote: > On Tue, 06 Jul 2010 07:51:36 +0200, Yves-Alexis Perez wrote: > >> Package: wicd-gtk >> Version: 1.7.0+ds1-5 >> Severity: normal >> >> Hey, > > Hello, > >> ---- >> cor...@hidalgo: wicd-client >> Has notifications support True >> Loading... >> Connecting to daemon... >> Connected. >> Traceback (most recent call last): >> File "/usr/share/wicd/gtk/wicd-client.py", line 1034, in <module> >> main(sys.argv) >> File "/usr/share/wicd/gtk/wicd-client.py", line 91, in wrapper >> return func(*args, **kwargs) >> File "/usr/share/wicd/gtk/wicd-client.py", line 1006, in main >> tray_icon = TrayIcon(animate, displaytray=display_app) >> File "/usr/share/wicd/gtk/wicd-client.py", line 139, in __init__ >> self.icon_info = self.TrayConnectionInfo(self, self.tr, animate) >> File "/usr/share/wicd/gtk/wicd-client.py", line 198, in __init__ >> self.update_tray_icon() >> File "/usr/share/wicd/gtk/wicd-client.py", line 91, in wrapper >> return func(*args, **kwargs) >> File "/usr/share/wicd/gtk/wicd-client.py", line 349, in update_tray_icon >> self.set_wireless_state(info) >> File "/usr/share/wicd/gtk/wicd-client.py", line 91, in wrapper >> return func(*args, **kwargs) >> File "/usr/share/wicd/gtk/wicd-client.py", line 289, in set_wireless_state >> 'network-wireless') >> File "/usr/share/wicd/gtk/wicd-client.py", line 233, in _show_notification >> self._last_bubble.show() >> glib.GError: Unable to connect to server >> ---- >> >> wicd-curses connects fine, so wicd server is ok. I'm not exactly sure what >> happens there, if you need more info, please ask. > > To exclude DBus issues, would you please run: > > $ dbus-send --print-reply --system --dest=org.wicd.daemon /org/wicd/daemon \ >> org.wicd.daemon.Hello
cor...@hidalgo: dbus-send --print-reply --system --dest=org.wicd.daemon /org/wicd/daemon org.wicd.daemon.Hello method return sender=:1.960 -> dest=:1.979 reply_serial=2 string "1.7.0" So I guess it works fine. > > ? I don't believe it's DBus-related, since wicd-curses works fine, but better > safe than sorry :) > > 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? Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
