Bug 404950 - Copy process notification stops at 4 GiB
Summary: Copy process notification stops at 4 GiB
Status: REPORTED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.55.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-01 16:10 UTC by Thomas
Modified: 2025-03-24 22:58 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
stopped progress bar (160.48 KB, image/png)
2019-03-01 16:10 UTC, Thomas
Details
attachment-11942-0.html (1.08 KB, text/html)
2019-03-02 13:30 UTC, Thomas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas 2019-03-01 16:10:50 UTC
Created attachment 118460 [details]
stopped progress bar

First: sorry I have no idea how the components work together and where this bug is coming from. Maybe you want to move the ticket to correct product / component for me.

When I copy a large file from a usb2 device (a smartphone) with dolphin and watch the copy process in notifications (using latte-dock) the notification stops at 4 GiB from 8.1 GiB and the speed rate drops to 0. The file still gets copied and you can see in a terminal and in dolphin that the file is still growing.

It seems that the file copy notification is using a 32 bit integer for the copied bytes.


STEPS TO REPRODUCE
1. copy a large file (over 4 GiB)
2. watch the notifications
3. wait till 4 GiB are finished

OBSERVED RESULT
the progressbar stops and the rate drops to 0

EXPECTED RESULT
the progressbar continues like the copy process is doing to

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: KDE neon 5.15
KDE Plasma Version: 5.15.2
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.0
Kernel Version: 4.15.0-45-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-7600U CPU @ 2.80GHz
Memory: 15,6 GiB
Comment 1 Patrick Silva 2019-03-02 00:50:02 UTC
what is the file system of the destination?
Comment 2 Thomas 2019-03-02 13:29:57 UTC
Created attachment 118479 [details]
attachment-11942-0.html

It is an ext4 fs and it is definitely not a problem because the whole file
gets copied.

Nate Graham <bugzilla_noreply@kde.org> schrieb am Sa., 2. März 2019, 14:09:

> https://bugs.kde.org/show_bug.cgi?id=404950
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |nate@kde.org
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Christoph Feck 2019-03-24 11:39:36 UTC
Could also be a KIO bug, please move if needed.
Comment 4 Kai Uwe Broulik 2019-05-23 16:54:55 UTC
Likely a bug in KIO CopyJob or even KJob as it sends us a percentage, we don't calculate in the notification plasmoid.
When I create a KJob setting 5 GiB of processed size, it works fine. KIO CopyJob is also using filesize_t (unsigned long long) so that shouldn't be an issue there either.