System reboot when granting access to location on arale

Bug #1512128 reported by Pat McGowan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
Critical
Thomas Voß
trust-store (Ubuntu)
Confirmed
Critical
Thomas Voß
webbrowser-app (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

arlae rc-proposed
(not sure this is really browser issue but its what i was using)

Open maps.google.com
Webbroser prompts to allow access for the page to my location, allow
Trust store prompt to allow access for webbrowser (I thought I had already granted it int he past), allow
The phone hangs for a few seconds then reboots. The Meizu logo was shown and it vibrated so not just a unity restart

Tags: lt-blocker
Revision history for this message
Olivier Tilloy (osomon) wrote :

I cannot replicate the issue here. My arale is running the latest rc-proposed, I wiped the location trust store DB and restarted the service. I get the two prompts upon browsing to maps.google.com, but the phone didn’t reboot.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Not surprised, I will watch for it but expect it will be difficult to reproduce, there are no traces on the system

Changed in webbrowser-app (Ubuntu):
status: New → Incomplete
Changed in trust-store (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for trust-store (Ubuntu) because there has been no activity for 60 days.]

Changed in trust-store (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for webbrowser-app (Ubuntu) because there has been no activity for 60 days.]

Changed in webbrowser-app (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Paweł Stołowski (stolowski) wrote :

This seems to be affecting the changes now in silo 65 (unity8-dash runs confined and requests location access shortly after boot), and it has been reproduced without much problem on two arale systems.

Revision history for this message
James Henstridge (jamesh) wrote :

Pawel asked me to attach the logs from my tests of silo 65 on Arale.

I brought up the "Near by" scope, which claimed not to have location access. When I tried reloading it, I got the trust store prompt. Clicking allow resulted in the device restarting.

Revision history for this message
James Henstridge (jamesh) wrote :

And here's a logcat taken while triggering the trust prompt reboot

Revision history for this message
James Henstridge (jamesh) wrote :

And a tail of /var/log/syslog from another repeat of the reboot.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

now that trust prompts are enabled for the dash, this issue is critical because users will always see the trust prompt almost immediately on first boot.

Changed in trust-store (Ubuntu):
status: Expired → Confirmed
Changed in canonical-devices-system-image:
milestone: none → 12
tags: added: lt-blocker
Changed in canonical-devices-system-image:
importance: Undecided → Critical
status: New → Confirmed
Changed in trust-store (Ubuntu):
assignee: nobody → Thomas Voß (thomas-voss)
importance: Undecided → Critical
Changed in canonical-devices-system-image:
assignee: nobody → Thomas Voß (thomas-voss)
summary: - System reboot when granting access to location
+ System reboot when granting access to location on arale
Revision history for this message
Víctor R. Ruiz (vrruiz) wrote :

I haven't been able to reproduce in krillin nor turbo, but in arale it is very easy removing the
files /home/phablet/.local/share/UbuntuLocationService/trust.db, /home/phablet/.config/.scopesLocationPrompt, rebooting and exercising the scopes.

Revision history for this message
James Henstridge (jamesh) wrote :

This is the last line of the logcat output prior to the reboot:

    E/libEGL ( 4160): call to OpenGL ES API with no current context (logged once per thread)

So presumably something in that process triggering some drawing from the wrong thread?

Revision history for this message
James Henstridge (jamesh) wrote :

Could this be a dupe of bug 1551811?

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.