We've changed the way the changed signal is dispatched due to Qt bug
32859 (tracked as bug #1460970 here), which leads to these signals not
being emitted at all anymore when changing a setting from qml.
I've attached a branch that explicitely emits those signals in that
case.
** Branch linked: lp:~larsu/gsettings-qt/lp1503693
** Changed in: gsettings-qt (Ubuntu)
Status: New => In Progress
** Changed in: gsettings-qt (Ubuntu)
Importance: Undecided => High
** Changed in: gsettings-qt (Ubuntu)
Assignee: (unassigned) => Lars Uebernickel (larsu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
Confirmed
Status in gsettings-qt package in Ubuntu:
In Progress
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
