Konqueror: "16.777.216,0 TB complete" when copying from smb share

Bug #65728 reported by jcfp
4
Affects Status Importance Assigned to Milestone
KDE Base
Fix Released
Medium
kdebase (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: konqueror

Used konqueror filemanager to copy two directories, containing one large (dvd iso of 4,3 GB) and a small number of small files each, from a samba share on the local lan to my home dir (reiserfs; encrypted partition via dm_crypt/cryptsetup, for as far as that's relevant).

After some time (about 2 GB into the copying), the copy dialog switches from the normal, correct information displayed so far to "16.777.216,0 TB of 16.777.216,0 TB complete" [*1]; despite what it says, the transfer is far from complete at this time though so I just let it run.

Then, once it reached (about?) 4 GB it started counting from 0 again ("1 MB of 16.777.216,0 TB complete", 0% completed, with about half a century remaining...);
Next, after a few hundred MB into this new count (end of first 4,3GB file I suspect) it changes over to what seems to be the correct total of about 4,4 GB (Still with the total of 16.777.216,0 TB though). [*2]
Reaching about 6,0 GB at this newish total count, the total transferred was decreased by 4GB back to 2GB (Once again, total to be transferred stayed at 16.777.216,0 TB). [*3]

Transfer speed indication kept working normally through most of this (indicating correct speeds as verified via other monitoring apps), only showing strange values for a short time around the sudden changes as described above.
Obviously, the "time remaining" indication made no sense at all, not only quantitatively but also in the sense that even minor changes (<< 5%) in the transfer speed caused a large (> 50x) difference in remaining time estimate.

Files eventually were transferred correctly (!). But something is obviously wrong; most users would probably have aborted the transfer either assuming it was actually complete or thinking the resulting files would be br0ken anyway.

[*n] = Screenshots:
[1] http://www.spunge.org/~yamal/bug-img/konqbug_1.png
[2] http://www.spunge.org/~yamal/bug-img/konqbug_2.png
[3] http://www.spunge.org/~yamal/bug-img/konqbug_3.png

Kubuntu 6.06 all updates, KDE/Konqueror 3.5.2

Revision history for this message
jcfp (jcfp) wrote :

Bug still present in 6.10 / KDE 3.5.5

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Does this only happen with samba? Have you tried a local copy of these files or anything else?

Changed in kdebase:
status: Unconfirmed → Needs Info
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

According to the upstream bug this was fixed about a month ago, so the fix should appear in KDE 3.5.6

Changed in kdebase:
status: Needs Info → Fix Committed
Revision history for this message
jcfp (jcfp) wrote :

No such problem on local disk copy. Don't know if it happens on other types of network shares than smb since I don't have any available to test.

Changed in kdebase:
status: Unknown → Fix Released
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

KDE 3.5.6 was just released, packages for Edgy are available on kubuntu.org, can you confirm that this was fixed?

Revision history for this message
jcfp (jcfp) wrote :

Appears to be fixed in 3.5.6 indeed, could not reproduce the problem anymore in a quick check after installing the packages from kubuntu.org.

Changed in kdebase:
status: Fix Committed → Fix Released
Changed in kdebase:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.