ok, i renamed this bug to be more specific. if that doesnt really match your issue, please file a new bug. This definitly includes when you have problems getting access to network.
Anyway, i see several issues reported so far here, which I would like to comment on now: 1. the original reporter (marcobra) was confused by the result of the managed=true setting in /etc/NetworkManager/nm-system-settings.conf and uninstalled. This issue should be fixed. 2. Dazzer, you apparently want to manage your ips in /etc/network/interfaces. if you do that you cannot do that in NM anymore. There was a bug that made all apps start in offline mode when you configured your devices like that, but that is fixed now. 3. Claudio, you were struck by the same bug that should be fixed now. With any device being unmanaged we will tell the applications that you are CONNECTED. so fixed too. 4. Kadafi, you didnt provide any info on what behaviour you see. if its exactly what the original reporter described, then its fixed for you too. 5. sheka, Ryan, mrbean, Raimund, Sokraates, lohmatyi your bug is fixed like i said in 2. and 3. above. 6. Bryson, the ifupdown plugin is ment for support of old configurations and not to edit it. You should remove your configuration from interfaces. then you can use managed=true or managed=false, just as you wish. 7. Claudio, Sergey, please file a bug about the not honoured config values and provide sample configuration. 8. Shirish, Jeffrey, please file an individual, proper bug too. Thanks. Closing this bug. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- network-manager unmanaged mode causes confusion (Devices not managed after reboot) https://bugs.launchpad.net/bugs/279262 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
