Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Pavel Simerda" > To: "Uldis Jansons" > Cc: "Thomas Haller" , networkmanager-list@gnome.org > Sent: Thursday, December 19, 2013 12:42:21 PM > Subject: Re: NetwokManager fails to start with core dumped > > - Original Message - > > From: "Uldis Jansons" > > To: "Thomas Haller" > > Cc: networkmanager-list@gnome.org > > Sent: Thursday, December 19, 2013 9:55:24 AM > > Subject: Re: NetwokManager fails to start with core dumped > > > > > > - Original Message - > > > From: "Thomas Haller" > > > To: "Uldis Jansons" > > > Cc: networkmanager-list@gnome.org > > > Sent: Thursday, December 19, 2013 10:00:02 AM > > > Subject: Re: NetwokManager fails to start with core dumped > > > > > > On Thu, 2013-12-19 at 09:27 +0200, Uldis Jansons wrote: > > > > > > > Unfortunately I cannot see it in > > > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/ > > > > Maybe I look in the whong place? > > > > > > Hi Uldis, > > > > > > it is the right place. See the branch 'nm-0.9.8' > > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-0-9-8 > > > > > > > > > Thomas > > > > Thanks Thomas, > > > > That solved build problem. Now execution of make finishes without > > errors. > > But we still have the netlink problem on a pristine Ubuntu without > app armor. Is there an Ubuntu bug report for that? > > Pavel Apparently the problem is releated to libnl included in Ubuntu packages. This package cannot be removed painlessly and obviously conflicts with the one built from source. In my case solution is to choose newer Ubuntu distro (13.10) as Ubuntu 12.04 LTS obvioulsy getting old after all. Thank you all for the input. Uldis ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Uldis Jansons" > To: "Thomas Haller" > Cc: networkmanager-list@gnome.org > Sent: Thursday, December 19, 2013 9:55:24 AM > Subject: Re: NetwokManager fails to start with core dumped > > > - Original Message - > > From: "Thomas Haller" > > To: "Uldis Jansons" > > Cc: networkmanager-list@gnome.org > > Sent: Thursday, December 19, 2013 10:00:02 AM > > Subject: Re: NetwokManager fails to start with core dumped > > > > On Thu, 2013-12-19 at 09:27 +0200, Uldis Jansons wrote: > > > > > Unfortunately I cannot see it in > > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/ > > > Maybe I look in the whong place? > > > > Hi Uldis, > > > > it is the right place. See the branch 'nm-0.9.8' > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-0-9-8 > > > > > > Thomas > > Thanks Thomas, > > That solved build problem. Now execution of make finishes without errors. But we still have the netlink problem on a pristine Ubuntu without app armor. Is there an Ubuntu bug report for that? Pavel > > Uldis > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Pavel Simerda" > To: "Uldis Jansons" > Cc: "Dan Williams" , networkmanager-list@gnome.org > Sent: Wednesday, December 18, 2013 2:06:22 PM > Subject: Re: NetwokManager fails to start with core dumped > > As I said already on IRC, I suspect some sort of a system problem > here. Did you check whether it could be caused by some selinux, > apparmor or similar tool or by some specific kernel configuration? > Is the system in any way specific, different from other systems? > Could you reproduce with a fresh installation? > > Cheers, > > Pavel This morning I reinsalled fresh copy of system: 1) Ubuntu 12.04.2 amd64 server 2) couple of necessary packages (build-essential intltool libglib2.0-dev libgudev-1.0-dev usb-modeswitch bison flex libdbus-1-dev libdbus-glib-1-dev uuid-dev ppp-dev libnss3-dev) 3) Installed from source libnl-3.2.23 and NetworkManager-0.9.8.8 (with patch supplied by Dan yesterday) 4) stopped appArmor along with its profiles System is generic as possible but still no luck. NM fails with GLib-GObject-CRITICAL and dumped core. :( I did strace for NetworkManager (http://pastelink.me/dl/34a69f), maybe this can bring some light? Uldis ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Thomas Haller" > To: "Uldis Jansons" > Cc: networkmanager-list@gnome.org > Sent: Thursday, December 19, 2013 10:00:02 AM > Subject: Re: NetwokManager fails to start with core dumped > > On Thu, 2013-12-19 at 09:27 +0200, Uldis Jansons wrote: > > > Unfortunately I cannot see it in > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/ > > Maybe I look in the whong place? > > Hi Uldis, > > it is the right place. See the branch 'nm-0.9.8' > http://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-0-9-8 > > > Thomas Thanks Thomas, That solved build problem. Now execution of make finishes without errors. Uldis ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
On Thu, 2013-12-19 at 09:27 +0200, Uldis Jansons wrote: > Unfortunately I cannot see it in > http://cgit.freedesktop.org/NetworkManager/NetworkManager/ > Maybe I look in the whong place? Hi Uldis, it is the right place. See the branch 'nm-0.9.8' http://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-0-9-8 Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Dan Williams" > To: "Uldis Jansons" > Cc: networkmanager-list@gnome.org > Sent: Wednesday, December 18, 2013 8:31:58 PM > Subject: Re: NetwokManager fails to start with core dumped > > On Wed, 2013-12-18 at 09:39 +0200, Uldis Jansons wrote: > > - Original Message - > > > From: "Dan Williams" > > > To: "Uldis Jansons" > > > > > > On Tue, 2013-12-17 at 13:34 +0200, Uldis Jansons wrote: > > > > Hi! > > > > > > > > Try to launch NetworkManager but it fails to start in ugly way. > > > > > > Which libnl version do you have? There were some versions in 3.x > > > that > > > did work, and some that didn't, due to bugs in libnl. v3.2.21 > > > should > > > work, as should 3.2.23. I believe 3.2.22 had a crashing bug, and > > > some > > > earlier versions like 3.2.7 had bugs too. > > > > > > Dan > > > > > > > Hi Dan, > > > > I am using libnl-3.2.23 which I believe is the latest. As you were > > mentioned 3.2.21 as bug-free version - tried this one as well. > > Unfortunately changing of NL version didn't solve the problem - > > compilation of NetworkManager fails: > > > > [...cut...] > > CC NetworkManager-nm-system.o > > nm-system.c: In function ‘nm_system_bond_enslave’: > > nm-system.c:1699:21: error: declaration of ‘link’ shadows a global > > declaration [-Werror=shadow] > > Fixed this in 0.9.8 git. > > Dan Thanks Dan, Unfortunately I cannot see it in http://cgit.freedesktop.org/NetworkManager/NetworkManager/ Maybe I look in the whong place? Uldis ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
On Wed, 2013-12-18 at 09:39 +0200, Uldis Jansons wrote: > - Original Message - > > From: "Dan Williams" > > To: "Uldis Jansons" > > > > On Tue, 2013-12-17 at 13:34 +0200, Uldis Jansons wrote: > > > Hi! > > > > > > Try to launch NetworkManager but it fails to start in ugly way. > > > > Which libnl version do you have? There were some versions in 3.x > > that > > did work, and some that didn't, due to bugs in libnl. v3.2.21 should > > work, as should 3.2.23. I believe 3.2.22 had a crashing bug, and > > some > > earlier versions like 3.2.7 had bugs too. > > > > Dan > > > > Hi Dan, > > I am using libnl-3.2.23 which I believe is the latest. As you were mentioned > 3.2.21 as bug-free version - tried this one as well. Unfortunately changing > of NL version didn't solve the problem - compilation of NetworkManager fails: > > [...cut...] > CC NetworkManager-nm-system.o > nm-system.c: In function ‘nm_system_bond_enslave’: > nm-system.c:1699:21: error: declaration of ‘link’ shadows a global > declaration [-Werror=shadow] Fixed this in 0.9.8 git. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Uldis Jansons" > To: "Dan Williams" > Cc: networkmanager-list@gnome.org > Sent: Wednesday, December 18, 2013 9:13:38 AM > Subject: Re: NetwokManager fails to start with core dumped > > > - Original Message - > > From: "Uldis Jansons" > > To: "Dan Williams" > > Cc: networkmanager-list@gnome.org > > Sent: Wednesday, December 18, 2013 9:39:59 AM > > Subject: Re: NetwokManager fails to start with core dumped > > > > > > - Original Message - > > > From: "Dan Williams" > > > To: "Uldis Jansons" > > > > > > Which libnl version do you have? There were some versions in 3.x > > > that > > > did work, and some that didn't, due to bugs in libnl. v3.2.21 > > > should > > > work, as should 3.2.23. I believe 3.2.22 had a crashing bug, and > > > some > > > earlier versions like 3.2.7 had bugs too. > > > > > > Dan > > > > > > > Hi Dan, > > > > I am using libnl-3.2.23 which I believe is the latest. As you were > > mentioned 3.2.21 as bug-free version - tried this one as well. > > Unfortunately changing of NL version didn't solve the problem - > > compilation of NetworkManager fails: > > > > [...cut...] > > CC NetworkManager-nm-system.o > > nm-system.c: In function ‘nm_system_bond_enslave’: > > nm-system.c:1699:21: error: declaration of ‘link’ shadows a global > > declaration [-Werror=shadow] > > cc1: all warnings being treated as errors > > make[4]: *** [NetworkManager-nm-system.o] Error 1 > > make[4]: Leaving directory > > `/home/vas/build/NetworkManager-0.9.8.8/src' > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory > > `/home/vas/build/NetworkManager-0.9.8.8/src' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory > > `/home/vas/build/NetworkManager-0.9.8.8/src' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory `/home/vas/build/NetworkManager-0.9.8.8' > > make: *** [all] Error 2 > > Update. > > Failing of make I solved by using --disable-more-warnings with ./configure. > So now everything is built without errors. Unfortunately starting of > NetworkManager still fails even with different netlink library > (libnl-3.2.21). > > [...cut...] > NetworkManager[1948]: Failed to connect to netlink: (4) unable to > allocate netlink link cache for monitoring link status: Operation not > supported > (NetworkManager:1948): GLib-GObject-CRITICAL **: g_type_instance_get_private: > assertion `instance != NULL && instance->g_class != NULL' failed > Segmentation fault (core dumped) As I said already on IRC, I suspect some sort of a system problem here. Did you check whether it could be caused by some selinux, apparmor or similar tool or by some specific kernel configuration? Is the system in any way specific, different from other systems? Could you reproduce with a fresh installation? Cheers, Pavel ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Uldis Jansons" > To: "Dan Williams" > Cc: networkmanager-list@gnome.org > Sent: Wednesday, December 18, 2013 9:39:59 AM > Subject: Re: NetwokManager fails to start with core dumped > > > - Original Message - > > From: "Dan Williams" > > To: "Uldis Jansons" > > > > Which libnl version do you have? There were some versions in 3.x > > that > > did work, and some that didn't, due to bugs in libnl. v3.2.21 > > should > > work, as should 3.2.23. I believe 3.2.22 had a crashing bug, and > > some > > earlier versions like 3.2.7 had bugs too. > > > > Dan > > > > Hi Dan, > > I am using libnl-3.2.23 which I believe is the latest. As you were > mentioned 3.2.21 as bug-free version - tried this one as well. > Unfortunately changing of NL version didn't solve the problem - > compilation of NetworkManager fails: > > [...cut...] > CC NetworkManager-nm-system.o > nm-system.c: In function ‘nm_system_bond_enslave’: > nm-system.c:1699:21: error: declaration of ‘link’ shadows a global > declaration [-Werror=shadow] > cc1: all warnings being treated as errors > make[4]: *** [NetworkManager-nm-system.o] Error 1 > make[4]: Leaving directory > `/home/vas/build/NetworkManager-0.9.8.8/src' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory > `/home/vas/build/NetworkManager-0.9.8.8/src' > make[2]: *** [all] Error 2 > make[2]: Leaving directory > `/home/vas/build/NetworkManager-0.9.8.8/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/vas/build/NetworkManager-0.9.8.8' > make: *** [all] Error 2 Update. Failing of make I solved by using --disable-more-warnings with ./configure. So now everything is built without errors. Unfortunately starting of NetworkManager still fails even with different netlink library (libnl-3.2.21). [...cut...] NetworkManager[1948]: Failed to connect to netlink: (4) unable to allocate netlink link cache for monitoring link status: Operation not supported (NetworkManager:1948): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed Segmentation fault (core dumped) Uldis ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
- Original Message - > From: "Dan Williams" > To: "Uldis Jansons" > > On Tue, 2013-12-17 at 13:34 +0200, Uldis Jansons wrote: > > Hi! > > > > Try to launch NetworkManager but it fails to start in ugly way. > > Which libnl version do you have? There were some versions in 3.x > that > did work, and some that didn't, due to bugs in libnl. v3.2.21 should > work, as should 3.2.23. I believe 3.2.22 had a crashing bug, and > some > earlier versions like 3.2.7 had bugs too. > > Dan > Hi Dan, I am using libnl-3.2.23 which I believe is the latest. As you were mentioned 3.2.21 as bug-free version - tried this one as well. Unfortunately changing of NL version didn't solve the problem - compilation of NetworkManager fails: [...cut...] CC NetworkManager-nm-system.o nm-system.c: In function ‘nm_system_bond_enslave’: nm-system.c:1699:21: error: declaration of ‘link’ shadows a global declaration [-Werror=shadow] cc1: all warnings being treated as errors make[4]: *** [NetworkManager-nm-system.o] Error 1 make[4]: Leaving directory `/home/vas/build/NetworkManager-0.9.8.8/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/vas/build/NetworkManager-0.9.8.8/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/vas/build/NetworkManager-0.9.8.8/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/vas/build/NetworkManager-0.9.8.8' make: *** [all] Error 2 Uldis ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetwokManager fails to start with core dumped
On Tue, 2013-12-17 at 13:34 +0200, Uldis Jansons wrote: > Hi! > > Try to launch NetworkManager but it fails to start in ugly way. Which libnl version do you have? There were some versions in 3.x that did work, and some that didn't, due to bugs in libnl. v3.2.21 should work, as should 3.2.23. I believe 3.2.22 had a crashing bug, and some earlier versions like 3.2.7 had bugs too. Dan > ~# NetworkManager --config=/etc/NetworkManager/NetworkManager.conf > --no-daemon > NetworkManager: /lib/libnl-genl-3.so.200: no version information available > (required by NetworkManager) > NetworkManager: /lib/libnl-3.so.200: no version information available > (required by NetworkManager) > NetworkManager: /lib/libnl-3.so.200: no version information available > (required by /usr/lib/libnl-route-3.so.200) > NetworkManager[2033]: NetworkManager (version 0.9.8.8) is starting... > NetworkManager[2033]: Read config file > /etc/NetworkManager/NetworkManager.conf > NetworkManager[2033]: WEXT support is enabled > NetworkManager[2033]: Failed to connect to netlink: (4) unable to > allocate netlink link cache for monitoring link status: Operation not > supported > NetworkManager[2033]: Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, > Inc. To report bugs please use the NetworkManager mailing list. > NetworkManager[2033]: monitoring kernel firmware directory > '/lib/firmware'. > NetworkManager[2033]: WiFi hardware radio set enabled > NetworkManager[2033]: WiFi enabled by radio killswitch; enabled by > state file > NetworkManager[2033]: WWAN enabled by radio killswitch; enabled by > state file > NetworkManager[2033]: WiMAX enabled by radio killswitch; enabled by > state file > NetworkManager[2033]: Networking is enabled by state file > NetworkManager[2033]: failed to allocate link cache: (-10) Operation > not supported > NetworkManager[2033]: Failed to connect to netlink: (4) unable to > allocate netlink link cache for monitoring link status: Operation not > supported > > (NetworkManager:2033): GLib-GObject-CRITICAL **: g_type_instance_get_private: > assertion `instance != NULL && instance->g_class != NULL' failed > Segmentation fault (core dumped) > > > In syslog along with this output there is one extra line (dumped core): > > Dec 17 12:43:32 lte kernel: [ 8225.410376] NetworkManager[2033]: segfault at > 18 ip 0046d106 sp 7fff7ebfa2a0 error 4 in > NetworkManager[40+101000] > > > From logfile output I assume the problem is somehow releated with Netlink. > Netlink lib is installed and as far as I found is linked correctly. > > ~# ldd /usr/sbin/NetworkManager > /usr/sbin/NetworkManager: /lib/libnl-genl-3.so.200: no version information > available (required by /usr/sbin/NetworkManager) > /usr/sbin/NetworkManager: /lib/libnl-3.so.200: no version information > available (required by /usr/sbin/NetworkManager) > /usr/sbin/NetworkManager: /lib/libnl-3.so.200: no version information > available (required by /usr/lib/libnl-route-3.so.200) > linux-vdso.so.1 => (0x7fffeb7ff000) > libmm-glib.so.0 => /usr/lib/libmm-glib.so.0 (0x7feea2662000) > libnm-util.so.2 => /usr/lib/libnm-util.so.2 (0x7feea23ff000) > libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 > (0x7feea21d8000) > libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 > (0x7feea1f94000) > libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 > (0x7feea1c45000) > libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 > (0x7feea1a4) > libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0 > (0x7feea1836000) > libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > (0x7feea15e7000) > libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 > (0x7feea12f1000) > libnl-route-3.so.200 => /usr/lib/libnl-route-3.so.200 > (0x7feea109e000) > libnl-genl-3.so.200 => /lib/libnl-genl-3.so.200 (0x7feea0e99000) > libnl-3.so.200 => /lib/libnl-3.so.200 (0x7feea0c8) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x7feea0a63000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7feea0767000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7feea03a6000) > libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 > (0x7feea01a1000) > libnss3.so => /usr/lib/x86_64-linux-gnu/libnss3.so > (0x7fee9fe99000) > libsmime3.so => /usr/lib/x86_64-linux-gnu/libsmime3.so > (0x7fee9fc71000) > libnspr4.so => /usr/lib/x86_64-linux-gnu/libnspr4.so > (0x7fee9fa32000) > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fee9f82a000) > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fee9f612000) > libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 > (0x7fee9f3f3000) > libresolv.s
NetwokManager fails to start with core dumped
Hi! Try to launch NetworkManager but it fails to start in ugly way. ~# NetworkManager --config=/etc/NetworkManager/NetworkManager.conf --no-daemon NetworkManager: /lib/libnl-genl-3.so.200: no version information available (required by NetworkManager) NetworkManager: /lib/libnl-3.so.200: no version information available (required by NetworkManager) NetworkManager: /lib/libnl-3.so.200: no version information available (required by /usr/lib/libnl-route-3.so.200) NetworkManager[2033]: NetworkManager (version 0.9.8.8) is starting... NetworkManager[2033]: Read config file /etc/NetworkManager/NetworkManager.conf NetworkManager[2033]: WEXT support is enabled NetworkManager[2033]: Failed to connect to netlink: (4) unable to allocate netlink link cache for monitoring link status: Operation not supported NetworkManager[2033]: Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[2033]: monitoring kernel firmware directory '/lib/firmware'. NetworkManager[2033]: WiFi hardware radio set enabled NetworkManager[2033]: WiFi enabled by radio killswitch; enabled by state file NetworkManager[2033]: WWAN enabled by radio killswitch; enabled by state file NetworkManager[2033]: WiMAX enabled by radio killswitch; enabled by state file NetworkManager[2033]: Networking is enabled by state file NetworkManager[2033]: failed to allocate link cache: (-10) Operation not supported NetworkManager[2033]: Failed to connect to netlink: (4) unable to allocate netlink link cache for monitoring link status: Operation not supported (NetworkManager:2033): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed Segmentation fault (core dumped) In syslog along with this output there is one extra line (dumped core): Dec 17 12:43:32 lte kernel: [ 8225.410376] NetworkManager[2033]: segfault at 18 ip 0046d106 sp 7fff7ebfa2a0 error 4 in NetworkManager[40+101000] >From logfile output I assume the problem is somehow releated with Netlink. >Netlink lib is installed and as far as I found is linked correctly. ~# ldd /usr/sbin/NetworkManager /usr/sbin/NetworkManager: /lib/libnl-genl-3.so.200: no version information available (required by /usr/sbin/NetworkManager) /usr/sbin/NetworkManager: /lib/libnl-3.so.200: no version information available (required by /usr/sbin/NetworkManager) /usr/sbin/NetworkManager: /lib/libnl-3.so.200: no version information available (required by /usr/lib/libnl-route-3.so.200) linux-vdso.so.1 => (0x7fffeb7ff000) libmm-glib.so.0 => /usr/lib/libmm-glib.so.0 (0x7feea2662000) libnm-util.so.2 => /usr/lib/libnm-util.so.2 (0x7feea23ff000) libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 (0x7feea21d8000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7feea1f94000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7feea1c45000) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7feea1a4) libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7feea1836000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7feea15e7000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7feea12f1000) libnl-route-3.so.200 => /usr/lib/libnl-route-3.so.200 (0x7feea109e000) libnl-genl-3.so.200 => /lib/libnl-genl-3.so.200 (0x7feea0e99000) libnl-3.so.200 => /lib/libnl-3.so.200 (0x7feea0c8) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7feea0a63000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7feea0767000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7feea03a6000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7feea01a1000) libnss3.so => /usr/lib/x86_64-linux-gnu/libnss3.so (0x7fee9fe99000) libsmime3.so => /usr/lib/x86_64-linux-gnu/libsmime3.so (0x7fee9fc71000) libnspr4.so => /usr/lib/x86_64-linux-gnu/libnspr4.so (0x7fee9fa32000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fee9f82a000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fee9f612000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7fee9f3f3000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7fee9f1d7000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fee9efd2000) libudev.so.0 => /lib/x86_64-linux-gnu/libudev.so.0 (0x7fee9edc5000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7fee9ebbd000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fee9e97f000) /lib64/ld-linux-x86-64.so.2 (0x7feea291c000) libnssutil3.so => /usr/lib/x86_64-linux-gnu/libnssutil3.so (
