← Back to team overview

ubuntu-phone team mailing list archive

uNav is killed by the system when it asks for geolocation (rc-proposed)

 

Hi!

Testers in rc-proposed are reporting this issue (this is not happen in the
current stable):

- Open uNav.
- Center position.
- uNav is killed (sometimes).

Usually when uNav has a dump, uNav stops the rutine and I can read the
issue in its log.
But with this kill, I can't read anything in the app log or in the system
log either:
http://paste.ubuntu.com/15409376/

In the PC (desktop 16.04 updated) I saw a weird behavior too. Previously
uNav gets the position because of the IP. Now I'm getting 2 types of dump
without any position (but never killed):

qml: [JS] (file:///home/costales/Desktop/unav/index.html:258) Starting
GPS...
[0322/100022:ERROR:oxide_access_token_store.cc(30)] Not implemented reached
in virtual void oxide::AccessTokenStore::LoadAccessTokens(const
LoadAccessTokensCallbackType&)

or this:

qml: [JS] (file:///home/costales/Desktop/unav/index.html:258) Starting
GPS...
*** Error in `/usr/lib/i386-linux-gnu/qt5/bin/qmlscene': corrupted
double-linked list: 0x09d1ba58 ***


I think this is happening when the GPS is not ready and uNav ask for it,
then the system kills uNav (?).

A few users tried the older version 0.50 in rc-proposed and it is happening
too.

I filled this bug:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1559428

Thanks in advance!

Follow ups