Tiny Core Linux
Tiny Core Extensions => TCE News => TCE 2.x => Topic started by: Jason W on November 21, 2009, 07:26:39 PM
-
Thanks to bmarkus for:
Title: wicd-doc.tcz
Description: Wired and wireless network manager with GUI
Version: 1.6.2.2
Author: Adam Blackburn, Dan O'Reilly, Andrew Psaltis
Original-site: http://wicd.sourceforge.net
Copying-policy: GPL v2
Size: 61k
Extension_by: bmarkus
Comments: Doc files
----
Compiled for TC2.x
----
PPI compatible
Change-log: ----
Current: 2009/11/21 First version
Title: wicd-locale.tcz
Description: Wired and wireless network manager with GUI
Version: 1.6.2.2
Author: Adam Blackburn, Dan O'Reilly, Andrew Psaltis
Original-site: http://wicd.sourceforge.net
Copying-policy: GPL v2
Size: 283k
Extension_by: bmarkus
Comments: Language files
----
Compiled for TC2.x
----
PPI compatible
Change-log: ----
Current: 2009/11/21 First version
Title: wicd.tcz (testing)
Description: Wired and wireless network manager with GUI
Version: 1.6.2.2
Author: Adam Blackburn, Dan O'Reilly, Andrew Psaltis
Original-site: http://wicd.sourceforge.net
Copying-policy: GPL v2
Size: 344k
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 'bootlocal.sh' or to Xfce4/LXDE startup
DESKTOP INTEGRATION
Add 'wicd-client' to Xfce4/LXDE startup to add wicd panel applet
----
Compiled for TC2.x
----
PPI compatible
Change-log: ----
Current: 2009/11/21 First version
-
thanks for your great efforts for wireless users like me first of all
in dep file there is wicd.tcz which causes a wget error message and ending with no wicd.tcz file in tce directory
-
in dep file there is wicd.tcz which causes a wget error message and ending with no wicd.tcz file in tce directory
Yeah, my fault... Will be removed. As a temporary fix just download it from
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/tcz/wicd.tcz
and put to /tce after appbrowser fails. It is the last item, so all dependencies are in place.
-
wicd.tcz removed from dep file.
-
Thanks to bmarkus for an update:
Title: wicd-doc.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: 74k
Extension_by: bmarkus
Comments: Doc files
----
Compiled for TC2.x
----
PPI compatible
Change-log: 2009/11/21 First version
Current: 2010/01/20 Updated to 1.7.0
Title: wicd-locale.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: 303k
Extension_by: bmarkus
Comments: Language files
----
Compiled for TC2.x
----
PPI compatible
Change-log: 2009/11/21 First version
Current: 2010/01/20 Updated to 1.7.0
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
Current: 2010/01/20 Updated to 1.7.0
-
In this version command line tools. wicd-cli and wicd-curses work fine. However, wicd-curses requires the new urwid.tcz extension which is increasing the installation size. For those using WICD in TC these command line tools and dependencies unnecessary. Also there are components not needed for those want to use in a pure MC with command line tools only.
If there is a demand, I can split it to 2 or 3 extensions (base, cli, gtk ???) to optimize it.
HAL dependency is another point. For sure HAL can be dropped safely.
Your feedback is appreciated.
-
What's new in 1.7.0?
The new work in wicd 1.7.0 includes connection information now being available when right-clicking on its system tray icon, the ability to set a host-name per network for all DHCP clients, support for version 0.99 of the urwid console user interface library, the introduction of wicd-cli as a command-line interface for scripts, support for numeric-only ESSIDs, the introduction of wicd-gtk as the preferred way of launching the GTK GUI, and support for using dhcpcd-bin on Debian systems. There are also a few other minor changes in the wicd 1.7.0 release.
-
I ran into two small problem with this extension:
(1) After it's installation the wbar "disappeared". Since I used a "clean" TC 2.7 boot (from CD, without any persistence) I was a bit surprised.
I realised that the icon file for wicd in /usr/local/tce.wbar does not exist. After changing therefore the respective entry from wicd-client.png to wicd-gtk.png and executing 'wbar.sh' the problem was resolved.
(2) I had to also install the ncurses-utils.tcz extension, since 'tput' was required by 'wicd-client'.
Furthermore I'd like to state that I like the idea to have several extensions that are supersets of a base extension very much. The current list of dependencies is pretty long (now 39, if my counting is correct). I guess for users of MC that might be a bit too much.
[edited: forgot to mention the additional extension]
-
maro,
thanks for the bug reports, I will fix them. Reorganization and to get rid of HAl will take some time, but will do it. At the moment I do not see a real alternative network manager.
-
(2) I had to also install the ncurses-utils.tcz extension, since 'tput' was required by 'wicd-client'.
Trying WICD on a stock TC 2.8rc4a only WICD dependencies installed wicd-client works fine and there are no any tput related messages. Where do you see tput missing?
-
Here is a simple way to show the warning messages:
tc@box:~$ wicd-client -?
/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
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".
Importing pynotify failed, notifications disabled.
Has notifications support False
Notifications disabled during setup.py configure
wicd 1.7.0
wireless (and wired) connection daemon front-end.
Arguments:
-n --no-tray Run wicd without the tray icon.
-h --help Print this help information.
-a --no-animate Run the tray without network traffic tray animations.
-o --only-notifications Don't display anything except notifications.
On re-testing I found that 'tput' does not appear to be really required. It's use is probably of a more "cosmetic" nature. I guess I had another problem that got meanwhile resolved and I (falsely) assumed that 'tput' was "the culprit".
I'd therefore "downgrade" my report to add ncurses-utils.tcz as a "nice to have", but not really vital extension.
-
Thanks to bmarkus for an update:
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
Current: 2010/01/24 Fixed missing WBAR icon
-
Thanks to bmarkus for an update:
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
Current: 2010/01/24 External icon theme dependency removed
-
Thanks to bmarkus for an update:
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
Current: 2010/01/25 Dropped HAL dependency
-
This latest version is now HAL-free. Removing gnome-icon-theme and HAL is significantly reducing installation size. Functionality is still the same, as HAL features were not used.
-
Hello All
The current version of wicd is not playing ball with my atheros wlan card. Yes I have checked that the ath9k module is loaded.
Here is the output from wicd-client
root@box:home/tc/# wicd-start
root@box:home/tc/# 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".
Traceback (most recent call last):
File "/usr/local/share/wicd/gtk/wicd-client.py", line 63, in <module>
from wicd import dbusmanager
File "/usr/local/lib/python2.6/site-packages/wicd/dbusmanager.py", line 93, in <module>
DBUS_MANAGER = DBusManager()
File "/usr/local/lib/python2.6/site-packages/wicd/dbusmanager.py", line 57, in __init__
self._bus = dbus.SystemBus()
File "/usr/local/lib/python2.6/site-packages/dbus/_dbus.py", line 202, in __new__
private=private)
File "/usr/local/lib/python2.6/site-packages/dbus/_dbus.py", line 108, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/local/lib/python2.6/site-packages/dbus/bus.py", line 125, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBu.ception: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
root@box:home/tc/#
Any suggestions would be great!
Many thanks, Miller.
-
According to the message it has nothing to do with the wireless card; DBUS subsystem is not running.
-
Hi Bela
How do I get the dbus subsystem to run please?
Miller.
-
wicd-start does the job normally, no any other action needed. However in some cases you have to wait a bit till it starts-up, so try to run client a bit later. Are you using LXDE or Xfce4? If not, use 'wicd-client -n' to start GUI.
One more thing. Run client as user (tc) and not as root. Lets see the result.
-
Hi Bela
Thanks for your reply.
I'm using FLWM topside (default). I ran wicd-client -n as non root user and the same error messages appears as before.
Miller.
-
Just tested WICD on 2.8.1 desktop without any wireless hardware. It works as expected and can manage wired Ethernet interface.
After issuing 'sudo wicd-start' command, you must see dbus-daemon running with the 'ps' command. If not, this is a dbus issue. If it is there, check wicd log in /var/log/wicd.
BTW, which TC version is used and what is the installation type? Are all components up to date?
-
Hi Bela
I'm using TC 2.8.1 as a fresh install (yesterday) onto a SD card. This card is sdb1. I have all extensions installed to /mnt/sdb1/tce/optional
The TC install is just your default type with nothing customised or hacked.
Yes all components are up to date. At your suggestion concering the dbus subsytem, I removed all 9 dbus files from the tce optional directory. ie dbus, dbus-python & dbus-glib (.tcz, .tcz.dep & .tcz.md5.txt variants) I replaced these extensions with older versions from Dec 2009 repository. Now wicd appears to be behaving itself!
It's getting close to midnight in this part of the world so I had best be away.
I will run the checks you suggest tomorrow and report back. Thanks for all your assistance. Much obliged.
Best
Miller.
-
The dbus and other extensions no longer start the service with the /usr/local/tce.installed startup script. This is being done to pave the way for recursive dependencies, and we can't have our cake and eat it too when it comes to recursion vs. controlling the order of dependency loading, which was necessary to have the startup scripts start daemons for some extensions.
The scripts in /usr/local/etc/init.d are now being used to start daemons, and those start commands can be placed in bootlocal.sh.
"/usr/local/etc/init.d/dbus start" would be the command.
-
Jason
WICD and DBUS installed just recently from the repo starts fine and works expected on my machines, so Miller's problem is not related to this change. Atleast as I see at the moment.
Lets wait for the report.
-
Hi all:
I get the same error as Miller regarding the wicd-client output in both of my laptops (Acer Aspire One D150 with a Broadcomm wlan card, the wl module loaded and a Dell Inspiron 9100). I used the latest tc 2.8.1 version default install on an usb (=sdb1) with persistent tce and home. Desktop is FLWM.
Tried what Jason suggested, but keep getting same error.
Cefcom
-
I'm trying to make Tiny Core 2.8 working on a HP Mini 1110NR with Broadcom chip. I followed the instructions on the wiki, plus this post on the forum, and I've got the exact same error message except from the last part. Instead of "No such file or directory", I get a "Connexion refused" error on /var/run/dbus/system_bus_socket. I'm using wicd-client -n as normal user. Thanks.
-
Thanks for the reports. Will check during the week-end :(
-
Good news, I get the same error on a fresh 2.8.1 installed from the repo, so I can fix it in few days. Please be patient a while.
As a temprary fix, do not use wicd-start, but:
sudo /usr/local/etc/init.d/dbus start
sudo wicd
Now WICD client will work as usual.
-
Greetings All
To summarize so far, wicd appears to be running properly on a fresh (4th Feb 2010 repository) install of TC 2.8.1 only when I replace the current (dbus.tcz, dbus-glib.tcz and dbus-python.tcz) extensions (plus their respective .tcz.dep & .tcz.md5.txt files) with older versions.
The older versions I used are: dbus.tcz ver: 1.2.16 , dbus-glib.tcel ver: 0.82 , dbus-python.tcz ver: 0.83.0
NB: I have attached to this post the 3 info files (prefixed with "good-") associated with each of these older extensions I installed.
The results of the terminal "ps" show the dbus subsystem running. This output is attached as good-wicd-ps-output.txt to this post.
/*************************************************************************/
As an aside, after wicd is installed I run this script to tidy up, then reboot. Thanks Bela for this.
#!/bin/sh
echo "This script will configure wicd..."
echo "wicd-start" >> /opt/bootlocal.sh
echo "usr/local/etc/wicd" >> /opt/.filetool.lst
echo "usr/local/var/lib/wicd/configurations" >> /opt/.filetool.lst
echo "All done, wicd changes effective on next boot..."
/*************************************************************************/
Today 5 Feb 2010 I reformatted the SD card and performed a fresh installation of TC 2.8.1. I only installed nano & wicd, both downloaded from the repository. wicd again would not run.
Here is the (faulty) wicd.log file contents:
2010/02/05 14:28:58 :: ---------------------------
2010/02/05 14:28:58 :: wicd initializing...
2010/02/05 14:28:58 :: ---------------------------
2010/02/05 14:28:58 :: wicd is version 1.7.0 552
2010/02/05 14:28:58 :: Traceback (most recent call last):
2010/02/05 14:28:58 :: File "/usr/local/share/wicd/daemon/wicd-daemon.py", line 1839, in <module>
2010/02/05 14:28:58 :: main(sys.argv)
2010/02/05 14:28:58 :: File "/usr/local/share/wicd/daemon/wicd-daemon.py", line 1801, in main
2010/02/05 14:28:58 :: bus = dbus.SystemBus()
2010/02/05 14:28:58 :: File "/usr/local/lib/python2.6/site-packages/dbus/_dbus.py", line 202, in __new__
2010/02/05 14:28:58 :: private=private)
2010/02/05 14:28:58 :: File "/usr/local/lib/python2.6/site-packages/dbus/_dbus.py", line 108, in __new__
2010/02/05 14:28:58 :: bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
2010/02/05 14:28:58 :: File "/usr/local/lib/python2.6/site-packages/dbus/bus.py", line 125, in __new__
2010/02/05 14:28:58 :: bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
2010/02/05 14:28:58 :: dbus.exceptions.DBu.ception: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
I have attached the results of the terminal "ps" which shows the dbus subsystem not running. This output is attached as faulty-wicd-ps-output.txt to this post.
I have installed Tiny Core 2.8.1 to a MSI-Wind U100. The sata HD has been replaced with a sata-CF adapter w/2Gb flash card (sda1). I pop a 1Gb SD card in the card slot (sdb1) and install TC on it. The internal wlan is an Atheros 9280 pci-e type.
Hope this helps,
Best
Miller.
-
With the current extension set start WICD as above.
-
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.
-
I will change the WICD startup script which will fix the issue.
-
Thanks to bmarkus for an update:
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
-
If I try to use wicd:
$ 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: Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.
dbus is running
-
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'
-
Testing WICD on a stock 2.11rc3 just works fine (for sure the same with 2.10):
(http://tc.hasix.org/scrcap/screenshot_0428071639A.jpg)
Installing ncurses-utils.tcz tput related error messages are gone:
(http://tc.hasix.org/scrcap/screenshot_0428071856A.jpg)
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 :)
-
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 :)
-
init.d script for wicd and hal is on the todo list :)
-
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
-
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.
-
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!
-
Hi fokcuk
The bootlocal.sh script runs as root, so sudo is not required for commands in that script.