touch-packages team mailing list archive

[kevin gunn <kevin.gunn@xxxxxxxxxxxxx>]

** No longer affects: telepathy-ofono (Ubuntu)

** Changed in: powerd (Ubuntu)
       Status: Incomplete => In Progress

** Changed in: powerd (Ubuntu)
   Importance: Undecided => High

** Changed in: powerd (Ubuntu)
     Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

** Branch linked: lp:~afrantzis/unity8/power-state-change-reason-snap-
decision

** Changed in: unity8 (Ubuntu)
       Status: Fix Released => In Progress

** Changed in: unity8 (Ubuntu)
     Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

-- 
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/1291455

Title:
  [greeter] Screen and input should be disabled with proximity sensor
  when on greeter

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Won't Fix
Status in Unity System Compositor:
  Fix Released
Status in powerd package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  * suspend your device
  * cover the proximity sensor (top left on mako)
  * call the phone

  Expecte result:
  * screen does not light up until you uncover the proximity sensor

  Current result:
  * screen lights up and you can answer the call

  This results in butt/pocket calls...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140306-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Wed Mar 12 13:14:37 2014
  InstallationDate: Installed on 2014-03-12 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

  ------------------------------
  UX Desired resolution:

  Unfortunately UX doesn't have a structured solution ready.
  UX is now collecting all the device capability related bugs as a
  requirement for the kick off of a bigger project:
  specification of device capability related behaviours.
  Marking this as "Won't fix", but it really means "it will get fixed in the future"

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