[Bug 1157504] New: Cura 4.3.0-1.1 fails to start in newly installed tumbleweed 20191116
http://bugzilla.opensuse.org/show_bug.cgi?id=1157504 Bug ID: 1157504 Summary: Cura 4.3.0-1.1 fails to start in newly installed tumbleweed 20191116 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jaisahn@pusan.ac.kr QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 824726 --> http://bugzilla.opensuse.org/attachment.cgi?id=824726&action=edit Output in command line Cura 4.3.0-1.1 fails to start in tumbleweed 20191116 (fresh installed). Many errors are from python, UM, QtCore, etc. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157504 Oscar Laborda <olaborda@yahoo.es> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olaborda@yahoo.es -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157504 http://bugzilla.opensuse.org/show_bug.cgi?id=1157504#c7 Kevin Adler <zeke@zekesdominion.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zeke@zekesdominion.com --- Comment #7 from Kevin Adler <zeke@zekesdominion.com> --- I'm getting the same error now with Cura 4.8.0-1.1 and python3-qt5-5.15.1-2.1. This seems to have been re-introduced by https://build.opensuse.org/request/show/846237, since it swapped the call to configure.py to use the pyqt_build macro instead, which I suspect passes --debug. Ultimately, though I think this is a bug in Cura. If PyQt5 expects a dictionary object, Cura should be passing a dictionary. Alternatively, PyQt5 could check for non-dictionary objects and return an error/raise a Python exception instead. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157504 http://bugzilla.opensuse.org/show_bug.cgi?id=1157504#c8 --- Comment #8 from Stefan Br�ns <stefan.bruens@rwth-aachen.de> --- Yes, thats correct. For the meantime, you can take python3-qt5 from https://download.opensuse.org/repositories/home:/StefanBruens:/branches:/KDE... Though, thats currently waiting to be built. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157504 http://bugzilla.opensuse.org/show_bug.cgi?id=1157504#c9 --- Comment #9 from Kevin Adler <zeke@zekesdominion.com> --- Thanks, I ended up patching Cura to get around the issue, but ran in to further issues with materials not working properly and ran out of time to debug so I switched to the AppImage. Here's the change I made: diff --git a/cura/API/Account.py b/cura/API/Account.py index 15bccb71e..c81e9a31a 100644 --- a/cura/API/Account.py +++ b/cura/API/Account.py @@ -258,7 +258,7 @@ class Account(QObject): user_profile = self._authorization_service.getUserProfile() if not user_profile: - return None + return {} return user_profile.__dict__ @pyqtProperty(str, notify=lastSyncDateTimeChanged) This does of course break the API docs which says it returns "None if no user is logged in otherwise the logged in user as a dict containing containing user_id, username and profile_image_url", but it seems like PyQt5 does not actually support converting None to a QVariantMap. There are other hits for @pyqtProperty("QVariantMap", ...) so they may also have similar issues, though I did not hit any other crashes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157504 http://bugzilla.opensuse.org/show_bug.cgi?id=1157504#c10 Benjamin Greiner <code@bnavigator.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |code@bnavigator.de --- Comment #10 from Benjamin Greiner <code@bnavigator.de> --- Reported upstream. This is a bug in cura, they should not force QT_NO_DEBUG. https://github.com/Ultimaker/Cura/issues/8875 -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com