network-manager crashes after recent update

Bug #37338 reported by foxy123
This bug report is a duplicate of:  Bug #37084: Crashes due to freeing unused mutex. Edit Remove
14
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Medium
Unassigned

Bug Description

Network-manager crashes on boot after the recent update. If I try to launch it manually I've got the following error:
~$ sudo NetworkManager --no-daemon
Password:
Sorry, try again.
Password:
NetworkManager: <information> starting...
NetworkManager: <WARNING> main (): nm_data_new: Setting up dbus filter
NetworkManager: <information> Deactivating device eth0.
NetworkManager: <WARNING> nm_signal_handler (): Caught signal 11. Generating backtrace...
NetworkManager: ******************* START **********************************
NetworkManager: (no debugging symbols found)
NetworkManager: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: [Thread debugging using libthread_db enabled]
NetworkManager: [New Thread -1212016960 (LWP 4864)]
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: 0xffffe410 in __kernel_vsyscall ()
NetworkManager: ******************* END **********************************

Revision history for this message
Christian Assing (chassing) wrote :

I am getting the same.

my solution was to clear the /etc/network/interface file completly

cat /etc/network/interface
# The loopback network interface
auto lo
iface lo inet loopback

nothing more.

Revision history for this message
WillDyson (will-dyson) wrote :

I had to do the same. If the /etc/network/interfaces parser cannot be made robust, perhaps it should be dropped?

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.