[Solved]Problem with Wicd and D-bus

Philip J. Fry · 2009-06-19 19:31:25

I get this error at login:

"could not connect wicd d-bus interface. Check thw wicd log for error messages"

I restarted both wicd and dbus demons, but didnt work.

bash-3.2# wicd-client
Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Connected.
ERROR:dbus.proxies:Introspect error on :1.29:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.29 was not provided by any .service files
warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.29 was not provided by any .service files
bash-3.2#

Last edited by Philip J. Fry (2009-06-29 20:05:33)

Philip J. Fry · 2009-06-21 14:57:18

Downgrading the package failed, same problem.

R00KIE · 2009-06-21 15:22:07

Did you make sure hal is started _before_ you try to start the wicd daemon?

Philip J. Fry · 2009-06-21 19:16:32

Hal is normally started, I didnt change anything...and hal daemon is started *before* wicd...

R00KIE · 2009-06-21 20:22:11

Then the only thing I can think of is that for some reason the wicd daemon isn't running due to so problem, check the logs and see if you can find anything that looks suspicious.

skottish · 2009-06-21 20:43:22

It isn't starting as a regular user here. Also, there's a bug report filed against it that's probably related:

http://bugs.archlinux.org/task/15089

panosk · 2009-06-23 10:23:38

Same problem here with KDE. The only version that works fine for me is 1.5.9. Try downgrading to this package.

R00KIE · 2009-06-23 17:46:38

It starts fine here on xfce, but I think I've seen a report of the latest wicd not working fine on xfce.

Philip J. Fry · 2009-06-26 12:17:32

I still cannot connect! Will it be solved?

barzam · 2009-06-26 13:32:14

Have you tried what the wiki suggests?
http://wiki.archlinux.org/index.php/Wic … ormal_User

Philip J. Fry · 2009-06-26 17:30:30

I did it.

bash-3.2# wicd-client
Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Wicd daemon is shutting down!
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 826, in <module>
main(sys.argv)
File "/usr/lib/wicd/wicd-client.py", line 88, in wrapper
return func(*args, **kwargs)
File "/usr/lib/wicd/wicd-client.py", line 798, in main
tray_icon = TrayIcon(animate)
File "/usr/lib/wicd/wicd-client.py", line 128, in __init__
self.icon_info = self.TrayConnectionInfo(self.tr, animate)
File "/usr/lib/wicd/wicd-client.py", line 164, in __init__
self.set_not_connected_state()
File "/usr/lib/wicd/wicd-client.py", line 88, in wrapper
return func(*args, **kwargs)
File "/usr/lib/wicd/wicd-client.py", line 254, in set_not_connected_state
self._show_notification(language['disconnected'], None, 'stop')
File "/usr/lib/wicd/wicd-client.py", line 169, in _show_notification
self._last_bubble = pynotify.Notification(title, details,
NameError: global name 'pynotify' is not defined
bash-3.2#

Philip J. Fry · 2009-06-29 20:05:12

Solved with
pacman -R wicd
rm -rf /etc/wicd /var/log/wicd /etc/dbus-1/system.d/wicd
pacman -S wicd

Wildgoose · 2009-07-01 16:31:44

Philip's solution wasn't complete for me.

You also need to ensure that you have installed the notification-daemon package, as seen here: http://bugs.archlinux.org/task/15089

If you still have problems, also look here with regards to connecting as a normal user: http://wiki.archlinux.org/index.php/Wic … ormal_User

1LordAnubis · 2009-07-09 21:58:45

If I'm running kdm, I have no issue at all with wicd-client loading, however if I log into a wm/de (usually openbox) without kdm running wicd-client will not load, even after trying the above solutions....

Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...

(gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
Connected.
ERROR:dbus.proxies:Introspect error on :1.10:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=19009 comm="python -O /usr/lib/wicd/wicd-client.py ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.10" (uid=0 pid=19066 comm="python -O /usr/lib/wicd/wicd-daemon.py "))
warning: ignoring exception org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=19009 comm="python -O /usr/lib/wicd/wicd-client.py ") interface="org.wicd.daemon" member="GetConnectionStatus" error name="(unset)" requested_reply=0 destination=":1.10" (uid=0 pid=19066 comm="python -O /usr/lib/wicd/wicd-daemon.py "))
warning: ignoring exception org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=19009 comm="python -O /usr/lib/wicd/wicd-client.py ") interface="org.wicd.daemon" member="GetNeedWiredProfileChooser" error name="(unset)" requested_reply=0 destination=":1.10" (uid=0 pid=19066 comm="python -O /usr/lib/wicd/wicd-daemon.py "))
anubis@thor ~/ $

rdmelin · 2009-07-10 22:54:57

Try adding this to autostart.sh

# D-bus
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
       eval `dbus-launch --sh-syntax --exit-with-session`
fi

1LordAnubis · 2009-07-12 20:33:05

Note: Solved by adding my user to the users group, and restarting dbus/wicd

h2vnteam · 2009-12-31 05:01:21

I had the same problem when I start my DE by startx, and tried those solutions mentioned above but didn't help anyway. Now, I start my DE by xinit, wicd works like a charm.

Thanks for your concern mates!

Arch Linux

#1 2009-06-19 19:31:25

[Solved]Problem with Wicd and D-bus

#2 2009-06-21 14:57:18

Re: [Solved]Problem with Wicd and D-bus

#3 2009-06-21 15:22:07

Re: [Solved]Problem with Wicd and D-bus

#4 2009-06-21 19:16:32

Re: [Solved]Problem with Wicd and D-bus

#5 2009-06-21 20:22:11

Re: [Solved]Problem with Wicd and D-bus

#6 2009-06-21 20:43:22

Re: [Solved]Problem with Wicd and D-bus

#7 2009-06-23 10:23:38

Re: [Solved]Problem with Wicd and D-bus

#8 2009-06-23 17:46:38

Re: [Solved]Problem with Wicd and D-bus

#9 2009-06-26 12:17:32

Re: [Solved]Problem with Wicd and D-bus

#10 2009-06-26 13:32:14

Re: [Solved]Problem with Wicd and D-bus

#11 2009-06-26 17:30:30

Re: [Solved]Problem with Wicd and D-bus

#12 2009-06-29 20:05:12

Re: [Solved]Problem with Wicd and D-bus

#13 2009-07-01 16:31:44

Re: [Solved]Problem with Wicd and D-bus

#14 2009-07-09 21:58:45

Re: [Solved]Problem with Wicd and D-bus

#15 2009-07-10 22:54:57

Re: [Solved]Problem with Wicd and D-bus

#16 2009-07-12 20:33:05

Re: [Solved]Problem with Wicd and D-bus

#17 2009-12-31 05:01:21

Re: [Solved]Problem with Wicd and D-bus

Board footer