SUMMARY Text-only sensor widgets are empty after booting into the 6.5 beta. Toggling between another display mode and text-only brings it back again until a relog. Other appearance variants do not seem to trigger this behavior on relog, for instance the network usage one (graph with text) or the color grid. STEPS TO REPRODUCE 1. Set up a text-only sensor widget with some sensor entries (like GPU VRAM or RAM usage) 2. Log out 3. Log back in OBSERVED RESULT The contents of the widget are gone while the title remains EXPECTED RESULT The contents of the widget remain visible SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.4.90 KDE Frameworks Version: 6.18.0 Qt Version: 6.10.0 Kernel Version: 6.16.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × AMD Ryzen AI 9 365 w/ Radeon 880M Memory: 32 GiB of RAM (27.2 GiB usable) Graphics Processor: AMD Radeon 880M Graphics
On my system all text-only sensors disappeared from System Monitor widgets placed on desktop after installing Plasma 6.5 beta and then rebooting. Operating System: Arch Linux KDE Plasma Version: 6.4.90 KDE Frameworks Version: 6.18.0 Qt Version: 6.10.0 Graphics Platform: Wayland
I can't immediately reproduce this on my KDE Linux system which is running git master.
Created attachment 185133 [details] Empty text only plasmoid
Adding a me too here Notice Arch uses Qt 6.10 beta as well on the kde beta/unstable branch, so maybe Qt related?
I can't reproduce this either Operating System: Fedora Linux 42 KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600 However we have a somewhat related bug report when it comes to system monitors losing information, maybe it may help with this case as well: https://bugs.kde.org/show_bug.cgi?id=508184
this one as well appears fixed after https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5842
Still an issue on beta 2
I haven't gotten the time to test beta 2 yet, but that is not a good sign :(
I can't repro this anymore Operating System: Fedora Linux 42 KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.16.9-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600
I guess it really might be Qt 6.10's fault. Is it possible for you to try it on 6.10?
built kde from source using master + qt 6.9, all good building with 6.10rc1 = failure
Hmm, then I guess we should report this to Qt. What would be the best place to do so?
This should do: https://bugreports.qt.io/
Done: https://bugreports.qt.io/browse/QTBUG-140864
We need someone to provide more details in the Qt task. It's currently assigned to QtCore (I'm the maintainer) and it's highly unlikely to be a QtCore issue. I don't even know if the portion in question is QML or not. A small reproducer would be helpful. Otherwise, this is going to go unresolved.
*** Bug 510680 has been marked as a duplicate of this bug. ***
Does the issue manifest itself only after an upgrade or for example is also triggered between boots when using Qt 6.10 ?
The problem also occurs between boots when using Qt 6.10.
*** Bug 510687 has been marked as a duplicate of this bug. ***
Would be nice if some KDE dev could provide more info on that Qt bug or come up with a workaround (at least for kde 6.5 approaching) Qt people needs a reproducer apparently... Even though this is marked as Resolved it is not Bug was only reported upstream....
That's why I am asking. And I think because it was marked resolved by the reporter fell through the cracks.
(In reply to David Redondo from comment #17) > Does the issue manifest itself only after an upgrade or for example is also > triggered between boots when using Qt 6.10 ? It does appear between boots if the widget is placed on desktop or panel. In fact, merely restarting plasmashell will make it happen. If the widget is created in the System Monitor app, restarting the app also makes the issue occur.
Adding here that I can reproduce on latest kde linux - updated it 5min before writing. Create "System Monitor Sensor" widget. Set the "Display Style" to "Text Only". (Apply) (plasmashell crash as Im literally typing this) Add a sensor to "Sensors"; for example CPUs > All > Total Usage. (Apply) (OK) Nothing shows up.
It is not fixed in plasma 6.5. Qt bug still there.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/libksysguard/-/merge_requests/447
Git commit f1e41f7e384f945de5947473341d68b545b0c26a by Arjen Hiemstra. Committed on 27/10/2025 at 11:36. Pushed by ahiemstra into branch 'master'. faces/text: Use proper type for lists of sensors This allows the QML engine to properly detect changes and trigger any bindings depending on them. It effectively works around QTBUG-140864 by making the code cleaner. M +2 -6 faces/facepackages/textonly/contents/ui/GroupedText.qml https://invent.kde.org/plasma/libksysguard/-/commit/f1e41f7e384f945de5947473341d68b545b0c26a
Git commit 60841538cc2e03a5b8f9ab3a29e3626d1f037553 by Arjen Hiemstra. Committed on 27/10/2025 at 14:34. Pushed by ahiemstra into branch 'Plasma/6.5'. faces/text: Use proper type for lists of sensors This allows the QML engine to properly detect changes and trigger any bindings depending on them. It effectively works around QTBUG-140864 by making the code cleaner. (cherry picked from commit f1e41f7e384f945de5947473341d68b545b0c26a) Co-authored-by: Arjen Hiemstra <ahiemstra@heimr.nl> M +2 -6 faces/facepackages/textonly/contents/ui/GroupedText.qml https://invent.kde.org/plasma/libksysguard/-/commit/60841538cc2e03a5b8f9ab3a29e3626d1f037553
for me, issue went away after 6.5.1 update