indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-bluetooth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
bluetooth ne start pas, l'indicateur crash probablement par la fermeture du drivers bluetooth
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: indicator-bluetooth 0.0.6+14.
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 21 13:55:27 2015
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2015-03-14 (7 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/bash
LANG=fr_CH.UTF-8
LANGUAGE=fr_CH:fr
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x40e760: mov (%rbx),%rdi
PC (0x0040e760) 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/
?? () from /usr/lib/
Title: indicator-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
upstart.
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 #1379752, 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.