wicd

[Jason W]

The only change in dbus has been the removal of it/'s automatic starting.  It looks like simply an issue of starting dbus before using WICD.

EDIT: Installed it and I see there is still an issue.  Let me take a look.

[bmarkus]

I will change the WICD startup script which will fix the issue.

[Jason W]

Thanks to bmarkus for an update:

Code: [Select]

Title:          wicd.tcz
Description:    Wired and wireless network manager with GUI
Version:        1.7.0
Author:         Adam Blackburn, Dan O'Reilly, Andrew Psaltis
Original-site:  http://wicd.sourceforge.net
Copying-policy: GPL v2
Size:           320k
Extension_by:   bmarkus
Comments:       Binaries only
                ----
                INSTALLATION

                Add following files to your backup:

                  /usr/local/etc/wicd
                  /usr/local/var/lib/wicd/configurations

                RUNNING

                Run 'wicd-start' as root to start wicd daemon
                You can add it to Xfce4/LXDE startup

                This version now packed with 'wicd-cli' and 'wicd-curses' command
                line tools.

                DESKTOP INTEGRATION

                Add 'wicd-client' to Xfce4/LXDE startup to have wicd panel applet
                ----
                Compiled for TC2.x
                ----
                PPI compatible
Change-log:     2009/11/21 First version
                2010/01/20 Updated to 1.7.0
                2010/01/24 Fixed missing WBAR icon
                2010/01/24 External icon theme dependency removed
                2010/01/25 Dropped HAL dependency
Current:        2010/02/06 Fixed DBUS initialization





[Juanito]

If I try to use wicd:

Code: [Select]

$ wicd-client --no-tray
/usr/local/bin/wicd-client: line 2: tput: command not found
/usr/local/bin/wicd-client: line 3: tput: command not found
/usr/local/bin/wicd-client: line 4: tput: command not found
Importing pynotify failed, notifications disabled.
Has notifications support False
Notifications disabled during setup.py configure
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Can't connect to the daemon, trying to start it automatically...
Failed to find a graphical sudo program, cannot continue.
/tmp/tcloop/wicd/usr/local/share/wicd/gtk/gui.py:152: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  self.wTree = gtk.glade.XML(gladefile)
Traceback (most recent call last):
  File "/usr/local/share/wicd/gtk/wicd-client.py", line 1033, in <module>
    main(sys.argv)
  File "/usr/local/share/wicd/gtk/wicd-client.py", line 91, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/share/wicd/gtk/wicd-client.py", line 999, in main
    the_gui = gui.appGui(standalone=True)
  File "/tmp/tcloop/wicd/usr/local/share/wicd/gtk/gui.py", line 155, in __init__
    size = daemon.ReadWindowSize("main")
AttributeError: 'NoneType' object has no attribute 'ReadWindowSize'

..looks like ncurses-utils is missing as a dep?

..but then:

Code: [Select]

Could not connect to wicd's D-Bus interface.  Check the wicd log for error messages.
dbus is running

[maro]

I had observed the 'tput' related messages earlier (see response #10) and I'm pretty sure that they are benign. As far as I can "see" it would just be used to change the color of some messages when using 'wicd-curses'. It might be prudent to wrap those three lines from '/usr/local/bin/wicd-client' into something like if [ `which tput` ]

Unfortunately that still leaves you with the daemon issue. Anything useful in '/var/log/wicd/wicd.log' ? I guess you've already done a few cycles of: sudo /usr/local/etc/init.d/dbus stop ; sudo wicd-start and  done a check with sudo netstat -anp | grep -i 'dbus|python'

[bmarkus]

Testing WICD on a stock 2.11rc3 just works fine (for sure the same with 2.10):



Installing    ncurses-utils.tcz tput related error messages are gone:



However you do not need ncurses-utils.tcz when GTK GUI used. Also, missing pynotify can be safely omitted but you can add notify-python.tcz if you wish.

BTW, I'm planning to split WICD to a GTK and CLI version to optimize its size and dependencies for TC/MC.

^thehatsrule^, please keep pictures. They are so small

[Juanito]

OK - had another go and got it working [I may have forgotten wicd-start  ]

The icon doesn't show (maybe for the reasons mentioned in another post) and wicd might benefit from an init.d script, but works otherwise 

[bmarkus]

init.d script for wicd and hal is on the todo list

[fokcuk]

Hi guys.
I know its an old post...
New to Linux and all...
I have an issue with wicd. When I open the GUI, it shows my wireless network, I can connect - all good.
What I cannot do is to make it connect automatically after restart =( When I connect, change some connection properties
(like static IP etc) it saves the settings to /usr/local/var/lib/wicd/configurations
But after a restart, the folder is empty =( Please help

[Rich]

Hi fokcuk
Try adding the following two lines to your   /opt/.filetool.lst   file
usr/local/etc/wicd
usr/local/var/lib/wicd/configurations

Add the following to   /opt/bootlocal.sh
wicd-start

The first step makes your settings persistent, the second step starts wicd upon boot up.

[fokcuk]

Hi fokcuk
Try adding the following two lines to your   /opt/.filetool.lst   file
usr/local/etc/wicd
usr/local/var/lib/wicd/configurations

Add the following to   /opt/bootlocal.sh
wicd-start

The first step makes your settings persistent, the second step starts wicd upon boot up.

Thanks, Rich!
Second part is already done. wicd starts fine (I think I might have added it as sudo wicd-start), it just does not connect.
Will do the first part tonight!

[Rich]

Hi fokcuk
The  bootlocal.sh  script runs as root, so  sudo  is not required for commands in that script.