touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

I don't think treating this separately to bug 1506358 will be helpful.

Firstly, there is proof in comment #40 that the original reporter hit
bug 1506358 at 13:31:08 on 10 January. Assuming Uranicus is 1 hour ahead
of UTC...

Secondly, if you look in bug 1506358 you'll find I mentioned that when
it occurs (client crashes) the server is unaffected and keeps running.
In the case of this bug where unity8 is the client, unity-system-
compositor is the server. So if unity-system-compositor has issues at
all it's likely unrelated to bug 1506358. And the bug most provably
related to this one is bug 1506358.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1532607

Title:
  Phone not usable while a call comes in - followed by "restart"

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  My system:

  current build number: 225
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-09 06:52:53
  version version: 225
  version ubuntu: 20160109
  version device: 20151216-378d4f3
  version custom: 20151111--36-46-vivid

  What happened:
  Someone called me and I wanted to take the call on the phone (nothing attached to the phone). The screen was locked and I pressed the power button to unlock the screen. The phone did not react on any pushed buttons. The phone continued ringing but I was not able to do anything with the phone during this time.

  During the next minute the phone was blocked. After this period a
  "restart" followed.

  "Restart":
  The restart was not a real reset. The phone screen was black. Then approx. 1 - 2 minutes after the call was gone, the screen went on again and the ubuntu logo with the dots appeared (same screen when you start the phone but without the "bq"-screen). 

  I did not need to enter the PIN code of the SIM card. The phone was
  again fully operational.

  This happened on January, 10th at approx. 13:30 h. I have attached the
  sys.log for your review and hopefully for tracing back the issue to
  the root cause.

  Matthias

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