Bug 161886

Summary:	Trash shows incorrect size of files
Product:	[Frameworks and Libraries] kio	Reporter:	Matej Repinc <mrepinc>
Component:	trash	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Trash wrong size info

Description Matej Repinc 2008-05-10 11:20:29 UTC

Version:            (using KDE 4.0.3)
Installed from:    Ubuntu Packages
OS:                Linux

When dragging the trash icon from Dolphin's Places to desktop (widgets unlocked) and right-clicking on trash icon on desktop and selecting properties and calculating size i get total size of 16,777,216.0 TiB in 0 files and folders.
Using KDE 4.0.3 (according to About Doplhin) and Kubuntu 8.04.

Comment 1 Matej Repinc 2008-05-19 00:48:35 UTC

Just compiled KDE from trunk today, I can confirm the bug still exists in trunk.
Recreate:
-Drag the Trash icon from Dolphin's places to desktop
-Right click on the icon and select properties
-Click on Calculate button in the first tab to calculate size
-I get the same result with trunk that i get with stable 4.0.3

Comment 2 Dario Andres 2008-08-05 15:58:06 UTC

Using KDE 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) (KDEmod) in ArchLinux i686:
I can confirm this bug.

Steps to reproduce:
- Empty your trashcan

- Open a Dolphin window and go to Trash:/
- Open the rightclick context-menu and select properties.
( Size is ""). 
- Click "Calculate"
And now Size is 16,777,216.0 TiB in 0 files and folders

Comment 3 Dario Andres 2008-08-05 16:04:24 UTC

Created attachment 26648 [details]
Trash wrong size info

This also happens in Konqueror (as it's a kio error)

Comment 4 Dario Andres 2008-08-19 17:09:53 UTC

I can also reproduce this bug with:
kdelibs4.2 svn rev.849324
kdebase4.2 svn rev.849337
ArchLinux 2.6.25-zen2-20080814 i686

Comment 5 Dario Andres 2008-11-30 00:04:46 UTC

This is a duplicate of bug 157023

Comment 6 Dario Andres 2008-12-04 23:57:15 UTC


*** This bug has been marked as a duplicate of bug 157023 ***