Opened 12 years ago
Closed 12 years ago
#1285 closed Bug (invalid)
don't inhibit power management when manually triggering suspend or hibernate
Reported by: | kiddo | Owned by: | charles |
---|---|---|---|
Priority: | Normal | Milestone: | None Set |
Component: | GTK+ Client | Version: | 1.34 |
Severity: | Normal | Keywords: | |
Cc: |
Description
Transmission currently inhibits gnome-power-manager's suspend and hibernate functions as longs as there is 1 "active" download (not paused).
However, I would need another level of logic: transmission should only inhibit "timed" actions, not "manual" actions. When I press the "suspend" button on my keyboard (or, in my case, when I close the lid of this laptop), I really "mean" suspend.
Today, I closed the lid while transmission was running because I had to GTFO, and a few hours later the battery was entirely drained. In situations like this, when I close the lid, I really mean to suspend, I don't care much what is running at that moment (anyway, when I fall out of range of the network, transmission will be useless).
So, to summarize:
- when the user starts the action manually: do not inhibit
- when the computer requests auto inhibition:
-- if downloads are active: inhibit -- if all downloads are paused: do not inhibit
Change History (2)
comment:1 Changed 12 years ago by kiddo
comment:2 Changed 12 years ago by charles
- Resolution set to invalid
- Status changed from new to closed
the GNOME Power Manager Spec doesn't have this degree of flexibility, there's no way for me to implement this request.
You may want to set the "allow-hibernation-even-when-torrents-are-active" flag in settings.json to always allow hibernation.
Stupid trac breaks formatting. The summary should read:
-- if downloads are active: inhibit
-- if all downloads are paused or complete: do not inhibit