Context: Wayfire 0.9.0; Dolphin built with `egl`, `sdl`, and `vulkan` flags enabled. After selecting a game and selecting "Play", a "Warning" dialog box appears with the message "Failed to create Vulkan surface", "Failed to initialize video backend", "Failed to create OpenGL window", depending on whether one has specified the Vulkan, OpenGL, or Software Renderer backend, respectively. Regardless of which dialog box action is selected, the game itself is not started. The current Flatpak version of Dolphin does not exhibit any of this behaviour. Reproducible: Always
Do you see any other error message when Dolphin is running from a terminal? As far as I know, Dolphin does not run on Wayland, based on commit https://github.com/dolphin-emu/dolphin/commit/a3b06b0572d7a16d8ede9c849e9f549a283123df Is it better if you run it with this command: ``` env QT_QPA_PLATFORM=xcb dolphin-emu ``` Also, can you provide `emerge --info gui-wm/wayfire games-emulation/dolphin` please?
> Do you see any other error message when Dolphin is running from a terminal? No. > As far as I know, Dolphin does not run on Wayland Ah! i'd assumed that it would straightforwardly be able to run under Xwayland, but apparently not. > env QT_QPA_PLATFORM=xcb dolphin-emu This works! i might create a 'Dolphin emulator' page on the wiki to note this. Thanks! > Also, can you provide `emerge --info gui-wm/wayfire games-emulation/dolphin` please? Sure, i'll attach that output here shortly.
Created attachment 930401 [details] Output of `emerge --info`
(In reply to Alexis from comment #2) > > As far as I know, Dolphin does not run on Wayland > > Ah! i'd assumed that it would straightforwardly be able to run under > Xwayland, but apparently not. You’re right, it should, as I understand from upstream’s commit (see link in URL). > > env QT_QPA_PLATFORM=xcb dolphin-emu > > This works! i might create a 'Dolphin emulator' page on the wiki to note > this. Thanks! It shouldn’t be necessary, and I guess it could be later an issue once Wayland is actually supported. So I suggest to avoid doing it as it might concern just a few cases, or to explicitly say it’s a temporary workaround and then referencing this bug. I have pushed a PR for the 2506 release, see bug 957145; it will be a good work to test and see if the issue is still present with this release before I (or someone else) create an issue report on upstream’s tracker https://bugs.dolphin-emu.org/projects/emulator/issues
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fb8d0e908fe84b832efdfd9db795137a9d519353 commit fb8d0e908fe84b832efdfd9db795137a9d519353 Author: Thibaud CANALE <thican@thican.net> AuthorDate: 2025-06-04 18:39:00 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2025-06-07 16:32:27 +0000 games-emulation/dolphin: add 2506 Closes: https://bugs.gentoo.org/952952 Closes: https://bugs.gentoo.org/957145 Bug: https://bugs.gentoo.org/956364 Signed-off-by: Thibaud CANALE <thican@thican.net> Part-of: https://github.com/gentoo/gentoo/pull/42449 Signed-off-by: Michał Górny <mgorny@gentoo.org> games-emulation/dolphin/Manifest | 1 + games-emulation/dolphin/dolphin-2506.ebuild | 301 ++++++++++++++++++++++++++++ 2 files changed, 302 insertions(+)
Alexis: does it work without the workaround with this the 2506 release? With a better look, the upstream commit "Enforce XCB within code" has been merged with release 2506. And the workaround was inside its desktop file, I think it should have work. Please confirm this has been solved.
Yep, the 2506 release works "out of the box", no workaround needed - thanks! Marking this as RESOLVED - FIXED. Thanks also for your edits to the "Dolphin emulator" page!
