bluetooth-applet crashed with SIGSEGV in g_variant_type_info_get_type_string()

[Khairul Nizam]

another problem:-
- software updater can't open
- software sources can't open
- the version of Ubuntu shown in "About This Computer" is different. I upgraded to 12.10 however once I click on "About This Computer" it still show Ubuntu 12.04 LTS

Description: Ubuntu quantal (development branch)
Release: 12.10

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-bluetooth 3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Sat Aug 11 01:21:35 2012
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: bluetooth-applet
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb70356e0: movzbl 0x4(%eax),%edx
 PC (0xb70356e0) ok
 source "0x4(%eax)" (0x000f9e70) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_type_info_get_type_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_get_type () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_is_of_type () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_lookup_value () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: bluetooth-applet crashed with SIGSEGV in g_variant_type_info_get_type_string()
UpgradeStatus: Upgraded to quantal on 2012-08-09 (1 days ago)
UserGroups:

[Apport retracing service (apport)]

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 #1023863, 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.