NetworkManager Warnings in Slackware 14 RCx

shadowsnipes · 08-26-2012, 12:49 PM

NetworkManager seems to be working properly for me most of the time. However, every bootup I get these warnings:

Code:

Aug 24 22:23:47 slackcur NetworkManager[1552]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory
Aug 24 22:23:47 slackcur NetworkManager[1552]: <warn> failed to allocate link cache: (-10) Operation not supported
Aug 24 22:23:47 slackcur NetworkManager[1552]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Aug 24 22:23:48 slackcur dhcpcd[1575]: eth0: sendmsg: Cannot assign requested address

I don't understand why it is looking in /usr/lib/NetworkManager for plugins (config issue during program building?), and I don't use anything bluetooth on my machine.

I'm just testing it with one ethernet interface using DHCP. As I mentioned previously, my connection is working just fine; I just find the initial warning/error strange.

Similarly, I often get this error on shutdown:

Code:

Aug 25 14:34:50 slackcur NetworkManager[1560]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.13': no such name

These are all from syslog. Anybody else seeing these? I can enable more verbose output to see what I get...

kingbeowulf · 09-01-2012, 02:20 PM

I'm getting the same networkmanager warning (connecting via wifi) on RC4

Code:

Aug 31 23:52:18 slacker64 NetworkManager[1696]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory

The 'link cache' warning appears also, but this might just be a networkmanager "feature" - not sure though.

I got rid of bluetooth warning/errors by disabling and blacklisting: as this laptop does not have BT capability, but does have chipset support for the [not present] add-on device, the kernel and KDE kept trying to find a nonexisting BT device. Although networkmanager, the idiot that it is, keeps looking for bluez.

I don't get the "org.freedesktop.NetworkManager.wifi.share.open" warning.

I think, though, that I will dump networkmanager for WICD until it matures a bit more. I don't need any of its fandangled features anyway.

Darth Vader · 09-01-2012, 02:44 PM

Quote:

Originally Posted by kingbeowulf

I'm getting the same networkmanager warning (connecting via wifi) on RC4

Code:

Aug 31 23:52:18 slacker64 NetworkManager[1696]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory

The directory /usr/lib/NetworkManager is where NetworkManager looks for plugins. Yes, it have plugins.

To note that directory doesn't exist in the its package, then I can invoke an wrong packaging for NetworkManager...

Quote:

Originally Posted by kingbeowulf

Although networkmanager, the idiot that it is, keeps looking for bluez.

No, isn't idiot, just compiled with bluez support.

Quote:

Originally Posted by kingbeowulf

I think, though, that I will dump networkmanager for WICD until it matures a bit more. I don't need any of its fandangled features anyway.

Lets do not compare an WiFi manager (WICD) with an complete integration of network management (NM)...

I.e. enlight me how you can manage with WICD an (Open)VPN connection over an USB 3G modem.

shadowsnipes · 09-01-2012, 02:57 PM

FWIW if you just create the directory /usr/lib/NetworkManager the first error (can't find plugin directory) will go away. This still doesn't explain why it looks there though.

Edit: To clarify what I meant, NetworkManager already appears to be using the plugins, but it definitely isn't finding them in /usr/lib/NetworkManager. Perhaps that's just where it looks first?

Maybe the directory should be added to the package...

kingbeowulf · 09-01-2012, 03:21 PM

Well, Darth Vader is both right and wrong.

Networkmanger should be smart enough to know that I do not have bluez devices installed.

The plugin directory should be there if it is needed and if its looked for (ie via "make install... or cmake whatever). shadowsnipes is correct, and there are examples where this was the fix for some 13.x packages (e.g. NFS). But this in "unclean" to have to set up package directories - that's what a package is used for.

Quote:

...I don't need any of its fandangled features anyway.

Enlighten me why I should give a damn about VPN on a 3G modem? Most users will used networkmanager as a simple network manager. WICD is plenty good enough for simple wired and wifi network management, and IMHO works a lot better.