Hi, I also had this strange behaviour. The ifupdown module wasn't loaded, anymore: $ cat /etc/NetworkManager/nm-system-settings.conf [main] plugins=keyfile
[ifupdown] managed=true I never removed it from there, definitely. Downgrading to 0.7.2 also fixed it for me, without changing this file. This means that 0.7.999 is too smart for real life. Why is actually possible to not load it if the system goes berserk without it? Additionally, it modified a file in /etc at runtime (/etc/hosts) which is not acceptable. OTOH, this bug should also be on the d-bus packages because software depending on d-bus (like whole KDE) shouldn't become useless just because the hostname changes! This is ridiculous. HS PS: The README.Debian section about managed mode is very hard to understand. Just don't use the word "unmanaged". Humans usually do not cope well with multiple negations Thus e.g. 'Devices listed in /etc/network/interfaces _will_ be managed by NetworkManager unless the ifupdown system-config-setting is enabled and is setup to run in "Unmanaged mode".' should better be something like 'Settings from /etc/network/interfaces are not considered by NetworkManager if the "ifupdown" plugin is not used.' -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
