#1051326 systemsettings: A lot of icons are just black squares

Package:
systemsettings
Source:
systemsettings
Description:
System Settings interface
Submitter:
Jan Gerber
Date:
2023-09-08 10:15:02 UTC
Severity:
normal
#1051326#5
Date:
2023-09-06 09:00:48 UTC
From:
To:
Dear Maintainer,

opening systemsettings while running gnome-shell most of the interface
is just black squares. The Appearance tab is completly empty.
This also results in black squares in ohter Qt based applications like
kdenlive.


Opening systemsettings in a temrinal I get some errors that might be
relevant:

QSocketNotifier: Can only be used with threads started with QThread
kf.kirigami: Failed to find a Kirigami platform plugin
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width"
kf.kirigami: Failed to find a Kirigami platform plugin
QSGTextureAtlas: texture atlas allocation failed, code=501
QSGTextureAtlas: texture atlas allocation failed, code=501
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
org.kde.kf5.kwindowsystem.kwayland: This compositor does not support the Shadow interface
#1051326#10
Date:
2023-09-06 10:15:26 UTC
From:
To:
turns out the issue was libqt5quick5-gles everything looks correct after installing libqt5quick5
is there any way to avoid libqt5quick5-gles getting installed on desktops?
#1051326#15
Date:
2023-09-06 18:21:03 UTC
From:
To:
Hi!

El miércoles, 6 de septiembre de 2023 07:15:26 -03 j@mailb.org escribió:
The question is: did you manually install any *-gles package yourself? They shouldn't be automatically installed, but we had issues like that before. If you have any dpkg/apt logs, the better.

Thanks!!!!
#1051326#20
Date:
2023-09-08 10:11:22 UTC
From:
To:
It was not installed manually as far as i remember but sadly no logs left over from the time libqt5quick5-gles was pulled in, the system has been installed for a long time so this could go back years. If I encounter the issue on other installations will try to see if I can find any trace.