PrusaSlicer V 2.9.0 for Linux arrives as a Flatpak, instead of the previous AppImage, which wouldn’t matter except that the Flatpak sandbox prohibits access to anything outside each user’s home directory. I long ago set up access to the fileserver in the basement through filesystems mounted on /mnt, which is now inaccessible.
Obviously, I’m not the first person to hit this issue, as some diligent searching turned up a hint leading to a description of Flatpak permissions, which eventually produced:
sudo flatpak override com.prusa3d.PrusaSlicer --filesystem="/mnt/bulkdata"
Overall, 2.9.0 seems significantly more sluggish and uglier than the 2.8.x series, but at least Prusa still supports Linux.
Just to show PrusaSlicer can fetch files from the server and to have some pictures enhancing this post’s negligible SEO, I built a couple of Gear Fidget Toys:

Which pop off the platform ready to roll:

A trace of silicone grease eased between the pieces on a slip of paper makes the spinning action so smooth.
As usual, the multi-material version takes twice as long to build due to all the filament swapping. I think I must improve the MMU3’s spoolholders, because the MMU3 (very) occasionally fails to ram the filament into the extruder, seemingly due to the force required to pull filament from the recalcitrant spools.
Comments
5 responses to “PrusaSlicer Flatpak: Adding an NFS Filesystem”
You might like to try this one: https://makerworld.com/en/models/898296#profileId-856782
That thing looks like it can’t possibly exist! :grin:
Printed well on my MK4S, spins like a charm!
I’m pretty sure π = 3.000 somewhere in there.
[…] The release notes for PrusaSlicer 2.9 mention the addition of scarf joints on outer perimeters. Smooth joints seem like a Good Idea™, so I turned it on for comparison with a recent object: […]