touch-packages team mailing list archive

[Cemil Azizoglu <cemil.azizoglu@xxxxxxxxxxxxx>]

rsalveti's original bug doesn't seem to be related to Mir. Marking it as
Invalid for Mir.

** Changed in: mir
       Status: Triaged => Invalid

** Changed in: mir (Ubuntu)
       Status: New => Invalid

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

Title:
  Unity8 completely frozen (unable to unlock, receive calls, etc)

Status in the base for Ubuntu mobile products:
  New
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 224
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-01-29 18:53:09
  version version: 224
  version ubuntu: 20150129
  version device: 20150129-c75dcfb
  version custom: 20150129-528-26-182

  Was driving around with my car, and noticed once I got back home that
  my clock was stuck in a previous time (~20min before getting home),
  and after trying to use the phone I noticed unity8 was completely
  stuck, but the underling OS was still running fine.

  The worst here is that we're unable to notify the user about calls, as
  the interface is completely stuck. Another bad thing is that this
  could as well happen when the user is sleeping or something, without
  an easy way to know until he tries to use the phone.

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