gnome-control-center crashed with SIGSEGV in dun_cleanup()

[Elroy]

crash

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu8
Uname: Linux 3.6.0-030600rc1-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
CrashCounter: 1
Date: Sat Aug 11 11:44:57 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120803.1)
ProcCmdline: gnome-control-center bluetooth
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xa3c11f04: mov 0x0(%ebp),%eax
 PC (0xa3c11f04) ok
 source "0x0(%ebp)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
 ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
 ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 dun_cleanup (info=info@entry=0xb7f88a50, message=message@entry=0xb8033508 "Error: timed out detecting phone details.", uncheck=uncheck@entry=1) at bt-widget.c:315
 dun_error (info=info@entry=0xb7f88a50, func=func@entry=0xa3c17b48 "dun_timeout_cb", error=error@entry=0x0, fallback=0xa3c17568 "timed out detecting phone details.") at bt-widget.c:377
 dun_timeout_cb (user_data=user_data@entry=0xb7f88a50) at bt-widget.c:762
 g_timeout_dispatch (source=source@entry=0xb8018f98, callback=0xa3c121a0 <dun_timeout_cb>, user_data=0xb7f88a50) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:4018
 g_main_dispatch (context=0xb7c97670) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:2707

[Sebastien Bacher (seb128)]

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions