Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16700 - [wicd] fails to connect to wep network but connects to wpa2

Attached to Project: Arch Linux
Opened by Matthew Shannon (mdshann) - Friday, 16 October 2009, 19:41 GMT
Last edited by Isenmann Daniel (ise) - Tuesday, 26 January 2010, 06:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Isenmann Daniel (ise)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: wicd fails to connect to the WEP network where I work but connects to the WPA2-PSK network at home.

This happens when I attempt to use my laptop at work on the WEP wireless network. Works fine at home on my WPA2-PSK network. ESSID is a 10 digit number. Key is a 26 character code. I am using Archlinux x86_64 with a BCM4321 card on an HP dv6640us. The driver I am using is from broadcom. Kernel module is wl and lib80211_crypt_tkip. Package name is broadcom-wl-4.150.10.5. I log into xfce4 and wicd-client starts up and sees the wireless network. I click connect on the GUI and it sits there saying 'Closing Active Connections...' on the bottom with the progress bar stuck in position. I go to the terminal and do

#iwconfig eth0 essid "essid" key somekey
#dhcpcd eth0

and it connects. Wicd then shows that I have an active connection. So far I have made sure that my modules and daemons are loading in the correct order according to the wicd entry in the Arch Wiki, uninstalled wicd and removed /etc/wicd/ and then reinstalled wicd. This is documented here : http://bbs.archlinux.org/viewtopic.php?pid=637752#p637752

I am not a programmer but if you need me to upload or change any files I can give it a try. If you need any more information please ask!


Additional info:
* package version(s)

wicd is version 1.6.2.2 463

* config and/or log files etc.

2009/10/15 21:06:48 :: ---------------------------
2009/10/15 21:06:48 :: wicd initializing...
2009/10/15 21:06:48 :: ---------------------------
2009/10/15 21:06:48 :: wicd is version 1.6.2.2 463
2009/10/15 21:06:48 :: setting backend to external
2009/10/15 21:06:48 :: trying to load backend external
2009/10/15 21:06:48 :: successfully loaded backend external
2009/10/15 21:06:48 :: trying to load backend external
2009/10/15 21:06:48 :: successfully loaded backend external
2009/10/15 21:06:48 :: Automatically detected wireless interface eth0
2009/10/15 21:06:48 :: setting wireless interface eth0
2009/10/15 21:06:48 :: automatically detected wired interface eth1
2009/10/15 21:06:48 :: setting wired interface eth1
2009/10/15 21:06:48 :: setting wpa driver wext
2009/10/15 21:06:48 :: setting use global dns to False
2009/10/15 21:06:48 :: setting global dns
2009/10/15 21:06:48 :: global dns servers are None None None
2009/10/15 21:06:48 :: domain is None
2009/10/15 21:06:48 :: search domain is None
2009/10/15 21:06:48 :: setting automatically reconnect when connection drops True
2009/10/15 21:06:48 :: Setting dhcp client to 0
2009/10/15 21:06:48 :: Wireless configuration file found...
2009/10/15 21:06:48 :: Wired configuration file found...
2009/10/15 21:06:48 :: chmoding configuration files 0600...
2009/10/15 21:06:48 :: chowning configuration files root:root...
2009/10/15 21:06:48 :: Using wireless interface...eth0
2009/10/15 21:06:48 :: Using wired interface...eth1
2009/10/15 21:06:54 :: Autoconnecting...
2009/10/15 21:06:56 :: No wired connection present, attempting to autoconnect to wireless network
2009/10/15 21:06:59 :: Autoconnecting...
2009/10/15 21:06:59 :: No wired connection present, attempting to autoconnect to wireless network
2009/10/15 21:07:04 :: Autoconnecting...
2009/10/15 21:07:04 :: No wired connection present, attempting to autoconnect to wireless network
2009/10/15 21:07:09 :: Autoconnecting...
2009/10/15 21:07:09 :: No wired connection present, attempting to autoconnect to wireless network
2009/10/15 21:08:24 :: canceling connection attempt


Steps to reproduce:

unknown... could be specific to my hardware.
This task depends upon

Closed by  Isenmann Daniel (ise)
Tuesday, 26 January 2010, 06:24 GMT
Reason for closing:  Fixed
Comment by Isenmann Daniel (ise) - Monday, 19 October 2009, 16:30 GMT Comment by Matthew Shannon (mdshann) - Tuesday, 20 October 2009, 23:25 GMT
Yeah I posted that too but forgot to link to it here. Looks like no one else has had this issue. Do you have any other suggestions other than what I have already tried? Anything more I can look at or upload that may shed some light on this issue? Thanks!
Comment by Isenmann Daniel (ise) - Tuesday, 19 January 2010, 18:02 GMT
Can you please test this with the newest wicd (1.7.0) version from extra.
Comment by Isenmann Daniel (ise) - Thursday, 21 January 2010, 11:14 GMT
If there is no feedback until 1st February, I will close this bug as fixed.
Comment by Matthew Shannon (mdshann) - Monday, 25 January 2010, 23:54 GMT
Sorry to take so long in getting back to you. The new version seems to have solved the problem. Are you able to tell me what the change may have been that solved this issue?
Comment by Isenmann Daniel (ise) - Tuesday, 26 January 2010, 06:24 GMT
No, not really. But you can have a look at the changelog here: http://bbs.archlinux.org/viewtopic.php?pid=689878#p689878

Loading...