You are not logged in.

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

Philip J. Fry
Member
From: Torino, Italia
Registered: 2008-06-02
Posts: 18

[Solved]Problem with Wicd and D-bus

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)

Offline

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

Philip J. Fry
Member
From: Torino, Italia
Registered: 2008-06-02
Posts: 18

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

Downgrading the package failed, same problem.

Offline

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

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,218

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

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


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

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

Philip J. Fry
Member
From: Torino, Italia
Registered: 2008-06-02
Posts: 18

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

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

Offline

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

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,218

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

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.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

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

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,931

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

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

Offline

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

panosk
Member
From: Athens, Greece
Registered: 2008-10-29
Posts: 241

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

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

Offline

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

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,218

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

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


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

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

Philip J. Fry
Member
From: Torino, Italia
Registered: 2008-06-02
Posts: 18

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

I still cannot connect! Will it be solved?

Offline

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

barzam
Member
From: Sweden
Registered: 2009-01-27
Posts: 277

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

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

Offline

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

Philip J. Fry
Member
From: Torino, Italia
Registered: 2008-06-02
Posts: 18

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

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#

Offline

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

Philip J. Fry
Member
From: Torino, Italia
Registered: 2008-06-02
Posts: 18

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

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

Offline

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

Wildgoose
Member
Registered: 2009-07-01
Posts: 1

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

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

Offline

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

1LordAnubis
Member
Registered: 2008-10-10
Posts: 250
Website

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

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 ~/ $

Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw

Offline

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

rdmelin
Member
From: Ellensburg, WA, USA
Registered: 2007-08-27
Posts: 45

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

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

Offline

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

1LordAnubis
Member
Registered: 2008-10-10
Posts: 250
Website

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

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


Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw

Offline

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

h2vnteam
Member
From: Saigon - vietnam
Registered: 2009-09-23
Posts: 10
Website

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

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!

Offline

Board footer

Powered by FluxBB