Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Wicd problems

  1. #1
    Join Date
    Oct 2004
    Location
    Poland
    Beans
    164

    Wicd problems

    Wicd seems to be the only program that will get my wireless card working but now I cannot get the program to start up. Here is the output of what happens.

    Code:
    steve@weronika:~$ sudo /opt/wicd/gui.py
    [sudo] password for steve:
    attempting to connect daemon...
    daemon not running, running gksudo ./daemon.py...
    You need to start the daemon before using the gui or tray.  Use the command 'sudo /etc/init.d/wicd start'.
    daemon still not running, aborting.
    Traceback (most recent call last):
      File "/opt/wicd/gui.py", line 36, in <module>
        daemon = dbus.Interface(proxy_obj, 'org.wicd.daemon')
    NameError: name 'proxy_obj' is not defined
    steve@weronika:~$ sudo /etc/init.d/wicd start
    Stopping any running daemons...
    Starting wicd daemon...
    /opt/wicd
    wicd daemon: pid 10526
    steve@weronika:~$ sudo /opt/wicd/gui.py
    attempting to connect daemon...
    daemon not running, running gksudo ./daemon.py...
    You need to start the daemon before using the gui or tray.  Use the command 'sudo /etc/init.d/wicd start'.
    daemon still not running, aborting.
    Traceback (most recent call last):
      File "/opt/wicd/gui.py", line 36, in <module>
        daemon = dbus.Interface(proxy_obj, 'org.wicd.daemon')
    NameError: name 'proxy_obj' is not defined
    any help to get this program running again would be much appreciated as I will be in a wireless only area for a few weeks. thanks!

  2. #2
    Join Date
    Mar 2005
    Location
    Texas
    Beans
    1,675
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Wicd problems

    gui.py shouldn't be run with sudo, so try it w/o sudo.
    100 buckets of bits on the bus,
    100 buckets of bits,
    Take one down, short it to ground,
    FF buckets of bits on the bus.

  3. #3
    Join Date
    Oct 2004
    Location
    Poland
    Beans
    164

    Re: Wicd problems

    Code:
    steve@weronika:~$ /opt/wicd/gui.py
    attempting to connect daemon...
    daemon not running, running gksudo ./daemon.py...
    You need to start the daemon before using the gui or tray.  Use the command 'sudo /etc/init.d/wicd start'.
    daemon still not running, aborting.
    Traceback (most recent call last):
      File "/opt/wicd/gui.py", line 36, in <module>
        daemon = dbus.Interface(proxy_obj, 'org.wicd.daemon')
    NameError: name 'proxy_obj' is not defined

    I tried to do the sudo /etc/init.d/wicd like it says there but this is all that happens:

    Code:
    steve@weronika:~$ sudo /etc/init.d/wicd start
    [sudo] password for steve:
    Stopping any running daemons...
    Starting wicd daemon...
    /opt/wicd
    wicd daemon: pid 10821

  4. #4
    Join Date
    Mar 2005
    Location
    Texas
    Beans
    1,675
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Wicd problems

    Looks like the daemon started, what happens if you try /opt/wicd/gui.py again?
    100 buckets of bits on the bus,
    100 buckets of bits,
    Take one down, short it to ground,
    FF buckets of bits on the bus.

  5. #5
    Join Date
    Oct 2004
    Location
    Poland
    Beans
    164

    Re: Wicd problems

    Code:
    steve@weronika:~$ /opt/wicd/gui.py
    attempting to connect daemon...
    daemon not running, running gksudo ./daemon.py...
    You need to start the daemon before using the gui or tray.  Use the command 'sudo /etc/init.d/wicd start'.
    daemon still not running, aborting.
    Traceback (most recent call last):
      File "/opt/wicd/gui.py", line 36, in <module>
        daemon = dbus.Interface(proxy_obj, 'org.wicd.daemon')
    NameError: name 'proxy_obj' is not defined

  6. #6
    Join Date
    Mar 2005
    Location
    Texas
    Beans
    1,675
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Wicd problems

    Hmm very odd. what if you do

    sudo /opt/wicd/daemon.py
    100 buckets of bits on the bus,
    100 buckets of bits,
    Take one down, short it to ground,
    FF buckets of bits on the bus.

  7. #7
    Join Date
    Dec 2006
    Location
    Manila, Philippines
    Beans
    1,886
    Distro
    Ubuntu Development Release

    Re: Wicd problems

    Did you upgrade your distro? Have you tried wireless manager now? If you're willing to run a KDE app, have you tried wlassistant?
    MacBook Air 3,1 128gb | Fujitsu Esprimo U9200 | Google Nexus One

    Pinoy ka ba? | Google Profile | Twitter: @AllanCaeg| Identi.ca: allancaeg

  8. #8
    Join Date
    Oct 2004
    Location
    Poland
    Beans
    164

    Re: Wicd problems

    Code:
    steve@weronika:~$ sudo /opt/wicd/daemon.py
    /opt/wicd
    wicd daemon: pid 11218
    steve@weronika:~$ lo        no wireless extensions.
    
    eth0      no wireless extensions.
    
    wifi0     no wireless extensions.
    as far as the upgrade I haven't done it yet. I actually just started runing the update now.

  9. #9
    Join Date
    Jun 2007
    Beans
    692

    Re: Wicd problems

    Try deleting /opt/wicd/data/wired-settings.conf, then try starting the daemon again. Sometimes the conf files get corrupted and cause the daemon to fail to start.

  10. #10
    Join Date
    Oct 2004
    Location
    Poland
    Beans
    164

    Re: Wicd problems

    Well in combination of deleting that file, running some of the previous commands, and then upgrading the system I got the program to start up and I have my wireless running. Weird how the network manager wont get it running and only that program will. Thanks for your help!

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •