Bug 183505

Summary: Idle laptop suspend when disconnected from AC
Product: [Unmaintained] solid Reporter: S. Umar <umar>
Component: powermanagement-kcmAssignee: Dario Freddi <drf>
Status: RESOLVED DUPLICATE    
Severity: normal CC: alex3255, ash.hunter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description S. Umar 2009-02-07 01:01:44 UTC 
Version:            (using Devel)
Compiler:          gcc-4.3.0 
OS:                Linux
Installed from:    Compiled sources

When I have my Thinkpad T61 connected to AC
but left idle for a while, and then disconnect
from AC to take it to another room, the
laptop suspends to ram. Powering up quickly
brings the system up perfectly.

It sounds like the idle time when it is
connected to AC gets transferred to idle
time when on battery thus trigerring suspend.
Thanks
Comment 1 Dario Freddi 2009-02-07 13:44:54 UTC 
Correct, though I don't know what would be the correct thing here: keeping idle time or resetting it. Any ideas/use cases/etc?
Comment 2 S. Umar 2009-02-09 14:55:42 UTC 
Well, since I presume powerdevil has to do with saving power
I don't see any need to even consider idle time when ac is
plugged in. Plus, suspend to ram is not activated during the
ac period but only when the machine is unplugged from ac.
Therefore, it seems logical to make the idle time counter only
start when it is on battery!

This is my logic...
Thanks
Comment 3 Ash Hunter 2009-09-02 15:12:24 UTC 
This seems like a trivial fix to me - just wondering when will it be implemented?

The idle time should *definitely* be reset whenever the powersave profile is changed for any reason, especially those caused by the user.
Comment 4 Alexander 2009-09-25 08:54:22 UTC 
bugs 206751 and 191545 are duplicate of this. 
I think, that idle time should be reset on plugging/unplugging AC adaptor.
Comment 5 Dario Freddi 2009-12-01 17:18:13 UTC 
Duplicating, will be fixed soon

*** This bug has been marked as a duplicate of bug 210389 ***