Bug 294021

Summary:	KTorrent inhibits powermanager actions inappropriately
Product:	[Applications] ktorrent	Reporter:	Ryan Rix <ry>
Component:	general	Assignee:	Joris Guisson <joris.guisson>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	nille_kungen, rdieter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Bug Depends on:
Bug Blocks:	289760

Description Ryan Rix 2012-02-13 21:17:29 UTC

Version:           unspecified (using Devel) 
OS:                Linux

Per https://bugs.kde.org/show_bug.cgi?id=289760#c70, it is no longer possible to suspend while KTorrent is running because it is inhibiting suspend if any torrents are active, whether there is traffic with them or not. 

Reproducible: Always

Steps to Reproduce:
# Configure some torrents
# Set up some powermanager actions (suspend on laptop lid closed, F.E.)
# trigger action

Actual Results:  
kded reports that actions are inhibited and they cannot be completed

Expected Results:  
The action should not be interrupted by KTorrent

This could be made in to a configuration option, but IMO it's not a great usability idea to inhibit systemwide actions for network applications. Instant Messaging clients do not inhibit, nor do browser or email clients for example.

Comment 1 Joris Guisson 2012-02-14 18:48:05 UTC

> This could be made in to a configuration option, but IMO it's not a great
> usability idea to inhibit systemwide actions for network applications.

It already is configurable:

Settings -> Application -> Suppress sleep when torrents are running

The idea is that, with this option your computer keeps running until all torrents are finished. If you don't have any running torrents, it acts normally.

If this behavior is not wanted it can be turned off using the option. It was an option several people requested, and I'm not gonna remove it.

Comment 2 Ryan Rix 2012-02-14 21:55:19 UTC

Hmm, and I looked for that config key when I wrote this report, too. Thanks for finding it for me :), I've just disabled it and it appears to be working properly.