[SOLVED] wicd-client problem

brixtoncalling · 02-28-2010, 01:08 PM

Hello all...

All of a sudden, wicd-client wont start. It spits out the following error messages:

Code:

Has notifications support True
Loading...
Connecting to daemon...
Connected.
Traceback (most recent call last):
  File "/usr/share/wicd/gtk/wicd-client.py", line 1033, 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 1005, 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 347, in update_tray_icon
    self.set_wired_state(info)
  File "/usr/share/wicd/gtk/wicd-client.py", line 259, in set_wired_state
    'network-wired')
  File "/usr/share/wicd/gtk/wicd-client.py", line 233, in _show_notification
    self._last_bubble.show()
glib.GError: The name org.freedesktop.Notifications was not provided by any .service files

I'm running current, but the last update that I installed was the one which moved us to KDE 4.3.4 (which was ages ago). Wicd-client only stopped working a couple of days ago and I can't think of what I could have done EXCEPT that I compiled a new kernel, ran it, didn't like it and went back to 2.6.29.6. I think wicd-client started failing after that.

I tried reinstalling and upgrading to wicd 1.7 but to no avail. Wicd-curses does work though...

Any ideas? Thanks!

PTrenholme · 02-28-2010, 01:59 PM

The freedesktop.Notifications.service should be in the dbus-1 list (/usr/share/dbus-1/services/org.freedesktop.Notifications.service). Perhaps the dbus service isn't running, or you (inadvertently) reconfigured the dbus whilst playing with your kernel(s).

brixtoncalling · 03-02-2010, 11:39 PM

I was away from the internet for a few days, but thanks belatedly for the answer.

So... the file org.freedesktop.Notifications.service does not exist. How should I get it back?

PTrenholme · 03-03-2010, 01:48 PM

First, please note that I'm not using a Slackware system, so the specifics may differ.

That said, the d-bus file is a simple ASCII text file:

Code:

$ cat /usr/share/dbus-1/services/org.freedesktop.Notifications.service
[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/libexec/notification-daemon

But the daemon is an executable:

Code:

$ file /usr/libexec/notification-daemon 
/usr/libexec/notification-daemon: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped

I believe you need to "emerge" the notification service which should fix your problem. But that belief is, as I said, based on speculation, not knowledge.

Chuck56 · 03-03-2010, 02:27 PM

Quote:

Originally Posted by brixtoncalling

I tried reinstalling and upgrading to wicd 1.7 but to no avail. Wicd-curses does work though...

Any ideas? Thanks!

I had a similar problem with wicd after my -current upgrade yesterday. My initial solution was to uninstall wicd and use inet1.conf and dhcpcd which worked.

Today I decided to give wicd another try. Prior to reinstalling wicd I searched for wicd in in the contents of the /var/log/packages files and noticed that KDE4 had 2 files that had wicd in their names. I left those files alone.

Next I ran updatedb and then slocate wicd and found a lot of directories and files with wicd in the name. The directories and files were scatted in many different locations and I deleted them all except the KDE4 files I found above.

I reset my /etc/rc.d/rc.inet1.conf back to empty values so dhcpcd wouldn't start back up. I installed wicd-1.7.0 using slackpkg and then rebooted. When it came back up I opened the wicd-client from the system tray, scanned and had to reset my AP's values. Wicd works as expected now.

YMMV!

brixtoncalling · 03-04-2010, 12:46 PM

Thanks for the answer Chuck. I tried what you recommended but no luck. Perhaps I didn't do everything right since i don't have an inet2.conf file. Should I?

Chuck56 · 03-04-2010, 12:54 PM

Quote:

Originally Posted by brixtoncalling

Thanks for the answer Chuck. I tried what you recommended but no luck. Perhaps I didn't do everything right since i don't have an inet2.conf file. Should I?

What was I thinking? I meant to type "/etc/rc.d/rc.inet1.conf". I corrected my post above.

grissiom · 03-05-2010, 06:49 AM

After upgrading to alien's KDE4.4.1( http://alien.slackbook.org/ktown/4.4.1/ ), this problem gone.

brixtoncalling · 03-07-2010, 01:27 PM

I'm not caught up with -current yet and I haven't installed KDE 4.4... In any case, why would upgrading KDE to 4.4.1 affect wicd?

grissiom · 03-07-2010, 11:26 PM

I'm not an expert in KDE or dbus or stuff like that. But I guess KDE4.4 can provide org.freedesktop.Notifications service which is not provided by KDE4.3. Have you tried XFce or other DEs?

brixtoncalling · 03-11-2010, 01:05 PM

I took this up again today and found that I could run wicd-client as long as I used the -n option (disabling the tray applet). In the end, I got it working by erasing the ~/.wicd directory. There were empty USE_NOTIFICATIONS and CLIENT_CURSES_WARNING files which apparently were causing wicd-client to crash on running.

UnIxBG · 02-03-2012, 05:19 AM

I had same error, simply remove .wicd "rm -r ~/.wicd" or "rm -r $home/.wicd" without quotes.