BeeRef 0.3.3 alpha appimage build (Linux only) #103
Replies: 3 comments 4 replies
-
Beta Was this translation helpful? Give feedback.
-
The issue is that the appimage includes a couple of gtk libs, and when you open the file dialog it wants to open the native Gnome one and runs into incompatible library version issues. I've excluded the offending libraries (as far as I can tell from the error message), assuming that these already exists on a Gnome desktop. Can you try the following build? (This is only fixing the library issue, not the metadata issue.) https://github.com/rbreu/beeref/releases/download/v0.3.3-apha1/BeeRef-0.3.3-alpha2.appimage If all else fails, there's always the option to let BeeRef use built-in QT file dialogs by default and let the user enable native file dialogs via a setting, the same way Krita does it. |
Beta Was this translation helpful? Give feedback.
-
This is an alpha version of the appimage build for the upcoming 0.3.3 version.
The plan is to switch Linux executables over to appimages for upcoming releases. Please report any problems you might have.
Known issues:
On Linux that's running Wayland < 1.19.91, starting BeeRef results in an
undefined symbol: wl_proxy_marshal_flags
error. This is an issue with QT happens regardless of using an appimage, the previous packaged PYInstaler executables, or executing the Python code directly. Workaround:This discussion was created from the release BeeRef 0.3.3 alpha appimage build (Linux only).
Beta Was this translation helpful? Give feedback.
All reactions