Ubuntu
telephony-service package

snap decision for an incoming call is not shown

Bug #1469262 reported by Pat McGowan on 2015-06-26

This bug report is a duplicate of: Bug #1453004: Phone is ringing but no sliders to pick up the call are presented. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Canonical System Image	Confirmed	Critical	Bill Filler	Canonical System Image ww28-2015 "ota5"
	telephony-service (Ubuntu)	Confirmed	Critical	Tiago Salem Herrmann

Bug Description

Arale running ota4 20150611.3

Incoming calls are not showing the snap decision to answer them, and in some cases the ringer is also not triggered. The call is then automatically sent to voicemail.

This seems to happen after a reboot perhaps with a subsequent suspend.

To dump the history:
adb shell sqlite3 /home/phablet/.local/share/history-service/history.sqlite 'select * from voice_events where senderId != \"self\"'

To capture dbus messages:
dbus-send --print-reply --dest=org.freedesktop.Telepathy.MissionControl5 /org/freedesktop/Telepathy/debug org.freedesktop.Telepathy.Debug.GetMessages

Pat McGowan (pat-mcgowan) on 2015-06-26

Changed in canonical-devices-system-image:
assignee:	nobody → Bill Filler (bfiller)
importance:	Undecided → Critical
milestone:	none → ww28-2015
status:	New → Confirmed

Revision history for this message

Ken VanDine (ken-vandine) wrote on 2015-06-26:

I've seen this as well, here's my dbus.log file for one of the missed calls. Note in this case, my phone didn't send it to voicemail, but it accepted the call. The caller was able to hear me while my phone was in my pocket, without me every hearing it ring or answering it.

http://paste.ubuntu.com/11774820/

Revision history for this message

Bill Filler (bfiller) wrote on 2015-06-29:

do we have steps to reproduce?
Also are there any crash files in /var/crash for telephony/telepathy related processes?

Revision history for this message

Bill Filler (bfiller) wrote on 2015-06-29:

Is this a dupe of https://bugs.launchpad.net/canonical-devices-system-image/+bug/1453004?

Revision history for this message

Tiago Salem Herrmann (tiagosh) wrote on 2015-06-29:

I managed to reproduce the auto-answer bug by sending a SIGSTOP to telephony-service-approver, which makes mission-control timeout the dispatch operation and send the channel to telephony-service-handler, which finally accepts the call, even though it was not approved by any approvers.

Boiko and I agreed to change telephony-service-handler to not accept any new channels in such case. Now we have to figure out why the approver is getting stuck.