Package Details: mongodb-compass-bin 1.46.3-1

Git Clone URL: https://aur.archlinux.org/mongodb-compass-bin.git (read-only, click to copy)
Package Base: mongodb-compass-bin
Description: The official GUI for MongoDB - binary version
Upstream URL: https://www.mongodb.com/products/compass
Keywords: compass mongodb
Licenses: SSPL-1.0
Conflicts: mongodb-compass
Provides: mongodb-compass
Submitter: dpeukert
Maintainer: dpeukert (ogarcia)
Last Packager: dpeukert
Votes: 3
Popularity: 1.77
First Submitted: 2025-05-12 06:05 (UTC)
Last Updated: 2025-06-05 23:35 (UTC)

Pinned Comments

dpeukert commented on 2025-05-12 06:08 (UTC)

The PKGBUILD for this package is hosted here (contributions are welcome!): https://gitlab.com/dpeukert/pkgbuilds/tree/main/mongodb-compass

Latest Comments

1 2 Next › Last »

dpeukert commented on 2025-06-17 10:01 (UTC)

@DFS, @BishWajit, @thyagocl, @datafieber: Looks like this was fixed by upstream by setting gtk-version internally (https://github.com/mongodb-js/compass/commit/919a84566558f5cc3408238b9005e6fe2687e164). Can you check if mongodb-compass-beta-bin fixes this for you?

thyagocl commented on 2025-06-16 09:53 (UTC)

Following my previous comment, I managed to update the package by running yay --mflags "--nocheck". Which is probably not great, but at least it worked. After that, I did what @datafieber suggested with the flags to force gtk 3 and managed to launch compass without problems, apparently. Hope this helps anyone else with this issue :)

datafieber commented on 2025-06-12 14:10 (UTC) (edited on 2025-06-12 14:14 (UTC) by datafieber)

running mongodb from terminal with this command works for me! mongodb-compass --gtk-version=3 --ignore-additional-command-line-flags

also with the customized gnome startscript unter /usr/share/applications/mongodb-compass.desktop. change the line with "Exec" to Exec=mongodb-compass --gtk-version=3 --ignore-additional-command-line-flags %U

thyagocl commented on 2025-06-12 09:19 (UTC) (edited on 2025-06-12 09:20 (UTC) by thyagocl)

@dpeukert I had a similar issue with Slack some weeks ago and fixed it by following this: https://aur.archlinux.org/packages/slack-desktop#comment-1024447.

But here, I'm getting the error still in the check for the installation of the update, so I don't know how to work around it. Any ideas? :/

By the way, I tried creating a .config/electron-flags.conf with the flag, but it didn't seem to change anything. I'm not sure that already affects the update process.

Bishwajit commented on 2025-06-07 08:11 (UTC)

@dpeukert tried on fresh arch install but same issue

Not found any solution till now

dpeukert commented on 2025-06-07 06:51 (UTC) 

GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported

@DFS, @Bishwajit: This seems to be an upstream Electron/Chromium issue (https://github.com/electron/electron/issues/46538, https://www.electronjs.org/blog/electron-36-0#behavior-changed-gtk-4-is-the-default-when-running-on-gnome), adding --gtk-version=3 to .config/electron-flags.conf should hopefully fix this (can't verify, as I haven't been able to reproduce this).

Bishwajit commented on 2025-06-07 04:15 (UTC) (edited on 2025-06-07 04:15 (UTC) by Bishwajit)

(process:31704): Gtk-ERROR **: 10:04:05.100: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported

==> ERROR: A failure occurred in check().

DFS commented on 2025-06-06 02:20 (UTC)

(process:324634): Gtk-ERROR **: 07:18:44.344: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported

leessmin commented on 2025-05-12 09:19 (UTC)

@dpeukert,Thank you for your hard work

dpeukert commented on 2025-05-12 09:17 (UTC)

@leessmin, @h44z: This package now has the debug flag disabled by default.

1 2 Next › Last »