Bambu Studio Flatpak -> after Linux updates -> GLib-GObject-Critical

Bambu Lab Software Bambu Studio
1

Hello there,

I am on CachyOS (Linux arch based distro) and due to system updates, I cant launch Bambu Studio anymore. Yesterday it workd like usual, no problems at all.

Unfortunately, I cant rollback the updates from yesterday.

Here is the error, that the terminal shows, if I want to launch Bambu Studio:

[2025-06-20 17:37:35.903947] [0x00007ff5c932b480] [trace] Initializing StaticPrintConfigs
add font of HarmonyOS_Sans_SC_Bold returns 1
add font of HarmonyOS_Sans_SC_Regular returns 1

(process:2): GLib-GObject-CRITICAL **: 17:37:35.949: invalid (NULL) pointer instance

(process:2): GLib-GObject-CRITICAL **: 17:37:35.949: g_signal_handlers_disconnect_matched: assertion ‘G_TYPE_CHECK_INSTANCE (instance)’ failed

I de-installed and re-installed Bambu Studio as flatpak several times. Nothing worked.

Anyone has some ideas?

3 Likes
2

Hey there,

I ran into the same issue.
Deleting the folder “com.bambulab.BambuStudio” in “/home/USER/.var/app/” fixed the issue for me. But I had to configure BambuStudio from scratch. Perhaps it’s possible to save certain config files to preserve those user information but I didn’t really try :sweat_smile:.

1 Like
4

I had the same issue with my Kali installation. Solved it by

rm ~/.config/BambuStudio -rf
rm ~/.cache/bambu-studio -rf

After those 2 commands, I was able to run the appimage, but it did make me set up everything again and reconnect my account.

but, your installation may vary, so I will show you how to determine where your files are. Run this command

find / -iname “*bambu*” 2>/dev/null

This will show you all the folders with the word “Bambu” in them (case-insensitive). From this output you should be able to determine where Bambu stores its files on your hdd.

Hope that helps!

1 Like
5

This is still happening on Kubuntu, at the end of 2026. What I found was that the BambuStudio.conf file is getting corrupted or something. It shows up as 0 B.

I only had to delete that single file. Not the directory. After doing so, started the app and it came right up, creating a new conf file.

I previously synced my settings with Bambu cloud, so no loss.

3 Likes
6

Same here on Fedora 43. Spent all yesterday trying to track down issues after an OS update and then found this thread and saw that my .conf file was also 0 bytes. Deleted and re-ran the appimage and all good again after first run wizard and profile sync