camera-app mic permission item blank

Looking at the trust.db, the mic request is in:
  ~/.local/share/PulseAudio/trust.db
  1|qtubuntu-camera|0|1440088476621790410|1

compared to the camera request in:
  ~/.local/share/CameraService/trust.db
  1|com.ubuntu.camera_camera|0|1440079963231981311|1

Whatever is inserting the request for mic access is using the wrong name.

Is this actually fixable? ie, does pulse know the camera (and not the plain audio subsystem) is the accessing party here?

I've subscribed tvoss who designed this arrangement, in case the bug is in the architecture, and not a boring string cockup.

<https://wiki.ubuntu.com/AccountPrivileges#permission-prompt>: "'Video recording' should be separate from 'Camera' so that an app does not need two permissions when recording video, one for the camera and one for the microphone. If an app has permission to record video, it should have access to the microphone whenever it is recording video."

Interestingly, the entry for the CameraService is correct and constitutes a valid App id. However, the entry for the microphone is not a valid app id but seems to come from a service that runs under an app-armor profile "qtubuntu-camera". I think we might need to patch the respective service, too, to enable trust integration.

@mpt: Sure, let's first iron out the actual underlying issues though.

@mpt, we may have to iterate on what we have to get to the desired aim of one prompt for two trust store requests.

@mpt, lp:1487152 also relevant to two-perms schema.

Ubuntu Touch is no longer supported.