indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke()

[Bernie Innocenti]

I switched the bluetooth enable switch to the ON position and the applet crashed a second later.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 11 01:07:46 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
SegvAnalysis:
 Segfault happened at: 0x40d880: mov (%rbx),%rdi
 PC (0x0040d880) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-bluetooth
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to trusty on 2013-07-03 (222 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tape video

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