MASTER cannot save "auto" connection without renaming the connection

[Jan]

In nm-connection-editor editing a wireless connection, selecting "System setting", and pressing "OK" does not work. This setting seems to be forgotten immediately. When open the connection again the "System setting" checkbox is still unchecked.

[Jan (jan23)]

I forgot to mention that I am using Ubuntu 8.10 Intrepid.

[Jean-Baptiste Lallement (jibel)]

thanks for your report. affecting to network-manager.

[Thierry Carrez (ttx)]

Confirmed here. This is not specific to wireless.

(Weird) workaround: check the "system settings" checkbox, THEN uncheck the "Automatic connection" checkbox, check "Automatic connection" again... click Validate : n-m should trigger the sudo authentication dialog box and let you save the settings.

[Shirish Agarwal (shirishag75)]

Confirmed, that one works.

The only difference is language, it should have been :-

check the "system settings" checkbox, THEN uncheck the "connect automatically" checkbox, check "connect automatically" again... wait for sometime and then click on "Authenticate": n-m should trigger the sudo authentication dialog box and let you save the settings.

But I would need to know on next reboot if it holds.

[jared_c (jared-c)]

Confirming the bug, the work-around, and that it works like it's supposed to after reboot.

[max (maxozilla)]

I can confirm I'm having the same problem, and the workaround seems to fix it. Although then the network manager applet in the notification area on the panel disappears. Clearly the 'system setting' option was not ready to be released.

[Donald Broatch (donaldbroatch)]

I've just had the same problem trying to get my wife's account to auto-connect to wireless- the workaround works, but logging into my account, Network Manager does not appear in the tray, although there is a connection.

[maris382 (maris382)]

Donald: Your other problem is related to bug #284596.
It seems Network Manager Applet 0.7 does not work with fast user switching...

[Donald Broatch (donaldbroatch)]

I don't know. After using the workaround, my wife can use the internet when she logs on to her account, i.e., with 'System Setting' checked.

However, Network Manager now lists the same wireless router twice, once with 'System Setting' checked, and again with it unchecked.

I can delete the second entry but it keeps coming back.

The second entry always says '21 days ago', and the first '3 days ago'.

[Bruma (matjaz.brumec)]

Confirming the bug.

[Andy Stallwood (andy-stallwood)]

I can confirm seeing the same symptoms as Donald, not due to fast user switching.

When I apply the workaround, Network manager doesn't appear in the tray, whereas it did before.

Andy

[Andy Stallwood (andy-stallwood)]

Also, I can get the tray icon to appear by running nm-applet, so that is definitely a different bug to bug #284596.

[B@MB@M (bart-bamweb)]

confirming the bug and the workaround.

ubuntu 8.10, Dell D610

[rynop (ryan-pendergast)]

The work around does not work as expected for me. I follow the steps above, and indeed it saves the 'system' setting as well as the wireless key.

However, on reboot, I expect the system setting for wireless to connect to the wireless router before logging in (so I should be connected by the time I see the login screen). This is not happening.

According to http://www.ubuntu.com/testing/intrepid/alpha5#Network%20Manager%200.7 "system wide settings (i.e., no need to log in in order to get a connection)". This function is not working for me with wireless connection...

Is there a workaround for this? 8.10, 32bit. Atheros driver.

[Andy Stallwood (andy-stallwood)]

ryanop, I used to have this problem, but the most recent update has solved this. If I'm quick logging in, then I can normally just catch the wireless trying to connect still, but if I take it a bit more leisurely, then it's normally connected before I log in.

PS you can ignore my comment about the tray icon as well, as that's working fine for me. Not sure what changed to make that happen. it fixed itself before the last update to NM, so it may have just needed a couple of reboots :-)

[Vitor Lamas Gatti (vitorgatti)]

This bug is already fixed.
Ubuntu devs just need to attach the LATEST version of NetworkManager, found here:
http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/

The latest released is 27-Nov-2008, and not a svn20081018, that is the one we are using now.

[Alexander Sack (asac)]

Vitor Lamas Gatti wrote:
> This bug is already fixed.
> Ubuntu devs just need to attach the LATEST version of NetworkManager, found here:
> http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
>
> The latest released is 27-Nov-2008, and not a svn20081018, that is the
> one we are using now.
>
>
for those eager to get final NM 0.7, you can get an intrepid build for
it from the ~network-manager PPA.

[nandemonai (junin-toiro)]

On Sun, Dec 28, 2008 at 10:59 AM, Alexander Sack <email address hidden> wrote:
> Vitor Lamas Gatti wrote:
>> This bug is already fixed.
>> Ubuntu devs just need to attach the LATEST version of NetworkManager, found here:
>> http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
>>
>> The latest released is 27-Nov-2008, and not a svn20081018, that is the
>> one we are using now.
>>
>>
> for those eager to get final NM 0.7, you can get an intrepid build for
> it from the ~network-manager PPA.
>
> --
> MASTER cannot save "auto" connection without renaming the connection
> https://bugs.launchpad.net/bugs/284298
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Is there an ETA on when/if this will make it into the repos?

Cheers.

--
Sam Jackson / Nandemonai / Junin Toiro

[Alexander Sack (asac)]

nandemonai wrote:
> On Sun, Dec 28, 2008 at 10:59 AM, Alexander Sack <email address hidden> wrote:
>
>> Vitor Lamas Gatti wrote:
>>
>>> This bug is already fixed.
>>> Ubuntu devs just need to attach the LATEST version of NetworkManager, found here:
>>> http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
>>>
>>> The latest released is 27-Nov-2008, and not a svn20081018, that is the
>>> one we are using now.
>>>
>>>
>>>
>> for those eager to get final NM 0.7, you can get an intrepid build for
>> it from the ~network-manager PPA.
>>
>> --
>> MASTER cannot save "auto" connection without renaming the connection
>> https://bugs.launchpad.net/bugs/284298
>> You received this bug notification because you are a direct subscriber
>> of a duplicate bug.
>>
>>
>
> Is there an ETA on when/if this will make it into the repos?
>
>
for jaunty soonish ... for intrepid ... unsure if we can do this at all
... most likely have to backport a bunch of patches instead.

[launcspad (weblev-deactivatedaccount)]

Thanks for the workaround! I opened a new bug which is parti duplication of this:

https://bugs.launchpad.net/ubuntu/+bug/314831

But I've written a little bit more about my experiences.

[benske (ben-beuster)]

Confirmed

[Paul Perkins (thirdspace)]

Ubuntu 8.10.
Wired and Wireless connections, sometimes use one, sometimes the other.
DHCP works, but I want to use fixed addresses on some networks even when DHCP server is available.
Bug: changes made via the NetworkManager applet sometimes stick, but usually get silently thrown away either at once, or after logout, or on reboot. Silently thrown away changes probably correlate to the "system settings" checkbox. I can sometimes get system to ask for my password using the workaround described above, but not always, and I'm not convinced even that assures my changes will stick.

When I delete the "Auto eth0" network, it comes back on the next reboot.
When I disable Wireless (applet right-click menu), it is enabled again on the next reboot.

There seems to be no documentation anywhere I can find that tells me anything about NetworkManager except that I am supposed to love it, and trust that it knows what I want better than I do. But it does not!!!

[Vitor Lamas Gatti (vitorgatti)]

Paul Perkins, this bug has already been fixed in the latest version of NetworkManager, but it is not available officially for Ubuntu 8.10 yet.
I don't know and I don't understand why, but it's not.

If you want an official patch, you'll have to wait. If you don't care about installing alternative patches, so follow these instructions Alexander Sack provided:
"for those eager to get final NM 0.7, you can get an intrepid build for
it from the ~network-manager PPA."

Good luck!

[Carles Codony (bitblitter)]

I got the 'fixed' version and now I'm not even able to edit the 'auto' connections to, for example, use OpenDNS instead of my ISP's DNS servers.

[Vladimir-csp (vladimir-csp)]

Auto connections are not to be edited.
Create new and change it the way you want. You would also want to make it system-wide and bind to your ethernet device by mac-address, so it would replace Auto connection with same mac-address.

[Phoenix (phoenix-dominion)]

I have created wired connections from scratch and I am not able to save "system setting"

Furthermore, NM nowhere says, that an "Auto" connection can not be modified, while it is true it is total obfuscation and can not be known by not digging some internet resource.

Anyhow, your answer does not state if you can't rename an Auto connection and thus migrate it into a regular connection - if this is possible, than I can still not apply "system setting" to my wireless connections and if not than it is a terrible design, by providing a drop down menu to choose a wireless network but if you want to have it system wide to make me type in the SSID by hand.

[Vitor Lamas Gatti (vitorgatti)]

Phoenix wrote:
> and if not than it is a terrible design, by providing a drop down
> menu to choose a wireless network but if you want to have it
> system wide to make me type in the SSID by hand.

I totally agree with that.
I can't understand why making everything more difficult, when was easier before.

[Alexander Sack (asac)]

this is fixed in jaunty; auto connections are now properly marked as read-only so you cannot really change them which makes this bug go away.

[Vitor Lamas Gatti (vitorgatti)]

Alexander,

Thanks a lot for the bugfix, but... and to set a connection as System-Configuration? Will this be possible or Only the read-only for auto-connections will be fixed?

Thanks

[Id2ndR (id2ndr)]

Actualy this "fix" (the word workaround sounds better to me) create other troubles.
I'm not able anymore to change my wired connexion settings : I can't manually set IP adress. I have to create a new connexion by hand BUT this will not be the one that will be use by default. NM will try the auto connexion before try an other when the DHCP timeout.

[Saivann Carignan (oxmosys)]

Alexander Sack : The initial problem was that wired connexion parameters did not survive to a reboot, now no parameter can be applied at all. I think it's obvious that we only have two options.

1. Re-open this bug.
2. Write a better new bug report.

However, the fact that wired network can't be configured in jaunty network-manager can't be ignored. Networking is vital, especially wired networks which are the most used networks.

[Bassu Khan (bashukhan)]

Saïvann Carignan, right said!
Interpid needs the fix as well because this is what currently recommended for production environments and it has a longer end of life than other versions.

So, please push the fix for Interpid as well.

Thanks.

[Max Bowsher (maxb)]

Bassu: Hardy is a Long Term Support release, Intrepid has the ordinary 18-month end-of-life.

[Bassu Khan (bashukhan)]

Thanks for the correction, Max.
I now can live with this bug because of course I cannot move back and forth with the reinstallation, LOL~

[Alexander Sack (asac)]

backporting the fix for this to intrepid without changing UI is a really tough task. if you have a safe patch i am willing to consider this. in the meantime i can only point you to the ~network-manager team ppa, where we provide backports.

[Bassu Khan (bashukhan)]

Thanks Alex.
That would be great. I really appreciate you help.

[Melkor (dan-aberg)]

The workaround does not work well for me. I click 'system setting', then change something else, and when I click ok the entry disappears from the list of network connections. To be able to keep the network setting between login's I have to repeat this step a couple of times. But after a reboot the setting is lost!
Is there an alternative to this Network Manager from Hell? And how can I configure it from a shell?

[Saivann Carignan (oxmosys)]

Melkor : This bug is fixed in jaunty (see status). If you're using a up-to-date ubuntu, you don't need a workaround.

[nandemonai (junin-toiro)]

2009/5/13 Saïvann Carignan <email address hidden>:
> Melkor : This bug is fixed in jaunty (see status). If you're using a up-
> to-date ubuntu, you don't need a workaround.
>

That being said, if you feel like sticking with Intrepid, delete the
auto connection, re-create the connection, enter in your details and
you should be asked to confirm it with gksudo.

Subsequent reboots will hold the setting then.

--
Sam Jackson / Nandemonai / Junin Toiro
http://rendai.homeunix.net/nandemonai/

[Sergio Zanchetta (primes2h)]

Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on 30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please feel free to report any other bugs you may find.
Thank you.

[Sergio Zanchetta (primes2h)]

I realized I had made a mistake.
Intrepid Ibex 8.10 "will reach" EOL on 30 "APRIL" 2010.

Sorry for this.

Anyway, I think that one month doesn't make any difference now.

[Uqbar (uqbar)]

In 10.10 and 10.04 there's no way to make a "system connection": the check box is permanently disabled.
This's a shame.

[Krzysztof Matusik (krzysztof-matusik)]

@Uqbar: check this:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/470049

[photon (photonxp)]

On Ubuntu 10.04, I had a similar problem related to /etc/resolv.conf editting.

I checked #91890,
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/91890

I found that someone already gave a nice solution for working around this weird problem as below:
Edit your /etc/resolv.conf for the nameservers you want.

And then

sudo chattr +i /etc/resolv.conf

The the resolv.conf is locked and no program could change it. If you want to change it back to be editable

sudo chattr -i /etc/resolv.conf

BTW, I found an dns checking script with the path of
/usr/lib/avahi/avahi-daemon-check-dns.sh

For those who might be interested, I pasted the script here:
https://photon.snipt.net/avahi-daemon-check-dnssh/