You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You don't have the right.
start prusa slicer from the terminal with: "sudo ./PrusaSlicer-2.7.4+linux-x64-GTK3-202404050928.AppImage"
Then it is started with root rights and you have full usb access.
You don't have the right. start prusa slicer from the terminal with: "sudo ./PrusaSlicer-2.7.4+linux-x64-GTK3-202404050928.AppImage" Then it is started with root rights and you have full usb access.
I can't run sudo in a kasm container. I've tried adding the user to the dialout group in the image build, but that doesn't seem to work either
You don't have the right. start prusa slicer from the terminal with: "sudo ./PrusaSlicer-2.7.4+linux-x64-GTK3-202404050928.AppImage" Then it is started with root rights and you have full usb access.
I can't run sudo in a kasm container. I've tried adding the user to the dialout group in the image build, but that doesn't seem to work either
It is also quite difficult to give a virtual environment hardware access to the real usb port. a lot can go wrong. i would not flash firmware over it, even if it should work.
virtualbox, for example, has a guest extension for this. I don't know if you have something similar.
The purpose of a virtual environment is actually to decouple it from the main system.
The text was updated successfully, but these errors were encountered: