[Desktop-packages] [Bug 1574851] Re: libgl not found on nvidia machines (so far)

[Alberto Aguirre]

I have snapd 2.0.10 now, still ubuntu-clock-app does not start

http://pastebin.ubuntu.com/19093778/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu.
https://bugs.launchpad.net/bugs/1574851

Title:
  libgl not found on nvidia machines (so far)

Status in Snappy:
  Triaged
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  So I've just had 2 recent complaints on libgl not being found on nvidia.
  here: 
http://askubuntu.com/questions/759647/opengl-error-in-snaps-ubuntu-16-04 
  and on IRC

  I cannot determine if anyone has had success running one of the 
desktop-example apps from the store on an nvidia gpu machine.
  I asked Alberto Aguirre on the mir team (who has a nvidia gpu) to try SDoC 
and install the ubuntu-clock-app from the store - he confirms seeing the exact 
same issue, he can be questioned if debug help is needed.

  Note, from an engagement on IRC earlier, the person confirmed that
  even rebuilding the clock snap locally and sideloading did not address
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1574851/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1574851] Re: libgl not found on nvidia machines (so far)

[Alberto Aguirre]

apt-cache policy snapd
snapd:
  Installed: 2.0.9
  Candidate: 2.0.9
  Version table:
 *** 2.0.9 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages

apt-cache policy snap-confine
N: Unable to locate package snap-confine


dpkg --get-selections | grep nvidia
nvidia-361 install
nvidia-opencl-icd-361 install
nvidia-prime install
nvidia-settings install


snap: ubuntu-clock-app version: 3.6+snap3, rev: 5

Running it results in:

$ubuntu-clock-app.clock
libGL error: No matchings fbConfigs or visuals found
libGL error: failed to load driver: swrast
Unrecognized OpenGL version
Unrecognized OpenGL version

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu.
https://bugs.launchpad.net/bugs/1574851

Title:
  libgl not found on nvidia machines (so far)

Status in Snappy:
  Triaged
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  So I've just had 2 recent complaints on libgl not being found on nvidia.
  here: 
http://askubuntu.com/questions/759647/opengl-error-in-snaps-ubuntu-16-04 
  and on IRC

  I cannot determine if anyone has had success running one of the 
desktop-example apps from the store on an nvidia gpu machine.
  I asked Alberto Aguirre on the mir team (who has a nvidia gpu) to try SDoC 
and install the ubuntu-clock-app from the store - he confirms seeing the exact 
same issue, he can be questioned if debug help is needed.

  Note, from an engagement on IRC earlier, the person confirmed that
  even rebuilding the clock snap locally and sideloading did not address
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1574851/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

[Alberto Aguirre]

So actually, fontconfig does not cache conf files at all... it caches
fonts but not conf files...

fontconfg needs support to also cache the result of the parsing of the
xml config file parsing. It seems a low priority effort for less than a
35ms improvement in startup.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1590804

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

[Alberto Aguirre]

Also FcInitReinitialize and FcInitBringUptoDate both will do the same
thing the first time is called in the process, so wouldn't help for
startup either.


** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1590804

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

[Alberto Aguirre]

>From the attached backtrace, It seems that Qt calls FcInitReinitialize
when populating its font database (a QGenericUnixFontDatabase instance
provided by Qtubuntu) - that explains why re-parses the conf files
everytime.

See
http://code.qt.io/cgit/qt/qtbase.git/tree/src/platformsupport/fontdatabases/fontconfig/qfontconfigdatabase.cpp?h=v5.4.1#n439


** Attachment added: "backtrace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1590804/+attachment/4689148/+files/backtrace.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1590804

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  New
Status in fontconfig package in Ubuntu:
  New

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

[Alberto Aguirre]

I tried fc-cache, but starting a qml app still continues to open up the
conf files.

Digging through Qt source to understand where these calls are coming
from.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1590804

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  New
Status in fontconfig package in Ubuntu:
  New

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1524131] Re: /usr/bin/mediaplayer-app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

[Alberto Aguirre]

The stack trace points to:

ss << "type='" << lut.at(d->type) << "'" << comma;

where lut is a static const std::map. So
perhaps the dbus::Object instance is destroyed after unloading the
libdbus-cpp.so.

Is libdbus-cpp.so being loaded dynamically? Or I guess a library linking
to libdbus-cpp is loaded dynamically.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1524131

Title:
  /usr/bin/mediaplayer-
  
app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

Status in Canonical System Image:
  Confirmed
Status in dbus-cpp package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Top 3 over the past week on errors.u.c. mediaplayer has not been
  updated for a while and the frequency increased significantly around
  mid-december, probably due to a change in an underlying component
  (gstreamer has been updated on Dec. 12th or it could be the major dbus
  match rules changes as the stacktrace would suggest)

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediaplayer-app.  This problem was most recently seen with
  version 0.20.5+15.04.20150701-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/a649a8d64746c3cce478208950c51611a06323cb
  contains more details.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1161206] Re: Mir EGL apps output worrying but harmless error: libEGL warning: unsupported platform (null)

[Alberto Aguirre]

I  cannot reproduce this anymore.

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1161206

Title:
  Mir EGL apps output worrying but harmless error: libEGL warning:
  unsupported platform (null)

Status in Mir:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  It seems all the EGL demo clients trigger this message to appear on
  stderr:

  libEGL warning: unsupported platform (null)

  Looks like a small change in libEGL has been overlooked.

  I am using:
  ii  libegl1-mesa:amd649.1~rc2-0ubuntu0+mir2-jenkins19 
   amd64free implementation of the EGL API -- runtime
  ii  libegl1-mesa-dbg:amd649.1~rc2-0ubuntu0+mir2-jenkins19 
   amd64free implementation of the EGL API -- debugging symbols
  ii  libegl1-mesa-dev  9.1~rc2-0ubuntu0+mir2-jenkins19 
   amd64free implementation of the EGL API -- development files
  ii  libegl1-mesa-drivers:amd649.1~rc2-0ubuntu0+mir2-jenkins19 
   amd64free implementation of the EGL API -- hardware drivers
  ii  libegl1-mesa-drivers-dbg:amd649.1~rc2-0ubuntu0+mir2-jenkins19 
   amd64free implementation of the EGL API -- driver debugging 
symbols

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1161206/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption running software clients (including Xmir) on android

[Alberto Aguirre]

@Daniel,

Yeah, those flags are used by the implementations to know when they need
to do cache coherency operations (flush, invalidate, etc).

In android, software buffers CAN be used as backing to textures for
opengl and can be passed directly to Hardware Composer HAL (HW
Composer), hence they are marked as such.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1406725

Title:
  Severe graphical corruption running software clients (including Xmir)
  on android

Status in Mir:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  I'm seeing severe graphical corruption running mir_demo_client_flicker
  on mako.

  Start a few instances of the client (or just one flicker and some
  other clients) and you'll see the mir_demo_client_flicker window
  contains significant corruption.

  I don't think it's an overlays issue. The problem occurs even without
  overlays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1480755] Re: [regression] Some Mir EGL demos don't get bypassed any more in fullscreen

[Alberto Aguirre]

** Changed in: mir
Milestone: 0.16.0 = 0.15.0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1480755

Title:
  [regression] Some Mir EGL demos don't get bypassed any more in
  fullscreen

Status in Mir:
  Fix Committed
Status in mesa package in Ubuntu:
  New

Bug description:
  [regression] Fullscreen GL apps don't get bypassed any more.

  As you can see in compositor report from any of our demo servers:
  [1438572052.621854] compositor: Display 0x7faea4306fa0 averaged 60.537 FPS, 
0.506 ms/frame, latency 15.669 ms, 61 frames over 1.007 sec, 0% bypassed
  [1438572053.622668] compositor: Display 0x7faea4306fa0 averaged 59.950 FPS, 
0.551 ms/frame, latency 15.814 ms, 60 frames over 1.000 sec, 0% bypassed
  [1438572054.623370] compositor: Display 0x7faea4306fa0 averaged 59.958 FPS, 
0.613 ms/frame, latency 15.721 ms, 60 frames over 1.000 sec, 0% bypassed

  I think this is only medium though, because it's a transparent
  optimization so its absence is very hard to notice in most cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1480755/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1377872] Re: Double-buffered compositing performance is very poor (30 FPS)

[Alberto Aguirre]

** Changed in: mir
Milestone: 0.9.0 = 0.10.0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872

Title:
  Double-buffered compositing performance is very poor (30 FPS)

Status in Mesa:
  Confirmed
Status in Mir:
  In Progress
Status in “mesa” package in Ubuntu:
  New

Bug description:
  Double-buffered compositing performance is poor.

  Fortunately we don't use double-buffering in our default compositor
  (mostly), and Ubuntu touch does not use the default compositor either.
  However, if you make the compositor double-buffered, then it quickly
  drops down to 30 FPS while not consuming any significant CPU or render
  time.

  Test case A:
  Convert your compositor to double buffering by the code change suggested in 
bug 1350725.

  Test case B (different bug?):
  Switch all clients to double-buffering using this branch:  
lp:~vanvugt/mir/double
  and then start a nested server.

  Now start a bunch of clients, and you will find they slow down to 30
  FPS after only starting a few. This does not happen with the default
  triple buffered compositor.

  I've been ignoring this issue for a little while [1] thinking I had simply 
run out of power, although suspected that can't be right as this is a powerful 
quad-core i7 and it's slowing down with only 10 clients.
  [1] https://bugs.launchpad.net/mir/+bug/1350725/comments/1

  Now today test case B has revealed (via MIR_CLIENT_PERF_REPORT) that
  the slowdown happens without using any significant render time (less
  than 2 ms) and without using any significant CPU (less than 20% of one
  out of four cores).

  So the conclusion is our default compositor is probably holding
  buffers for a little too long somewhere. Because that's the only
  sensible reason I can think of for my system to bog down to 30 FPS
  without stressing the CPU or GPU. We've got poor parallelism in our
  code somewhere. And once that's solved, we'll be able to make further
  improvements such as resolving bug 1350725.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1377872/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1361642] Re: DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

[Alberto Aguirre]

** Branch linked: lp:~mir-team/dbus-cpp/fix-1361642-with-30sec-timeout

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1361642

Title:
  DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

Status in DBus C++:
  Confirmed
Status in “dbus-cpp” package in Ubuntu:
  New

Bug description:
  This causes issues such as found here:

  https://code.launchpad.net/~jpakkane/indicator-
  network/grace/+merge/232194

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1361642/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1364453] Re: Brightness setting does not persist across reboots

[Alberto Aguirre]

** Changed in: unity-system-compositor (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-ubuntu-touch-schemas in
Ubuntu.
https://bugs.launchpad.net/bugs/1364453

Title:
  Brightness setting does not persist across reboots

Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “unity-system-compositor” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  When altering the brightness setting, it is always reset to the
  default value after a reboot. It is expected that changing the setting
  should persist across reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-ubuntu-touch-schemas/+bug/1364453/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1364453] Re: Brightness setting does not persist across reboots

[Alberto Aguirre]

** Changed in: unity8 (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-ubuntu-touch-schemas in
Ubuntu.
https://bugs.launchpad.net/bugs/1364453

Title:
  Brightness setting does not persist across reboots

Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “unity-system-compositor” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  When altering the brightness setting, it is always reset to the
  default value after a reboot. It is expected that changing the setting
  should persist across reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-ubuntu-touch-schemas/+bug/1364453/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1273174] Re: Manage auto brightness synchronisation

[Alberto Aguirre]

** Changed in: unity-system-compositor
   Status: New = Fix Released

** Changed in: unity-system-compositor (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-ubuntu-touch-schemas in
Ubuntu.
https://bugs.launchpad.net/bugs/1273174

Title:
  Manage auto brightness synchronisation

Status in Unity System Compositor:
  Fix Released
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “unity-system-compositor” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  powerd doesn't handle the saving or restoring of the automatic
  brightness boolean itself. Something else (likely unity8) should do
  this.

  I'm adding a GSettings boolean which should be monitored and
  synchronised to powerd using userAutoBrightnessEnable on its D-Bus
  API.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1230345] Re: Unity8 should control the display lock after idle (with a way to configure the delay)

[Alberto Aguirre]

** Changed in: gsettings-ubuntu-touch-schemas
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-ubuntu-touch-schemas in
Ubuntu.
https://bugs.launchpad.net/bugs/1230345

Title:
  Unity8 should control the display lock after idle (with a way to
  configure the delay)

Status in GSettings schemas for Ubuntu touch:
  Fix Released
Status in Unity System Compositor:
  Fix Released
Status in The Unity 8 shell:
  In Progress
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged

Bug description:
  Currently powerd is doing that but apparently unity8 is going to take
  over that.

  Some questions:
  - when is the work going to happen (before or after v1)
  - is that going to be an unity8 configuration (user owned?)
  - is it going to be stored in gsettings?

  We need to know the answer the those questions to be able to do the
  system-settings corresponding work...

  Note that currently we write a powerd gsettings key, but that's buggy
  since powerd is running as root and we write an user key. There is
  also no way to write a system key on the ro image

  Should we drop that setting for v1?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-ubuntu-touch-schemas/+bug/1230345/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp