Dim timeout gsetting key not set anymore
Bug #1503693 reported by
Alexandros Frantzis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Bill Filler | ||
gsettings-qt (Ubuntu) |
Fix Released
|
High
|
Lars Karlitski | ||
ubuntu-system-settings (Ubuntu) |
Invalid
|
High
|
Jonas G. Drange |
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/
Not sure if this is a problem in the way ubuntu-
Related branches
lp:~larsu/gsettings-qt/lp1503693
- Albert Astals Cid (community): Approve
-
Diff: 49 lines (+16/-2)2 files modifiedGSettings/gsettings-qml.cpp (+13/-1)
tests/tst_GSettings.qml (+3/-1)
Changed in canonical-devices-system-image: | |
milestone: | none → ww46-2015 |
assignee: | nobody → Bill Filler (bfiller) |
Changed in ubuntu-system-settings (Ubuntu): | |
assignee: | nobody → Jonas G. Drange (jonas-drange) |
status: | New → In Progress |
Changed in canonical-devices-system-image: | |
importance: | Undecided → High |
Changed in ubuntu-system-settings (Ubuntu): | |
importance: | Undecided → High |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
Changed in ubuntu-system-settings (Ubuntu): | |
status: | In Progress → Incomplete |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
Changed in ubuntu-system-settings (Ubuntu): | |
status: | Incomplete → Invalid |
To post a comment you must log in.
I did this: qt1,qtdeclarati ve5-gsettings1. 0}=0.1+ 15.04.20150810- 0ubuntu1
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-
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.