Regression: Maguro receiving calls fails to open dailer app

Bug #1257000 reported by Dave Morley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity8 (Ubuntu)
Fix Released
High
Gerry Boland

Bug Description

In image 42. If you open the dialer app and goto call logs. Then hit the power button to put the phone in sleep mode. Then ring the phone the dialer app doesn't appear only the lock screen. If you do the same thing but with the app closed all you get is a grey app holder instead of the Dialer app.

This is a regression over image 35 which works correctly.

Steps:
1. Unlock the maguro
2. Open the dialer app
3. Move to the Calls log
4. Hit the power button to put the device in sleep mode
5. Call the device

Result: The "calls log" page of the dialer app is changed to the "in call" page but it is minimized and and not displayed on the locked device.

Steps (part 2):
1. Unlock the Maguro
2. Confirm the dialer app is closed
3. Hit the power but to put the device in sleep mode
4. Call the device

Result: The dialer app never fully opens instead the screen is just the grey holder for an app to open into. The app again never shows in the lock screen.

Revision history for this message
Dave Morley (davmor2) wrote :
kevin gunn (kgunn72)
Changed in unity8:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Nick Dedekind (nick-dedekind)
assignee: Nick Dedekind (nick-dedekind) → Gerry Boland (gerboland)
Revision history for this message
Gerry Boland (gerboland) wrote :

Using image 45. I'm unable to reproduce the first part of this bug - if I accept the call, the Dialer app is revealed showing the In Call screen. Once call ends, dialer app returns to Call Log screen.

For part 2 of this bug, the dialer app is prevented from opening by the application manager - note the log message:
>> ApplicationManager REJECTED connection from app with pid 2230 as no desktop_file_hint specified
I find highly likely this is likely due to https://bugs.launchpad.net/unity-mir/+bug/1234538

Revision history for this message
Dave Morley (davmor2) wrote :

Confirmed on r47 the first part seems to be working, now \o/ no idea what the random cause of that was then.

I agree that your referred bug does sound very similar. This doesn't however seem to be random but constant so it might be a good case for testing if the fix in mir makes things work correctly here too maybe?

Revision history for this message
Dave Morley (davmor2) wrote :

So today on image 50 this worked with no perceivable issues so I am assuming therefore that it is very closely tied into the other bug.

Revision history for this message
Gerry Boland (gerboland) wrote :

Fix for https://bugs.launchpad.net/unity-mir/+bug/1243665 will land soon, let's see if it fixes this issue.

Revision history for this message
Gerry Boland (gerboland) wrote :

Can this still be reproduced?

Revision history for this message
Dave Morley (davmor2) wrote :

Gerry no it is now fixed it has been reliable for 3 tests now.

Changed in unity8:
status: Confirmed → Fix Released
Revision history for this message
Gerry Boland (gerboland) wrote :

Great, thanks for confirming that Dave

Michał Sawicz (saviq)
affects: unity8 → unity8 (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.