network manager not keeping the wep key (intrepid)

Bug #270818 reported by James Dupin
10
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

my bug looks like old bug #36651

Put my wep key in, it works.

If i restart the computer or If I log out or if I switch wifi AP then it asks me again for the key.

Ubuntu intrepid (development branch) alpha 5 up to date as of Sept 16, 7:00 UTC
network-manager:
  Installed: 0.7~~svn20080908t183521+eni0-0ubuntu2
  Candidate: 0.7~~svn20080908t183521+eni0-0ubuntu2
  Version table:
 *** 0.7~~svn20080908t183521+eni0-0ubuntu2 0

Revision history for this message
Steven (stebalien) wrote :

Same problem here. Network Manager will neither store the WEP key in the gnome-keyring nor in the system configuration file (If I check the "system wide" checkbox).

Revision history for this message
Davíð Jakobsson (rimmugygur) wrote :

I have the same problem with nm 0.7 on hardy. It only remembers passwords during the session and the password that where in the keyring before upgrading to nm 0.7. Also I am not able to add the password to the ssid through edit connection. NM forgets it as soon as I hit OK.

I am running:
apt-cache showsrc network-manager | grep dsc |awk '{split($0,out," "); print out[3]}'
network-manager_0.6.6-0ubuntu5.dsc
network-manager_0.7~~svn20080908t183521+eni0-0ubuntu4~nm1~hardy1.dsc

Revision history for this message
Yotam Benshalom (benshalom) wrote :

I can confirm the same problem. My 128/40 bit key was stored correctly while using Hardy, but after upgrading to Intrepid I have to re-enter it each time even though "edit connection". I have Intel 3945 wireless chipset on a 32-bit system; I will be happy to supply further details if needed.

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #271097, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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

Other bug subscribers

Remote bug watches

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