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

Prusa Slicer 2.9.0-beta1 crashing if using "Send to Connect" #13773

Closed
2 tasks
Graloth opened this issue Dec 16, 2024 · 2 comments
Closed
2 tasks

Prusa Slicer 2.9.0-beta1 crashing if using "Send to Connect" #13773

Graloth opened this issue Dec 16, 2024 · 2 comments

Comments

@Graloth
Copy link

Graloth commented Dec 16, 2024

Description of the bug

I wanted to give the improved multi-bed slicing a try, but it seems that when trying to upload any sliced file to the printer via the "Send to Connect", instantly crashes the app.

The only way for it not to crash is to save the generated gcode locally and then manually uploading it to Prusa Connect via the browser.

Project file & How to reproduce

  1. Open Prusa Slicer 2.9.0-beta1
  2. Log in to Prusa Connect inside the slicer, if you haven't already
  3. Add any model to be sliced, in my tests I just added a basic cube shape
  4. Slice the model
  5. Click the "Send to Connect"
  6. See that the application instantly crashes, triggering the macOS crash reporter.

Below are linked the crash report generated by macOS, as well as a video showing the exact steps taken (as listed above) to trigger the crash.

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.9.0-beta1

Operating system

macOS Sequoia 15.1.1

Printer model

Prusa MK4S

@SachCZ
Copy link
Collaborator

SachCZ commented Dec 16, 2024

Hello, sorry there has been a mistake when releasing the macOS beta version. Please refer to #13750 (comment)

It should fix your issue. Thank you for your patience.

@Graloth
Copy link
Author

Graloth commented Dec 16, 2024

Hello, sorry there has been a mistake when releasing the macOS beta version. Please refer to #13750 (comment)

It should fix your issue. Thank you for your patience.

Thanks, that did indeed fix it!

@Graloth Graloth closed this as completed Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants