Ubuntu UX

Cannot answer after unlock

Bug #1588437 reported by Oleg
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Incomplete
Undecided
Unassigned
Ubuntu UX
New
Undecided
Unassigned
dialer-app
New
Undecided
Tiago Salem Herrmann

Bug Description

Steps to reproduce:

1. Lock the phone
2. Call your Ubuntu Phone from another phone
3. Slide (hide) the incoming call notification (the phone is till ringing)
4. Slide home screen to unlock the phone
5. The dialer app will open with "Enter a number" screen, the phone is ringing but you can't answer or hang, in top notifications bar there is nothing

Hardware: Meizu PRO 5
OS Version: OTA-11

Revision history for this message
Devid Antonio Filoni (d.filoni) wrote :

I can reproduce this too. Not sure about it, looks like an UX issue, bug maybe it's just a bug.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Sorry didn't quite follow the description, what do you do in step 3 to hide the notification? If I swipe it away it sends the call to voice mail

Changed in canonical-devices-system-image:
status: New → Incomplete
Revision history for this message
Oleg (arteniioleg) wrote :

I don't have voice mail or call forwarding enabled.

I will try to make a video with another phone how to reproduce the bug, but not sure.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

@tiagosh Maybe not having voice mail causes an issue?

Changed in dialer-app:
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

I am not sure if not having voice mail could cause this. It's more likely a bug between unity-notifications/telephony-service-approver.

From the description it seems that either unity is not notifying the approver to reject the call or the approver is not behaving correctly when asked by unity/notifications to reject the call.

On my tests I see the approver rejecting the call correctly.

Could you attach $HOME/.upstart/dbus.log to the bug report?

Also, if you have adb access to the device, it would help a lot if you could do the following:

1) adb shell dbus-monitor > dbus_session-call.log
2) reproduce the bug
3) attach dbus_session-call.log to this bug report.

Thank you.

Revision history for this message
Oleg (arteniioleg) wrote :

Here is a video of how to reproduce the bug https://youtu.be/oHFRr7JhAGg

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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