*** This bug is a duplicate of bug 1453004 ***
https://bugs.launchpad.net/bugs/1453004
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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1469262
Title:
snap decision for an incoming call is not shown
Status in the base for Ubuntu mobile products:
Confirmed
Status in telephony-service package in Ubuntu:
Confirmed
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1469262/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
