"The display compositor is frequently crashing. Goodbye."

[Techokami]

Describe the bug
I am using Fedora 36 and wish to use GB Studio. I downloaded the official "GB Studio for Fedora/Red Hat Linux" package from itch.io and installed the RPM, and then when I went to actually run it... it never ran. I tried running it from the terminal, and I got the cryptic error shown in the subject of this bug report. However, my display compositor is not crashing, and I can run any other Electron-based app without issue (Discord, Visual Studio Code, unofficial Linux port of GitHub Desktop). I have even mentioned this issue to one of the people on the Fedora team, and he found it to be absolutely bizzare.

To Reproduce
Steps to reproduce the behavior:

1. Install official RPM of GB Studio on Fedora 36
2. Run it
3. ???????????????????
4. See error

Expected behavior
I expected the program to launch like any other program made with Electron.

Screenshots

[techokami@markv ~]$ gb-studio
No language pack for user setting, falling back to en
Add a language pack by making the file src/lang/en-US.json
[2488:0414/181859.935493:FATAL:gpu_data_manager_impl_private.cc(1034)] The display compositor is frequently crashing. Goodbye.
Trace/breakpoint trap (core dumped)
[techokami@markv ~]$ 

Platform (please complete the following information):

• OS: Fedora 36 x86-64
• Desktop: KDE Plasma
• Video Card: RTX 2060
• App version 3.0.3

[gedaerm]

This isn't specific to Fedora, btw. The same happens to a fully rolled up Arch.
If I had to guess: the bundled browser/electron is too old.

[Takuyax]

I can confirm this issue on my desktop with Kubuntu 22.04.
Desktop: KDE Plasma
Video Card: GTX 1060
App version 3.0.3

It runs fine on my laptop with Kubuntu 21.04

[RichardULZ]

No idea what any of this is about, but searching for the error on another electron app, users with arch linux and ubuntu 22 had the same issue. Must be something recent between the os and specific version of electron.
mifi/lossless-cut#1025 (comment)

Running the app with --no-sandbox seemed to be a workaround for them, maybe the same would apply here?
Ultimately an electron update might solve it, as the other post suggests.

[Takuyax]

No idea what any of this is about, but searching for the error on another electron app, users with arch linux and ubuntu 22 had the same issue. Must be something recent between the os and specific version of electron. mifi/lossless-cut#1025 (comment)

Running the app with --no-sandbox seemed to be a workaround for them, maybe the same would apply here? Ultimately an electron update might solve it, as the other post suggests.

Thanks! I can confirm that workaround fixes it for me. When I tried the workaround the first time last night, it started, worked briefly, then replaced the interface with a "loading" message. When I closed the window, I saw a segmentation fault error in the terminal. Not sure if that's related. Since then it has been working without issues.

[Techokami]

No idea what any of this is about, but searching for the error on another electron app, users with arch linux and ubuntu 22 had the same issue. Must be something recent between the os and specific version of electron. mifi/lossless-cut#1025 (comment)
Running the app with --no-sandbox seemed to be a workaround for them, maybe the same would apply here? Ultimately an electron update might solve it, as the other post suggests.

Thanks! I can confirm that workaround fixes it for me. When I tried the workaround the first time last night, it started, worked briefly, then replaced the interface with a "loading" message. When I closed the window, I saw a segmentation fault error in the terminal. Not sure if that's related. Since then it has been working without issues.

Huh, did that and now it works! This is a very stupid bug though, so it should still be investigated as to why this occurs at all.

[1j01]

For me, running from the command line (with or without --no-sandbox) allowed it to run.
Trying to launch it from the Activities panel (apps menu) in Ubuntu 22 is giving this error, installed with an AppImage.
Running by double clicking on the AppImage in Thunar usually fails, without notification, but occasionally launches.

[java-py-c-cpp-js]

For me, this issue still exist in April 2023 with the Flatpak version of this software:

$ flatpak run dev.gbstudio.gb-studio 
Gtk-Message: 14:07:21.639: Failed to load module "xapp-gtk3-module"
Gtk-Message: 14:07:21.639: Failed to load module "appmenu-gtk-module"
Gtk-Message: 14:07:21.668: Failed to load module "canberra-gtk-module"
Gtk-Message: 14:07:21.669: Failed to load module "canberra-gtk-module"
[3:0407/140722.426162:FATAL:gpu_data_manager_impl_private.cc(1034)] The display compositor is frequently crashing. Goodbye.
/app/bin/gb-studio: Zeile 2:     3 Trace/Breakpoint ausgelöst   zypak-wrapper /app/lib/gb-studio/gb-studio

Is it possible to apply the --no-sandbox workaround here, too?

$ flatpak run dev.gbstudio.gb-studio --no-sandbox doesn't change anything.

[SaraVieira]

I am having the same issue in Ubuntu 22.04.2 LTS and running it with --no-sandbox fixes it

[ntippie]

Either --no-sandbox or --disable-seccomp-filter-sandbox both fix the issue for me.