I did this:
1. Build and install gsettings-qt from
lp:~unity-team/gsettings-qt/bump-changelog
2. Log on onChanged in GSettings in SleepValues.qml
3. Change the sleep value, I get a log and therefore changed event.
4. Reinstall using sudo apt-get install
{libgsettings-qt1,qtdeclarative5-gsettings1.0}=0.1+15.04.20150810-0ubuntu1
5. Do step 2 and 3 without any log.
It seems changing a setting using the GSettings binding does not
generate the “changed“, but changing it from the command line does.
--
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:
New
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
