ubuntu-location-serviced crashed with SIGSEGV in com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::Impl::Impl()

Bug #1503844 reported by green-elephant999
14
This bug affects 2 people
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-location-service-bin 3.0.0-0ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-15.17-lowlatency 4.2.3
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/ubuntu-location-serviced
ExecutableTimestamp: 1438623816
InstallationDate: Installed on 2015-01-05 (274 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64+mac (20140619)
ProcCmdline: /usr/bin/ubuntu-location-serviced --bus system --provider gps::Provider --provider remote::Provider --remote::Provider::name=com.ubuntu.espoo.Service.Provider --remote::Provider::path=/com/ubuntu/espoo/Service/Provider
ProcCwd: /
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: location-service
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
green-elephant999 (gergarfe) wrote :
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 : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in location-service (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Thomas Voß (thomas-voss) wrote :

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.

Changed in location-service (Ubuntu):
status: New → Invalid
no longer affects: location-service (Ubuntu)
Changed in canonical-devices-system-image:
assignee: nobody → Thomas Voß (thomas-voss)
importance: Undecided → High
milestone: none → backlog
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in platform-api (Ubuntu):
status: New → Confirmed
Changed in platform-api (Ubuntu):
importance: Undecided → High
importance: High → Critical
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.