ubuntu-phonedations-bugs team mailing list archive

[Tiago Salem Herrmann <tiago.herrmann@xxxxxxxxxxxxx>]

I am seeing timeout from the approver while trying to create an instance
of media-hub in the dbus.log file.

Media-hub is a telepathy observer (it watches telepathy to stop music
when there is an incoming call), and telepathy by design won't forward
the incoming call to the approver (to display the snap decision) until
all observers confirm receiving the incoming channel first.

If media-hub is really stuck for some reason, that would explain the
issue, since after a dbus timeout trying to deliver the channel to
media-hub, telepathy would still try to deliver the channel to the
approver, which would make the snap decision appear, and quickly
disappear (since the incoming call is already gone).

This is a guess, but seems to match what Matthew described, and what I
see in the logs:

-----

virtual QMediaService* AalServicePlugin::create(const QString&)
"org.qt-project.qt.mediaplayer"
Failed to start a new media-hub player session:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
Failed to create a new media player backend. Video playback will not function.

Could not finish contructing new AalMediaPlayerService instance since
m_hubPlayerSession is NULL

----

-- 
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions