desktop-packages team mailing list archive

[Launchpad Bug Tracker <1503693@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package gsettings-qt -
0.1+16.04.20151104-0ubuntu1

---------------
gsettings-qt (0.1+16.04.20151104-0ubuntu1) xenial; urgency=medium

  [ Lars Uebernickel ]
  * qgsettings-qml: explicitly emit changed events (LP: #1503693)

gsettings-qt (0.1+15.04.20150810-0ubuntu1) vivid; urgency=medium

  [ Lukáš Tinkl ]
  * Force handling deferred delete events to avoid memory leaks (LP:
    #1460970)
  * Force handling deferred delete events to avoid memory leaks (LP:
    #1460970)

 -- Sebastien Bacher <seb128@xxxxxxxxxx>  Wed, 04 Nov 2015 17:59:13
+0000

** Changed in: gsettings-qt (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  Dim timeout gsetting key not set anymore

Status in Canonical System Image:
  Fix Committed
Status in gsettings-qt package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  The dim-timeout gsettings key is not set anymore when the activity-
  timeout key changes, so a default value of 45sec is used for dim-
  timeout regardless of the activity timeout selected by the user in the
  batter plugin.

  The logic to set the dim timeout value is there in
  battery/SleepValues.xml in the GSettings onChanged handler, but it
  seems that the onChanged handler is not called when the activity-
  timeout value changes.

  Not sure if this is a problem in the way ubuntu-system-settings uses
  the GSettings QML item, or if the item implementation itself is broken
  somehow.

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