[kscreenlocker] [Bug 378906] New: Ktorrent disables automatic screen lock

[Ofnuts]

https://bugs.kde.org/show_bug.cgi?id=378906

Bug ID: 378906
Summary: Ktorrent disables automatic screen lock
Product: kscreenlocker
Version: 5.5.5
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: plasma-***@kde.org
Reporter: ***@gmx.com
CC: ***@gmail.com, ***@kde.org
Target Milestone: ---

In System settings>Desktop behavior>Screen locking, I set a time-out of 2mn. I
leave the system alone and lock-up doesn't happen after 2mn.

Then I remember I have Ktorrent running with the "Prevent going to sleep"
option. I quit ktorrent, wait 2mn, and the screen locks up. Some more trials
show that screen lock up doesn't happen if ktorrent is downloading and ktorrent
"Prevent sleep" option is set.

Screen lock-up occurs if either

* ktorrent is not running
* ktorrrent has no active torrent
* ktorrent "prevent sleep" option is not set

I do appreciate the usefulness of the "Prevent sleep" option, but it shouldn't
interfere with screen lockup. This is a security issue.

I made my experiments with ktorrent, but it is unlikely that ktorrent
explicitly prevents lock-up, so this would be an unwanted coupling of the
"Prevent sleep" function and other applications could have the same problem.

Version of the component is hard to tell... Running KDE from Kubuntu 16.04
which seems to be KDE Framework 5.18, while System Settings report v5.5.5.

[Rex Dieter]

https://bugs.kde.org/show_bug.cgi?id=378906

Rex Dieter <***@math.unl.edu> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@math.unl.edu

--- Comment #1 from Rex Dieter <***@math.unl.edu> ---
As far as I know, the "Prevent going to sleep" option makes no distinction
between the 2 you mention (system sleep vs screen sleep), ie, you cannot have
one without th other

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=378906

Martin Gräßlin <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|5.5.5 |unspecified
Component|general |general
Product|kscreenlocker |ktorrent
Assignee|plasma-***@kde.org |***@gmail.com

--- Comment #2 from Martin Gräßlin <***@kde.org> ---
Reassign to ktorrent - not a bug in kscreenlocker

[Ofnuts]

https://bugs.kde.org/show_bug.cgi?id=378906

--- Comment #3 from Ofnuts <***@gmx.com> ---
(In reply to Rex Dieter from comment #1)

Post by Rex Dieter
As far as I know, the "Prevent going to sleep" option makes no distinction
between the 2 you mention (system sleep vs screen sleep), ie, you cannot
have one without th other

I'm not talking about screen sleep but about screen lock which is a different
functionality...

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=378906

Martin Gräßlin <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC|***@kde.org |

[Rex Dieter]

https://bugs.kde.org/show_bug.cgi?id=378906

--- Comment #4 from Rex Dieter <***@math.unl.edu> ---
OK, in this case, I'm still not sure there's any distinction between screen
lock vs screen sleep

[Ofnuts]

https://bugs.kde.org/show_bug.cgi?id=378906

--- Comment #5 from Ofnuts <***@gmx.com> ---
IMHO these are three very different purposes. I understand that applications
such as ktorrent want to prevent the machine from going to sleep (which would
interrupt their job) but screen lock/sleep is none of their business, they can
run in a locked-up machine.

Screen lock and sleep serve also different purpose, you may want to turn off
the screen without locking the machine (which requires entering password).

[Andrius Štikonas]

https://bugs.kde.org/show_bug.cgi?id=378906

Andrius Štikonas <***@stikonas.eu> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@stikonas.eu

--- Comment #6 from Andrius Štikonas <***@stikonas.eu> ---
I looked at KTorrent code. It seems that only mediaplayer inhibits screensaver.
So you can just disable mediaplayer plugin and Screensaver shoudln't be
inhibited.

[Ofnuts]

https://bugs.kde.org/show_bug.cgi?id=378906

--- Comment #7 from Ofnuts <***@gmx.com> ---
My only enabled plugin in the Information Widget.

[Dr. Chapatin]

https://bugs.kde.org/show_bug.cgi?id=378906

Dr. Chapatin <***@gmx.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmx.com

--- Comment #8 from Dr. Chapatin <***@gmx.com> ---
Confirmed on Arch Linux.
plasma 5.12 beta
ktorrent 5.1.0

Automatic screen locking does not work if some torrent is active.
mediaplayer plugin is not enabled here.

[Valeriy Malov]

https://bugs.kde.org/show_bug.cgi?id=378906

Valeriy Malov <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Valeriy Malov]

https://bugs.kde.org/show_bug.cgi?id=378906

--- Comment #9 from Valeriy Malov <***@gmail.com> ---
I get the impression that this is related more to kscreenlocker than ktorrent,
because kscreenlocker doesn't seem to differentiate between screensaver
inhibition and power management inhibition:

https://github.com/KDE/kscreenlocker/commit/39152af231d2c76163699ba8e99228f40c46f269

Because screen saver interface is considered obsolete (I guess?), so media
players use power management inhibition to inhibit the screen locker. Which
means that ktorrent has no way of inhibiting suspend without inhibiting screen
locker. In the end it seems to be an FDO spec issue (or lack of thereof).