You are not logged in.

#1 2011-01-28 17:13:06

flan_suse
Member
Registered: 2010-10-28
Posts: 120

Wicd stopped working, had to reinstall the package. Unknown cause...

Something strange happened recently on my setup. The Wicd client, and even wicd-curses, complained about not being able to connect to the Wicd daemon. I  tried restarting the daemon, which reported success, but I still could not use Wicd. I then deleted /etc/wicd/* and /etc/dbus-1/system.d/wicd.conf, restarted the daemon, but still no success. It appeared that the daemon was not running. Even if I rebooted into runlevel 3, the same problem still happened.

I tried some solutions on this board, since others went through similar problems, but they made no difference. So I manually configured my network interface, hooked it up to a wired connection, removed the wicd package and it's dependencies (-Rs wicd), and then reisntalled the wicd package (I had cleaned my pacman cache earlier). Without having to reboot or revisit /etc/rc.conf or /etc/wicd/*, it began working again.

I'm just not sure what caused this problem to occur in the first place. I was using Wicd just fine, up to that point, and I had not touched anything under rc.conf, /etc/wicd/, or /etc/dbus-1/ anyways. Even after the major upgrade to Xfce (4.6 -> 4.8), Wicd was working like normal.

If anyone has the same issue, it doesn't hurt to try reinstalling the wicd package and its dependencies.

Last edited by flan_suse (2011-01-28 17:15:57)

Offline

#2 2011-01-28 17:39:37

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: Wicd stopped working, had to reinstall the package. Unknown cause...

maybe you should check your logs which might be able to throw more light on the issue.


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#3 2011-01-28 18:16:38

flan_suse
Member
Registered: 2010-10-28
Posts: 120

Re: Wicd stopped working, had to reinstall the package. Unknown cause...

The only thing of interest was the same output trying to run wicd-curses already showed me anyways. This repeats in the log file:

2011/01/27 21:16:52 :: Traceback (most recent call last):
2011/01/27 21:16:52 ::   File "/usr/share/wicd/daemon/wicd-daemon.py", line 1839, in <module>
2011/01/27 21:16:52 ::     main(sys.argv)
2011/01/27 21:16:52 ::   File "/usr/share/wicd/daemon/wicd-daemon.py", line 1802, in main
2011/01/27 21:16:52 ::     wicd_bus = dbus.service.BusName('org.wicd.daemon', bus=bus)
2011/01/27 21:16:52 ::   File "/usr/lib/python2.7/site-packages/dbus/service.py", line 129, in __new__
2011/01/27 21:16:52 ::     retval = bus.request_name(name, name_flags)
2011/01/27 21:16:52 ::   File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 306, in request_name
2011/01/27 21:16:52 ::     'su', (name, flags))
2011/01/27 21:16:52 ::   File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
2011/01/27 21:16:52 ::     message, timeout)
2011/01/27 21:16:52 :: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.3" is not allowed to own the service "org.wicd.daemon" due to security policies in the configuration file

After doing the steps in the first post, nothing worked until I reinstalled the wicd package. Sometimes it's quicker to try the simple solutions first, since it got me back to where I left off without needing to mess with different files and configs. I want to also add that I did not mess with anything dbus-related, so this sudden issue with Wicd took my by surprise.

I even tried the solution posted in this thread: https://bbs.archlinux.org/viewtopic.php?id=111131

Last edited by flan_suse (2011-01-28 18:23:41)

Offline

Board footer

Powered by FluxBB