bluetoothd crashed with SIGSEGV in g_main_context_dispatch()

[Matthias Redlich]

bluetoothd seems to crash in Ubuntu 12.04 beta. The problem occurs immediately after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Thu Mar 29 08:42:40 2012
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 4242PT2
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=b0a2add5-ac89-412c-ae05-b0550b8acc9d ro quiet splash vt.handoff=7
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bluez
Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2012-03-16 (17 days ago)
UserGroups:

dmi.bios.date: 10/21/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET53WW (1.33 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4242PT2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8AET53WW(1.33):bd10/21/2011:svnLENOVO:pn4242PT2:pvrThinkPadT520:rvnLENOVO:rn4242PT2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4242PT2
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO
hciconfig:

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