The version you've just bumped is not working for me. Leaving the default cfg settings I get: ug 21 14:20:36 whitebox NetworkManager: <ERROR> [1282393236.430344] main (): Fai led to initialize the network manager: Could not load plugin 'ifnet': /usr/lib64/Network Manager/libnm-settings-plugin-ifnet.so: cannot open shared object file: No such file or directory Aug 21 14:20:36 whitebox NetworkManager: traceback: Aug 21 14:20:36 whitebox NetworkManager: /usr/sbin/NetworkManager(main+0xf89) [0x 43a9d9] Aug 21 14:20:36 whitebox NetworkManager: /lib/libc.so.6(__libc_start_main+0xfd) [ 0x7f2c3c726bbd] Aug 21 14:20:36 whitebox NetworkManager: /usr/sbin/NetworkManager() [0x41bb19] Aug 21 14:20:36 whitebox kernel: NetworkManager[23212] trap int3 ip:43aa5e sp:7fff4aa462 60 error:0 Aug 21 14:20:49 whitebox dbus-daemon: [system] Reloaded configuration Aug 21 14:20:49 whitebox dbus-daemon: [system] Reloaded configuration I had to remove "ifnet" from "plugins=ifnet,keyfile" in /etc/NetworkManager/nm-system-settings.conf and then everything has started running smooth.
I have networkmanager installed only with "bluetooth" and "connection-sharing" useflags.
Seeing this as well. The lib /usr/lib64/NetworkManager/libnm-settings-plugin-ifnet.so is needed, but not provided by NetworkManager.
I am in the process of rebuilding my machine, so I don't have NetworkManager installed yet. Could someone seeing this bug please post 'emerge --info'.
Created attachment 243875 [details] emerge --info
(In reply to comment #2) > Seeing this as well. > > The lib /usr/lib64/NetworkManager/libnm-settings-plugin-ifnet.so is needed, but > not provided by NetworkManager. > That plugin is provided by NetworkManager ebuild in version 0.8.1-r5 so I guess it is something related to that.
Created attachment 243879 [details] emerge --info
I had the same issue and resolved it by upgrading to a newer version of networkmanager. After emerging eix, I ran "eix networkmanager" and found that the newest unstable version is 0.8.1-r3. I unmasked it by adding networkmanager and a dependency to /etc/portage/package.keywords: "net-misc/networkmanager ~amd64" "net-dial/ppp ~amd64" Then I ran my world update "emerge -avuDN world". After that finished, networkmanager automatically started and my nm-applet was working as well. I havent tried any i686 kernels with the "~x86" keyword, but I'd say it's worth a shot. I really hope this helps.
The ebuilds for NetworkManager all insert a common nm-system-settings.conf from the FILESDIR. This config file is only compatible with version 0.8.1-r3 since it's the only version bundled with the ifnet plugin. There needs to be 2 versions of nm-system-settings.conf one for 0.8.1 and another for 0.8, 0.7.2 and 0.7.1
(In reply to comment #8) > The ebuilds for NetworkManager all insert a common nm-system-settings.conf from > the FILESDIR. This config file is only compatible with version 0.8.1-r3 since > it's the only version bundled with the ifnet plugin. > > There needs to be 2 versions of nm-system-settings.conf one for 0.8.1 and > another for 0.8, 0.7.2 and 0.7.1 > I agree with that but I wonder why the maintainer bumped it if such a huge bug is there. Don't get me wrong, I don't want to start a discussion here, but I think things like these should be avoided. Moreover if the app won't work at all and, as happened to me, I had to debug the issue without having net support. It's not a nice.
I think this bug is a duplicate of bug #333257 and I guess we have to give a version number to nm-system-settings.conf.
I'm really sorry, that was my mistake. Everything should be now fixed. If you're using 0.8-r1, please re-emerge it.
