Crash on startup with Flatpak + GNOME Platform 48

[jijinbei]

Bambu Studio Version

2.4.0 Public Release

Where is the application from?

Bambu Lab Official website（Flathub（Flatpak）？？？）

OS version

Ubuntu 25.10

Additional system information

No response

Printer

Banbu Lab a1 mini

Printer Firmware Version

01.07.02.00

How to reproduce

1. Install Bambu Studio from Flathub:

flatpak install flathub com.bambulab.BambuStudio

2. Launch the application:

flatpak run com.bambulab.BambuStudio

3. The application crashes immediately during startup.

Notes:

• Forcing X11 does not resolve the issue:

flatpak run --env=GDK_BACKEND=x11 com.bambulab.BambuStudio

• Forcing Qt XCB backend does not resolve the issue:

flatpak run --env=GDK_BACKEND=x11 --env=QT_QPA_PLATFORM=xcb com.bambulab.BambuStudio

• Forcing GTK theme (e.g. Adwaita) does not resolve the issue.

Actual results

The application crashes at startup:

[trace] Initializing StaticPrintConfigs

with the following errors:

GLib-GObject-CRITICAL **: invalid (NULL) pointer instance
GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Gtk-CRITICAL **: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed

No UI window is shown.

Expected results

Bambu Studio should start normally and display the main application window.

Project file & Debug log uploads

• Project file: Not available (application crashes before any project can be created or opened).
• Debug log: Not available. The application crashes before the configuration/log directory ($HOME/.config/BambuStudio/) is created.

Instead, a screenshot captured at the time of the crash is attached.

Checklist of files to include

• Log file
• Project file

Additional clarification about runtime and WebKitGTK dependency

I would like to clarify some points after further investigation.

• The Flatpak package depends on: (confirmed via flatpak info com.bambulab.BambuStudio).

org.gnome.Platform//48

• org.gnome.Platform//48 ships WebKitGTK 4.1, not WebKitGTK 4.0.
• The Linux AppImage builds (including Fedora and Ubuntu variants) and the Flatpak build appear to require

libwebkit2gtk-4.0.so.37

which corresponds to WebKitGTK 4.0 ABI.

• On Ubuntu 25.10, only WebKitGTK 4.1 is available:

libwebkit2gtk-4.1-0

WebKitGTK 4.0 (libwebkit2gtk-4.0.so.37) is not provided by the distribution.

• In Flatpak, users cannot install or downgrade WebKitGTK independently, as it is bundled inside the GNOME runtime.
  Therefore, this issue cannot be worked around on the user side by installing WebKitGTK 4.0.

This suggests an ABI/runtime mismatch between the current Linux builds of Bambu Studio and modern Linux environments
using WebKitGTK 4.1 (both via Flatpak GNOME Platform 48 and recent distributions such as Ubuntu 25.10).

[jijinbei]

#9345
flathub/com.bambulab.BambuStudio#83

[sgieske]

exact same issue here.
Error can be reproduced with flatpak and appimage Version.
OS: Ubuntu 25.10
GNOME 49

[maoztamir]

I have the same issue for some time now, it was not resolved in 2.5.0

[MackBambu]

Will the Bambu Studio AppImage version for Ubuntu 24.04 work normally?

[jijinbei]

No.
The AppImage is built for Ubuntu 24.04 and depends on libwebkit2gtk-4.0.so.37.
On Ubuntu 25.x, only WebKitGTK 4.1 is available, so the AppImage cannot run normally unless the build is updated to support WebKitGTK 4.1.

[doccy-doc]

This has now become a hard blocker for anyone on Fedora 43+, Ubuntu 25+, and other fully up-to-date distributions.

With WebKitGTK 4.0 removed from modern repositories (Fedora 43+, Ubuntu 25+), there is no longer a viable way to run Bambu Studio v2.3+ on a maintained Linux stack. This creates a dependency loop that effectively blocks support for all 2nd-generation hardware (P2S, AMS2, etc.):

• Software requirement: v2.3+ is mandatory for full 2nd-gen hardware support and feature parity.
• Flatpak (v2.3+): Hard-pinned to org.gnome.Platform//48. Since this runtime only provides WebKitGTK 4.1, the binary linked against 4.0 crashes immediately with GLib-GObject-CRITICAL NULL pointer errors.
• AppImage: Fails due to missing libwebkit2gtk-4.0.so.37 (WebKitGTK 4.0, deprecated since 2021).
• Source build: Blocked by the same EOL dependency.

This results in a complete loss of functionality for users with current printers on modern distributions. Alternatives such as OrcaSlicer/PrusaSlicer do not yet provide full 2nd-generation feature parity, so there is presently no workable path on Linux.

Related Issues

• Crash on startup with Flatpak + GNOME Platform 48 #9450 (This issue)
• Flatpak crash on startup with GNOME Platform 48 (GLib-GObject NULL pointer) #9217
• BambuStudio for Fedora (43) #8736
• No display update Fedora 43, Gnome 49 #8724

---

Status Request

Is there an active branch or PR tracking migration to WebKitGTK 4.1?

If so, could you share its status? If not, is there an expected timeline for this work? A status update would clarify whether users on current Linux releases should expect a near-term resolution.

[doccy-doc]

Temporary Workaround

For anyone needing a workaround for the missing AppImage dependencies, here is a temporary solution until the maintainers provide an official fix.

Fedora 43+

You can force dnf to install the missing dependencies by creating a repo file pointing to the Fedora 42 archive:
https://dl.fedoraproject.org/pub/fedora/linux/releases/42/Everything/x86_64/os/
then enabling the repo temporarily to install the webkit2gtk4.0 package.

Ubuntu 25.xx+

A similar approach works by pinning the 24.04 (Noble) repo in apt:
http://archive.ubuntu.com/ubuntu/dists/noble/main
then installing libwebkit2gtk-4.0 directly from the repo.

Important

Use at your own risk. This "Franken-repo" method involves mixing release sources. It is highly recommended to disable or remove these sources immediately after installing the specific missing libraries to avoid system-wide dependency conflicts.

[Swoy]

It is amazing that premium tools like this lacks a stable and widely distributed software stack. Also, the fact that they don't allow us to create our own RFID chips and use a open source network code is going to hurt this company in the long run, but alas. For those that are tired of waiting for the company, here is another route to renewed motivation:

Switching to Platform 47 resolves the crash for now and is to me a much safer workaround.
Both runtimes provide the same soname (libwebkit2gtk-4.1.so.0), so the switch is ABI-compatible. One library
(libhidapi-hidraw.so.0) was added in Platform 48 and is absent in 47, so it needs to be provided separately.

Steps (Fedora 43):

1. Install Platform 47 (still available on Flathub, marked EOL):
   flatpak install flathub org.gnome.Platform//47
2. Copy libhidapi-hidraw.so.0 from Platform 48 to a local directory:

mkdir -p ~/bambu-runtime-fix
cp /var/lib/flatpak/runtime/org.gnome.Platform/x86_64/48/active/files/lib/x86_64-linux-gnu/libhidapi-hidraw.so.0.14.0 ~/bambu-runtime-fix/
ln -sf libhidapi-hidraw.so.0.14.0 ~/bambu-runtime-fix/libhidapi-hidraw.so.0

3. Patch the metadata and add an override (requires root):

sudo sed -i \ -e 's|runtime=org.gnome.Platform/x86_64/48|runtime=org.gnome.Platform/x86_64/47|' \ 
-e 's|sdk=org.gnome.Sdk/x86_64/48|sdk=org.gnome.Sdk/x86_64/47|' \
/var/lib/flatpak/app/com.bambulab.BambuStudio/x86_64/stable/active/metadata                                                                              

Then:

sudo flatpak override --system com.bambulab.BambuStudio \
--filesystem=$HOME/bambu-runtime-fix:ro \
--env=LD_LIBRARY_PATH=$HOME/bambu-runtime-fix

4. Launch normally. No crash.

Caveats:

• flatpak update will revert the metadata when a new app commit is pulled. Re-run the sed command after updates.
• Platform 47 is EOL since October 2025. It will eventually be removed from Flathub.

Tested on Fedora 43, kernel 6.19.7, BambuStudio 2.5.0.66 Flatpak. Runs butter smooth.

[jm355]

I'm getting the same issue on debian arm, the platform 47 workaround did not work for me (i replaced x86_64 with aarch64).