Michael, please file a new separate bug. You're almost certainly not
seeing the same crash. If the dialog for apport pops up again, please
let it create a new bug report. Alternatively, and if you still have the
crash file in /var/crash, you can start it like so:

ubuntu-bug /var/crash/_usr_sbin_NetworkManager...

Jason, I'll close this bug right away to give other users a chance to
report a new instance of this, because I'm pretty sure this was caused
by dbus/dbus-glib/glib breakage we had at that point during the cycle,
as per the attached WifiSyslog which shows, around the middle part of
the log, a boot that immediately saw NM and MM being respawned by
upstart forever. They spew out dbus errors, too :)

So; Invalid, following the assumption that this has been fixed with an
update of packages.

** Changed in: network-manager (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810335

Title:
  NetworkManager crashed with SIGABRT in __kernel_vsyscall()

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to