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

Bug #1497785 reported by Alan Pope 🍺🐧🐱 🦄
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-bluetooth (Ubuntu)
New
Medium
Unassigned

Bug Description

Installing daily updates via apt and suddenly I got this crash popup. Wasn't actually using bluetooth at all.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: indicator-bluetooth 0.0.6+15.10.20150915-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
Uname: Linux 4.2.0-10-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 20 22:32:15 2015
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
InstallationDate: Installed on 2014-06-16 (461 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x408515: mov (%rax,%r12,4),%rdi
 PC (0x00408515) ok
 source "(%rax,%r12,4)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-bluetooth
StacktraceTop:
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-bluetooth-service crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to wily on 2015-05-09 (134 days ago)
UserGroups: adm autopilot cdrom dialout dip kismet libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 bluez_update_device (self=0x14cc890, object_path=<optimized out>) at bluez.c:1414
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fff7bbe7b90, fn=<optimized out>, rvalue=0x7fff7bbe7af0, avalue=avalue@entry=0x7fff7bbe7a90) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic (closure=0x14e7220, return_gvalue=0x0, n_param_values=<optimized out>, param_values=0x7fff7bbe7dc0, invocation_hint=<optimized out>, marshal_data=0x0) at /build/glib2.0-hcw3A1/glib2.0-2.45.7/./gobject/gclosure.c:1481
 g_closure_invoke (closure=0x14e7220, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0x7fff7bbe7dc0, invocation_hint=invocation_hint@entry=0x7fff7bbe7d40) at /build/glib2.0-hcw3A1/glib2.0-2.45.7/./gobject/gclosure.c:801

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-bluetooth (Ubuntu):
importance: Undecided → Medium
summary: - indicator-bluetooth-service crashed with SIGSEGV in ffi_call_unix64()
+ indicator-bluetooth-service crashed with SIGSEGV in
+ bluez_update_device()
tags: removed: need-amd64-retrace
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.