NetworkManager crashed with SIGSEGV in g_object_unref()

[inode77]

Binary package hint: network-manager

New bug because of this comment.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/274760/comments/10

$ lsb_release -r
Release: 9.10

# apt-cache policy network-manager
network-manager:
  Installed: 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
  Candidate: 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
  Version table:
 *** 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6 0
        500 http://ch.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
CrashCounter: 1
Date: Tue Sep 22 00:03:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IpRoute:
 147.87.225.0/24 dev eth0 proto kernel scope link src 147.87.225.221 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 147.87.225.1 dev eth0 proto static
Package: network-manager 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic-pae
SegvAnalysis:
 Segfault happened at: 0xb7bb72a1 <g_object_unref+33>: cmpl $0x50,(%eax)
 PC (0xb7bb72a1) ok
 source "$0x50" ok
 destination "(%eax)" (0x000000a1) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 g_value_unset () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_object_unref()
Uname: Linux 2.6.31-10-generic-pae i686
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #432452, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.