desktop-packages team mailing list archive

[Szabolcs Seláf <1539513@xxxxxxxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1539513

Title:
  networkmanager segfaults with 3.2.21-1ubuntu1

Status in libnl3 package in Ubuntu:
  Confirmed

Bug description:
  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 ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1539513/+subscriptions