Bug 476516 - Crashes with "could not connect to display" and "no Qt platform plugin could be initialised"
Summary: Crashes with "could not connect to display" and "no Qt platform plugin could ...
Status: RESOLVED NOT A BUG
Alias: None
Product: XWaylandVideoBridge
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-03 17:00 UTC by nw1905
Modified: 2024-03-19 13:59 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nw1905 2023-11-03 17:00:08 UTC
STEPS TO REPRODUCE
1.  Install the flatpak version (https://invent.kde.org/system/xwaylandvideobridge/-/jobs/1290531) on GNOME 45
2. attempt to start from terminal emulator
3. 

OBSERVED RESULT
Crashes with this output:
```
qt.qpa.xcb: could not connect to display 
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, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
```

SOFTWARE/OS VERSIONS
Fedora Linux 39 with GNOME 45.0
Comment 1 David Edmundson 2024-03-04 09:50:20 UTC
This warning means it failed to connect to the X server. 

This is going to be a setup issue.  Does loading xterm or something work? Is the flatpak being restrictedto the X server (see flatseal)?
Comment 2 Bug Janitor Service 2024-03-19 03:46:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 nw1905 2024-03-19 13:53:06 UTC
By default the Flatpak appears to be limited to just the x11 socket, but I had already added those overrides to allow the wayland and fallback-x11 sockets too.

Xterm (and all other Xwayland apps I've tried) run fine under wayland it just seems to be XWaylandVideoBridge that keeps crashing with this error.
Comment 4 nw1905 2024-03-19 13:59:35 UTC
(In reply to nw1905 from comment #3)
> By default the Flatpak appears to be limited to just the x11 socket, but I
> had already added those overrides to allow the wayland and fallback-x11
> sockets too.
> 
> Xterm (and all other Xwayland apps I've tried) run fine under wayland it
> just seems to be XWaylandVideoBridge that keeps crashing with this error.

It appears precisely that was what was causing this crash.
Now however it is throwing "failed to create session" every time it is run.
I apologise for wasting your time.