One problem as I see it is that the Network Manager applets/widgets should have a simple option to changed "unmanaged" devices to "managed." All it takes is for a "managed=true" line in nm-settings.conf to be changed to "managed=false" and Network Manager is stuck! The only way to fix it is to fix that configuration file, and if a user can't get online to find the solution, he'll be stuck! (And probably will switch to Windows, too.)
This or a similar problem happened when I ran nm-applet in KDE because of plasma-widget-networkmanager's inability to handle DSL PPPoE connections. Suddenly after rebooting, the line in the conf file was set to managed=false, and the widget lacks the ability to return the device to managed mode, and so I couldn't get online. Deleting the file and restarting NM fixes it, or doing: $(sudo sed -i "s/managed=false/managed=true/g" /etc/NetworkManager/nm- system-settings.conf && sudo restart network-manager) fixes it also. I remember encountering this bug over a year ago when testing a newer release of Kubuntu...and so I stayed with Hardy. But here we are in Maverick and the bug is still there. *sigh* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/279262 Title: [regression] devices/interfaces not set to "auto" in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before) -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
