System Information:
OS: Solus 4.8
Desktop: KDE Plasma (Wayland)
Application: Plasma Discover
Description:
Plasma Discover consistently crashes on startup with a segmentation fault. The crash happens immediately after launch, before the UI fully renders.
Error Output:
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
adding empty sources model QStandardItemModel(...)
qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:119:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15.
render glyph failed err=62 face=0x..., glyph=54
Segmentation fault (core dumped)
Launch Plasma Discover: plasma-discover
Application crashes immediately.
Troubleshooting Performed. Reinstalled Discover and PackageKit stack. Cleared user and system caches. Tested different Qt rendering backends:
QT_QUICK_BACKEND=software plasma-discover
QT_QPA_PLATFORM=wayland plasma-discover
QT_QPA_PLATFORM=xcb plasma-discover
QT_OPENGL=software plasma-discover
Reset font configuration and caches. Reinstalled font packages: noto, dejavu and liberation. Verified font selection using FC_DEBUG: FC_DEBUG=1 plasma-discover
→ System selects Noto Sans (/usr/share/fonts/.../NotoSans-Regular.ttf)
Removed and reinstalled Noto fonts manually. Reinstalled full rendering stack: freetype2, fontconfig, harfbuzz, qt6-base, qt6-declarative and qt6-wayland
Observed Behavior: Crash is consistent across all attempts. Happens regardless of rendering backend (Wayland, XCB, software). Not related to PackageKit or Discover configuration. Occurs during font rendering stage
Expected Behavior: Plasma Discover should launch normally and display its UI. The error "render glyph failed err=62" strongly suggests a failure in the font rendering pipeline? Most likely causes: Incompatibility between Qt and FreeType, Issue in font shaping/rendering stack (possibly involving HarfBuzz) or Broken or incompatible build of Qt6 or FreeType in Solus 4.8
Since the issue persists after: (1) full font reset, (2) cache rebuild, (3) full stack reinstall. This appears to be a system-level bug, not user configuration.
Additional Notes: Issue occurs even with clean font cache and default fonts. Not limited to a specific font file after reinstall. Likely affects other Qt6 applications (not fully tested)
