Bug 500160 - Icon size discrepancy between folders when "Show Previews" is enabled
Summary: Icon size discrepancy between folders when "Show Previews" is enabled
Status: RESOLVED DUPLICATE of bug 499509
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 24.12.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-16 03:41 UTC by deadinside777
Modified: 2025-02-21 01:03 UTC (History)
3 users (show)

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


Attachments
Image of issue (63.08 KB, image/png)
2025-02-16 03:41 UTC, deadinside777
Details

Note You need to log in before you can comment on or make changes to this bug.
Description deadinside777 2025-02-16 03:41:39 UTC
Created attachment 178419 [details]
Image of issue

SUMMARY


STEPS TO REPRODUCE
1. Open Dolphin
2. Enable "Show Previews"

OBSERVED RESULT
Content previews are shown correctly but icon sizes of some folders change to a smaller size.

EXPECTED RESULT
Show preview of folder content and increase icon size of all folders to uniform size.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 41 Plasma Spin
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
This happens inside my home folder and to a lesser extent inside /.  It does this for both hidden and normal folders/files.  Issue persists in all view modes (icon, compact, details) as long as previews are enabled.  No other folder or subfolder appears to have this issue.  Increasing icon sizes several steps "fixes" this, but then I end up with oversized icons.
Comment 1 Giuseppe Calà 2025-02-16 14:42:31 UTC
I confirm the bug with the following setup:
Dolphin: 24.12.2
KDE Frameworks: 6.10.0
Qt: Utilizza 6.8.2 e compilato con 6.8.1
Arch Linux (Wayland)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.12.13-1-lts
Comment 2 TraceyC 2025-02-21 01:03:18 UTC
Thanks for the bug report. This looks to be the same as bug 499509. Please follow that report for updates.

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