SliTaz SliTaz Forum

You are not logged in.

#1 2014-09-01 08:16:46

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

slitaz 5.0 - wicd does not start

On my Slitaz 5.0 installation I cannot start wicd.

[c]tux@slitaz:~$ wicd-gtk --no-tray &

** (process:6201): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:6201): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:6201): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
Importing pynotify failed, notifications disabled.[/c]
[c]Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.[/c]

[c]sh: syntax error: unterminated quoted string[/c]

In /var/log/wicd I find only an empty file. Wicd does not accept the correct root passwd.

Anybody else having the same problem?

Offline

#2 2014-09-01 12:26:21

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: slitaz 5.0 - wicd does not start

Please try this: http://cook.slitaz.org/packages/wicd-1.7.2.4.tazpkg

Offline

#3 2014-09-01 16:39:12

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: slitaz 5.0 - wicd does not start

As usual: thanks a lot for the quick response!!!

Can I try that with Slitaz 4.0 as well? Stay tuned, I will test it this evening.;-)

Offline

#4 2014-09-01 17:08:43

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: slitaz 5.0 - wicd does not start

Problem,wicd won't autostart on my system...

It adds /etc/xdg/autostart/wicd-tray.desktop which autostarts wicd-gtk

When wicd-gtk starts and can't connect to wicd-daemon it asks for password.

I add wicd to DAEMONS= of /etc/rcS.conf

The bootlog message indicates wicd started but when I run [c]ps -A | grep wicd[/c] its not running.

Someone else will have to figure out this problem.

Offline

#5 2014-09-01 17:22:30

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: slitaz 5.0 - wicd does not start

Hmmh, here it autostarts - but with the old problem. Nothing has changed! I did not yet add wicd to the Daemons in /etc/rcS.conf. And there is no log-file in /var/log/wicd.

The result is this:

root@slitaz:/var/log/wicd# wicd-client &

root@slitaz:/var/log/wicd# /usr/bin/wicd-client: line 2: tput: not found

/usr/bin/wicd-client: line 3: tput: not found

/usr/bin/wicd-client: line 4: tput: not found

** (process:1463): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:1463): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:1463): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'

Importing pynotify failed, notifications disabled.

Has notifications support False

Loading...

Connecting to daemon...

Can't connect to the daemon, trying to start it automatically...

/usr/bin/tazbox: exec: line 682: --message: not found

Can't connect to the daemon, trying to start it automatically...

/usr/bin/tazbox: exec: line 682: --message: not found

I had removed the old package and installed the new wicd-1.7.2.4.tazpkg package.

Offline

#6 2014-09-01 18:23:22

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: slitaz 5.0 - wicd does not start

Hmmh, here it autostarts - but with the old problem. Nothing has changed! I did not yet add wicd to the Daemons in /etc/rcS.conf. And there is no log-file in /var/log/wicd.

The result is this:

root@slitaz:/var/log/wicd# wicd-client &

root@slitaz:/var/log/wicd# /usr/bin/wicd-client: line 2: tput: not found

/usr/bin/wicd-client: line 3: tput: not found

/usr/bin/wicd-client: line 4: tput: not found

** (process:1463): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:1463): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:1463): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'

Importing pynotify failed, notifications disabled.

Has notifications support False

Loading...

Connecting to daemon...

Can't connect to the daemon, trying to start it automatically...

/usr/bin/tazbox: exec: line 682: --message: not found

Can't connect to the daemon, trying to start it automatically...

/usr/bin/tazbox: exec: line 682: --message: not found

I had removed the old package and installed the new wicd-1.7.2.4.tazpkg package.

Now, after having added the daemon to /etc/rcS.conf and rebooting, the new error message is:

„ Wicd daemon due to an access denied error from DBus. Please check that your user is in the users group.“

I started it manually as root: wicd-client &

Now it opened and started to work, but could not connect:

root@slitaz:/home/tux# setting encryption info...

/usr/share/wicd/gtk/gui.py:458: Warning: Source ID 3499 was not found when attempting to remove it

  gobject.source_remove(self.update_cb)

ERROR:dbus.connection:Exception in handler for D-Bus signal:

Traceback (most recent call last):

  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message

    self._handler(*args, **kwargs)

  File "/usr/share/wicd/gtk/gui.py", line 253, in handle_connection_results

    error(self.window, language[results], block=False)

KeyError: dbus.String(u'failed')

root@slitaz:/home/tux# /usr/share/wicd/gtk/gui.py:458: Warning: Source ID 25952 was not found when attempting to remove it

  gobject.source_remove(self.update_cb)

ERROR:dbus.connection:Exception in handler for D-Bus signal:

Traceback (most recent call last):

  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message

    self._handler(*args, **kwargs)

  File "/usr/share/wicd/gtk/gui.py", line 253, in handle_connection_results

    error(self.window, language[results], block=False)

KeyError: dbus.String(u'failed')

But there is now a log file in /var/log/wicd. Its last lines:

2014/09/01 19:57:20 :: Attempting to authenticate...

2014/09/01 19:57:47 :: canceling connection attempt

2014/09/01 19:57:47 :: attempting to set hostname with dhclient

2014/09/01 19:57:47 :: using dhcpcd or another supported client may work better

2014/09/01 19:57:47 :: running kill dhcp.

2014/09/01 19:57:47 :: attempting to set hostname with dhclient

2014/09/01 19:57:47 :: using dhcpcd or another supported client may work better

2014/09/01 19:57:47 :: running kill dhcp.

2014/09/01 19:57:48 :: Exception in thread Thread-20:

2014/09/01 19:57:48 :: Traceback (most recent call last):

2014/09/01 19:57:48 ::   File "/usr/lib/python2.7/threading.py", line 808, in __bootstrap_inner

2014/09/01 19:57:48 ::     self.run()

2014/09/01 19:57:48 ::   File "/usr/lib/python2.7/site-packages/wicd/networking.py", line 342, in run

2014/09/01 19:57:48 ::     self._connect()

2014/09/01 19:57:48 ::   File "/usr/lib/python2.7/site-packages/wicd/networking.py", line 920, in _connect

2014/09/01 19:57:48 ::     if not wiface.ValidateAuthentication(time.time()):

2014/09/01 19:57:48 ::   File "/usr/lib/python2.7/site-packages/wicd/wnettools.py", line 1371, in ValidateAuthentication

2014/09/01 19:57:48 ::     result = misc.RunRegex(auth_pattern, output)

2014/09/01 19:57:48 ::   File "/usr/lib/python2.7/site-packages/wicd/misc.py", line 204, in RunRegex

2014/09/01 19:57:48 ::     m = regex.search(string)

2014/09/01 19:57:48 :: RuntimeError: internal error in regular expression engine

2014/09/01 19:57:48 ::

2014/09/01 19:57:48 :: Sending connection attempt result aborted

I use a local small WLAN that is set up with WEP. Shared-restricted: this works under Mandriva.

Offline

#7 2014-09-02 09:33:51

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: slitaz 5.0 - wicd does not start

Michael, you might try connman - it is in the repos

https://wiki.archlinux.org/index.php/Connman

for UMTS support you need also ophono + usb-modeswitch

Offline

#8 2014-09-02 11:53:26

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: slitaz 5.0 - wicd does not start

@kultex

Thank you very much! Unfortunately before Friday I am on the road but I will report here then! Anyway, there seem to be some configuration problems with wicd under Slitaz and I just wanted to keep people informed about that. Wicd under Debian Squeeze works out of the box, with this small WLAN as well, of course.

Offline

#9 2014-09-09 21:04:44

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: slitaz 5.0 - wicd does not start

Ok, I now checked my Slitaz 4.0 Wifi in our local Linux group. With Connman I had no success, Wicd does not start and I was not able to correct it. But with tazpanel I could start the Wifi connection. It was difficut to follow it on the command line, though.

To be frank: how the Slitaz wifi configuration works I did not yet understand. Network manager and these wifi tools seem to bite each other. My impression as a non-technician. Thanks for your patience!

Offline

#10 2014-09-10 10:30:19

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: slitaz 5.0 - wicd does not start

@michaelbishof

documentation is here:    http://doc.slitaz.org/en:guides:wifi-easy

how I use it: normally it runs the default /etc/network.conf file - with the wired cable

then I have some .desktop files with wifi connections I use often in  /home/tux/.local/share/applications

the configs in /home/tux/.net

for example my desktopentry for the train is: OEBB.desktop

[Desktop Entry]

Encoding=UTF-8

Name=1-OEBB

Exec=tazbox su /etc/init.d/network.sh restart /home/tux/.net/OEBB.conf

Icon=network-wireless

Type=Application

Categories=Network;WebBrowser;

OEBB.conf looks like this (only important lines)

INTERFACE="eth1"

DHCP="yes"

STATIC="no"

WIFI="yes"

# Wifi interface (iwconfig) and ESSID.

WIFI_INTERFACE="eth1"

WIFI_ESSID="OEBB"

WIFI_AP=""

WIFI_MODE="managed"

WIFI_KEY=""

WIFI_KEY_TYPE="off"

WPA_DRIVER=""

WIFI_CHANNEL=""

WIFI_IWCONFIG_ARGS=""

if I am in a hotel (use the internet connection only once), I open this OEBB configuration (to get up the wireless hardware) - then the wifi - box - I see all the wifis available -  select the wifi essid, then enter the password and it works......

Offline

#11 2014-09-10 12:10:17

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: slitaz 5.0 - wicd does not start

Thank you, kultex!

One question:

why do you use

„WIFI_INTERFACE="eth1"

instead of „WIFI_INTERFACE="wlan0"?

Thanks for to remember me to use wifibox instead of this wicd (which I cannot move to work, somehow).

Offline

#12 2014-09-10 13:33:43

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: slitaz 5.0 - wicd does not start

because my wireless hardware (Intel Corporation PRO/Wireless 2200BG) comes up as eth1

tux@slitaz:~ $ iwconfig

lo        no wireless extensions.

eth1      IEEE 802.11bg  ESSID:off/any

          Mode:Managed  Channel:0  Access Point: Not-Associated

          Bit Rate:0 kb/s   Tx-Power=20 dBm   Sensitivity=8/0

          Retry limit:7   RTS thr:off   Fragment thr:off

          Power Management:off

          Link Quality:0  Signal level:0  Noise level:0

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

tunl0     no wireless extensions.

dummy0    no wireless extensions.

eth0      no wireless extensions.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]