NetworkManager crashes after upgrade, preventing nm-applet to show

[Adam Ryczkowski]

After the last upgrade of Ubuntu 14.04.3 LTS , NetworkManager keeps crashing.

after `sudo service network-manager start` I get the following output in dmesg:

[2016-01-31 14:28:47] traps: NetworkManager[11040] general protection ip:469fee sp:7ffc6879aa00 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11040) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11049] general protection ip:469fee sp:7ffecca7d9d0 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11049) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11062] general protection ip:469fee sp:7ffc218a9f50 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11062) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11076] general protection ip:469fee sp:7fff7f128270 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11076) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11088] general protection ip:469fee sp:7fff66528f90 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11088) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11092] general protection ip:469fee sp:7fffab819070 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11092) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11096] general protection ip:469fee sp:7ffe7aa91c20 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11096) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11100] general protection ip:469fee sp:7ffedfe81460 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11100) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11104] general protection ip:469fee sp:7ffdc475f140 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11104) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] traps: NetworkManager[11108] general protection ip:469fee sp:7ffdeb437010 error:0 in NetworkManager[400000+10d000]
[2016-01-31 14:28:47] init: network-manager main process (11108) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager main process ended, respawning
[2016-01-31 14:28:47] init: network-manager main process (11112) killed by SEGV signal
[2016-01-31 14:28:47] init: network-manager respawning too fast, stopped

This problem prevents me to see nm-applet, and makes me unable to connect to WiFi network.

[Launchpad Janitor (janitor)]

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

[Marcelo Ruiz (marcelo-javier-ruiz-yahoo)]

I am having the same problem. What helped me have back Internet access was to bring up the interfaces and running dhclient from the command line:

sudo ifconfig eth0 up
sudo dhclient

Replace eth0 with the interface you want to use.
This will not bring the applet back to life, but at list you will have Internet.

[Average User (lurider)]

yes, manually like in 2004... i'm having a bad time explaining this to my little daughter

[jhansonxi (jhansonxi)]

Probably a duplicate of bug #1540014 which has a link to a workaround.

[Average User (lurider)]

great, i confirm that workaround worked for me, thanks

[[e-mail] (ablmf)]

Also have this problem.

I tried sudo ifconfig eth0
And then sudo dhclinet.

Bit the second command does not terminate.
And I still don't have internet.

[paolinuz (paolovg)]

I have the same issue after to have updated to:

Kubuntu 14.04.3 LTS

[Martin Beynon (mebeyn)]

Same issue. In my case it appeared to happen after an upgrade of libnl package.

<email address hidden> (ablmf) -> you need to type 'sudo ifconfig eth0 up', followed by 'sudo dhclient eth0'

[Miguel (aglanor)]

This has happened to me after updating yesterday.

Recovered network access as per #2 instructions.

It's weird that this is happening to my system after several months.

[thomas a. (sarg314)]

This happened to me last night after I did update. The "ifconfig eth0 up" and "dhclient eth0"
(or dhclient without the eth0 argument), do not work for me. Booting previous kernel versions does not work for me. I am running 4.2.0-36-generic 64-bit.

[Oleg (oleg-poligon)]

Hi, there.

I've encountered same problem.
After getting network to work without nm I've reinstalled nm with command:

sudo apt-get install --reinstall network-manager

then, after reboot, nm works in normal mode.

[gasmichou (gaszwarc)]

I had the exact same issue after updating last week. I only shut my computer down for the weekends... When I came back from weekend this morning, BAM ! That issue....

I had to boot with Windows to search a solution.
I wrote yours down and will try, I will tell you which one works for me.

[gasmichou (gaszwarc)]

I am writing to you from my Ubuntu session

Thank you, this saved my work life ^^ :

$ sudo ifconfig eth0
$ sudo dhclinet eth0