[Touch-packages] [Bug 1540088] Re: NetworkManager crashes after upgrade, preventing nm-applet to show
*** This bug is a duplicate of bug 1539634 *** https://bugs.launchpad.net/bugs/1539634 Same issue. In my case it appeared to happen after an upgrade of libnl package. ab...@hotmail.com (ablmf) -> you need to type 'sudo ifconfig eth0 up', followed by 'sudo dhclient eth0' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1540088 Title: NetworkManager crashes after upgrade, preventing nm-applet to show Status in network-manager package in Ubuntu: Confirmed Bug description: 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[40+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[40+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[40+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[40+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[40+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[40+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[40+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[40+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[40+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[40+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 (2) 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Unfortunately, I have found that it did not work for me. I first tried a standard apt-get upgrade (in which I noticed a new network-manager package) and rebooted, to find no real change - network- manager still SEGVs. Then I tried downgrading libnl-3 (as described above) and rebooted. Again, no change - network-manager still SEGVs. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: Fix Committed 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. [Impact] * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200 libnl-route-3-200) and when libnl is updated to proposed 3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM validation packets. This affects the 0.98 release of NetworkManager and has already been fixed in newer releases. * Backporting fixes from upstream release is required to prevent NetworkManager from faulting which breaks networking on most Desktop releases. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing. [Test Case] * Reproduce crash test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In terminal, enable proposed 4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 5. sudo restart network-manager # note the nm-applet disappears as NM has now crashed, no network conn. 6. dmesg to confirm network-manager crash 7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 8. sudo start network-manager # nm-applet reappears, network connectivity restored * Successful upgrade test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In a terminal, sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 4. sudo restart network-manager # NM still runs, no crash, net up 5. enable trusty-proposed in /etc/apt/sources.list 6. sudo apt-get update 7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 8. sudo restart network-manager # NM still runs, no crash, net up. [Regression Potential] * NetworkManager is a highly visible package, so testing NetworkManager functionality is critical. The patch does address the crash specificly introduced by the updated libnl SRU. * We need to ensure that users have installed this NetworkManager update before installing libnl3 update (special phasing needed). [Original 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Unfortunately, I have found that it did not work for me. I first tried a standard apt-get upgrade (in which I noticed a new network-manager package) and rebooted, to find no real change - network- manager still SEGVs. Then I tried downgrading libnl-3 (as described above) and rebooted. Again, no change - network-manager still SEGVs. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: Fix Committed 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. [Impact] * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200 libnl-route-3-200) and when libnl is updated to proposed 3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM validation packets. This affects the 0.98 release of NetworkManager and has already been fixed in newer releases. * Backporting fixes from upstream release is required to prevent NetworkManager from faulting which breaks networking on most Desktop releases. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing. [Test Case] * Reproduce crash test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In terminal, enable proposed 4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 5. sudo restart network-manager # note the nm-applet disappears as NM has now crashed, no network conn. 6. dmesg to confirm network-manager crash 7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 8. sudo start network-manager # nm-applet reappears, network connectivity restored * Successful upgrade test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In a terminal, sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 4. sudo restart network-manager # NM still runs, no crash, net up 5. enable trusty-proposed in /etc/apt/sources.list 6. sudo apt-get update 7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 8. sudo restart network-manager # NM still runs, no crash, net up. [Regression Potential] * NetworkManager is a highly visible package, so testing NetworkManager functionality is critical. The patch does address the crash specificly introduced by the updated libnl SRU. * We need to ensure that users have installed this NetworkManager update before installing libnl3 update (special phasing needed). [Original 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
