Bug Description

[Triage Notes]

This regression is caused by a libnl proposed update tracked in bug 1511735. It has not been released as an update, only proposed as an update for early testing. If you volunteered to test proposed updates, then thank you. Your care and attention will stop this regression from hitting ordinary users, and we appreciate your contribution to Ubuntu.

If you are not aware that you volunteered to test proposed updates, then please be aware that your system is configured to do so. In this case, you probably should turn this off. I'd appreciate if someone could explain how to do this in the comments.

[Original Report]

Description: Ubuntu 14.04.3 LTS

Release: 14.04

After upgrading to 3.2.21-1ubuntu1 network-manager 0.9.8.8-0ubuntu7.2 segfaults:

[ 21.367977] init: network-manager main process (1000) killed by SEGV signal

[ 21.367989] init: network-manager main process ended, respawning

[ 21.424932] init: network-manager main process (1060) killed by SEGV signal

[ 21.424943] init: network-manager main process ended, respawning

[ 21.451519] init: network-manager main process (1066) killed by SEGV signal

[...]

xxx@yyy:/tmp/bla# gdb /usr/sbin/ NetworkManager CoreDump

[...]

Reading symbols from /usr/sbin/ NetworkManager. ..(no debugging symbols found)...done.

[New LWP 3550]

[New LWP 3551]

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib/x86_ 64-linux- gnu/libthread_ db.so.1" .

Core was generated by `NetworkManager'.

Program terminated with signal SIGSEGV, Segmentation fault.

#0 0x0000000000469fee in nm_netlink_ monitor_ attach ()