-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Cura crashes when slicing any object #4
Comments
Are you using an existing config? |
i am! it's the same config as the cura from my windows and macOS machines. my hope was to replace both with this web-based solution |
Looking at your logs though, it could be some dependencies that are missing. What extensions have you got installed? |
yes, the issue is that some extensions require dependencies. the container its of no use for me to use a different config as my printing profiles depend on extensions like elegoo thumbnail generator |
If you provide the dependencies that's needed, we can look at getting them added in. |
here is the list of all my extensions used in cura (working on windows/macos) but causing issues in this container
i appreciate your time and effort! |
If you could provide the error from cura log itself (not the container ones), we might be able to figure out what is missing. |
for future reference, current logs are at @j0nnymoe here are the cura logs: https://justpaste.it/5r6z1 |
Are you able to trim that a bit to the specific time where it crashes please? |
sure:
seems related to a thumbnail generation..
|
Curious, if you start with a fresh config, install the extensions you need, does it crash in the same way? |
@rursache does this tag work? |
on a fresh cura install, the issue is not happening
still fails with the same UI error and this new errors in the logs:
|
Your error seems to be this:
I wonder if this is just a Linux thing, if you are waiting for us to figure out this specific issue with these specific plugins I wouldn't. Not to be a downer but I made this image for another team member that has a 3d printer, my ability to troubleshoot is very limited and basically boils down to clear errors like you posted in your first message in this thread:
That is the sys dep I installed in that development version to get it in sync with bambu studio and orcaslicer from a base packages perspective. You gotta keep digging if you want this to work is all I am trying to say, maybe something more clear than a python error that does not point to anything I can change with the image. |
@thelamer i appreciate the effort. until today I used the i happily migrated to the linuxserver image as i'm a big fan of your work. maybe that container does something special? unfortunately i'm not docker-literate enough to dig into this further 😞 |
You could try running these commands to install all the packages and relaunch cura: (the image has passwordless sudo by default and stuff can be accessed by right clicking the desktop) There is no way that image has GPU acceleration it is simply not possible using a virtual framebuffer (xvfb) and a version of noVNC from 2019, afaik dri3 support is exclusive to KasmVNC, but is Intel and AMD only.
|
oh, I know. never expected it. I was just the reason I wanted to move to the LS container. I managed to find the culprit extension. With "CuraEngineTiledInfill" enabled, the slicing errors occur. with it disabled, it works (both the Not sure if its worth digging into it more however considering its an official extension... you might wanna consider it? It could also collide somehow with the other extensions but I'm glad I got it working in the end. Unsure if I should close the issue or not, please do as you consider. |
I think it is worth running these installs and seeing if it is one of the packages. This is a kitchen sink approach as these commands install a ton of stuff, but it would help us understand if it is a package disconnect:
See if the error still occurs. (prob best to close and open cura after the install of these packages) |
i tried this and it didn't work, the error would be the same as before installing the packages. i also restarted the container after installing the packages |
@rursache looks like this might be known: It might just be a general incompatibility with Bookworm, the image you referenced with noVNC is based on buster. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
Cura crashes when an object is sliced. A container restart is required
Expected Behavior
Cura shouldn't crash
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
docker run -d \ --name cura \ --restart unless-stopped \ --device /dev/dri:/dev/dri \ --security-opt seccomp=unconfined \ -p 3140:3000 \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Europe/Bucharest \ -e TITLE=Cura \ -v /home/radu/.cura:/config \ -v "/media/radu/Media/3D Printing/1. Models":/prints/ \ lscr.io/linuxserver/cura:latest
Container logs
The text was updated successfully, but these errors were encountered: