Could not load the Qt platform plugin "xcb" in "" even though it was found.

[muffinjets]

[muffinjets@archlinux ~]$ flatpak run org.DolphinEmu.dolphin-emu
qt.qpa.xcb: could not connect to display 
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-egl, wayland, xcb.

/app/bin/dolphin-emu-wrapper: line 6:    13 Aborted                 (core dumped) dolphin-emu "$@"
[muffinjets@archlinux ~]$ flatpak update && sudo flatpak update
Looking for updates…

Nothing to do.
Looking for updates…

Nothing to do.
[muffinjets@archlinux ~]$ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
[muffinjets@archlinux ~]$ neofetch
                   -`                    muffinjets@archlinux 
                  .o+`                   -------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: 90H00006US ideacentre 720-18IKL 
               `+oooooo:                 Kernel: 6.8.4-arch1-1 
               -+oooooo+:                Uptime: 15 mins 
             `/:-:++oooo+:               Packages: 766 (pacman), 18 (flatpak) 
            `/++++/+++++++:              Shell: bash 5.2.26 
           `/++++++++++++++:             Resolution: 1920x1080 
          `/+++ooooooooooooo/`           DE: Hyprland 
         ./ooosssso++osssssso+`          Theme: Material-Black-Blueberry-BE [GTK2/3] 
        .oossssso-````/ossssss+`         Icons: Adwaita [GTK2/3] 
       -osssssso.      :ssssssso.        Terminal: kitty 
      :osssssss/        osssso+++.       CPU: Intel i7-7700 (8) @ 4.200GHz 
     /ossssssss/        +ssssooo/-       GPU: NVIDIA GeForce GTX 1050 Ti 
   `/ossssso+/:-        -:/+osssso+-     GPU: Intel HD Graphics 630 
  `+sso+:-`                 `.-/+oso:    Memory: 3480MiB / 11871MiB 
 `++:.                           `-/+/
 .`                                 `/                           

[muffinjets@archlinux ~]$ 

I did reinstall Dolphin, no clue what else I can be doing here, though I'll admit that I'm still a noob.

[cpba]

From here it looks like you don't have xwayland support and dolphin fails to start because it can't run on wayland without it.

This is a baffling issue as xwayland is everywhere, but this being arch, I guess maybe you didn't install it?

I've never used arch so I can't be of much help here, you likely will get better help at some arch specific forum.

El dt., 9 d’abr. 2024, 1:31, MuffinJets @.***> va escriure:

@.*** ~]$ flatpak run org.DolphinEmu.dolphin-emu qt.qpa.xcb: could not connect to display 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-egl, wayland, xcb.

/app/bin/dolphin-emu-wrapper: line 6: 13 Aborted (core dumped) dolphin-emu "$@" @.*** ~]$ flatpak update && sudo flatpak update Looking for updates…

Nothing to do. Looking for updates…

Nothing to do. @. ~]$ sudo pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date multilib is up to date :: Starting full system upgrade... there is nothing to do @. ~]$ neofetch -***@***.*** .o+ -------------------- ooo/ OS: Arch Linux x86_64+oooo: Host: 90H00006US ideacentre 720-18IKL +oooooo: Kernel: 6.8.4-arch1-1 -+oooooo+: Uptime: 15 mins/:-:++oooo+: Packages: 766 (pacman), 18 (flatpak) /++++/+++++++: Shell: bash 5.2.26/++++++++++++++: Resolution: 1920x1080 /+++ooooooooooooo/ DE: Hyprland ./ooosssso++osssssso+Theme: Material-Black-Blueberry-BE [GTK2/3] .oossssso-````/ossssss+ Icons: Adwaita [GTK2/3] -osssssso. :ssssssso. Terminal: kitty :osssssss/ osssso+++. CPU: Intel i7-7700 (8) @ 4.200GHz /ossssssss/ +ssssooo/- GPU: NVIDIA GeForce GTX 1050 Ti /ossssso+/:- -:/+osssso+- GPU: Intel HD Graphics 630+sso+:-`.-/+oso: Memory: 3480MiB / 11871MiB ++:. -/+/ . `/

@.*** ~]$

I did reinstall Dolphin, no clue what else I can be doing here, though I'll admit that I'm still a noob.

— Reply to this email directly, view it on GitHub https://github.com/flathub/org.DolphinEmu.dolphin-emu/issues/192, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACZPHZHRFM2ANVDI5KYWP7TY4MSGBAVCNFSM6AAAAABF5RW2H2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTEMZRGM3TONI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[supra0]

I'm having this exact issue on Fedora 40 (KDE spin) as well. XWayland is installed.

username@fedora:~$ flatpak run org.DolphinEmu.dolphin-emu
qt.qpa.xcb: could not connect to display 
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-egl, wayland, xcb.

/app/bin/dolphin-emu-wrapper: line 6:    12 Aborted                 (core dumped) dolphin-emu "$@"

username@fedora:~$ Xwayland -version
The X.Org Foundation Xwayland Version 24.1.1 (12401001)
X Protocol Version 11, Revision 0
Build ID: xorg-x11-server-Xwayland 24.1.1-1.fc40

It runs if I change QT_QPA_PLATFORM to wayland, but I'm unsure if it was set to xcb due to wayland support issues or something like that.

EDIT: I can't actually start any games while running on wayland so I would assume that yes, that's why.

[cpba]

This is a truly baffling issue, all the dependencies are in the runtime and socket it set to x11, there's no reason for it to fail.

@supra0 It's got to be something silly, have you made sure that you aren't overriding the --socket=x11 option in any way? It's set that way in the manifest, but people sometimes install flatseal and override options globally and then forget that they've done it.

Even if you don't remember doing it, I would advise that you install com.github.tchx84.Flatseal and remove all global overrides, then go to dolphin's and make sure x11 is set and neither wayland nor fallback-x11 are set. This will go a long way towards eliminating possibilites.

It runs if I change QT_QPA_PLATFORM to wayland, but I'm unsure if it was set to xcb due to wayland support issues or something like that.

Dolphin doesn't have any real wayland support (the ui works, but that's it), so it was set to xcb in order to override the global QT_QPA_PLATFORM (on the off chance that somebody might be setting it globaly to wayland).

[supra0]

Well I definitely feel silly now, the wayland and x11-fallback sockets were indeed toggled on for dolphin specifically and marked as "changed by the user". First time using the dolphin flatpak in a while so I don't remember when or why I set it, but regardless, toggling them off fixed the issue.

[cpba]

Oh that's good to hear, I was worried something truly bizarre might be happening.

@muffinjets can you test whether your issue is caused by the same problem detailed here?