touch-packages team mailing list archive

[Alberto Aguirre <alberto.aguirre@xxxxxxxxxxxxx>]

** Changed in: unity-system-compositor
   Importance: Undecided => Critical

** Changed in: unity-system-compositor
     Assignee: (unassigned) => Alberto Aguirre (albaguirre)

** Changed in: unity-system-compositor
       Status: New => In Progress

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

Title:
  No powerd suspend blocker after boot (just after first screen off/on
  cycle)

Status in Unity System Compositor:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  The way system-compositor holds down suspend is by acquiring a suspend
  blocker from powerd. This is currently working fine for all cases but
  the one after booting the system.

  What you would expect after boot:
  phablet@ubuntu-phablet:~$ powerd-cli list
  powerd-cli: Running as user is not fully supported.
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.9, State: 1

  What you get:
  phablet@ubuntu-phablet:~$ powerd-cli list
  powerd-cli: Running as user is not fully supported.
  System State Requests:
    None

  That makes the system to automatically suspend in a weird way when
  someone tries to play a music/video (which basically mean an extra
  suspend blocker acquire/release), making the system to suspend
  directly.

  To reproduce:
  - Boot the system
  - Open media-player
  - Play one song
  - Stop

  System will suspend and screen will be off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1353647/+subscriptions