-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Cura locks up when run on Monitor 2 of a system with 2 monitors. #14268
Labels
Type: Bug
The code does not produce the intended behavior.
Comments
theojt
added
Status: Triage
This ticket requires input from someone of the Cura team
Type: Bug
The code does not produce the intended behavior.
labels
Jan 11, 2023
Hey @theojt, Welcome to the Ultimaker Cura Github 🚀 We've had a number of reports like this. There have already been some workarounds
|
MariMakes
added
the
Status: Needs Info
Needs more information before action can be taken.
label
Jan 16, 2023
github-actions
bot
removed
the
Status: Needs Info
Needs more information before action can be taken.
label
Jan 16, 2023
Hurray! I'm glad to hear your issue is resolved. I'll be closing the ticket, happy printing! |
MariMakes
removed
the
Status: Triage
This ticket requires input from someone of the Cura team
label
Jan 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Application Version
5.2.1
Platform
Windows 11, Ryzen 9 5900, 64GB DDR4, Nvidia GeForce RTX 2060, 2X ASUS 1920x1080 monitors
Printer
Ankermake M5
Reproduction steps
The new window then opens on Monitor 2 and the app freezes once again.
Actual results
As noted above, Cura fails when run on Monitor 2
Expected results
Cura should run without issues on either Monitor 1 or Monitor 2.
Checklist of files to include
Additional information & file uploads
I have received my Ankermake M5 and it seems that a modified version of Cura is used by Anker for its Slicer. This problem also exists within that software (Ankermake v0.9.2_3) though it behaves slightly differently.
The text was updated successfully, but these errors were encountered: