> why do you want to use the applet? If you want to use them you should enable
> managed=true in /etc/NetworkMananger/nm-system-settings.conf
> otherwise you opt into using the old ifupdown - thats the feature.
I would not have complained if that was really the case. The problem is that NetworkManager
kills my eth0 and then nm-applet does not offer any way to get network connectivity back.
If I restart NetworkManager later, it suddenly works, which is not consistent in its own right.
I believe that NetworkManager should have two absolute requirements:
1. if any device is touched at all by NetworkManager, then nm-applet must be visible
2. a restart of NetworkManager may not change nm-applet's view of the NM state.
BTW: my "wanted" operation mode for NM would be to leave my wired connection's initial state alone,
or at least leave the /etc/network/interfaces decision on the default interface active. I'd like to use
NM for wireless, and I'd be ok to use it for wired (if it'd work).
> why do you want to use the applet? If you want to use them you should enable anger/nm- system- settings. conf
> managed=true in /etc/NetworkMan
> otherwise you opt into using the old ifupdown - thats the feature.
I would not have complained if that was really the case. The problem is that NetworkManager
kills my eth0 and then nm-applet does not offer any way to get network connectivity back.
If I restart NetworkManager later, it suddenly works, which is not consistent in its own right.
I believe that NetworkManager should have two absolute requirements:
1. if any device is touched at all by NetworkManager, then nm-applet must be visible
2. a restart of NetworkManager may not change nm-applet's view of the NM state.
BTW: my "wanted" operation mode for NM would be to leave my wired connection's initial state alone, interfaces decision on the default interface active. I'd like to use
or at least leave the /etc/network/
NM for wireless, and I'd be ok to use it for wired (if it'd work).