network-manager issues with system settings AND secrets (Was: doesn't save wep key on a "system setting" connection)

[Fausto Piovesan]

Binary package hint: network-manager

Network manager on intrepid beta doesn't save your wep key if you set a connection as "system setting", so I have to re-type the wep key every time I reboot.

Steps to reproduce:
1. Create a connection and check the "system setting" option
2. Enter your wep key on the wireless security tab
3. Reboot

After the reboot you won't be able to connect by selecting the connection on the drop down on the network-manager applet. Instead it immediately tells me that I'm disconnected without even trying to connect or asking for the key. The only way to re-enable the connection is to go back to the edit dialog and re-enter the key there (the field will be empty).

Also if you create a connection without setting "system setting" and later change to "system setting" it will keep using the key from the keyring for the purpose of displaying it on the edit dialog, but won't use it to connect.

Steps to reproduce:
1. Create a connection and do not check "system setting"
2. Enter your wep key on the wireless security tab
3. Create a new keyring to store the wep as prompted.
4. Go back to "Editing SSID" dialog and check "system setting". Important: also change any other settings on the bottom tabs or else it won't save the change to the "system setting" flag.
5. Reboot

After the reboot you won't be able to connect by selecting the connection on the drop down on the network-manager applet. The only way to connect is by following this steps:
1. Go back to the edit dialog for that connection. Note: at this point you have to type your keyring password because it is still reading the password from the keyring for the purpose of displaying on this dialog only.
2. On the wireless security tab delete one character from the key and retype it (or type a random char and then delete it)
3. Click ok

I found this post on the ubuntu forums that appears to be related but I'm not sure:
http://ubuntuforums.org/showthread.php?t=934575

[Alexander Sack (asac)]

the latest intrepid version should fix this. please verify.

[Fausto Piovesan (faustop)]

No, the bug still persists after latest upgrades.

Also, I forgot to mention, I'm using the 64 bit version of intrepid
(it probably doesn't make any difference).

2008/10/12 Alexander Sack <email address hidden>:
> the latest intrepid version should fix this. please verify.
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> network-manager doesn't save wep key on a "system setting" connection
> https://bugs.launchpad.net/bugs/281711
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Alexander Sack (asac)]

On Sun, Oct 12, 2008 at 12:06:36PM -0000, Fausto Piovesan wrote:
> No, the bug still persists after latest upgrades.
>
> Also, I forgot to mention, I'm using the 64 bit version of intrepid
> (it probably doesn't make any difference).

you have to create a new connection. that should work.

>
> 2008/10/12 Alexander Sack <email address hidden>:
> > the latest intrepid version should fix this. please verify.
> >
> > ** Changed in: network-manager (Ubuntu)
> > Status: New => Incomplete
> >
> >
>

 - Alexander

[Sandor Pinter (pinter-sandor)]

I can confirm this bug.... Just now I upgraded from hardy, and it does not save the wep-key..... even if I create a new connection.
I seems it saves the wep-key in the configuration file, and it is in the dbus-message too, but it does not connect, and it is not in the dialog.

[Alexander Sack (asac)]

OK, this seems to be tricky and there are a bunch of problems involved here.

Fausto, can you confirm that your bug evaluation in description is still accurate with the latest NM in intrepid?

[Fausto Piovesan (faustop)]

Alexander, I just tested it again and yes, bug is still there in latest NM (0.7~~svn20081018t105859-0ubuntu1).

[ChrisH (tipichris)]

I'm experiencing the same issue with a fresh installation of intrepid. Connections not marked system are retained, but those marked system are not. Additionally, a 'non-system' setting can not be changed to system - this setting is also lost.

$ dpkg -l network-manager* | grep ^ii
ii network-manager 0.7~~svn20081018t105859-0ubuntu1 network management framework daemon
ii network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1 network management framework (GNOME frontend
ii network-manager-openvpn 0.7~~svn20081015t024626-0ubuntu1 network management framework (OpenVPN plugin

[Gene Caldwell (gene-caldwell)]

I too have this problem, however I am not sure the details are the same. As stated, when system setting is checked for a wireless connection, upon reboot the status is reverted to the previous state where its unchecked. this results in frequent connection/disconnection from the AP. The symptom however goes away if a checkmark is placed in the system setting box, BUT NOT rebooted. Then it returns on the next re-boot. I have deleted the connection several times and re-created a new one but nothing seems to fix this issue. I have also gone in to authorizations and explicitly added my self to the system setting network-manager with no restrictions and that does not resolve the problem either.

Of interesting note however: when I preform a clean install of 8.10, AND the wireless drivers are available DURING install AND wirelessly connected to the AP, Then everything seems to work as it should, the connection does get saved as a system setting and no disconnects happen. the only time I seem to have this problem is after the fact CHANGES to the wireless connections. So in short, this system setting only works during initial install IF all the details of the connection AP are known and working.

[Alexander Sack (asac)]

(Confirmed will make it less likely that a dev looks at this than triaged)

Could you please test the intrepid packages in the network-manager team PPA? https://edge.launchpad.net/~network-manager/+archive

Thanks!

[schmeii (schmeii)]

This is fixed in jaunty (0.7-0ubuntu1)

[ozstriker78 (ozstriker78)]

I went ahead and installed the new intrepid PPA release and I noticed that the "system setting" check-box is missing. Since this is missing, how can I make my wireless connection auto-connect at boot time without having to log into my desktop?

[schmeii (schmeii)]

In jaunty you have a checkbox "All users" in the bottom.

[Gene Caldwell (gene-caldwell)]

"In jaunty you have a checkbox" well, that's nice, however this is an issue with intrepid and this bug was reported for intrepid. Can we please keep THIS bug post limited to intrepid and open a bug report for jaunty when it is released ? We are here looking for solutions to a current release OS bug. I do not see how this PPA proposed update has solved the problem. I have installed the PPA for intrepid and see only a limited reduction in disconnects and now I'm starting to see other issues as a result. I'm not convinced removing the check box has solved the problem. I took note that DBUS was updated when I upgraded NM to this PPA version and now I see other issues that I am still trying to nail down. So in short, how was removing this checkbox susposed to resolve the problem ? What other changes were made to the PPA version that were trying to address this issue ?

[Gene Caldwell (gene-caldwell)]

I'm not finding that this ppa has fixed the disconnect issues in 8.10. I just can't get the wireless to stay connected.

[Alexander Sack (asac)]

On Thu, Feb 05, 2009 at 02:22:42PM -0000, Gene Caldwell wrote:
> "In jaunty you have a checkbox" well, that's nice, however this is an
> issue with intrepid and this bug was reported for intrepid. Can we
> please keep THIS bug post limited to intrepid and open a bug report for
> jaunty when it is released ? We are here looking for solutions to a

No, please nominate _this_ bug for intrepid and don't open a new bug.

Thanks!

 - Alexander

[Alexander Sack (asac)]

On Fri, Feb 06, 2009 at 04:07:46PM -0000, Gene Caldwell wrote:
> I'm not finding that this ppa has fixed the disconnect issues in 8.10. I
> just can't get the wireless to stay connected.
>

Thats not this bug. Most likely its a driver issue; so either file
against linux package or against NM if you want me to take a
look. Remember to include your syslog part that shows the disconnect.

Also consider to test the latest jaunty kernel as wireless drivers are
constantly improving.

 - Alexander

[Sandor Pinter (pinter-sandor)]

For me it works fine now. Thanks!

I have the latest packages from the lauchpad repository, and it works fine. Actually I don't know which package fixed this issue, becuase I have checked it just now, after I saw the activity on this bug.