desktop-packages team mailing list archive

[HugoHirsch <1539634@xxxxxxxxxxxxxxxxxx>]

Is it possible to somehow block libnl-updates until the network-manager
fix is available as well?

Otherwise people are going to run into networkless systems as reported in #1539513
Since 14.04 is a LTS this is rather risky indeed.

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged

Bug description:
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+subscriptions