Wicd-1.7.0 fails to "lock-on" wifi signal, repeatedly drops connection

Bug #530292 reported by Odysseus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
New
Undecided
Unassigned

Bug Description

New version of Wicd-1.7.0 has several issues that need addressing. The first and foremost issue I'm having is its inability to "lock-on" to the wifi signal at my local "hot-spot". It repeatedly drops the signal, will attempt to reconnect once, then just sits there doing nothing until I manually intervene and force it to reconnect. Then in a short period of time it will disconnect again, then I must repeat the procedure.

In version 1.6.2.2 I don't have these problems. It would only disconnect after long periods of inactivity (which I believe was initiated by the "hot-spot"). Then it would attempt (and usually succeed) at reconnection. But unfortunately, if it couldn't reconnect it too would just sit in the tray doing nothing. But it wasn't much of an issue because it would succeed most of the time.

I'm running Gentoo "testing" ~x86.

With version 1.6.2.2 463 I'm using the following use flags; ioctl, libnotify, ncurses, and pm-utils. I used ipw as my WPA Supplicant driver and ioctl for the backend.

With version 1.7.0 552 I'm using the following use flags; X, gtk, libnotify, ncurses, nls, and pm-utils. Ioctl is no longer a valid use flag and isn't being supported in this version. So I'm using external as my backend choice since ioctl is no longer a valid choice and ipw as my WPA Supplicant driver.

I've switched back to 1.6.2.2 463 and have been pleased that my connection is behaving like it was before.

Why was support for ioctl dropped? Could this be a factor in why the newer version doesn't work as well as the previous one?

Attached is my Wicd log file.

Revision history for this message
Odysseus (robcab666) wrote :
Revision history for this message
Odysseus (robcab666) wrote :

I got tired of this issue and tried experimenting on my own. If I forcibly enable the use of ioctl by placing "net-misc/wicd -ioctl" in /etc/portage/profile/package.use.mask I'm able to recompile using the ioctl feature. Doing so then re-enabling it in the WICD applet returns ver. 1.7.0 552 to the same level of performance and connectivity I've enjoyed with previous versions.

Because of this one must assume that there is an issue with "external" that causes this choice to have much poorer connectivity than using "ioctl".

I'll attach a current WICD log file later.

I hope this helps

Revision history for this message
Ferdinand (office-chricar) wrote :

r 560
Have the same issue (added debug text)
2010/08/26 11:05:47 :: /etc/wicd/scripts/postconnect/proxy.instantinawien returned 0
2010/08/26 11:05:47 :: Connecting thread exiting.
2010/08/26 11:05:47 :: ifconfig eth1
2010/08/26 11:05:47 :: IP Address is: 192.168.2.2
2010/08/26 11:05:47 :: Sending connection attempt result Success
2010/08/26 11:05:47 :: ifconfig eth0
2010/08/26 11:05:47 :: Forced disconnect on value: True

changed the backend to "ioctl NOT SUPPORTED" and it WORKS out of the box

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.