-
-
Notifications
You must be signed in to change notification settings - Fork 9
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 fails to start, dead processes still listed by task manager #15182 #35
Comments
Can confirm this is an issue, with this plugin Cura opens successfully only about 30% of the time On MacOS Cura is just active in the Dock with no actual windows open |
Me too. |
Thanks for reporting. I'm looking in to it. The previous version is still available here: |
Strange, the v3.7.1 update is a fairly minor change from v3.7.0. Here are all the code-changes: It would be really nice if you could confirm that 3.7.0 does not exhibits the problem. |
I have (temporarily) removed the plugin from the Marketplace, so users are no longer told to update to this problematic version. |
Please help test this easter-morning hotfix: |
The hotfix works, Cura now opens perfectly fine |
Thanks for the quick test! Unfortunately it is going to take a little while before a new version of the plugin is going to be available in the Marketplace. Any update is tested before it is published, and I assume the Cura team are enjoying Easter. |
+1 The fix seems fine. FYI...I heard from the Tooth Fairy that the Easter Bunny is a myth. |
It looks like there is a possible racecondition caused by the presence of qml/RenameDialog.qml inside a resource searchpath. contributes to #35
Version 3.7.2 is now available in the Marketplace, fixing this issue. |
See: Ultimaker/Cura#15182
It turns out, that this new plugin version 3.7.1 prevents my cura from starting up.
The blue start window from cura shows the last message "Loading UI...", dissapears, and nothing more happens.
Without the MeshTools 3.7.1 all is working well in Cura again.
The text was updated successfully, but these errors were encountered: