I get a lot of these on LInux (Ubuntu 25.10) using the AppImage. It is especially bad during start-up.
I believe the Bambu Studio problems are related to the network plugin. When I open the appimage for the first time on Ubuntu and configure the program without installing the network plugin, the program appears to work properly. However, as soon as I try to install it, messages appear, either forcing it to close or prompting me to wait. The messages repeat, and the program becomes unusable.
The problems also appear to be related to the use of libraries that aren’t exactly the correct or expected versions.
Before making any changes, it’s recommended to delete the Bambu Studio configuration and cache directory by running the following two commands from the shell:
rm -rf .config/BambuStudio
rm -rf .cache/bambu-studio
So far, I’ve solved it like this:
- If it’s not present, install the libwebkit2gtk library
sudo apt install libwebkit2gtk-4.1-0 - Create symbolic links
sudo ln -sf /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0 /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
and
sudo ln -sf /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.1.so.0 /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18 - Disable Split Lock Mitigation
sudo sysctl -w kernel.split_lock_mitigate=0 - Since the setting that modifies that kernel entry is reset to the default value (i.e., kernel.split_lock_mitigate=1) on every reboot or boot from a powered-off state, you could make it permanent by modifying Grub with:
4a. Edit the /etc/default/grub file and add split_lock_detect=off to GRUB_CMDLINE_LINUX_DEFAULT
4b. Save and update Grub from the shell with
sudo update-grub
4c. Reboot.
4d. Instead of editing the grub file, you can edit the /etc/sysctl.conf file by inserting the line:
kernel.split_lock_mitigate=0
We kindly ask BambuLab to resolve the issue, which is almost certainly related to the network plugin!
Great, thank you it worked
Yes lets hope BambuLab fixes the issue ![]()
I also noticed that when running the Bambu Studio appimage as root, it seems (perhaps) not to be as affected by those messages that render it unusable.
If you want to use the program as a normal user, you might consider running, in addition to the others already described, the following:
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
It worked for me too. Thanks user_893430467.
I was able to fix it with an apparmor config:
vi /etc/apparmor.d/bambu-studio
abi <abi/4.0>,
include <tunables/global>
profile bambu-studio "/path/to/your/Bambu_Studio_*.AppImage" flags=(unconfined) {
userns,
include if exists <local/bambu-studio>
}
sudo systemctl reload apparmor
