[phone-app] is stuck on "calling" screen every other call

Bug #1368862 reported by Olga Kemmet
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu UX
In Progress
Critical
Olga Kemmet
dialer-app
In Progress
Critical
Gustavo Pichorim Boiko

Bug Description

Steps to reproduce:

1. Open phone app
2. Call device, an incoming call snap decision appears on screen
3. Accept the call
4. View switches to active call screen
5. Hang up after a few seconds and wait until view switches back to the main keypad
6. Call the device again
7. An incoming call snap decision appears again, accept the call

Actual result:
The view doesn't switch to the active call anymore, only the indicator bar states that there is an active call going on.
If you tap on the indicator bar, view navigates to the active call screen but it is stuck on the CALLING screen. The screen is not responsive and it is not possible to hang up the call. Hang up the device you called from and navigate back to the keypad via the BACK button in the header (this works!). Alternatively kill the app and repeat all steps again.

Expected result - desired solution:
If you are in the phone, receiving a call & accepting it - the view should always switch automatically to the active call screen. The screen should say CONNECTING and not DIALLING/CALLING. After connection is established, the usual active call screen should be visible.

P.S.: if you navigated BACK from the frozen screen and call the device again, it will most likely switch to the active call screen. If you hang up and call the device for the 4th time, it will be stuck again. Therefor every other call in the description.

description: updated
Revision history for this message
Victor Tuson Palau (vtuson) wrote :

this should be critical

Changed in ubuntu-ux:
importance: High → Critical
status: New → Fix Committed
status: Fix Committed → In Progress
Bill Filler (bfiller)
Changed in dialer-app:
importance: Undecided → Critical
assignee: nobody → Gustavo Pichorim Boiko (boiko)
tags: added: touch-2014-09-25
Revision history for this message
Bill Filler (bfiller) wrote :

I'm seeing it too, on testing with silo 10 on rtm, assuming it is there is stock rtm image on krillin.

Seeing this in the log:
file:///usr/share/dialer-app/LiveCallPage/LiveCall.qml:441:5: QML Row: Binding loop detected for property "height"
file:///usr/share/dialer-app/LiveCallPage/LiveCall.qml:441:5: QML Row: Binding loop detected for property "height"
file:///usr/share/dialer-app/LiveCallPage/LiveCall.qml:462: ReferenceError: calls is not defined
file:///usr/share/dialer-app/LiveCallPage/LiveCall.qml:477: ReferenceError: calls is not defined

Changed in dialer-app:
status: New → Confirmed
Bill Filler (bfiller)
Changed in dialer-app:
status: Confirmed → In Progress
Revision history for this message
Gustavo Pichorim Boiko (boiko) wrote :

This is actually a bug in snap decisions.

When we click the snap decision it is setting the application active property to false, and it doesn't get set back to true after the snap decision is gone. As we unregister the telepathy stuff when active=false, we are not getting updates about calls anymore. I'll mark the bug as a duplicate of the unity8 report.

Bill Filler (bfiller)
tags: added: touch-2014-10-02
removed: touch-2014-09-25
tags: removed: rtm14 touch-2014-10-02
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.