[camera-app] mir/trust-store fails to show up the trust-store dialog when enabling location support

Bug #1381105 reported by Ricardo Salveti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mir (Ubuntu RTM)
New
High
Unassigned
trust-store (Ubuntu)
New
High
Unassigned

Bug Description

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 104
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2014-10-14 14:30:18
version version: 104
version ubuntu: 20141014
version device: 20141013-0e11263
version custom: 1413152967

Flashed with --bootstrap.

Right after the first boot, or even after a reboot, camera-app freezes for a few seconds (~10-15) when enabling location support (probably because the trust-store dialog never shows up).

phablet@ubuntu-phablet:~$ ps -ef | grep trust
phablet 4139 1755 0 14:45 ? 00:00:00 /usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=system --local-agent MirAgent --trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service UbuntuLocationService --with-text-domain ubuntu-location-service --store-bus session
phablet 4283 4139 3 14:45 ? 00:00:00 /usr/lib/arm-linux-gnueabihf/trust-prompt --mir_server_socket fd://15 --title camera --description camera wants to access your current location.

tags: added: rtm14
Bill Filler (bfiller)
Changed in mir (Ubuntu RTM):
importance: Undecided → Critical
Changed in trust-store (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

phablet@ubuntu-phablet:~$ cat ./.cache/upstart/ubuntu-location-service-trust-stored.log
reattempt connection to mir...
reattempt connection to mir...
reattempt connection to mir...
reattempt connection to mir...
Error during initialization and startup: Dynamic exception type: N4core5trust3mir20InvalidMirConnectionE
std::exception::what: Cannot create instance for invalid connection to Mir.

reattempt connection to mir...
reattempt connection to mir...
reattempt connection to mir...
reattempt connection to mir...
Error during initialization and startup: Dynamic exception type: N4core5trust3mir20InvalidMirConnectionE
std::exception::what: Cannot create instance for invalid connection to Mir.

reattempt connection to mir...
reattempt connection to mir...
/usr/lib/arm-linux-gnueabihf/trust-prompt: unrecognized option '--mir_server_socket'
/usr/lib/arm-linux-gnueabihf/trust-prompt: unrecognized option '--title'
/usr/lib/arm-linux-gnueabihf/trust-prompt: unrecognized option '--description'
UbuntuWindow - regular geometry

Revision history for this message
Alberto Aguirre (albaguirre) wrote :

Yes I can replicate this - you have to start the camera app right after rebooting.

Attempting a workaround here: lp:~albaguirre/qtubuntu-sensors/fix-1381105 prevents the freeze but the trust-store prompt is never shown.

It looks like com::ubuntu::location::service::Stub::create_session_for_criteria times out:

http://pastebin.ubuntu.com/8562388/

Revision history for this message
Alberto Aguirre (albaguirre) wrote :

com::ubuntu::location::service::Stub::create_session_for_criteria in camera-app context may be timing out because
trusted-stored-skeleon seems to be stuck in core::trust::mir::Agent::authenticate_request_with_parameters

http://pastebin.ubuntu.com/8562429/

tags: added: touch-2014-10-23
Revision history for this message
Thomas Voß (thomas-voss) wrote :

Yup, it times out because the trust-prompt started by:

  core::trust::mir::Agent::authenticate_request_with_parameters

Almost never succeeds to connect to Mir/Unity8 via its trusted socket. It seems like U8 is entirely blocked by something, probably on the graphics pipeline as a whole (but other parts might obviously cause the issue, too).

Olli Ries (ories)
Changed in trust-store (Ubuntu):
importance: Critical → High
Changed in mir (Ubuntu RTM):
importance: Critical → High
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.