Bug 32509 - Dolphin reports incorrect partition size when including directory proc/.
Summary: Dolphin reports incorrect partition size when including directory proc/.
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-11 08:02 CET by Ben McMonagle
Modified: 2023-11-11 13:14 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Ben McMonagle 2023-11-11 08:02:06 CET
Description of problem: In an attempt to find out what was using the / partition space:

df /dev/sda7
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda7        24G   22G  772M  97% /

I stumble upon this .
Using dolphin, select:
bin/
boot/
dead.letter
dev/  
etc/  
initrd/
lib/   
lib64/
lost+found/
media/
mnt/
opt/

results in, when right mouse click, and selecting "properties" returns a real value.

in my case :
13.8 GiB (14,768,037,636)
4,926 files, 1,076 sub-folders.

adding just one extra directory:
proc/  

results in an unusual value:

128.0 TiB (140,752,239,833,922)
359,828 files, 15,700 sub-folders

SSD is a 520GB device.

system is up-to-date

Version-Release number of selected component (if applicable):
dolphin-23.04.1-1.1.mga9



How reproducible: on this hardware, always


Steps to Reproduce:
1.select 1st 11 directories excluding home and any special partition mountpoints
2.right click mouse and select properties.
3.
Comment 1 Ben McMonagle 2023-11-11 08:04:20 CET
step 3. add an extra directory and recheck "properties"
Comment 2 Ben McMonagle 2023-11-11 08:11:41 CET
it appears that just selecting proc/ reports the incorrect value.
Ben McMonagle 2023-11-11 08:13:08 CET

Summary: Dolphin reports incorrect partition size. => Dolphin reports incorrect partition size when including directory proc/.

Comment 3 Morgan Leijström 2023-11-11 13:14:08 CET
I believe this is fully upstream caused.
Have you checked upstream bugzilla?
Assigning KDE team anyway.

Assignee: bugsquad => kde
CC: (none) => fri


Note You need to log in before you can comment on or make changes to this bug.