after upgrading updates and having done a full system shutdown; DUN connectivity using bluetooth stopped working. I removed the profile and recreated. blue tooths settings immediately closed down and this is when the error occured
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Apr 14 10:41:59 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-control-center bluetooth
SegvAnalysis:
Segfault happened at: 0xbfd8f96: mov 0x1c(%eax),%edx
PC (0x0bfd8f96) ok
source "0x1c(%eax)" (0x0000001c) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
?? () from /usr/lib/libnm-glib.so.4
?? () from /usr/lib/libnm-glib.so.4
g_cclosure_marshal_VOID__VOIDv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_cclosure_marshal_VOID__VOIDv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
activity-log-manager-control-center 0.9.4-0ubuntu3
deja-dup 22.0-0ubuntu2
gnome-bluetooth 3.2.2-0ubuntu5
indicator-datetime 0.3.94-0ubuntu1
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #976283, 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.