sudden, out-of-the-blue crash

[Robert B]

Binary package hint: network-manager

I wasn't even consciously running NetworkManager -- I didn't see any icons. I was updating my packages, however, when it got the SEGV.

I'm on Ubuntu 4.10.

network-manager:
  Installed: 0.7~~svn20081018t105859-0ubuntu1
  Candidate: 0.7~~svn20081018t105859-0ubuntu1
  Version table:
     0.7~~svn20081018t105859-0ubuntu1.8.10.1 0
        400 http://mirrors.kernel.org intrepid-proposed/main Packages
 *** 0.7~~svn20081018t105859-0ubuntu1 0
        500 http://mirrors.kernel.org intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

Package: network-manager 0.7~~svn20081018t105859-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 g_slist_foreach () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: NetworkManager crashed with SIGSEGV in g_object_unref()
Uname: Linux 2.6.27-9-generic i686
UserGroups:

WpaSupplicantLog:

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/libglib-2.0.so.0
dbus_g_proxy_dispose (object=0x85ff4b0) at dbus-gproxy.c:1470
g_object_unref () from /usr/lib/libgobject-2.0.so.0
g_slist_foreach () from /usr/lib/libglib-2.0.so.0
?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Robert B (robertbub)]

Unfortunately, this problem has not happened again. If nothing jumped out at you, you may as well close this bug.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!