Bug 502709

Hi - for what it's worth, I can't reproduce on my Fedora KDE 41 device that's still on Qt 6.8.2 (but has Frameworks 6.13.0), so you might be on to something about Qt 6.9!

Just to double-check, does that issue occur on a freshly-created user account with no customizations?

(In reply to John Kizer from comment #1)
> Hi - for what it's worth, I can't reproduce on my Fedora KDE 41 device
> that's still on Qt 6.8.2 (but has Frameworks 6.13.0), so you might be on to
> something about Qt 6.9!
> 
> Just to double-check, does that issue occur on a freshly-created user
> account with no customizations?

I created a new user account, and tested it there: yes, the same thing occurs. I'm not sure how to add an attachment for that now, but I took a screenshot. By default, though, it used the EndeavourOS theme of Breeze, which seems to just change the accent colour to purple, and use some custom wallpapers. I tested it in both light and dark themes, but the graph did not show.

Created attachment 180278 [details]
Filelight doesn't show the graph, but it shows some info when hovering over it with the mouse

Hello,

I'm experiencing the same issue. The steps to reproduce the issue are the same:
1. Open Filelight.
2. Select one of the three options.
3. Wait for the scan to complete.

In my case, I always use the Breeze theme, as seen on the screenshot. I tried to change between Breeze and Breeze dark, but it stays the same on both themes.

My system details:
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4070 Ti SUPER

Best regards!

I can reproduce as well on my NVIDIA system.

Logs output the following:

qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object was not placed in the graphics scene.

Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2

filelight 24.12.3-1
nvidia-dkms 570.133.07-1

Note: My AMD system with the exact same KDE, KDE Frameworks, QT and Filelight versions can render the graph without any issues.

(In reply to Andrew Moore from comment #4)
> qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object
> was not placed in the graphics scene.

I've seen this same message appear multiple times, not just for filelight. I'd taken to ignoring it, after it happened with a Kirigami app I was building, where everything was still displaying.

(In reply to Andrew Moore from comment #4)
> Note: My AMD system with the exact same KDE, KDE Frameworks, QT and
> Filelight versions can render the graph without any issues. 

That's very frustrating to hear. I hate when the problem seems to be related to the GPU, because then it's way harder to track down. And I was so relieved to get Krunner working again properly now with the update to Qt 6.9, where previously it was having issues on NVIDIA GPUs. Either way, this makes it seem like it might be an upstream issue?

I also have this bug. 

I don't know if this is helpful but when I run it from konsole, I get this:

qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object was not placed in the graphics scene.



Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-3-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9700X 8-Core Processor
Memory: 123.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4070 Ti SUPER

(In reply to Darryl from comment #6)
> I also have this bug. 
> 
> I don't know if this is helpful but when I run it from konsole, I get this:
> 
> qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object
> was not placed in the graphics scene.
> 
> 
> 
> Operating System: Manjaro Linux 
> KDE Plasma Version: 6.3.4
> KDE Frameworks Version: 6.12.0
> Qt Version: 6.9.0
> Kernel Version: 6.14.2-3-MANJARO (64-bit)
> Graphics Platform: Wayland
> Processors: 16 × AMD Ryzen 7 9700X 8-Core Processor
> Memory: 123.5 GiB of RAM
> Graphics Processor: NVIDIA GeForce RTX 4070 Ti SUPER

Updating the nvidia driver to 570.144 fixes the issue for me. 
I do use the nvidia-open driver but I assume the regular proprietary driver would also work.

(In reply to Darryl from comment #7)
> (In reply to Darryl from comment #6)
> > I also have this bug. 
> > 
> > I don't know if this is helpful but when I run it from konsole, I get this:
> > 
> > qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object
> > was not placed in the graphics scene.
> > 
> > 
> > 
> > Operating System: Manjaro Linux 
> > KDE Plasma Version: 6.3.4
> > KDE Frameworks Version: 6.12.0
> > Qt Version: 6.9.0
> > Kernel Version: 6.14.2-3-MANJARO (64-bit)
> > Graphics Platform: Wayland
> > Processors: 16 × AMD Ryzen 7 9700X 8-Core Processor
> > Memory: 123.5 GiB of RAM
> > Graphics Processor: NVIDIA GeForce RTX 4070 Ti SUPER
>

I can reproduce as well on my NVIDIA system too.

Filelight 25.04.0

The scan completes and states the sizes in the list on the left, but the graph itself is not shown.

Logs output the following:
qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object was not placed in the graphics scene.


OS: Arch Linux x86_64
Kernel: Linux 6.14.2-arch1-1
Display (LG HDR QHD): 2560x1440 @ 75 Hz (as 2332x1311) in 32" [External]
DE: KDE Plasma 6.3.4
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3/4]
CPU: AMD Ryzen 9 3900X (24) @ 4.67 GHz
GPU: NVIDIA GeForce RTX 4080 SUPER [Discrete]
NVIDIA Driver version: 570.133.07

I can reproduce with NVIDIA graphics driver 570.144, Qt 6.9 and Filelight 25.04.0 on Fedora KDE 42. 

For what it's worth, I don't *think* that the "Created graphical object was not placed in the graphics scene" log messages are related: https://bugs.kde.org/show_bug.cgi?id=501674

The fact that:
* The chart shows up as normal with the Flatpak, using Qt 6.8
* The chart shows up as normal when run with QT_QPA_PLATFORM=xcb
* The chart shows up as normal on my wife's AMD-only laptop

Would lead me to guess that this is a Qt 6.9 + NVIDIA + Wayland upstream issue...but I don't know how to diagnose where that is, or if there's something that needs adapted in the Filelight code.

*** Bug 503071 has been marked as a duplicate of this bug. ***

(In reply to Andrew Moore from comment #4)
> I can reproduce as well on my NVIDIA system.
> 
> Logs output the following:
> 
> qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object
> was not placed in the graphics scene.
> 
> Operating System: Arch Linux 
> KDE Plasma Version: 6.3.4
> KDE Frameworks Version: 6.12.0
> Qt Version: 6.9.0
> Kernel Version: 6.14.2-zen1-1-zen (64-bit)
> Graphics Platform: Wayland
> Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
> 
> filelight 24.12.3-1
> nvidia-dkms 570.133.07-1
> 
> Note: My AMD system with the exact same KDE, KDE Frameworks, QT and
> Filelight versions can render the graph without any issues.

Can still reproduce on:

KDE Frameworks 6.13.0
nvidia-dkms 570.144-1
filelight 25.04.0-1

*** Bug 503269 has been marked as a duplicate of this bug. ***

*** Bug 503389 has been marked as a duplicate of this bug. ***

I confirm this bug too, KDE team when you will fix this, I use filelight almost daily in order to monitor my system's tidyness...

Operating System: EndeavourOS 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti
Manufacturer: MSI
Product Name: MS-7972
System Version: 2.0

Another confirmation of the bug:

Package versions:
- filelight 25.04.0-1
- nvidia-open 570.144-4

Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660

(In reply to honkanen.ap from comment #16)
> Another confirmation of the bug:
> 
> Package versions:
> - filelight 25.04.0-1
> - nvidia-open 570.144-4
> 
> Operating System: Arch Linux 
> KDE Plasma Version: 6.3.5
> KDE Frameworks Version: 6.13.0
> Qt Version: 6.9.0
> Kernel Version: 6.14.5-arch1-1 (64-bit)
> Graphics Platform: Wayland
> Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
> Memory: 31.3 GiB of RAM
> Graphics Processor: NVIDIA GeForce GTX 1660

An additional observation: 

The problem dissappears when running Plasma in X11. The error message "qrc:/ui/OverviewPage.qml:11:1: QML OverviewPage: Created graphical object was not placed in the graphics scene." still persists though.

Bug exists only when plasma renderer set to auto or opengl, in vulkan pie is visible. But kdenlive crashes in vulkan...

Package versions:
- filelight 25.04.1-1
- nvidia-open 570.144-4

Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i7-10700K CPU @ 3.80GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti

(In reply to Egor Tkachev from comment #18)
> Bug exists only when plasma renderer set to auto or opengl, in vulkan pie is
> visible. But kdenlive crashes in vulkan...

It's a pity, kdenlive is really needed. The best program for editing. Can you tell me how you turn on vulkan?

Created attachment 181280 [details]
pie shows up when plasma renderer set to vulkan

(In reply to Konstantin from comment #19)
> (In reply to Egor Tkachev from comment #18)
> > Bug exists only when plasma renderer set to auto or opengl, in vulkan pie is
> > visible. But kdenlive crashes in vulkan...
> 
> It's a pity, kdenlive is really needed. The best program for editing. Can
> you tell me how you turn on vulkan?

type "plasma renderer" in start menu (i don't know if this is right on english) or add/edit the
[QtQuickRendererSettings]
SceneGraphBackend=vulkan
in ~/.config/kdeglobals

> type "plasma renderer" in start menu (i don't know if this is right on
> english) or add/edit the
> [QtQuickRendererSettings]
> SceneGraphBackend=vulkan
> in ~/.config/kdeglobals

Can you tell me how it will be in Russian? I did not find this command in the application menu. Maybe you need to install something for this? And can you tell me how you learned this command? I want to read the documentation.

Thank you for the tip that this was specific to nvidia/Wayland. I help support a qtwebengine app which has seen issues with this lately (Qt 6.9 and nvidia have not been fully working yet) so it's suddenly very familiar.

Be advised that the nvidia vulkan drivers (all of them currently available) have a bug regarding excessive CPU utilisation, so you probably don't want to set your system up to use it globally.

Since this is Wayland-specific, we can work around this with an environment variable, and run it in XWayland until it's fixed:

QT_QPA_PLATFORM=xcb filelight

(In reply to Konstantin from comment #22)
> > type "plasma renderer" in start menu (i don't know if this is right on
> > english) or add/edit the
> > [QtQuickRendererSettings]
> > SceneGraphBackend=vulkan
> > in ~/.config/kdeglobals
> 
> Can you tell me how it will be in Russian? I did not find this command in
> the application menu. Maybe you need to install something for this? And can
> you tell me how you learned this command? I want to read the documentation.

Отрисовка рабочего стола или что-то похожее, не у компьютера сейчас

(In reply to pallaswept from comment #23)
> Thank you for the tip that this was specific to nvidia/Wayland. I help
> support a qtwebengine app which has seen issues with this lately (Qt 6.9 and
> nvidia have not been fully working yet) so it's suddenly very familiar.
> 
> Be advised that the nvidia vulkan drivers (all of them currently available)
> have a bug regarding excessive CPU utilisation, so you probably don't want
> to set your system up to use it globally.
> 
> Since this is Wayland-specific, we can work around this with an environment
> variable, and run it in XWayland until it's fixed:
> 
> QT_QPA_PLATFORM=xcb filelight

could you please advise a noob like me how to do that ? I tried 'set QT_QPA_PLATFORM=xcb filelight' and got an error message :(

setting the plasma renderer backend to 'Vulkan' also didn't stick (though I pressed the 'OK' button after...)

(In reply to Kobi Hersh from comment #25)
> (In reply to pallaswept from comment #23)
> > Thank you for the tip that this was specific to nvidia/Wayland. I help
> > support a qtwebengine app which has seen issues with this lately (Qt 6.9 and
> > nvidia have not been fully working yet) so it's suddenly very familiar.
> > 
> > Be advised that the nvidia vulkan drivers (all of them currently available)
> > have a bug regarding excessive CPU utilisation, so you probably don't want
> > to set your system up to use it globally.
> > 
> > Since this is Wayland-specific, we can work around this with an environment
> > variable, and run it in XWayland until it's fixed:
> > 
> > QT_QPA_PLATFORM=xcb filelight
> 
> could you please advise a noob like me how to do that ? I tried 'set
> QT_QPA_PLATFORM=xcb filelight' and got an error message :(
> 
> setting the plasma renderer backend to 'Vulkan' also didn't stick (though I
> pressed the 'OK' button after...)

You can use KDE Menu Editor, search for Filelight, click on it, then on the right hand side in the General tab there is an option "Environment Variables:" enter the following: QT_QPA_PLATFORM=xcb

Then save.

*** Bug 504857 has been marked as a duplicate of this bug. ***

I would caution against changing the QtQuick renderer to Vulkan to resolve this, it's likely you might hit problems later on that are strange and non-obvious, having forgotten entirely that you changed the setting. It's why we've hidden it.

Starting filelight from the terminal with:

QT_QPA_PLATFORM=xcb filelight

would be the best workaround.

If you want to use native wayland filelight you can also use zink to work around the issue.

__GLX_VENDOR_LIBRARY_NAME=mesa __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink filelight

https://wiki.archlinux.org/title/OpenGL#OpenGL_over_Vulkan_(Zink)

Instead of workarounds, I'd suggest just fixing the bug instead. Don't get me wrong, but I keep seeing users coming up with worse and worse ideas for short term duct-taping, which gonna cause more problems in the long run. Better just hotfix the issue to prevent users sharing any further and terrible brainstorming in this ticket..

(In reply to Örs V from comment #30)
> Instead of workarounds, I'd suggest just fixing the bug instead. Don't get
> me wrong, but I keep seeing users coming up with worse and worse ideas for
> short term duct-taping, which gonna cause more problems in the long run.
> Better just hotfix the issue to prevent users sharing any further and
> terrible brainstorming in this ticket..

Obviously, the intention is a long-term actual fix. 'Short term duct taping'/workarounds are not for the long run, it's just a temporary thing so that the software works while we wait for a fix from upstream, who are aware of these issues and already working on 'just fixing the bug instead'.

BTW, I mentioned the performance issues with vulkan above, which is why I didn't suggest the zink workaround earlier, and instead suggested xwayland. Of course, some users may not have X11 support at all, so the zink workaround would be required for them.

Thanks, Colin & Oliver Beard both your workarounds (comment #28 and comment #29) work for me aswell.

I wonder how many developers in the FOSS world have Nvidia hardware though AND are willing to fix Nvidia only bugs for free... a constellation of two exceedingly rare events ;)

However a bugfix would be appreciated since Filelight is a pretty prominently featured application in KDE (comes up in Context menu on any Folder by default. Plus I know and like using this app since day 1 and I bet a lot of other folks are aswell.

As a data point filelight draws the graph properly on my nVidia system
nvidia proprietary driver 570.153.02
Qt 6.8.3
Wayland

(In reply to TraceyC from comment #33)
> As a data point filelight draws the graph properly on my nVidia system
> nvidia proprietary driver 570.153.02
> Qt 6.8.3
> Wayland

Yeah, it's a specific issue with 6.9 on Wayland, with NVIDIA. Has to be all three of those, if using AMD, it's fine. If using X11, it's fine. It using old versions of Qt, it's fine.

yes, thank you @Darryl - I've implemented your explanation and it's working great now

Confirmed on Nvidia beta drivers 575.57.08 + Qt 6.9.1

Created a bug report at Nvidia forums since it's likely a problem in the Nvidia drivers: https://forums.developer.nvidia.com/t/kde-app-filelight-broken-in-wayland-qt-6-9-or-newer/335357

*** Bug 505646 has been marked as a duplicate of this bug. ***

this is obviously Nvidia generation related. On my GTX 1050 Ti (Pascal series), the rendering is broken. However on my older Quadro K620 (Kepler series) the rendering works right out of the box, so this bug only affects newer series.. Hope this info is helpful, and helps the devs to fix this issue, cause for example this issue also affects rendering within Plasma's Settings, for example the notification there are little dots, and behind it there should be a sample monitor graphic rendered, that is also not rendered on my pascal serie nvidia, but is rendered on the kepler serie.

I can reproduce this (including fixing it by setting the renderer to vulkan) on bazzite 42, KDE 6.4.0, frameworks 6.15.0, QT 6.9.1 running on an nvidia GTX 1660

*** Bug 506666 has been marked as a duplicate of this bug. ***

*** Bug 507045 has been marked as a duplicate of this bug. ***

An NVIDIA employee wrote in the linked thread that an internal bug report has been created - (5413500)

https://forums.developer.nvidia.com/t/kde-app-filelight-broken-in-wayland-qt-6-9-or-newer/335357/3

*** Bug 507586 has been marked as a duplicate of this bug. ***

The problem is mainly caused by Filelight trying to use 32x MSAA. Not every hardware supports 32x MSAA. 2, 4 and 8 are the most common numbers.

There are two ways to handle this bug. Either Qt can clamp the requested sample count to the maximum number that the hardware supports (https://bugreports.qt.io/browse/QTBUG-138986) or the requested sample count can be reduced in Filelight (src/qml/MapPage.qml, layer.samples property of the item with "shapeItem" id). 2, 4 or 8 should work.

(In reply to Doğukan Korkmaztürk from comment #44)
> The problem is mainly caused by Filelight trying to use 32x MSAA. Not every
> hardware supports 32x MSAA. 2, 4 and 8 are the most common numbers.
> 
> There are two ways to handle this bug. Either Qt can clamp the requested
> sample count to the maximum number that the hardware supports
> (https://bugreports.qt.io/browse/QTBUG-138986) or the requested sample count
> can be reduced in Filelight (src/qml/MapPage.qml, layer.samples property of
> the item with "shapeItem" id). 2, 4 or 8 should work.

I am confused...
 if a fix is as simple as making a change on a single file. Why this has not been applied in the past 5 months as a permanent fix or applied as a workaround?

(In reply to CesarinPillin from comment #45)
> I am confused...
>  if a fix is as simple as making a change on a single file. Why this has not been applied in the past 5 months as a permanent fix or applied as a workaround?

Apparently, because the poster directly above you was the first person to figure it out, so the fix has been known for 2 weeks not 5 months, and the fix is not so simple, the fix was to escalate this to Qt, which the above legend did 2 weeks ago, and the fix has already been merged into Qt, so you will have it soon.

Thank you Doğukan Korkmaztürk!

*** Bug 508234 has been marked as a duplicate of this bug. ***

is it normal that on my end it's still bugged??
Or am I missing the point here? It says its fixed upstream, on Nvidia forum, someone had it working screenshot on 6.4.5 plasma, 5.8.0 driver. I have same versions and 580 Nvidia driver on my end too, and yet for me it's still bugged? Either the screenshot taker did the tricks before, and forgot it's there and falsely reported it as resolved?! Reopening this now.

Operating System: Kubuntu 25.10
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-5-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 1050 Ti
Manufacturer: MSI
Product Name: MS-7972
System Version: 2.0

Created attachment 186224 [details]
still bugged as of 2025.10.27

added screenshot with versions for proof

(In reply to Sylens from comment #49)
> still bugged as of 2025.10.27

It is fixed in Qt 6.9.3, you're on an older version.

yepp, noticed, I just switched to Kubuntu's backport where all the Qt stuffs are more recent, and the issue is truly resolved. Would be nice if the 'versionfixedin' field is filled out to letting know people of which version this fixed is from, to prevent confusion such as it was in my case :P

> It is fixed in Qt 6.9.3, you're on an older version.

Adding my 2cents here, even with Kubuntu's backport Qt is 6.9.2, yet the issue is fixed. What changed here is that now I'm on Plasma 6.5.0, with 6.19.0 Frameworks and Filelight 25.08.02. So either one of these changes made it fixed, but I think it mostly was the Frameworks.

There is a workaround (Don't try to use big AA settings) in Filelight, which is in 25.08.2
https://invent.kde.org/utilities/filelight/-/merge_requests/197

There is a fix (Don't try to use unsupported AA settings) in Qt, which is in Qt 6.9.3. This was linked at the end of this thread:
https://bugreports.qt.io/browse/QTBUG-138986

The versions they are fixed in, are listed on those pages.

This bug was marked resolved when the fix was committed upstream, but the upstream version where the resolution will be included, is not always known when the bug report is resolved, so in those cases, the 'version fixed in' field is unknown. But the link was there to get the answers, if we visited in the future, so that's OK. 

Every time we change a bug report like this, we are emailing lots of important people (see the top of your page):
 	34 users including you 

So it would be polite to leave this bug as it is. I put the correct versions in the place where you wanted them, I hope that will be sufficient.

In the future for stuff like this, it might be good to drop by a place like the KDE Discuss forums: https://discuss.kde.org/ or your distro's forums or chatroom or something. It is encouraged to ask about bugs in those places, if we're unsure, before we file or edit a bug report. You can ask other friendly users about your bug and some will know why it isn't working. I hope that helps, I might see you there :)