[Wayland] Heroic does not open

[SamRodri]

Describe the bug

Heroic doesn't open on Ubuntu 24.10 with Wayland and NVIDIA drivers. Both Flatpak and .deb fails with the same error.

Add logs

[13:1030/105151.856892:ERROR:wayland_event_watcher.cc(43)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D

Steps to reproduce

1. Open the launcher from command line to see errors, flatpak run com.heroicgameslauncher.hgl.

Expected behavior

Expected launcher window to open.

Screenshots

No response

Heroic Version

Latest Stable

System Information

• OS: Ubuntu 24.10
• Window System: Wayland
• Driver: nvidia-driver-560

Additional information

No response

[LazyStability]

Not on Ubuntu but on nixos, with a similiar problem the heroic window does not open in wayland, but it does in xwayland/x11.

Steps to reproduce

1. type in cmd heroic --enable-features=UseOzonePlatform --ozone-platform=wayland, no window opens
2. type in cmd heroic --enable-features=UseOzonePlatform --ozone-platform=x11, window opens

System Information:
[...]
GPUs:
  GPU 0:
    [...]
    Driver: nvidia
OS: NixOS 24.11 (Vicuna) (linux)

The current system is not a Steam Deck
We are not running inside a Flatpak container

Software Versions:
  Heroic: 2.15.2 Emeth
  Legendary: 0.20.34 Direct Intervention
  gogdl: 1.1.2
  comet: comet 0.1.2

  Nile: 1.1.2 Will A. Zeppeli

[SamRodri]

Command heroic --enable-features=UseOzonePlatform --ozone-platform=x11 works for me too. Thanks for the workaround.

[azomDev]

Same here. I am using arch linux, wayland, nvidia 40 series, gnome, flatpack and Heroic (installed with flatpack). When trying to launch the app from gnome, nothing happens. When running in the cli this:
flatpak run com.heroicgameslauncher.hgl
I get:

which: no wine in (/app/bin:/app/bin:/app/utils/bin:/usr/bin:/usr/lib/extensions/vulkan/MangoHud/bin:/usr/lib/extensions/vulkan/gamescope/bin:/usr/lib/extensions/vulkan/OBSVkCapture/bin:/app/bin/heroic/resources/app.asar.unpacked/build/bin/linux)
(19:01:22) INFO:    [Legendary]:        Legendary location: /app/bin/heroic/resources/app.asar.unpacked/build/bin/x64/linux/legendary
(19:01:22) INFO:    [Gog]:              GOGDL location: /app/bin/heroic/resources/app.asar.unpacked/build/bin/x64/linux/gogdl
(19:01:22) INFO:    [Connection]:       Connectivity: check-online
(19:01:22) INFO:    [Connection]:       Pinging external endpoints
(19:01:22) INFO:    [Gog]:              Checking for existing gog manifests
LaunchProcess: failed to execvp:
xdg-settings
(19:01:22) WARNING: [Backend]:          Failed to register protocol with OS.
[13:1202/190122.544551:ERROR:browser_main_loop.cc(278)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
(19:01:22) INFO:    [Legendary]:        Running command: LEGENDARY_CONFIG_PATH=/home/azom/.var/app/com.heroicgameslauncher.hgl/config/heroic/legendaryConfig/legendary /app/bin/heroic/resources/app.asar.unpacked/build/bin/x64/linux/legendary --version
(19:01:22) INFO:    [Gog]:              Running command: GOGDL_CONFIG_PATH=/home/azom/.var/app/com.heroicgameslauncher.hgl/config/heroic/gogdlConfig /app/bin/heroic/resources/app.asar.unpacked/build/bin/x64/linux/gogdl --auth-config-path /home/azom/.var/app/com.heroicgameslauncher.hgl/config/heroic/gog_store/auth.json --version
(19:01:22) INFO:    [Nile]:             Running command: NILE_CONFIG_PATH=/home/azom/.var/app/com.heroicgameslauncher.hgl/config/heroic/nile_config /app/bin/heroic/resources/app.asar.unpacked/build/bin/x64/linux/nile --version
[13:1202/190122.585565:ERROR:wayland_event_watcher.cc(43)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D

/app/bin/heroic-run : ligne 6 :    13 Trappe pour point d'arrêt et de trace              (core dumped)zypak-wrapper /app/bin/heroic/heroic "$@"

And it does not launch (note that the last sentence is in french because of my system. It is basically saying /app/bin/heroic-run: line 6: 13 Trap for breakpoint and trace (core dumped) zypak-wrapper /app/bin/heroic/heroic "$@")

With the following command:
flatpak run com.heroicgameslauncher.hgl --enable-features=UseOzonePlatform --ozone-platform=x11
It launches (this time using the flatpack command instead of heroic like @LazyStability used).

I quickly tried this:
flatpak run com.heroicgameslauncher.hgl --enable-features=UseOzonePlatform
and it did not work, but the following command did work:
flatpak run com.heroicgameslauncher.hgl --ozone-platform=x11

[azomDev]

I just tried to install discord canary for the new screen sharing on wayland. Anyways, like Heroic, it wouldn't launch in the gnome shell, so I tried to run flatpak run com.discordapp.DiscordCanary and got this:

Disabling updates already done
DiscordCanary 0.0.528
Starting app.
Starting updater.
2024-12-03T21:20:34.095Z [Modules] Modules initializing
2024-12-03T21:20:34.095Z [Modules] Distribution: remote
2024-12-03T21:20:34.095Z [Modules] Host updates: disabled
2024-12-03T21:20:34.095Z [Modules] Module updates: enabled
2024-12-03T21:20:34.095Z [Modules] Module install path: /home/azom/.var/app/com.discordapp.DiscordCanary/config/discordcanary/0.0.528/modules
2024-12-03T21:20:34.095Z [Modules] Module installed file path: /home/azom/.var/app/com.discordapp.DiscordCanary/config/discordcanary/0.0.528/modules/installed.json
2024-12-03T21:20:34.095Z [Modules] Module download path: /home/azom/.var/app/com.discordapp.DiscordCanary/config/discordcanary/0.0.528/modules/pending
splashScreen.initSplash(false)
CDM component API found
blackbox: 2024-12-03T21:20:34.149Z 0 

----------------------------------------------
blackbox: 2024-12-03T21:20:34.156Z 1 Discord starting: {"releaseChannel":"canary","version":"0.0.528"}, modulepath: /home/azom/.var/app/com.discordapp.DiscordCanary/config/discordcanary/0.0.528/modules
blackbox: 2024-12-03T21:20:34.159Z 2 ✅ webContents.created web1 "index.html"
blackbox: 2024-12-03T21:20:34.162Z 3 ✅ window.created win1 "discord"
[5:1203/162034.168032:ERROR:wayland_event_watcher.cc(43)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D

/app/bin/com.discordapp.DiscordCanary : ligne 18 :     5 Trappe pour point d'arrêt et de trace              (core dumped)env TMPDIR=$XDG_CACHE_HOME zypak-wrapper /app/discord-canary/DiscordCanary "${FLAGS[@]}" "$@"
2024/12/03 16:20:35 socat[3] W exiting on signal 15

Which has essentially the same error @SamRodri and I got when trying to launch Heroic:
[5:1203/162034.168032:ERROR:wayland_event_watcher.cc(43)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D

I might update this with other apps I try, but I am not completely certain this is a problem with Heroic. This might either be something bigger (Flatpak or Wayland mabye), a compatibility problem or just a random thing.

I do want to note that I never developed a Flatpak app, so I don't exactly understand exactly which logs are from Flatpak or from the app itself.

EDIT

Got the same error when trying to run flatpak run com.github.IsmaelMartinez.teams_for_linux:

No config file found, using default values
all good with appLogLevels you aren't using them
all good with onlineCheckMethod you aren't using them
Initialising logger with config: {"transports":{"console":{"level":"info"},"file":{"level":false}}}
16:28:21.458 › configPath: /home/azom/.var/app/com.github.IsmaelMartinez.teams_for_linux/config/teams-for-linux
16:28:21.460 › Running under Wayland, switching to PipeWire...
LaunchProcess: failed to execvp:
xdg-settings
[2:1203/162821.783856:ERROR:browser_main_loop.cc(279)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[2:1203/162821.918149:ERROR:wayland_event_watcher.cc(47)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D

I just looked very quickly through Heroic's code, and I am pretty sure it uses Electron, which all of the apps I tried to run use (discord canary, teams for Linux and Heroic)

I tried to dig a little deeper, so I tried normal discord as I didn't remember having issues launching it. And it worked! I have Flatseal installed so I took a quick peak at the config of discord vs discord canary and the only thing I had changed was i was forcing socket=wayland on discord canary since the new screen-sharing fix is on Wayland. So I tried to set discord canary to use x11 like @LazyStability said for Heroic and it now worked. I still don't understand exactly the problem, but it appears to be about electron running in Wayland.

TL;DR: From my testing, the issue is probably more about Electron running on Wayland than about Heroic specifically. However, since I don't feel like a lot of people is having this issue, there is probably another condition that I am unsure of at the moment.

[SamRodri]

VSCode is an Electron app and it works fine for me. Could be the Electron version?

[azomDev]

This is the default for my VSCode Flatpak config seen in Flatseal. I don't know if for you it is the same but mine is running using x11, which from my test works for all the different apps I have tested (while when choosing the wayland option they do not). I tried this config (the warning symbols just mean that the setting has been changed by the user, aka me):

and I can't start it from gnome shell. However, when trying to run flatpak run com.visualstudio.code
I now get the message:

Warning: 'ms-enable-electron-run-as-node' is not in the list of known options, but still passed to Electron/Chromium.

And nothing else, nothing before or after, just this and it does not start.

Edit: I still get the same warning even with the default Flatpack config in Flatseal. But with the default config (using x11) VSCode does launch.

[SamRodri]

I have it installed directly from MS repo, I believe I followed these instructions, it has been a while, I remember that it was blurry at some point and I changed some configs (back when Ubuntu was just X11 for NVIDIA).

I just tried code --enable-features=UseOzonePlatform --ozone-platform=wayland and it works, VSCode about:

Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 6.11.0-9-generic

[azomDev]

I might try later to install it with pacman to test. Meanwhile, here is VSCode about when in x11 for me (exactly the same except the OS)

Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 6.12.1-arch1-1

[SamRodri]

Same Electron. I will try to find the configs I changed.

[azomDev]

So I installed the official binary of VSCode from the AUR since it is not in the official arch linux pacman repositories (I changed nothing after the install). When launching it by running code it really seems it is using x11 because it appears a bit blurry (I have a 4k monitor).

I tried running code --enable-features=UseOzonePlatform --ozone-platform=wayland but it still did not launch. I got the same warning:

Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

I search a bit online and found microsoft/vscode#207033 which seems to describe a similar issue with the last comment being:

I've also noticed that this not only affects VS Code, but all apps built in Electron. So this is an Electron issue, meaning it's completely broken in all Electron apps.

For now I think it might be a compatibility issue with something, but I really don't know what. Since you mentionned you were using nvidia, it might not be that. In the issue I linked has a few people on ubuntu having a similar problem as me, so it might not even be that.

[azomDev]

For future reference, here is all the info from running fastfetch while keeping everything I thought could be ever so slightly linked to the issue.

OS: Arch Linux x86_64
Host: B650 GAMING X AX
Kernel: Linux 6.12.1-arch1-1
Packages: 803 (pacman), 67 (flatpak)
Shell: bash 5.2.37
Display (MAG274UPF): 3840x2160 @ 144 Hz (as 3072x1728) in 27" [External]
DE: GNOME 47.2
WM: Mutter (Wayland)
WM Theme: Adwaita
Theme: Adwaita [GTK2/3/4]
Icons: Adwaita [GTK2/3/4]
Font: Inter Variable (12pt) [GTK2/3/4]
Cursor: Adwaita (24px)
Terminal: GNOME Console 47.1
Terminal Font: Source Code Pro (10pt)
CPU: AMD Ryzen 7 7800X3D (16) @ 5.05 GHz
GPU 1: NVIDIA GeForce RTX 4070 [Discrete]
GPU 2: AMD Raphael [Integrated]

[SamRodri]

I found the config I changed, in ~/.vscode/argv.json I have "disable-hardware-acceleration": true, if I remove this vscode does not open on Wayland, but it still opens if I force x11 with code --enable-features=UseOzonePlatform --ozone-platform=x11.

I'm now convinced the error is due to a combination of Wayland+GPU on Electron.

I'm using the nvidia proprietary driver-560. Do you know if there is a way to force the use of the integrated GPU? I have an Intel CPU, so between us we can cover all GPU manufacturers.

Edit: I also have a 4k screen, just tested without screen scaling and it fails the same, screen scaling not to blame.

[azomDev]

I tried for a good 30 minutes to get the iGPU to work for an app, but I was not able to. I decided that it was better just to disconnect completely my Nvidia GPU from my system and plug my display cable into the motherboard. Here is what I got:

At the right is the flatpack version (which looks the same as just running code. At the left is when I run one of the following commands:

code --enable-features=UseOzonePlatform --ozone-platform=wayland
code --ozone-platform=wayland

However, I saw on other comments that the following command kills windows using Xwayland:
killall -vws2 Xwayland
And it killed both windows so I am unsure what to make of this...

[SamRodri]

I guess Code is doing too many custom things with Electron.

I believe electron/electron#44607 is tracking this bug on Electron, I'm surprised they are taking so long to fix this to be honest.

[azomDev]

I do want to point out that I just tried again with Heroic (btw my Nvidia GPU is back as the main GPU) and it still failed (like before).

I tried to go into Flatseal to put this Flatpack config for Heroic:

But it did not work. For VSCode or Discord, this does work, but for some reason it does not work for Heroic. As of right now, the only way I can launch Heroic is using flatpak run com.heroicgameslauncher.hgl --enable-features=UseOzonePlatform --ozone-platform=x11

When I say it failed, I mean using gnome shell to launch it (so using the desktop normally). However, if I run flatpak run com.heroicgameslauncher.hgl with the config in the image, I get:

[12:1203/213254.934026:ERROR:wayland_connection.cc(197)] Failed to connect to Wayland display: Aucun fichier ou dossier de ce type (2)
[12:1203/213254.934054:ERROR:ozone_platform_wayland.cc(264)] Failed to initialize Wayland platform
[12:1203/213254.934058:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.
/app/bin/heroic-run : ligne 6 :    12 Erreur de segmentation  (core dumped)zypak-wrapper /app/bin/heroic/heroic "$@"

Which indicates it is trying to use Wayland I assume.

[SamRodri]

I'm not sure how it is on Arch, for me I created a replacement desktop file in ~/.local/share/applications/heroic.desktop

[Desktop Entry]
Name=Heroic Games Launcher
Exec=/opt/Heroic/heroic --enable-features=UseOzonePlatform --ozone-platform=x11 %U
Terminal=false
Type=Application
Icon=heroic
StartupWMClass=Heroic
Comment[de]=Ein Open Source Spielelauncher for GOG und Epic Games
Comment=An Open Source Launcher for GOG and Epic Games
MimeType=x-scheme-handler/heroic;
Categories=Game;

After a session restart gnome picks up this new exec command

[LazyStability]

There is a global variable to tell Electron to always use x11 or wayland. I just switched that back to x11 and all of my electron apps are working smoothly again.

For me on nixos its this NIXOS_OZONE_WL=0 from here.
For other linux systems it should be this ELECTRON_OZONE_PLATFORM_HINT=x11 from here.

Just set those on startup and all your electron apps should work fine using x11.

Edit: The nixos one is incorrect, setting it to zero will still enable wayland usage, you have to unset it by removing any mention of it from your config.

[azomDev]

I'm not sure how it is on Arch, for me I created a replacement desktop file in ~/.local/share/applications/heroic.desktop

I tried earlier and it does not seem to work for some reason. Tried to change the file name and app name that you sent so it would not interfere with the flatpack version (the Flatpalk entries are not in the ~/.local/share/applications/ directory afaik) and it did not work. But I could probably go look where the flatpak apps are defined for the desktop. Thanks for the tip anyways!

@LazyStability I think it's a little more complex than this (even I don't really understand what is going on and some parts might just be my system).

running code in a terminal does open code in x11 by default. Although I can do some work on it, the text is a bit blurry which is not ideal. When trying to use the Flatpak version, I can set the config with Flatseal to either only try to use wayland or only try x11. In the case of x11, it basically does the same thing as running code. When trying wayland, it does not launch. When switching my whole system to amd iGPU, I am able to run code with the ozone plateform wayland argument I mentioinned earlier and it does open while being not blurry. However, the Flatpak version does not launch with the wayland mode in Flatseal. Furthermore, with my iGPU, when running code with the ozone argument, I ran the command I mentionned earlier to kill all windows using Xwayland, and it kills the window that is not blurry. (note that I know a minumum what the command does, but I might check in more details later). While I don't really have a problem with Xwayland, it might help us to understand what is going on.

As for the other apps, I will have to check to be sure, but for "teams on linux" in Flatpak I have not looked yet at the Flatseal config to see if I can get teams to launch as I was not able before.

For discord, putting it to x11 seems to work. I was even able to use the new screen sharing feature using the x11 version, although it is very possible that since it is using the x11 version, the screensharing was working on it before the new canary update..

I will test later teams to be sure about the following conclusion, but for now, I see that:

• VSCode on Flatpak and from the AUR act differently about x11/Wayland when not using Nvidia (with Nvidia, electron on Wayland appears to not work at all?)
• From my testing, only electron apps are affected

As I said, I'll test teams on Flatpak and edit this comment later today (if I remember)

EDIT FOR TEAMS TEST:

In the gnome shell, teams from Flatpack won't start. Even if I change which between X11 and Wayland is preferred in Flatseal.

When running flatpak run com.github.IsmaelMartinez.teams_for_linux I get:

[2:1207/173221.009226:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Aucun fichier ou dossier de ce type
No config file found, using default values
all good with appLogLevels you aren't using them
all good with onlineCheckMethod you aren't using them
Initialising logger with config: {"transports":{"console":{"level":"info"},"file":{"level":false}}}
17:32:21.146 › configPath: /home/azom/.var/app/com.github.IsmaelMartinez.teams_for_linux/config/teams-for-linux
17:32:21.148 › Running under Wayland, switching to PipeWire...
LaunchProcess: failed to execvp:
xdg-settings
[2:1207/173221.220233:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Aucun fichier ou dossier de ce type
[2:1207/173221.220259:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Aucun fichier ou dossier de ce type
[2:1207/173221.248243:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Aucun fichier ou dossier de ce type
[2:1207/173221.248264:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Aucun fichier ou dossier de ce type
[2:1207/173221.248278:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Aucun fichier ou dossier de ce type
[2:1207/173221.294432:ERROR:browser_main_loop.cc(279)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[2:1207/173221.336330:ERROR:wayland_event_watcher.cc(47)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D

Which is similar to the originial Heroic problem.

When running flatpak run com.github.IsmaelMartinez.teams_for_linux --enable-features=UseOzonePlatform --ozone-platform=x11 I get:

[2:1207/173333.987863:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Aucun fichier ou dossier de ce type
No config file found, using default values
all good with appLogLevels you aren't using them
all good with onlineCheckMethod you aren't using them
Initialising logger with config: {"transports":{"console":{"level":"info"},"file":{"level":false}}}
17:33:34.116 › configPath: /home/azom/.var/app/com.github.IsmaelMartinez.teams_for_linux/config/teams-for-linux
17:33:34.117 › Running under Wayland, switching to PipeWire...
LaunchProcess: failed to execvp:
xdg-settings
[2:1207/173334.134101:ERROR:ozone_platform_x11.cc(245)] Missing X server or $DISPLAY
[2:1207/173334.134108:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.

Which is a bit weird since with these arguments it works on Heroic for example.

Anyways, I can't really make more conclusions out of this.

[SamRodri]

The dir ~/.local/share/applications/ is just for overrides, I just copied the /usr/share/applications/heroic.desktop file and modified it.

I have Heroic installed directly from the .deb, I think Flatpak desktop files are in /var/lib/flatpak/exports/share/applications, or you can sudo the original file I suppose.

[Klubas]

Same problem here in silverblue/bluefin with nvidia, heroic only opens with ozone-platform=x11

[Etaash-mathamsetty]

wtf nvidia + electron wayland is still broken ? I guess I'll put x11 back to default then. Nvidia got to get their stuff together at some point man

[natervader]

Hey! I ran into this issue as well. Someone made another issue related to flatpak #4173 but from what I gather the packaged version doesn't really matter. If you all want details on my end it's in the thread.

As I said there, if there's anything I can do to help troubleshoot let me know.

[azomDev]

wtf nvidia + electron wayland is still broken ?

Yeah seems like it. Although when using flat pak versions of some apps that are not using electron, I sometimes have issue running it from the gnome shell in the drawer (or anywhere graphical like that). But that could be another unrelated problem with maybe flatpak, Wayland and maybe Nvidia.

but from what I gather the packaged version doesn't really matter.

That's probable. However, It's possible that it is not helping in some cases as I said above. We'll have to see.

As I said there, if there's anything I can do to help troubleshoot let me know.

Same here, if I can do anything to help find out the issue, let me know. I already did a quick dump of a few logs and system info earlier in this thread, but if anything needs testing I'm here.

EDIT: After reading more of #4173, I saw that the error over there does not seem to be the same as the ones we are having here. Might be because it's a different problem or not, but I am also using the Flatpak version so I don't know...