Failed to report Network Manager bug after restart

[Andres Monroy-Hernandez]

Binary package hint: apport

I keep getting a crash icon in the GNOME toolbar. I click on it and it start trying to report the bug. It seems like the bug it's related to Network Manager even though it's running just fine. Then I get "The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes"

ProblemType: Bug
Architecture: i386
Date: Sun Sep 20 20:33:06 2009
DistroRelease: Ubuntu 9.10
Package: apport 1.9-0ubuntu6
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SourcePackage: apport
Uname: Linux 2.6.31-10-generic i686

[Martin Pitt (pitti)]

 status wontfix

 affects ubuntu/network-manager
 importance wishlist
 status triaged

Andres Monroy-Hernandez [2009-09-21 0:35 -0000]:
> I keep getting a crash icon in the GNOME toolbar. I click on it and it
> start trying to report the bug. It seems like the bug it's related to
> Network Manager even though it's running just fine. Then I get "The
> program crashed on an assertion failure, but the message could not be
> retrieved. Apport does not support reporting these crashes"

The original problem is in network-manager itself (the assertion
failure). We shouldn't report them as bugs if we cannot retrieve the
assert message, it would just create noise in the bug tracker (since
these reports are useless for developers).

However, network-manager should use the standard glib or libc assert
macros, or alternatively set __abort_msg in its own macros.

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[Bryan Quigley (bryanquigley)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

I'm going to close this bug report as their is nothing else we can do with this old report in a now unsupported version of Ubuntu.