bluetooth-wizard crashed with SIGSEGV in g_markup_parse_context_parse()

[Nick Russell]

In 12.10, double clicking on bluetooth device immediately after it has been discovered but before the name has resolved causes this crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-bluetooth 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 12 20:25:43 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bluetooth-wizard
InstallationDate: Installed on 2012-05-20 (236 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: bluetooth-wizard
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fef7306305f: movzbl (%rsi),%edx
 PC (0x7fef7306305f) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_markup_parse_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 get_pincode_for_device ()
Title: bluetooth-wizard crashed with SIGSEGV in g_markup_parse_context_parse()
UpgradeStatus: Upgraded to quantal on 2012-09-08 (126 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1053881, 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.