Bug 504857 - Filelight doesn't display diagram on NVIDIA GPU with automatic rendering backend
Summary: Filelight doesn't display diagram on NVIDIA GPU with automatic rendering backend
Status: RESOLVED DUPLICATE of bug 502709
Alias: None
Product: filelight
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.04.1
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-27 11:50 UTC by lolkek202k
Modified: 2025-05-29 23:04 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lolkek202k 2025-05-27 11:50:46 UTC
SUMMARY
Filelight fails to display diagram on systems with NVIDIA graphics cards when using automatic desktop rendering backend selection. The issue doesn't occur on AMD Radeon systems.

STEPS TO REPRODUCE
Install system with NVIDIA graphics card
Keep desktop rendering backend set to "Automatic" in system settings
Launch Filelight
Select any folder for analysis

OBSERVED RESULT
Disk usage diagram is not displayed in Filelight window. The interface loads but the visualization is missing.

EXPECTED RESULT
Should display circular diagram with disk space usage visualization, as it works on AMD Radeon or when forcing other renderers.

SOFTWARE/OS VERSIONS
Arch Linux, 6.14.7-arch2-1, KDE Plasma 6.3.5, Wayland
Qt 6.9.0
KDE Frameworks 6.14.0
Filelight Version: 25.04.1
GPU: NVIDIA RTX 3070 Ti (issue reproduces), driver 570.153.02
GPU: AMD Radeon RX 5700 XT (works correctly)

ADDITIONAL INFORMATION
Workarounds that solve the issue:

Launch with environment variable: QT_QUICK_BACKEND=software filelight
Change desktop rendering backend to Vulkan in system settings
Using AMD Radeon instead of NVIDIA (issue doesn't reproduce)

The problem is specific to NVIDIA GPUs and related to Qt Quick's automatic renderer selection. When forcing software renderer or Vulkan, everything works correctly.
Comment 1 Oliver Beard 2025-05-29 23:04:27 UTC

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