-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Upgrading to Qt 5.9.2: Cura doesn't start #2596
Comments
I don't see how upgrading would influence your local files. Backing up those files (and restoring them) should work. I use that myself to set Cura to certain states (I am on fedora, but that shouldn't be an issue). As for the custom scripts; The plugin now only checks in own location for scripts. If anyone has a good suggestion where else it should check, it's not that hard to expand on it. |
i can confirm this issue |
@nallath When I encounter a bug in Cura, I back up these files, then eras them, uninstall and reinstall cura. Just to make sure that my config files are not the problem. But each time I try to restore, it fails, and I have to recreate machines/plugins/settings. Is there any other file/directory I should back up ? How do you back up ? Do you have a script ? |
Looks like you need the |
I can confirm the issue of the missing main window when upgrading to Qt 5.9.2. |
Here is a "clean" print of the console (after removing all user configs temporarily), showing that the issue is not related to the missing zeroconf or bad plugin:
After that, the executable continues to run (so it is no crash) but no mainwindow is shown... |
Thank god, there are more people experiencing this. |
Thought about zeroconf at first, but this stays after I added the module.
|
Yes, this affects all archlinux users who have recently updated. I hope someone from Ultimaker can fix this soon... |
As far as I know, they already fixed it by switching to AppImage. According to the bugreport on bugs.archlinux.org that works. Any other Cura distribution is a community effort, so it is also a community effort to keep them running. |
I'd be more than happy to invest some time to keep this working. Do you have any suggestions where to start looking? Without an error or crash I'd be looking for a needle in a haystack... I'll start by search for changelogs in Qt. |
Also I didn't manage to use custom plugins with the AppImage. Any idea how to do it ? |
Custom plugins can (and should!) be installed to the configuration folder, not inside the application bundle |
And where is that exactly ? With AppImage 2.7, I tried to install my But when I try to use them, it seems I'm using the default |
Ah, you mean postprocessing scripts, not Cura plugins. Yes, sorry, that's a bit of a problem, because they are only read from the application resources. Good point. |
Ah ! Yes the name is a bit ambiguous. Would it require much work to make have a look at |
Regarding the real issue: I verified against qt 5.10.0 and the issue persist. Sooner or later this is going to become an issue for a next appimage too... ;-) @nallath, @fieldOfView, any suggestions where I might start looking? Have you seen such behavior (no crash, but no mainwindow) before or maybe a hunch about where things may go wrong? |
I have neither. My first try would be to see if a minimal pyqt application works. Cura creates a window in QML here: https://github.com/Ultimaker/Cura/blob/master/resources/qml/Cura.qml |
@fieldOfView thanks. I already reverted all changes to qt5-quickcontrols made in 5.9.2 creating a package that is indentical to 5.9.1 (keeping the 5.9.2 version number to fool the version checks) and this results in the same issue. The problem is therefore likely not in quickcontrols. I'll do the same for other qt packages later. |
The MainWindow.py file is loaded but the constructor is indeed never called :s |
Workaround Ultimaker/Cura#2596
When I upgraded to qt 5.9.2 on my MacOS (10.12.6) I experienced this also when running Cura from the commandline. |
@Appesteijn your phrasing suggests that there is another way to start cura that does work? Is that correct? |
No unfortunately I haven't found a solution to get Cura running from the commandline with Qt 5.9.2 |
@Appesteijn The way you particularly stated, that it would not work, when starting it via commandline, suggests you are able to start it, if you don't do it via commandline, eg. a desktop shortcut or something; |
No I can run the download (and the daily builds) perfectly. Only when I run 'master' from source it doesn't work anymore. |
I guess @Appesteijn means that he can run the AppImages... |
I am quite stumped by qt-quicks decision to no longer launch the main window. The python class is run but never called. I have asked around in #qt-quick on freenode but havn't gotten an answer :s |
Just to confirm. This is also a problem on Fedora 27 with Qt 5.9.2 and Cura 3.0.3. |
Maybe related https://bugreports.qt.io/browse/QTBUG-63770 |
These are the packages that I needed to downgrade to in order to get Cura showing again:
|
BTW When reverting a particular commit from Qt, the problem is gone. Identified by Rex Dieter: |
I can confirm that reverting the commit that @hroncok identified makes things work. |
Hi guys, Cura 3 is out for Archlinux. Has anyone tried it ? Is the bug still present ? |
This is relevant for 2.7.0 as well as 3.0.3. (I'm not or Archlinux, but Fedora, however I thought it might help you.) |
@JPFrancoia I just tried Cura 3.0.3-1… I get the splash screen, it disappears, then Cura crashes
|
@protist did you also update uranium package? I have seen that issue when using Cura git with older uranium. |
unexpected keyword argument 'title' is definitely a discrepancy between Cura and Uranium (we added a new property to the message class to accept a message title). |
Ah apologies. It looks like Arch updated Cura but not Uranium. (Related: why is the latest version of Uranium in such small type?) However, when I manually update uranium to 3.0.3, cura now launches perfectly! |
It's small because a git tag was created but no GitHub release (which is sort of a wrapper around git tags if you wanna add release notes and binaries). |
Sorry for the partial update of uranium/curaengine. Arch has also revert the same commit as Fedora did to make cura launch again. Hopefully Qt fixes this in their new release. |
@ChrisTerBeke Thanks for the info. It's quite confusing, especially as the previous version says "Latest release"! @jelly No worries. It's all good now, and thank you for the quick response. |
Looks like a bugfix might be coming up in Qt 5.9.3: https://bugreports.qt.io/browse/QTBUG-64017 |
Yeah — there seems to be a proposed patch set at https://codereview.qt-project.org/#/c/209990/ but I have not had time to test it. |
Arch linux people, is it safe to upgrade Qt and related packages, or not yet ? From what I understand the problem comes from QtDeclarative and there is a new revision: 5.9.2-1 -> 5.9.2-2 |
@JPFrancoia cura starts fine with that version. |
Ok, cura works fine now. The Qt fix in the repo fixed it. Also updated to cura 3, and all works fine. Closing issue. |
I'm on Archlinux. After upgrading to Qt 5.9.2, Cura doesn't start anymore.
I had to downgrade all these packages:
Just to let you know.
I like Cura but every week, an upgrade will break it. I wouldn't mind if I was using it for hobby stuff, but I use it for work almost everyday. I'd like something more stable.
Of course, each time I find a workaround for a bug, I loose all my profiles/machines/settings. Even if I backup
.local/share/cura
and.config/cura
and restore these folders, I never managed to restore my settings.For now I'm going to use the AppImage. It's not ideal because I can't use my custom postProcessing scripts.
Any idea/advice to improve my situation is very welcome.
The text was updated successfully, but these errors were encountered: