[BUG] Nvidia with Wayland unable to start (Flatpak)

[azomDev]

• I have searched and found no existing issues on the same topic
• I have searched the wiki and found no mention of my problem

Description

App fails to launch when started from the gnome shell or from the terminal

Steps to Reproduce

Nvidia + Wayland + Flatpak i'm guessing.

I am on a fresh fedora 41 install. (fresh from today)

Expected Behavior

Expected to open :P

Actual Behavior

$ flatpak run io.github.milkshiift.GoofCord
Using NVIDIA on Wayland, applying workaround
Passing the following arguments to Electron: --ozone-platform-hint=auto --enable-gpu-rasterization --ignore-gpu-blocklist --enable-zero-copy --enable-drdc --enable-wayland-ime --wayland-text-input-version=3 --disable-gpu-sandbox --enable-features=UseSkiaRenderer,VaapiVideoDecoder,VaapiVideoEncoder,PulseaudioLoopbackForScreenShare,VaapiVideoDecodeLinuxGL,WaylandWindowDecorations
[2:0120/183152.457852:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
GoofCord 1.8.1
[2:0120/183152.596206:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0120/183152.596231:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
You are using Wayland! >ᴗ<
[Timer] Electron loaded in: 0.88ms
[Message Encryption] Loaded encryption passwords
[Firewall] Set up CSP unstricter
[Firewall] Firewall initialized
[2:0120/183152.672392:ERROR:browser_main_loop.cc(279)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[Asset Loader] Categorized files with extension .js
[Asset Loader] Categorized files with extension .css
[Window] Opening window...
[Window] Setting up window...
[Timer] GoofCord fully loaded in: 147.424ms
[Mod Loader] Downloading mod bundles for: vencord
[Mod Loader] Downloading mod bundles for: shelter
[2:0120/183152.749042: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

Environment

• Operating System (name and version): Fedora 41
• GoofCord Version: 1.8.1 (on flatpak)
• Way of installing: Flatpak

Additional Information

Part of this error seems to be similar to Heroic-Games-Launcher/HeroicGamesLauncher#4083, but I thought it would be worth mentioning here since I saw the log Using NVIDIA on Wayland, applying workaround

[Milkshiift]

I updated the flatpak with a possible fix
flathub/io.github.milkshiift.GoofCord#19

Try it out when it's available to you

[azomDev]

I am trying it right now. I am new to testing Flatpak, so I may need some help.

I ran flatpak install --user https://dl.flathub.org/build-repo/158935/io.github.milkshiift.GoofCord.flatpakref
from the PR you linked

Then I ran flatpak list and got:

GoofCord                                           io.github.milkshiift.GoofCord                            1.8.1                                stable                  flathub                     system
GoofCord                                           io.github.milkshiift.GoofCord                            1.8.1                                test                    goofcord-origin             user

Finally I tried running flatpak run --user io.github.milkshiift.GoofCord//test and got:

Using NVIDIA on Wayland, disabling gpu sandbox
Wayland socket is available, running natively on Wayland.
To disable, remove the --socket=wayland permission.
Passing the following arguments to Electron: --enable-gpu-rasterization --ignore-gpu-blocklist --enable-zero-copy --enable-drdc --disable-gpu-sandbox --ozone-platform-hint=auto --enable-wayland-ime --wayland-text-input-version=3 --enable-features=UseSkiaRenderer,VaapiVideoDecoder,VaapiVideoEncoder,PulseaudioLoopbackForScreenShare,VaapiVideoDecodeLinuxGL,WaylandWindowDecorations
[2:0121/160158.475511:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
GoofCord 1.8.1
[2:0121/160158.604383:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0121/160158.604410:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
You are using Wayland! >ᴗ<
[Timer] Electron loaded in: 0.786ms
[Message Encryption] Loaded encryption passwords
[Firewall] Set up CSP unstricter
[Firewall] Firewall initialized
[2:0121/160158.671009:ERROR:browser_main_loop.cc(279)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[Asset Loader] Categorized files with extension .js
[Asset Loader] Categorized files with extension .css
[Window] Opening window...
[Window] Setting up window...
[Timer] GoofCord fully loaded in: 135.207ms
[Mod Loader] Downloading mod bundles for: vencord
[Mod Loader] Downloading mod bundles for: shelter
[2:0121/160158.753602:ERROR:wayland_event_watcher.cc(78)] Fatal Wayland communication error: Connection reset by peer.
[2:0121/160158.753664:FATAL:electron_browser_main_parts.cc(504)] Failed to shutdown.

Am I doing this right?

[Milkshiift]

Yep. Is it working now?

[azomDev]

Nope, I got the log I sent in my previous message and it stopped after (nothing appeared on the screen).

Edit: If there is anything I can try doing to help, let me know!

[Milkshiift]

The signature error Could not bind the given EGLImage to a CoglTexture2D is gone though.
I think the other errors are not related.

Strangely enough, I can reproduce this behaviour with heroic, but not with GoofCord (flatpak and native).
Heroic doesn't output any errors, so logs aren't of help it seems.

Can you try a native build to be sure it's not flatpak?

[azomDev]

Ok, here is what I just did:

1. Uninstalled the official one from Flatpak
2. Uninstalled the testing one from earlier
3. Installed with the rpm release
4. Tried to launch it from the gnome-shell (trying to click on the icon basically), it did nothing
5. Run goofcord from the terminal. It successfully opens with the following logs:

GoofCord 1.8.2-beta.1
You are using Wayland! >ᴗ<
[Timer] Electron loaded in: 0.788ms
[Message Encryption] Loaded encryption passwords
[Firewall] Firewall initialized
[Firewall] Set up CSP unstricter
[Asset Loader] Categorized files with extension .js
[Asset Loader] Categorized files with extension .css
[Window] Opening window...
[Window] Setting up window...
[Timer] GoofCord fully loaded in: 120.621ms
[Mod Loader] Downloading mod bundles for: vencord
[Mod Loader] Downloading mod bundles for: shelter
[Mod Loader] Bundles downloaded for: shelter
[2025-01-21 17:01:54.621] [venmic] [info] [patchbay] (handle) found default metadata: 38
[2025-01-21 17:01:54.621] [venmic] [info] [patchbay] (meta_update) speaker name: "alsa_output.pci-0000_10_00.6.analog-stereo"
[2025-01-21 17:01:54.621] [venmic] [info] [patchbay] (get) running venmic 6.1.0
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

[Mod Loader] Bundles downloaded for: vencord

Edit: just tried rebooting and trying to start it from the gnome-shell still fails

[azomDev]

Strangely enough, I can reproduce this behaviour with heroic, but not with GoofCord (flatpak and native).
Heroic doesn't output any errors, so logs aren't of help it seems.

That is very weird. I just installed Fedora a few days ago, and after re-installing Heroic, it seems to be starting normally (using the Flatpak). I got the logs from running it with the flatpak cli and posted them in Heroic-Games-Launcher/HeroicGamesLauncher#4083

I am on the same hardware as I was on arch, only thing I changed was the os (which does change a lot)

[SteamAutomata]

I have this issue too on my RTX 3050 with Wayland :(
This issue doesn't seem to be unique to Goofcord, most Discord clients have the same issue.