On 12/01/2016 14:39, Michał Sawicz wrote:
> Review: Needs Fixing
>
> QA found a problem with this and I can confirm on devel-proposed/mako.
>
> Trying to follow steps from Victor [1] I got into a state where unity8 rejects the camera app:
>
> qtmir.applications: ApplicationManager::onProcessStarting(appId="com.ubuntu.camera_camera") - User wants to start a new instance of an application that is still closing and is already queued to start later.
> qtmir.mir: SessionAuthorizer::connection_is_allowed - this= SessionAuthorizer(0xb16defe4) pid= 22192
> qtmir.applications: ApplicationManager::authorizeSession - pid= 22192
> ApplicationManager REJECTED connection from app with pid 22192 as it was not launched by upstart, and no desktop_file_hint is specified
> qtmir.applications: ApplicationManager::onProcessFailed - appId= "com.ubuntu.camera_camera"
> qtmir.applications: ApplicationManager::onProcessStopped - appId= "com.ubuntu.camera_camera"
>
> Victor can confirm the same happened to him with camera and settings apps.
>
> [1] https://trello.com/c/nAccJ8Qd/2639-854-ubuntu-landing-030-gsettings-qt-unity8-qtmir-qtubuntu-saviq
I followed the steps below:
"""
* Open messaging app.
* Slide up to create a new message.
* Tap on the camera icon.
* In content hub tap on the camera app.
* Take a photo in the camera app.
* Tap on the big tick. Returned to the messaging app with the image in
the text window.
* Swipe in from the right to reveal the spread.
* Open spread.
* Switch to the camera app.
Expected result:
* Camera app should display the live view.
Actual result:
* Camera app shows a black screen
"""
A second after switching to camera-app it goes away.
Log shows that camera-app quit (closed itself). Which is expected as it
was summoned by the content hub as a helper and was no longer needed.
Different from the log you got.
In this situation there's nothing unity8 can do. If the app closes
itself shortly after it's focused, I don't think unity8 should go and
restart it.
On 12/01/2016 14:39, Michał Sawicz wrote: mako. ger::onProcessS tarting( appId=" com.ubuntu. camera_ camera" ) - User wants to start a new instance of an application that is still closing and is already queued to start later. er::connection_ is_allowed - this= SessionAuthoriz er(0xb16defe4) pid= 22192 ger::authorizeS ession - pid= 22192 ger::onProcessF ailed - appId= "com.ubuntu. camera_ camera" ger::onProcessS topped - appId= "com.ubuntu. camera_ camera" /trello. com/c/nAccJ8Qd/ 2639-854- ubuntu- landing- 030-gsettings- qt-unity8- qtmir-qtubuntu- saviq
> Review: Needs Fixing
>
> QA found a problem with this and I can confirm on devel-proposed/
>
> Trying to follow steps from Victor [1] I got into a state where unity8 rejects the camera app:
>
> qtmir.applications: ApplicationMana
> qtmir.mir: SessionAuthoriz
> qtmir.applications: ApplicationMana
> ApplicationManager REJECTED connection from app with pid 22192 as it was not launched by upstart, and no desktop_file_hint is specified
> qtmir.applications: ApplicationMana
> qtmir.applications: ApplicationMana
>
> Victor can confirm the same happened to him with camera and settings apps.
>
> [1] https:/
I followed the steps below:
"""
* Open messaging app.
* Slide up to create a new message.
* Tap on the camera icon.
* In content hub tap on the camera app.
* Take a photo in the camera app.
* Tap on the big tick. Returned to the messaging app with the image in
the text window.
* Swipe in from the right to reveal the spread.
* Open spread.
* Switch to the camera app.
Expected result:
* Camera app should display the live view.
Actual result:
* Camera app shows a black screen
"""
A second after switching to camera-app it goes away.
Log shows that camera-app quit (closed itself). Which is expected as it
was summoned by the content hub as a helper and was no longer needed.
Different from the log you got.
In this situation there's nothing unity8 can do. If the app closes
itself shortly after it's focused, I don't think unity8 should go and
restart it.