I’m trying to get Bambu Studio running on a new system. I haven’t run it on NixOS before. So far, I’ve tried the version in nixpkgs unstable, which crashes when logging in (this seems to be related to the network plugin as the backtrace goes through there, see bambu-studio: failed to install network library · Issue #391622 · NixOS/nixpkgs · GitHub for some more info). I’ve also tried the version in flatpak on flathub, which is a newer version of Bambu Studio. This one lets me log in, and can see my printer, but it doesn’t actually render anything in the preview, whether loading a .3mf from their online models or a local STL.
Actually, the nixpkgs one doesn’t render stuff either. It’s worth noting that I’m on Wayland, in Niri specifically, using xwayland-satellite.
Anyone have a working setup for this program on NixOS, or for using the bambu printers over the network with some other slicer?
I’d still love to get the one from nixpkgs to run, though. It’s clearly a different issue, though it wouldn’t surprise me if it also has the same 3D rendering issues.
Same here. I’ve tried to rollback to about 2 weeks ago, but rerunning everything still leads to the same error message:
loading network module at /home/andy/.config/BambuStudio/plugins/libbambu_networking.so
after dlopen, network_module is 0xd69b1a0
free(): invalid pointer
Aborted (core dumped)
I’ve removed the plugin directory under ~/.config and it simply redownloads leading to the same result.
Do you know if there is a cached pacakge I could install from Hydra? When searching for bambu-studio I only get 10 results and none is older that 6 days
There is some years old problem that BambuStudio is a for of PrusaSlider and that BambuLab doesn’t really respect the license terms. I didn’t really know that before and found out googling for this question.
Thanks for sharing. Sadly, it did not seem to work for me. Replacing my *.so files with yours leads to Bambu-Studio opening (the GUI opens fine), redownloading network_plugin, and then crashing again.
I ended up doing an aggressive clean up as well so I’m not sure if the overlay alone is sufficient. The cleanup did cause me to lose some history and logged me out of Bambu Studio.
I’ve also tried to compile v2 locally to create a PR on the repo, but compilation fails and is SUPER slow - it always starts from a clean make, which makes trying to fix it a nightmare. I wish there was a way to resume a failed build using whatever the valid objects from the previous compilation attempt
For anyone having the issue with nvidia drivers (and yes, weirdly enough, that includes the network plugin failing to install / crashing as @smolwaffle expected ), I solved my issue with an overlay, inspired by all the answers and clues given above :
I switched to OrcaSlicer. Not really what I wanted since I was happy with Bambu Studio but I gave it a go and it seems to work quite well. Same workflow, same presets, transition went without a hitch. Not really noticing any difference in ease of use or features.
Ahh, interesting - so that’s taking the same env vars that I’ve seen suggested (and that I’m currently using) for the flatpak, but passing them via a shell wrapper instead. I don’t fully understand the driver layering here.
To avoid rebuilding, it should be possible to take the outputs of the bambu-studio and either symlink or copy them into a new derivation, then wrap that. pkgs.symlinkJoin would allow it.
Ah that explains it – just tried it. Thanks anyway, I now know it’s possible to modify a package without copying the package with overlays, so time well spent anyway.
Also @smolwaffle I forgot about OrcaSlicer. I think that’s the better option here anyway. Cheers for the prompt!