How to get OrcaSlicer working in qubesOS

Hey!

So I have been trying to get OrcaSlicer working in QubesOS for a little bit with no luck. The software launches but any dropdown would disappear. This isn’t sepeific to QubeOS but a few window managers also have this problem.

This fix requires you to compile the software yourself. It isn’t too complicated and will leave you with a Flatpak. The only thing I haven’t got working is the video stream for my printer (Bambu p1s). I think this is because it requires a proprietary video codac which I haven’t spent time debugging. Never the less, you will now be able to use OrcaSlicer in QubesOS.

This guide will assume you are using Fedora as I haven’t testing this on Debian. It shouldn’t be to hard to build on Debian but you might need to figure out package names.

One thing to note, this is currently fixed in Bambu Studio (which I refuse to use after all the stuff they did), so it should be coming to OrcaSlicer some time soon so it might be worth checking.

When you do have OrcaSlicer installed, if you are using a BambuLabs printer you will have to manually add the printer, when you enter the IP + PIN it will fail and you will have to also enter some other details (there should be a button that appears called something like “Manual Setup”). You will then add the model number, serial and select the model from a dropdown list.

Clone the code

I am using the main branch. OrcaSlicer - Github

Modify two parts of the code

You need to modify these two files:
src/slic3r/GUI/Widgets/PopupWindow.cpp
src/slic3r/GUI/Widgets/PopupWindow.hpp

In each, find and replace topWindowActiavate with topWindowActivate
For vim, you can use :%s/topWindowActiavate/topWindowActivate/g

Install Build Deps

dnf install flatpak-builder fuse

You can do this in your template or in your live VM but, if you do it in the live VM, the packages won’t persist.

Build the RPM

Now you want to navigate to where you cloned the git repo too. You then will want to run:

./build_flatpak.sh -i

This will require 10GB-ish of ram but if you pass the option -j 1 it will limit how many cores it uses. When I was building it without that it would crash the VM. Personally, I set mine to -j 4 and it worked fine but you might have to play around with it.

Done

Now you should have a Flatpak file, you can go ahead and install it. If you don’t have the flatpak stuff setup, you should referance this guide: dataswamp.org’s Artical

Conclusion

I think I should have covered all the steps required to get this working. If you have a problem, please reply and I will try to get back to you.

Sources:

UPDATE: For some reason, the video stream started working. Not sure why.

2 Likes

I’m curious how long the build took with 8GB RAM & 4 cores

Or do you have 16GB, and still throttled to 4 cores?

1 Like

Sorry, so I have 32GB of ram that I assigned 16GB to the build VM. I would recommend running with -j 2. The build probably took like 40~ mins to build on mine. Not sure how long it would take on your machine but I am guessing hour+.

If you have another machine to build on that is more powerful, I would recommend that but you probably can build it on your laptop.

I am going to check the rules of the forum but if it is allowed, I can link to the build I created. Though, people would have to trust my build.

I think the problem was all of the cpu cores being used on the vm causing crashing. Limiting it fixed it.