indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-bluetooth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I tried to switch Bluetooth on system settings, after few times from Fn+F5. All the sudden Bkuetooth seemed to be on, but then the program crashed.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-bluetooth 0.0.6+14.
ProcVersionSign
Uname: Linux 3.13.0-15-generic i686
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CurrentDesktop: Unity
Date: Tue Mar 4 22:41:20 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-03-18 (351 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=en_US:en
XDG_RUNTIME_
LANG=en_US.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_
g_closure_invoke () from /usr/lib/
Title: indicator-
UpgradeStatus: Upgraded to trusty on 2014-03-04 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
upstart.
** (process:1953): CRITICAL **: bluez.vala:104: GDBus.Error:
** (process:1953): WARNING **: desktop.vala:258: unable to launch 'obex:/
** (process:6070): CRITICAL **: bluez.vala:104: GDBus.Error:
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.