Powerdevil should inhibit any suspend / hibernate action when a file transfer (at least a Dolphin file transfer) is in progress. Reproducible: Always
It's the application's job (or in this case KIO) to request that from PowerDevil, re-assigning to KIO.
But how? KIO can't depend on powerdevil (which is in workspace).
It just needs to send a DBus message to PowerDevil (and as a fallback to the FDO interface). Also, if... this [1] lands there'll be a Tier 1(?) solution for that. [1] https://git.reviewboard.kde.org/r/126650/
The problem persists. Computer sleeps while dolphin copies data to another internal partition. When computer resumes, copy process continues from the point where it stopped. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1
*** Bug 478785 has been marked as a duplicate of this bug. ***
*** Bug 466704 has been marked as a duplicate of this bug. ***
I just went through this...
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1868
Git commit 60191c0473a96c41279519845030efa12fdd0bb4 by Kai Uwe Broulik. Committed on 04/05/2025 at 09:29. Pushed by broulik into branch 'master'. CopyJob: Inhibit suspend during copy operation Avoids the system going to sleep during a lengthy copy operation. M +21 -0 src/core/copyjob.cpp https://invent.kde.org/frameworks/kio/-/commit/60191c0473a96c41279519845030efa12fdd0bb4
Why is this fixed only for the copy operation? Shouldn't be fixed also for the move operation? Which is actually even more dangerous than the copy operation! As with a broken copy you can just delete all the already copied folders and files in the destination ans start over the copy. But with an interrupted move operation, it's hard to know what has already been moved and what happens when you try to move again the remaining items. Another thing, can't this also be extended to inhibit the suspend for the archive / unarchive operations too?
John, that's just the terminology. If you look at the commit: https://invent.kde.org/frameworks/kio/-/commit/60191c0473a96c41279519845030efa12fdd0bb4#a255943687657ca8eb60300f623327855b34bd67_739_752 it covers also move transfers.
(In reply to postix from comment #11) > it covers also move transfers. As someone who can't necessarily parse CPP well, does it also include (un)archival, like John mentions? > can't this also be extended to inhibit the suspend for the archive / unarchive operations too? I ask because I've NVMe drives, so intra and inter-drive transferral never takes much time, but my CPU can't unarchive > 3 GiB Tape Archive files particularly quickly. That's when I'd use this.
> As someone who can't necessarily parse CPP well, does it also include (un)archival, like John mentions? Please see https://blog.broulik.de/2025/05/kio-goodies/#comment-214149 > Unfortunately it does not. The infrastructure (and corresponding job API) is private to KIO right now. > That’s a good point, though, and might justify making this feature available to all of KJob.