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

Bug #1301028 reported by Francisco Javier Teruelo de Luis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-bluetooth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Bluetooth out when manual start.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic i686
ApportVersion: 2.14-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Tue Apr 1 23:28:22 2014
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
InstallationDate: Installed on 2014-03-10 (22 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140223)
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=ca
 XDG_RUNTIME_DIR=<set>
 LANG=ca_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8054fd8: mov (%ebx),%eax
 PC (0x08054fd8) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-bluetooth
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
upstart.indicator-bluetooth.log: ** (process:12706): CRITICAL **: bluez.vala:104: GDBus.Error:org.bluez.Error.NoSuchAdapter: No such adapter

Revision history for this message
Francisco Javier Teruelo de Luis (teruelolf) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1278680, 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.

information type: Private → Public
tags: removed: need-i386-retrace
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.