Skip to content
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

Slice faling with 5.8.1 #19885

Open
berrabozz opened this issue Nov 9, 2024 · 3 comments
Open

Slice faling with 5.8.1 #19885

berrabozz opened this issue Nov 9, 2024 · 3 comments
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.

Comments

@berrabozz
Copy link

Cura Version

5.8.1

Operating System

MacOS 15.1

Printer

Ultimaker 2+ Extended

Name abnormal settings

No response

Describe model location

No response

Describe your model

Very simple water tight model

Add your .zip here ⬇️

CasingLid.stl.zip

@berrabozz berrabozz added Slicing Error 💥 A crash is caused by a model or a user interaction. This needs a differnt troubleshooting approach Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Nov 9, 2024
@GregValiant GregValiant added the Status: Needs Info Needs more information before action can be taken. label Nov 10, 2024
@GregValiant
Copy link
Collaborator

Thanks for the report.
We ask for project files and log files because without your settings we often can't duplicate the problem.
This is both right side up and upside down. I could not make it "not slice".
image

@berrabozz
Copy link
Author

berrabozz commented Nov 10, 2024

Hi there. I solved it. It turned out to be the NOD32 Antivirus that for some reason blocked some sockets used between internal components of Cura. NOD32 judged Cura as been infected by some virus. You should look into this, as it might cause issues for others also. Found this WARNING in the log that led me to the solution:

WARNING - [MainThread] UM.Backend.Backend._onSocketError [267]: Unhandled socket error ErrorCode.AcceptFailedError

The Error-code for the user "Unable to slice" without any further details is not very helpful :)

The solution was to add some exceptions in NOD32 for these sockets.

I have used Cura and NOD32 on my mac's for many years... never had these kind of problems before...

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Nov 10, 2024
@GregValiant GregValiant added Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. and removed Status: Triage This ticket requires input from someone of the Cura team Slicing Error 💥 A crash is caused by a model or a user interaction. This needs a differnt troubleshooting approach labels Nov 10, 2024
@GregValiant
Copy link
Collaborator

Good catch.
This was a problem with some previous versions of Cura but I seem to recall the installation was blocked rather than something happening further down the road (like you are getting).
I'll leave the bug label on this. Someone from the Cura team will take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

2 participants