Issues with wicd 1.6.0

fettouhi · 2009-06-09 10:22:01

I've been using wicd for quite some time now and I use both to manage my wired connection and wireless (using broadcom-wl driver) on my stationary pc. Usually wicd autoconnects to my wired evey time I start my machine but since the upgrade to 1.6.0 yesterday wicd doesn't autoconnect to my wired network anymore. I have to manually connect after each start. Why is that? I haven't changed the slightest in my network setup. My wired connection is named eth1 and my wireless is eth0 by the way.

Regards

André

R00KIE · 2009-06-09 12:50:56

I have updated, rebooted and wicd connects fine to the wired network, I don't need to do anything.

moljac024 · 2009-06-09 13:00:50

I don't generally use wired so I wouldn't know, I just manually connect to a wireless all of the time lately.
But what I do notice is that wicd-curses doesn't work:

bojan ~ $  wicd-curses 
Traceback (most recent call last):
  File "/usr/lib/wicd/wicd-curses.py", line 42, in <module>
    import urwid
ImportError: No module named urwid

EDIT: After actually reading the message I see that it's a dependency issue.
So, python-urwid should be a dependency of the new wicd....bug report ?

Last edited by moljac024 (2009-06-09 13:03:15)

ise · 2009-06-09 13:32:09

moljac024 wrote:

EDIT: After actually reading the message I see that it's a dependency issue.
So, python-urwid should be a dependency of the new wicd....bug report ?

Already created and assigned to me. http://bugs.archlinux.org/task/14992

EDIT: @fettouhi: Wired network works here without any configuration changes, like in 1.5.9 before.

Last edited by ise (2009-06-09 13:34:53)

fettouhi · 2009-06-09 15:59:07

Well, that's great but for it doesn't work anymore. When I log into my KDE4 (KDEmod) desktop after a new start. My wired network gets disconnected immediately . I have to then manually reconnect it.

Regards

André

PS. I'm using static IP with a local DNS server.

Last edited by fettouhi (2009-06-09 15:59:33)

Llama · 2009-06-09 16:25:03

fettouhi wrote:

I've been using wicd for quite some time now and I use both to manage my wired connection and wireless (using broadcom-wl driver) on my stationary pc. Usually wicd autoconnects to my wired evey time I start my machine but since the upgrade to 1.6.0 yesterday wicd doesn't autoconnect to my wired network anymore. I have to manually connect after each start. Why is that?

Exactly my case. Wireless too.

mini · 2009-06-10 05:46:04

The same here with wireless

fettouhi · 2009-06-10 06:11:04

Hmm... maybe we should make bug report since more users have this issue.

Regards

André

panosk · 2009-06-10 08:18:17

Hi,

After upgrading wicd, I have issues too with wireless (haven't tried wired). In addition, the wicd applet has disappeared from my KDE tray, and there is no way I can bring it back.

Edit: Wired connection worked, but still the tray icon will not appear. Downgrading wicd solved the problems.

Panos

Last edited by panosk (2009-06-10 08:49:43)

ise · 2009-06-10 09:19:05

panosk wrote:

After upgrading wicd, I have issues too with wireless (haven't tried wired). In addition, the wicd applet has disappeared from my KDE tray, and there is no way I can bring it back.

Can you please start wicd-client from a shell and post the output of it.

panosk · 2009-06-10 09:34:47

ise wrote:

panosk wrote:
After upgrading wicd, I have issues too with wireless (haven't tried wired). In addition, the wicd applet has disappeared from my KDE tray, and there is no way I can bring it back.
Can you please start wicd-client from a shell and post the output of it.

Atlhough I have downgraded wicd, I had already done that. I got no output at all, which I suppose means the client started OK. Nevertheless, the icon wouldn't appear in the tray.

ChemBro · 2009-06-10 17:24:06

I get this output:

$ wicd-client                                                                                          
Has notifications support True                                                                                               
Loading...                                                                                                                   
Connecting to daemon...                                                                                                      
Can't connect to the daemon, trying to start it automatically...                                                             
Connected.
/usr/lib/wicd/wicd-client.py:419: GtkWarning: Im Modulpfad »clearlooks« konnte keine Themen-Engine gefunden werden,
  self.menu = (self.manager.get_widget('/Menubar/Menu/About').
/usr/lib/wicd/wicd-client.py:419: GtkWarning: Im Modulpfad »murrine« konnte keine Themen-Engine gefunden werden,
  self.menu = (self.manager.get_widget('/Menubar/Menu/About').
ERROR:dbus.proxies:Introspect error on :1.40:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.40 was not provided by any .service files
warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.40 was not provided by any .service files

I'm using kdemod, too. And I installed python-something, but that didn't worked, too.

R00KIE · 2009-06-10 18:11:30

Did you start hal _ before_ starting the wicd daemon? And do you have the wicd daemon running _before_ you start wicd-client ?

Fixed · 2009-06-10 19:55:31

Here is what I see after starting wicd-client from root:

# wicd-client
Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Connected.
Done loading.
/usr/lib/python2.6/site-packages/wicd/gui.py:151: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  self.wTree = gtk.glade.XML(gladefile)

I am using XFCE, and wicd doesn't start automatically anymore. I didn't change anything in rc.conf or other conf files in between.

And yes, I am using Arch64.

Last edited by Fixed (2009-06-10 20:57:26)

R00KIE · 2009-06-10 20:28:46

I just did a clean install of my system (transition to Arch64) and everything works fine here as far as I can see, nothing changed for me with the update to 1.6.0 .

ChemBro · 2009-06-10 23:12:51

R00KIE wrote:

Did you start hal _ before_ starting the wicd daemon? And do you have the wicd daemon running _before_ you start wicd-client ?

I did and I do. I changed nothing. Only thing that happened was the update of wicd. After that, wicd stopped working. Or the client. Looks like the daemon starts as usual.

coreyography · 2009-06-11 01:07:19

I have the same problem of wicd not starting up in XFCE after my 1.6 upgrade. I worked around it as follows:

In the file /etc/dbus-1/system.d/wicd.conf, look for this section:

      <policy user="root">
                <allow own="org.wicd.daemon"/>
                <allow send_destination="org.wicd.daemon"/>
                <allow send_interface="org.wicd.daemon"/>
                <allow send_destination="org.wicd.daemon.wireless"/>
                <allow send_interface="org.wicd.daemon.wireless"/>
                <allow send_destination="org.wicd.daemon.wired"/>
                <allow send_interface="org.wicd.daemon.wired"/>
                <allow send_destination="org.wicd.daemon.config"/>
                <allow send_interface="org.wicd.daemon.config"/>
        </policy>

Change the first line from <policy user="root"> to <policy group="blah"> where "blah" is a group your UID and root belong to. Might also work if you change user="root" to user="me" or something too, but I did not try that. It is a quick, lazy hack and probably creates some big security hole or something, but it works for now.

Side comment: It took awhile for me to find this. Linux is getting dangerously close to having a Windows registry with all these damn, mostly uncommented XML config files. I DO NOT like it.

R00KIE · 2009-06-11 11:04:34

ChemBro wrote:

R00KIE wrote:
Did you start hal _ before_ starting the wicd daemon? And do you have the wicd daemon running _before_ you start wicd-client ?
I did and I do. I changed nothing. Only thing that happened was the update of wicd. After that, wicd stopped working. Or the client. Looks like the daemon starts as usual.

The only thing I seem to have different is the lack of pynotify or whatever provides it

$ wicd-client
Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Connected.
Done loading.

cb474 · 2009-06-11 23:54:33

I'm also having a problem with wicd since upgrading to 1.6.0, which I posted about here: http://bbs.archlinux.org/viewtopic.php?id=73662 and in the wicd forums here: http://wicd.net/punbb/viewtopic.php?pid=2368.

When I start up the wicd-client gui endlessly says "obtaining IP address" and the icon in the panel notification area shows that I'm not connected, even though I am connected. This consistently happens with certain access points, but not others. However, if after I start up I stop the wicd daemon and quit the wicd-client, and then relaunch wicd from the command line and wicd-client with the Alt-F2 run dialogue, it works normally. 1.5.9 worked fine when started as a daemon at startup.

Last edited by cb474 (2009-06-11 23:57:14)

ChemBro · 2009-06-12 12:21:42

Okay, I managed to get wicd(-client) get working. I stopped wicd, removed wicd (pacman -R), removed any files in /etc/wicd and /var/log/wicd und reinstalled it again. Now wicd works (with wired connection), but I can hit the refresh-button as often as I can, it doesn't see my router (iwlist scan does). And no error message, sadly. :-(

wicd-curses has the same problem. And the log-file says: 0 networks found.

Does anyone know how I can get rid of this?

R00KIE · 2009-06-12 15:33:53

@cb474
I've seen something on the log you posted back at the wicd forum

wlan0: no IPv6 routers present

Try to disable ipv6 completely (check the wiki) and give it another try, I doubt that it will solve the problem but who knows, some routers don't play well with ipv6 enabled clients.

Anonymo · 2009-06-12 21:36:12

Offtopic:

I can't tell from the changelogs, but does WICD have VPN pptp support?

cb474 · 2009-06-13 02:39:49

R00KIE wrote:

@cb474
I've seen something on the log you posted back at the wicd forum
wlan0: no IPv6 routers present
Try to disable ipv6 completely (check the wiki) and give it another try, I doubt that it will solve the problem but who knows, some routers don't play well with ipv6 enabled clients.

Thanks for the suggestion. I noticed that too and wondered about it, but since the wicd developers didn't say anything, I figured it wasn't an issue. Nonetheless I have now tried disabling ipv6, on your suggestion, but it didn't solve the problem. I did finally get the content of the wicd.log when starting wicd as a daemon as startup, which seems to have some errors that weren't in the other log I posted, and posted that over in the wicd forums, so hopefully this will lead to a solution.

Llama · 2009-06-13 09:34:53

ChemBro wrote:

Okay, I managed to get wicd(-client) get working. I stopped wicd, removed wicd (pacman -R), removed any files in /etc/wicd and /var/log/wicd und reinstalled it again.

This part worked for me, too (wireless connects automatically again).

kgas · 2009-06-13 12:09:51

After wicd upgrade wirelss (AR242x) is woking fine without ndiswrapper. This is for the records.

08:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

Arch Linux

#1 2009-06-09 10:22:01

Issues with wicd 1.6.0

#2 2009-06-09 12:50:56

Re: Issues with wicd 1.6.0

#3 2009-06-09 13:00:50

Re: Issues with wicd 1.6.0

#4 2009-06-09 13:32:09

Re: Issues with wicd 1.6.0

#5 2009-06-09 15:59:07

Re: Issues with wicd 1.6.0

#6 2009-06-09 16:25:03

Re: Issues with wicd 1.6.0

#7 2009-06-10 05:46:04

Re: Issues with wicd 1.6.0

#8 2009-06-10 06:11:04

Re: Issues with wicd 1.6.0

#9 2009-06-10 08:18:17

Re: Issues with wicd 1.6.0

#10 2009-06-10 09:19:05

Re: Issues with wicd 1.6.0

#11 2009-06-10 09:34:47

Re: Issues with wicd 1.6.0

#12 2009-06-10 17:24:06

Re: Issues with wicd 1.6.0

#13 2009-06-10 18:11:30

Re: Issues with wicd 1.6.0

#14 2009-06-10 19:55:31

Re: Issues with wicd 1.6.0

#15 2009-06-10 20:28:46

Re: Issues with wicd 1.6.0

#16 2009-06-10 23:12:51

Re: Issues with wicd 1.6.0

#17 2009-06-11 01:07:19

Re: Issues with wicd 1.6.0

#18 2009-06-11 11:04:34

Re: Issues with wicd 1.6.0

#19 2009-06-11 23:54:33

Re: Issues with wicd 1.6.0

#20 2009-06-12 12:21:42

Re: Issues with wicd 1.6.0

#21 2009-06-12 15:33:53

Re: Issues with wicd 1.6.0

#22 2009-06-12 21:36:12

Re: Issues with wicd 1.6.0

#23 2009-06-13 02:39:49

Re: Issues with wicd 1.6.0

#24 2009-06-13 09:34:53

Re: Issues with wicd 1.6.0

#25 2009-06-13 12:09:51

Re: Issues with wicd 1.6.0

Board footer