On 3/28/20 11:35 AM, Chris Murphy wrote:
On Sat, Mar 28, 2020 at 12:29 PM Samuel Sieb <samuel@xxxxxxxx> wrote:
On 3/28/20 11:24 AM, Chris Murphy wrote:
Using dconf editor, I changed the
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
Custom value 30 and the problem doesn't happen. Is there a way to
increase debug messages somehow to find out whether this timeout is
being reached? And what process or policy is causing it to be reset?
With the available information I can't figure out what's preventing
sleep.
What was there before you changed it to 30? If you reset it to the
default value what happens and what is the default value?
The default is 20 minutes, and I had it set to 20 minutes at the time
of the suspend failure.
Was it at the default value or you had it set to 20? (It could possibly
make a difference.) When you changed it to 30, it suspended after 30
minutes?
Did you make another test to see if it would suspend after 20 minutes at
the default value? Maybe there was some reason it didn't think it was
idle that one time. I've had mice that would randomly send movement and
keep waking up the screen.
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
