networkmanager segfaults with 3.2.21-1ubuntu1

Bug #1539513 reported by Th W on 2016-01-29
344
This bug affects 71 people
Affects Status Importance Assigned to Milestone
libnl3 (Ubuntu)
Undecided
Unassigned

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 ()

Th W (u-ubuntuone-1) wrote :

The crashdump

minimalprocedure (zairik) wrote :

Same problem.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libnl3 (Ubuntu):
status: New → Confirmed
minimalprocedure (zairik) wrote :

Reverting to packages:
libnl-3-200_3.2.21-1_amd64.deb
libnl-genl-3-200_3.2.21-1_amd64.deb
libnl-route-3-200_3.2.21-1_amd64.deb
Solve problem for me.

alex (a-trinkl) wrote :

Happened to me today (2016-01-29) after updates, reverting to the packages listed by minimalprocedure works also for me.

Jimmie H. III (jimmiecrackcorn) wrote :

Same problem. Used systemback to restore packages cause I had clue how to
do this offline without internet connection. I hope people don't find themselves in a position
worse than I did.

alex (a-trinkl) wrote :

I downloaded the 3 packages on another machine, transferred by usb-stick and installed with sudo dpkg -i *.deb

Th W (u-ubuntuone-1) wrote :

apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1
does the same by forcing the version which is not in trusty-proposed.

I would appreciate a fix (don't care if in networkmanager or libnl3) more than this simple workaround.

murzzz (murzzz) wrote :

Did the same as in comment #8, easiest solution.

Corneille (cvdp) wrote :

Comment #4/#7 worked for me.

Anthony A. (y-ubuntf-r) wrote :

Same bug for me on my two Ubuntu

Comment #4/#7 worked for me.

Nikolay (koliasvskj) wrote :

Experienced this bug 2016-01-29 after libnl upgrade to 3.2.21-1ubuntu1.
Trying #4 results in apt-get complaining about dependencies of wireless-crda (crda) package when apt-get install libnl-3-200=3.2.21-1

murzzz (murzzz) wrote :

Николай (koliasvskj), try all packages a once in one command line like it is suggested in comment #8: apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1

r2rien (r2rien) wrote :

Experienced same bug
Downgrading to 3.2.21-1 also solved it for me

Szabolcs Seláf (selu) wrote :

Same here, after downgrade I used sudo apt-mark hold libnl-3-200 libnl-genl-3-200 libnl-route-3-200 to prevent accidental upgrade, of course, once it's fixed sudo apt-mark auto libnl-3-200 libnl-genl-3-200 libnl-route-3-200 enables upgrade again.

BOGOTblPb (bogotblpb) wrote :

Comment #4/#7 worked for me.

Same issue here. Proposed downgrade (#4) solved the problem.

CrazySky (makarovdenis11) wrote :

I think this help to prevent upgrade:

sudo apt-mark hold libnl-3-200 libnl-genl-3-200 libnl-route-3-200

until the bug was fixed.

Ryan Harper (raharper) wrote :

This bug is related to an attempted SRU for libnl here:

https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735

The updated package exposes a bug in NetworkManager, which we're testing a fix:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634

Dmitriy Kodanev (dkodanev) wrote :

Same issue. Just did as #4/#7 and it helped.

Daniel Wind Sam (danielwsam) wrote :

Same issue, which quite drive me mad without the network. Just install the packages list in #8 via an usb stick and the net works again.

Daniel Eckl (daniel-eckl) wrote :

For having temporary wired network to make the downgrade suggested in #8, you could do:

ifconfig eth0 up && dhcpcd eth0 &

Wireless of course is more tricky.

Pavel Rojtberg (rojtberg) wrote :

I hope you can resolve/ revert this ASAP as it brings network down and finding information on how to fix it becomes very complicated.

Anyway another solution to revert to the working packages is:

if you have an Ubuntu USB stick somewhere
1. Boot "try out Ubuntu"
2. mkdir installation
3. sudo mount /dev/sdXX installation # where sdXX is your ubuntu root partition
4. sudo chroot installation
5. apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1

this saves you manually downloading and copying the packages

Eduards Bezverhijs (mjasnik) wrote :

Guys, this definately needs a fix, imagine single computer at home + ordinary user (not advanced users like us) = no way of fixing this at all.

Marsh (marsh) wrote :

I experienced the same problem on my 14.04 desktop after a reboot this morning. After the shock I initiated recovery
using ancient spells and incantations.

#> ifconfig 192.168.0.11 eth0 up
#> route add default gw 192.168.0.2 eth0
#> ifconfig 192.168.0.1 eth2 up

After that I downgraded the nl lib's per Th W post #8

Brian Byrne (brianlinuxing) wrote :

Confirmed my end too. Plugging in cable, fixing interfaces & reverting as per #8 works well.

mirak011 (mirak) wrote :

The same problem with Ubuntu 14.04.3,
I restored network with:

:# ip link set dev eth0 up
:# ip addr add 192.168.x.z/24 dev eth0
:# ip route add default via 192.168.x.y dev eth0
:# echo nameserver 192.168.x.y >> /etc/resolve.conf

and then followed #8. Tricky issue indeed!

What a nasty issue - in case other people run into it as well (like said in the forums:
http://ubuntuforums.org/showthread.php?t=2311705).

A direct download link for 14.04.0.3 is:
http://packages.ubuntu.com/trusty/amd64/libnl-route-3-200/download
http://packages.ubuntu.com/trusty/amd64/libnl-genl-3-200/download
http://packages.ubuntu.com/trusty/amd64/libnl-3-200/download
so you can choose a mirror near you.

This time it has not been a kernel issue, luckily.

This bug relates to #1539634 - make sure that you only install newer libnl versions with a patched NetworkManager as well.

jordan (jordan-b) wrote :

I just run an upgrade and hit the same problem. Lots of messages in syslog like:

Jan 30 21:04:14 sony ModemManager[767]: <info> ModemManager (version 1.0.0) sta
rting...
Jan 30 21:04:16 sony NetworkManager[924]: <info> NetworkManager (version 0.9.8.8
) is starting...
Jan 30 21:04:16 sony NetworkManager[924]: <info> Read config file /etc/NetworkMa
nager/NetworkManager.conf
Jan 30 21:04:16 sony NetworkManager[924]: <info> WEXT support is enabled
Jan 30 21:04:16 sony kernel: [ 42.654682] init: network-manager main process (
924) killed by SEGV signal
Jan 30 21:04:16 sony kernel: [ 42.654699] init: network-manager main process e
nded, respawning

I restored network using the method suggested by post #7 and using the links from #28.

Tobiz (pjrobinson) wrote :

Reverting to packages:
libnl-3-200_3.2.21-1_amd64.deb
libnl-genl-3-200_3.2.21-1_amd64.deb
libnl-route-3-200_3.2.21-1_amd64.deb
Solve problem for me.

Vicki Fletcher (vfletcher) wrote :

I needed to use a different command for dhcp. nasty bug!

ifconfig eth0 up && dhclient eth0

apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1

Luca Cere' (ermago) wrote :

Great! Solution is working! Thanks

Jacques (jacques-lebourlot) wrote :

Did #4/#7 and it worked for me
Also used #15 for security
This bug is critical (agreed with #24). Thank you to all for the fix.

VB (jfscreep) wrote :

Did the same as #32 and it worked.
Critical bug !

klemens_u (klemens) wrote :

Oh my god! This put me into a lot of troubles this morning! How will a non-tech person deal with this issue???

Workaround for me:

- Plugin in ethernet cable ("wired")
- Open Terminal
- sudo ifconfig eth0 up && dhclient eth0
- sudo apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1
reboot

Robie Basak (racb) on 2016-02-01
description: updated
GOLDERWEB (golderweb) wrote :

As mentioned in updated description this should only affect users who have activated trusty-proposed.

Non-techs normaly won't have it active. Otherwise it can be simply deactivated by unchecking the related box on "Software & Updates" settings. See https://wiki.ubuntu.com/Testing/EnableProposed?action=AttachFile&do=get&target=Software_Sources.png. There remove the hook before Pre-released updates (trusty-proposed).

This should only be active if you know what you are doing and never on productive systems. See documentation on https://wiki.ubuntu.com/Testing/EnableProposed.

delmic (delmic) wrote :

Same bug for me on my Ubuntu Thinkpad

Comment #4/#7 worked for me.

LucaChiampo (luca-chiampo) wrote :

Also I had the problem.

Got a working wired network using the suggestion in comment #27
 and than updated NetworkManarger to proposed version 0.9.8.8-0ubuntu7.3 via synaptic
no downgrade of libnl.

Solved for me

castlehard (castlehard) wrote :

My network-manager was still the "old" 0.9.8.8-0ubuntu7.2 after installing yesterdays patchset. So it seems for me like the update of the network-manager did not make it into the "yesterday's patchset", and now we are a bit offline.

So: update the patchset-list to make both changes happen the same time. I think this would solve all the problems with this bug finally.

First I did downgrade the libnl packages to get the network up and running quick and dirty. (worked).

After that I manually updated network-manager to the 7.3 Version:
# sudo apt-get install network-manager
and started update-manager (did an update to these libnl things) and rebooted as wanted by the update-manager.

Everything works fine now.

castlehard (castlehard) wrote :

https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735 (should not happen to anyone from now on;) Thanks)

Tonny (tonnydourado) wrote :

I do not have trusty-proposed enabled and my libnl-* packages are already in the 3.2.21-1 version, I rebooted several times, and yet the network-service won't start, I just keep getting this message on syslog: init: network-manager main process killed by SEGV signal.

Tom Dalton (tom-dalton) wrote :

My Ubuntu 14.04 laptop downloaded these 3 3.2.21-1ubuntu1 packages on Friday 13th May, and after a restart my network manager was unable to start (segfaulting presumably for the same reasons as original).

Solution in #4 (downgrade to the -1 packages) worked for me.

I do not have proposed updates enabled so it appears that the 1ubuntu1 packages are now the official packages, but are broken for me.

Happy to provide any more info requested.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers