Bug 513472 - Missing libraries breaking X11 compatibility
Summary: Missing libraries breaking X11 compatibility
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Qt/KDE Flatpak Runtime
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-17 10:23 UTC by Julian Groß
Modified: 2025-12-21 12:43 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Groß 2025-12-17 10:23:56 UTC
SUMMARY

When using 
```yaml
runtime: org.kde.Platform
runtime-version: 6.10
sdk: org.kde.Sdk
```
Qt doesn't work on X11 anymore:
```
juliangro@x299-workstation ~> flatpak run com.github.Murmele.Gittyup
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-brcm, wayland-egl, wayland, xcb.

juliangro@x299-workstation ~ [SIGABRT]> 
```
https://github.com/flathub/com.github.Murmele.Gittyup/blob/master/com.github.Murmele.Gittyup.yml is affected by this.

STEPS TO REPRODUCE
1. Install a Qt application such as `com.github.Murmele.Gittyup` on an X11 system.
2. Run it via `flatpak run com.github.Murmele.Gittyup` to be able to see the error message.

OBSERVED RESULT
Application fails to launch due to missing KDE runtime library.

EXPECTED RESULT
KDE runtime library should contain the library mentioned in the error message and the application should start.
Comment 1 Nicolas Fella 2025-12-21 12:43:46 UTC
The xcb-cursor message is unrelated to the actual issue.

The issue seems specific to Gittyup, see https://github.com/Murmele/Gittyup/issues/912