wicd freezes and throws error about dbus

TheBukwus · 2011-08-18 05:30:35

I recently installed Arch Linux on a new netbook, and all seems well except the following: when attempting to connect to a wireless network using wicd-curses, the system freezes for about thirty seconds and wicd-curses crashes with the error below. However, wicd has successfully connected to the network and seems to work without problem from then on.

DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
    self.update_ui(True)                                
  File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 915, in update_ui
    self.handle_keys(input_data[1])
  File "/usr/share/wicd/curses/wicd-curses.py", line 836, in handle_keys
    self.connect("wireless",pos)
  File "/usr/share/wicd/curses/wicd-curses.py", line 929, in connect
    wireless.ConnectWireless(networkid)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 143, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Output of "lspci | grep -i net"

01:00.0 Ethernet controller: Atheros Communications AR8152 v1.1 Fast Ethernet (rev c1)
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000

Thanks for the help!

Meyithi · 2011-08-18 05:50:19

Start the dbus daemon before the wicd one, and don't @ it.

TheBukwus · 2011-08-18 06:11:49

I can confirm that dbus is in fact running.
Here's the daemons array: DAEMONS=(syslog-ng dbus !network wicd netfs crond @cpufreq slim)

And the output of "rc.d list"

[STOPPED][    ] adsl
[STOPPED][    ] alsa
[STOPPED][    ] avahi-daemon
[STOPPED][    ] avahi-dnsconfd
[STOPPED][AUTO] cpufreq
[STARTED][AUTO] crond
[STARTED][AUTO] dbus
[STOPPED][    ] git-daemon
[STOPPED][    ] gpm
[STOPPED][    ] hwclock
[STOPPED][    ] ifplugd
[STOPPED][    ] krb5-kadmind
[STOPPED][    ] krb5-kdc
[STOPPED][    ] mdadm
[STOPPED][    ] mpd
[STOPPED][    ] net-auto-wired
[STOPPED][    ] net-auto-wireless
[STOPPED][    ] net-profiles
[STOPPED][    ] net-rename
[STARTED][AUTO] netfs
[STOPPED][    ] network
[STOPPED][    ] nscd
[STOPPED][    ] ppp
[STOPPED][    ] rfkill
[STARTED][AUTO] slim
[STOPPED][    ] sshd
[STARTED][AUTO] syslog-ng
[STARTED][AUTO] wicd

lolilolicon · 2011-08-18 06:32:23

First confirm that wicd is running (`ps aux | grep wicd`).
Also take a look at /var/log/wicd/wicd.log and /var/log/kernel.log. Enabling "verbose" option for wicd helps further debugging, too.
I also suspect that maybe your hostname settings are not correct. Did you configure your localhost hostname in /etc/hosts to match the one in rc.conf?

Last edited by lolilolicon (2011-08-18 06:35:32)

TheBukwus · 2011-08-18 08:23:58

wicd is running, hostnames match, and neither log give any indication of an error.

Let me clarify, wicd successfully connects and is generally functional. The problem is that every time I connect to a network, the system freezes for about 30 seconds and then the dbus error is displayed. After that everything works fine. Searching the web failed to turn up anything helpful.

lolilolicon · 2011-08-18 09:03:31

So the problem is reproducible everytime you connect to a network throught wicd-curses, right?
Try restarting the daemons: stop wicd, dbus, then start dbus, wicd, in that order.

If that didn't help:
- Try enabling debug: run wicd-curses, press P, select the "Advanced Settings" tab, and check "enable debug mode". Then, try to reproduce the behavior and see if there's anything useful added to wicd.log.
- Make sure your mirror is up to date and run `pacman -Syyu`.
- If you did a system update and haven't rebooted, try rebooting.
- Try networkmanager or netcfg.

mattfitz · 2011-08-22 01:57:52

I have been experiencing the same 20-30 second system freeze. The wicd log indicated a long delay after "ifconfig eth0 up/down", and running the command alone in the terminal reproduced the same freeze. For now, removing the wired interface from wicd in settings prevents the issue, but perhaps someone more knowledgeable than I might shed light on what causes this hang in the first place.

Arch Linux

#1 2011-08-18 05:30:35

wicd freezes and throws error about dbus

#2 2011-08-18 05:50:19

Re: wicd freezes and throws error about dbus

#3 2011-08-18 06:11:49

Re: wicd freezes and throws error about dbus

#4 2011-08-18 06:32:23

Re: wicd freezes and throws error about dbus

#5 2011-08-18 08:23:58

Re: wicd freezes and throws error about dbus

#6 2011-08-18 09:03:31

Re: wicd freezes and throws error about dbus

#7 2011-08-22 01:57:52

Re: wicd freezes and throws error about dbus

Board footer