As I understand it, dim-timeout is expected to be relative to activity-
timeout. I have a branch for ubuntu-system-settings that changes dim-
timeout whenever the activity-timeout gsetting value changes. This
feels like a work around for broken logic. If we don't want to set dim-
timeout separately, and remain relative to activity-timeout, we should
drop the setting completely and ubuntu-system-compositor should dim the
screen on activity-timeout - 10.
** Changed in: unity-system-compositor (Ubuntu)
Status: Invalid => New
** Changed in: unity-system-compositor (Ubuntu RTM)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1437510
Title:
Screen dim is not following the lock screen timeout (always dimming
after 50 seconds)
Status in the base for Ubuntu mobile products:
Confirmed
Status in ubuntu-system-settings package in Ubuntu:
In Progress
Status in unity-system-compositor package in Ubuntu:
New
Status in unity-system-compositor package in Ubuntu RTM:
New
Bug description:
current build number: 258
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-03-26 16:39:52
version version: 258
version ubuntu: 20150326
version device: 20150310-3201c0a
version custom: 20150216-561-29-186
Go to system settings, security, lock when idle, and change to any
value higher than 1 minute. Now wait and you will see that the screen
will dim after 50 seconds, no matter what value you set.
The screen should only dim 10 seconds before reaching the screen lock
value.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1437510/+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
