ubuntu-location-serviced crashed with SIGSEGV in com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::Impl::Impl()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
High
|
Thomas Voß | ||
platform-api (Ubuntu) |
Confirmed
|
Critical
|
Unassigned |
Bug Description
had a crash, needed to reboot
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: ubuntu-
ProcVersionSign
Uname: Linux 4.2.0-15-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 7 19:16:26 2015
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/
ExecutableTimes
InstallationDate: Installed on 2015-01-05 (274 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64+mac (20140619)
ProcCmdline: /usr/bin/
ProcCwd: /
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: location-service
SystemImageInfo: Error: command ['system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
information type: | Private → Public |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Thomas Voß (thomas-voss) |
importance: | Undecided → High |
milestone: | none → backlog |
status: | New → Confirmed |
Changed in platform-api (Ubuntu): | |
importance: | Undecided → High |
importance: | High → Critical |
Caused by a race with the android container/the underlying gps chipset driver. We have been experiencing the issue on and off for the last months. The location-service or the GPS provider implementation can hardly do anything about the underlying issue, so I'm removing location-service from being affected. Instead, we should start tracking down the issue in the context of platform- api/libhybris.