[BUG] - (Linux) Using GTK 2/3 and GTK 4 in the same process is not supported

[Captn138]

Describe the bug When running r2modman since 3.2.4 up to 3.2.6, the application didn't start. I tried running it from command line and got the following result :

 $ r2modman

(process:83785): Gtk-ERROR **: 18:12:04.377: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
[1]    83785 trace trap (core dumped)  r2modman

NB : the app core-dumped itself, I did not intervene.

To Reproduce Steps to reproduce the behavior:

1. Update to any version of 3.2.4, 3.2.5 or 3.2.6
2. Run r2modman using the command line
3. Observe misbehavior

Expected behavior The app was launching just fine before 3.2.4

Additional context I am running Arch Linux, everything is up to date. I am using Gnome, version 48 (49 not released yet on Arch). The app is installed using this PKGBUILD which is using the .pacman export in the release. I don't know if you are the origin of this PKGBUILD but I inspected it and it does not seem to be badly typed.

I can provide more info if needed, please tell me.

[devleonardoamaral]

Describe the bug

This is also happening on Debian.

$ r2modman

(process:25838): Gtk-ERROR **: 16:32:26.930: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
Trace/breakpoint trap

To Reproduce

Same reproduction steps as the original report.

Additional context

• Installed via GNOME Software
• Debian GNU/Linux 13.1 (trixie)
• GNOME 48.4
• The issue occurs with both the native package (.deb) and the .AppImage version

[ebkr]

This is an issue with the version of Electron that the manager is using.

Reportedly you can append a --gtk-version=3 launch argument to get it working.

[Captn138]

I can confirm that using the option you provided it works as intended. @ebkr could it be integrated to the base executable ?

[devleonardoamaral]

@ebkr I tested using the --gtk-version=3 argument, and it now works as expected. This works both with the AppImage and the native (.deb) version.

[ebkr]

@ebkr could it be integrated to the base executable ?

I’m not entirely sure.

I’ve tried to add —no-sandbox as an appended switch before and it didn’t work, so I don’t know how likely it is that appendSwitch would work here either.

I won’t be able to do a release for a few days either.

This must be related to your systems using GTK and other people who aren’t affected I guess are using Qt based DEs. I’ve sent out a couple of test builds whilst working on it and people haven’t reported these before 🤔

It could turn out that an Electron update resolves the issue too.

[Gamey404]

I get the same issue on Fedora 42 Workstation using the rpm but for some reason everything worked fine till 3.2.6 and now none of the affected versions seem to work. If anyone reads this who has the issue too, either use --gtk-version=3 or if that just gets you stuck on the loading screen like me manually downgrading a none auto updating package like the rpm seems to work. On Fedora you just navigate to the folder with the rpm and do sudo rpm -Uvh --oldpackage r2modman-3.2.3.x86_64.rpm to downgrade.

[JumperLuko]

TY, --gtk-version=3 worked!