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

[James System]

After activating bluetooth.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
Uname: Linux 3.13.0-1-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jan 25 15:02:43 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
InstallationDate: Installed on 2013-12-10 (45 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20131210)
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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 org_bluez_adapter_set_property (self=0x0, name=0x42072d "Discoverable", value=0x2338e90, _callback_=0x0, _user_data_=0x0) at org-bluez.c:2057
 bluez_real_try_set_discoverable (base=<optimized out>, b=1) at bluez.c:2030
 __lambda17_ (_data4_=<optimized out>, _data4_=<optimized out>) at desktop.c:1240
 ___lambda17__g_object_notify (_sender=<optimized out>, pspec=<optimized out>, self=<optimized out>) at desktop.c:1246
 g_closure_invoke (closure=0x2337c10, return_value=0x0, n_param_values=2, param_values=0x7fff0219ff80, invocation_hint=0x7fff0219ff20) at /build/buildd/glib2.0-2.39.3/./gobject/gclosure.c:777

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

e.u.c report on https://errors.ubuntu.com/problem/9dbea1c66761e5143deabb815d8e4153c3578fb0

[Robert Ancell (robert-ancell)]

This is a bug in src/bluez.vala try_set_discoverable().

default_adapter can be null because it's not set when the Bluez object is created or it might have disappeared. I'm not sure what the code is supposed to do in this case, just ignore the try_set_discoverable() call?

I think try_set_enabled() will also have the same problem.

[Vassili Leonov (vleolml)]

I also got this bug manifest itself when my BT controller stopped working for some reason (another bug?)

lsusb -s 024 -v

Bus 001 Device 024: ID 13d3:3362 IMC Networks
Couldn't open device, some information will be missing

Asus notebook model N76V, internal USB adapter

[Sebastien Bacher (seb128)]

seems like reports stopped in newer series, unsure why since the code didn't change...

[Timo Jyrinki (timo-jyrinki)]

The problem always seemed to me to be lower level problem than indicator-bluetooth. That is, when it happened there was BT problems in general.