Filelight pie chart invisible on Fedora KDE 42 with nVidia drivers

This issue is already tracked as a KDE bug, but mentioning it here in case anyone finds this and it can shorten their bug-hunting journey.

In Fedora KDE 42, Filelight won’t show pie charts when using nVidia drivers. (The app is functional, it still calculates and shows the directory usage textually, it just doesn’t render the pie chart.)

This issue is only seen with Qt 6.9, so you won’t find it in earlier Fedora releases. For example, Fedora 41 has Qt 6.8, so you won’t see the bug there.

KDE bug tracker link: https://bugs.kde.org/show_bug.cgi?id=502709

nVidia forum link (issue raised by KDE developers): KDE App Filelight broken in Wayland + Qt 6.9 or newer - Linux - NVIDIA Developer Forums

Update:
A fix has been made in Qt and is pending release.

Qt bug tracker link (raised by Nvidia developers): https://bugreports.qt.io/browse/QTBUG-138986

1 Like

Nice.

Is there a fix for this? Like using software rendering for updating a chart which changes at, like, 0fps until it’s interracted with (changing once per interaction)?

A CPU can run Half Life 1 and Ion Fury and Wrath, so why not have this fallback?[1]


  1. I know YOU are not a dev and can not implement this things directly, I am just voicing out loud my opinion in the right context. ↩︎

1 Like

Great idea, thanks!

I hadn’t thought of trying that, but it works. We can force software rendering by setting the environment variable QT_QUICK_BACKEND to software.

So from a terminal, this works and gives a fully functioning Filelight with pie charts:

QT_QUICK_BACKEND=software filelight

You could also change the .desktop file via the KDE Plasma application editor: right-click on the Filelight app in the start menu and do this:

Then when you launch Filelight from the Plasma GUI it will use software rendering for the pie charts.

(And then I guess revert the change once the bug has been fixed).

2 Likes

Btw, funnily enough because of the wording of the PSA, would you select your own message as “the Solution”?

I believe this more or less bandaids the problem.

1 Like

Oh yeah, I don’t disagree.

But I’m a tinkerer and yet I hadn’t thought to do this particular tinker, so thanks for the prompt :grinning_face:

Right, and for just this reason, I didn’t actually make that change to my own .desktop file. But it’s an alternative to running from the terminal for anyone who prefers that.

1 Like

I have just now tried out this thing on the GT 1030 PC.

I want to remind any reader that I have a “normal release” version of Fedora KDE.


The Konsole command works and gives this output:

~$ QT_QUICK_BACKEND=software 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
qrc:/ui/SettingsPage.qml:12:1: QML SettingsPage: Created graphical object was not placed in the graphics scene.
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
kf.kirigami.layouts: Could not create delegate for ToolBarLayout
kf.kirigami.layouts: file:///usr/lib64/qt6/qml/org/kde/kirigami/ActionToolBar.qml: Object or context destroyed during incubation
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.
qrc:/ui/SettingsPage.qml:12:1: QML SettingsPage: Created graphical object was not placed in the graphics scene.
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.
qrc:/ui/SettingsPage.qml:12:1: QML SettingsPage: Created graphical object was not placed in the graphics scene.

It renders the pie slices.
The obvious negative is that it starts out from “beyond root”, at the selector screen.


Changing the other thing, instead, has mixed results.

If I right_click a folder and select FileLight the pie slices are invisible,
but if I instead right_click, go to properties, and then select FileLight, then they actually render.


It’s not unusable, but it’s also not ideal.

1 Like

That’s weird! For me both of those methods do the same thing. (They show the pie if the environment variable is set for the application, and don’t show the pie if it isn’t.)

True. If you prefer, you can make it start up in the root directory by doing: QT_QUICK_BACKEND=software filelight /. Or in your home directory with: QT_QUICK_BACKEND=software filelight ~ … et cetera.

Indeed!

Unfortunately, Qt 6.9.2 was supposed to fix this, but as far as I can see, the fix isn’t in Fedora’s qt6-qtbase-6.9.2. I’ll try to dig a bit more to see why.

Edit: my bad, the Qt fix is expected in 6.9.3 according to their ticket upstream.

1 Like

I have high functioning autism and Alexithymia and found your post offensive.

Don’t expect any empathy or sympathy from me as I have none.

@isaac0clarke I am very sorry that you feel that way, but keep in mind that we have a Code of Conduct that counts for everyone. We try to be as open to all ways expressing and perceptions as far as possible and leave what is possible, but as you see, your posts can feel offensive to others, and when there are different people’s interests we have to align, we stick radically with the CoC: keep in mind that people read your posts without knowing of your context, this means people consider the type of posts you were writing with a high likelihood as making fun of a group of people in a negative way. And additionally, it is again highly off-topic.

Since I already read an earlier post of you, in which you elaborated your condition, I did not radically enforce the CoC here with a warning and suspension, but with setting the system to send you the messages to adjust so that you get incentives about the rules, and learn about the boundaries in this forums, which starts with being on-topic and avoiding off-topic stuff: this topic is an ask-topic.

Your recent posts, including an offense against another user with terms like “disgustingly”, and the repeated off-topic posts already justify further measures, but as indicated, we try to be as open as possible to any type of expression, and since I expect that your posts have not really hostile intentions even if they often read that way, I try to exploit the rules in your favor as far as possible, and that is the mentioned incentives about our rules and allowing you to adjust the posts rather than just deleting them or warning and suspending you. I really do not like to do that.

But no one here is the prince of the world, and that also includes you. We cannot tailor the whole community towards you. Please understand that we have to align here a lof of interests, and we have to use constants to align everything and everyone, and that is our CoC.

Because you already elaborated your condition, I leave this once more without a warning or so. But please understand that we cannot ignore when a user is persistently posting offtopic posts that are not related to the topic and that often can be read in very hostile ways (which makes it more likely that you get hostile responses, which is also what we want to avoid, as this almost always ends up in vicious circles) nor that one user quickly starts to attack others. We simply are not allowed to ignore that, as we are obligated to enforce the CoC. So if you again attack someone else, please understand that we have to follow the procedure and go ahead with a warning and then a suspension.

Also, if you want to raise a discussion about how to align interests, do it in the category where it belongs: Site Help & Feedback

This is and remains an ask topic