touch-packages team mailing list archive

[Josh Arenson <1483752@xxxxxxxxxxxxxxxxxx>]

@John theoreticaly the camera app could handle this, but I think we have
a work-around, as well as a proper fix in the works.

This branch is a work-around. 
https://code.launchpad.net/~josharenson/unity8/fix_tps_active
I'm not quite sure what the far reaching implications of this fix are yet. However, I have performed some manual/automated testing, and I certainly don't see anything obviously wrong. I'm going to kick off a ci build for it in a bit as well (for even more automated testing)

This branch contains the proper fix.
https://code.launchpad.net/~dandrader/qtmir/mirSurface/+merge/264923
It removes the same code that the first branch does, but it depends on 2 other branches (in two different projects), so getting it landed will take some effort. 

I imagine that the first branch should work, in a pinch, but I'd
appreciate confirmation from dandrader.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1483752

Title:
  Trusted prompts make application inactive: Qt.application.active ==
  false

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When a trusted prompt shows up the application becomes "inactive",
  concretely QML applications receive a signal that
  Qt.application.active has changed to 'false'.

  This is will be an issue for example in the case of the camera-app
  trying to start recording a video, a pulseaudio trusted prompt will
  show up to ask for permission to record from the microphone but the
  camera-app believing that it's become inactive will immediately stop
  the recording.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483752/+subscriptions