Bug 508234

Summary: Filelight fails to display usage graph
Product: [Applications] filelight Reporter: genosimple
Component: generalAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: basiqueevangelist, clintonthegeek, martin.sandsmark, nate, sitter
Priority: NOR    
Version First Reported In: 25.04.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description genosimple 2025-08-14 10:00:44 UTC
SUMMARY
Filelight opens and scans folders normally; but the usage graph on the right side isn't rendered at all.
Moving mouse over the invisible graph still opens up popups with directory locations and other data.

STEPS TO REPRODUCE
1. Open filelight, scan some folder
2. wait until the scan is complete

OBSERVED RESULT
There is no usage graph on the right side of the screen https://imgur.com/pk6isZq

EXPECTED RESULT
A space usage graph is rendered like shown in https://apps.kde.org/filelight/

SOFTWARE/OS VERSION:
Operating System: EndeavourOS 
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.15.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × 12th Gen Intel® Core™ i5-12400
Memory: 16 GiB of RAM (15.4 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060

ADDITIONAL INFORMATION
Tried installing from extra/filelight as well as with KDE's own Discover app, same result
Comment 1 genosimple 2025-08-14 10:07:08 UTC
Additional info: launching filelight from console produced following output:

> filelight

qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object was not placed in the graphics scene.
QObject::disconnect: wildcard call disconnects from destroyed signal of WindowThemer::unnamed
Inadequate access permissions:  "/home/pavel/.cache/yay/gridmonger-git/pkg/"
Inadequate access permissions:  "/home/pavel/.cache/yay/gridmonger-git/pkg/"
qrc:/qt/qml/org/kde/desktop/MenuItem.qml:84:13: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 16. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:987:9: QML QQuickItem*: StackView has detected conflicting anchors. Transitions may not execute properly.
Comment 2 Nate Graham 2025-08-14 14:14:24 UTC
Huh, works for me. Maybe an NVIDIA graphics glitch, since this is a hardware-accelerated graph. Do the graphs in System Monitor show up for you?
Comment 3 genosimple 2025-08-14 18:41:47 UTC
(In reply to Nate Graham from comment #2)
> Huh, works for me. Maybe an NVIDIA graphics glitch, since this is a
> hardware-accelerated graph. Do the graphs in System Monitor show up for you?

The tabs in the System Monitor look like this 
https://i.imgur.com/4QnSDBv
https://imgur.com/c1S2fYA

They seem to display just fine.
Comment 4 Nikolay Kochulin 2025-08-26 18:17:58 UTC
Can confirm under Arch Linux with NVIDIA proprietary drivers.
However, interestingly, forcing Vulkan via `QSG_RHI_BACKEND=vulkan` makes the usage graph show up again.
Comment 5 genosimple 2025-08-27 09:06:52 UTC
(In reply to Nikolay Kochulin from comment #4)
> Can confirm under Arch Linux with NVIDIA proprietary drivers.
> However, interestingly, forcing Vulkan via `QSG_RHI_BACKEND=vulkan` makes
> the usage graph show up again.

Can confirm that starting it with "QSG_RHI_BACKEND=vulkan filelight" indeed fixes the problem.

This seems to be either a flaw of NVidia's opengl implementation, or Qt/KDEs bug. I noticed that another program written in Qt(86box) freezes when I choose OpenGL renderer, but works fine with vulkan's backend.

Also Steam and games seem to work just fine under Proton, but maybe they all use Vulkan and not OpenGl.

Running glxinfo doesn't seem to show any anomalies, and glxgears test program performs absolutely fine as well. So this seems to be limited to Qt/KDE OpenGL implementation.
Comment 6 genosimple 2025-08-27 10:57:20 UTC
I added "export QSG_RHI_BACKEND=vulkan" to .config/plasma-workspace/env/opengl.sh for now. This works as a workaround, and also seemed to fix some other graphical artifacts I noticed in some other KDE apps.
Comment 7 Harald Sitter 2025-09-16 10:06:56 UTC

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