Hi all — I think I’ve found a major regression in Bambu Studio 2.5 on Linux AppImage, specifically around Bambu Cloud user preset sync (custom filaments / user presets).
Environment
OS: Ubuntu 24.04.3 LTS (astro-linux)
Install type:AppImage from Bambu Lab GitHub releases
The really bad part: 2.5 “poisons” the profile for 2.4
After running 2.5 once, if I close it and re-launch 2.4 PR-8834 again:
2.4 no longer shows the custom filaments/presets either
The only way to restore normal behavior is:
completely delete ~/.config/BambuStudio
re-launch 2.4, log in, and force a fresh cloud sync download
So 2.5 isn’t only “not syncing”; it seems to modify the local profile into a state where 2.4 can’t see the previously synced presets until you wipe the profile.
Steps to reproduce (simple)
Delete local profile: rm -rf ~/.config/BambuStudio
Run 2.4: Bambu_Studio_ubuntu-24.04_PR-8834.AppImage
Two weeks and nothing changes. I think H2C is my last bambu printer. If they not fix this problems to the end of this month, I sell it and buy Prusa. INDX will be soon here.
Running 2.5.0.66 on Linux (flatpak) and having the same issue. Even when copying the presets into the flatpak folder they get deleted on startup. The only workaround I found now is start the appimage version 2.4, which syncs all presets (printer, filament and process) and export the full bundel. Then start the 2.5 flatpak and import the presets. Now they remain available
The only thing I saw was that the appimage folder with the presets has a setting_id set, the flatpak folder has none set. So maybe the flatpak searches for matches/mismatches on settings_id in the info file and when it doesn’t match it deletes it.
Yeah, as long as we don’t know the logic the BL devs build we are only guessing or have to go over the full source code. But my experience, since they went to 2.x it is a hassle on linux (especially with NVIDIA cards). Had to disable the split lock in the kernel, but still I need to switch windows when opening BS before I see a build plate.
But just to be clear, the Flatpak is not managed by Bambu, it is a seperate developer. But since the removal of the presets happened in 2.5 both on the Flatpak and the Appimage (which is provided by Bambu) the issue is in the source code of Bambu Studio
And to make it even more fun, I have another post on an issue I had with connecting to my printer on a different VLAN. Prior I did not had the issue of presets being deleted until I fixed the issue of my printer being disconnected all the time. From that point on my presets got deleted both from the appimage and the flatpak. So definite a BS 2.5 issue here
The reason I encountered this issue in the first place was was I was essentially forced to build a Linux box to run Bambu Studio with one of my Nvidia cards. I have a PC with a 5090 but lots of other boxes around my lab ranging from 4090’s to a 3090 also running windows. Across all of them with large or complex project, Studio frequently just crashes suddenly and closes the app without warning exclusively when I try to slice a plate. Was driving me nuts but no matter what version of Windows I would build fresh box with (Win 10 or 11) or the version of Nvidia driver the problem persisted.
Then prior to 2.5 I tried Ubuntu on the same hardware and magically everything just worked with 100% stability on anything I would throw at it. Then 2.5 broke Linux…
My take on it is that Windows and MacOS is just the “preferred / supported” standard.
Thanks for the info about 2.4 and restoration of custom filaments. Not the ideal solution but (fir me) an acceptable work around. If I get desperate and HAVE to run the latest version, I can fire up a Windows 11 machine
Problem still exists in latest appimage BambuStudio_ubuntu-24.04_v02.05.02.51-20260327222803.AppImage
