[SOLVED] can't start wicd-client. python errors

leo2501 · 2009-02-25 10:03:29

when i run wicd-client it gives the following errors, but i can browse internet and such, because is like wicd works right, it seems that only the gui is broken...

[aleyscha@aleyscha 1 ~ 00:25]$ wicd-client 
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Traceback (most recent call last):
  File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
    import wicd.gui as gui
  File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 2006, in <module>
    setup_dbus()
  File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 174, in setup_dbus
    proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files

Last edited by leo2501 (2009-02-25 22:21:40)

Allan · 2009-02-25 10:13:27

Do you have dbus running?

leo2501 · 2009-02-25 10:20:18

yes...

[aleyscha@aleyscha 10 ~ 02:35]$ sudo /etc/rc.d/dbus start
:: Starting D-BUS system messagebus                                                                       [BUSY] Failed to start message bus: The pid file "/var/run/dbus.pid" exists, if the message bus is not running, remove this file
                                                                                                          [FAIL]

toad · 2009-02-25 10:29:40

A quick google came up with this - appears to have something to do with your problem:

http://wicd.sourceforge.net/punbb/viewtopic.php?pid=561

iosonofabio · 2009-02-25 12:25:16

The first errors are Xlib linked and have nothing to do with wicd in particular. After Traceback, have a look at the given reference.

scottuss · 2009-02-25 13:39:01

Are you sure D-Bus is actually running though? It looked to me as though it failed...

toad · 2009-02-25 13:42:28

Well, if dbus and hal are listed in the daemon array of rc.conf it is definitely worth a try commenting dbus out (since hal calls it up automagically).

yvonney · 2009-02-25 20:06:37

Yep, seems like lots of us are getting this.
I thought it was actually stopping scrot though the screen shot does occur. The message looks like it's fatal though.
i would have thought that scrot didn't start 'till i found screenshots.
wicd working here on fresh 2009.02.

I guess it'll be one of those that jst resolves itself soon.

Pretty certain you've seen all most all of these though put 'em here anyways:

http://lists.freedesktop.org/archives/x … 39132.html
http://lists.freedesktop.org/archives/x … 39131.html

http://bugs.archlinux.org/task/13223
http://bbs.archlinux.org/post.php?tid=66199

http://bbs.archlinux.org/viewtopic.php?id=65403

Last edited by yvonney (2009-02-25 20:09:33)

leo2501 · 2009-02-25 22:21:16

well after a really PAINFULL experience, i did a reboot (because when i get home the pc was nearly freezed, working slow and strange after the -Syu), first... a GRUB ERROR 2 after nearly died myself, i discover that i had the USB HD connected and the laptop want to boot from there... solved that i get a FILESYSTEM CHACK FAILED at boot, and after 2 reboots it checked the disk and booted... but now wicd-client WORKS AS ALWAYS

yvonney · 2009-02-25 22:58:14

hurray! yes, it's been an interesting few days of little errors. Iv'e got a few more still though loving the clean-ness of everything comparatively! I'll be writing good stuff soon! thanks! Wishing you a lovely warm evening etc. [no reply needed - life's busy enough] hehehe

Arch Linux

#1 2009-02-25 10:03:29

[SOLVED] can't start wicd-client. python errors

#2 2009-02-25 10:13:27

Re: [SOLVED] can't start wicd-client. python errors

#3 2009-02-25 10:20:18

Re: [SOLVED] can't start wicd-client. python errors

#4 2009-02-25 10:29:40

Re: [SOLVED] can't start wicd-client. python errors

#5 2009-02-25 12:25:16

Re: [SOLVED] can't start wicd-client. python errors

#6 2009-02-25 13:39:01

Re: [SOLVED] can't start wicd-client. python errors

#7 2009-02-25 13:42:28

Re: [SOLVED] can't start wicd-client. python errors

#8 2009-02-25 20:06:37

Re: [SOLVED] can't start wicd-client. python errors

#9 2009-02-25 22:21:16

Re: [SOLVED] can't start wicd-client. python errors

#10 2009-02-25 22:58:14

Re: [SOLVED] can't start wicd-client. python errors

Board footer