Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#70936 - [cura] Unable to run: No module named 'UM.Qt.Bindings.FileProviderModel'
Attached to Project:
Community Packages
Opened by Bin Jin (bjin) - Tuesday, 18 May 2021, 16:20 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 30 September 2022, 09:50 GMT
Opened by Bin Jin (bjin) - Tuesday, 18 May 2021, 16:20 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 30 September 2022, 09:50 GMT
|
DetailsDescription:
cura-4.9.1 is unable to run, it seems that some file is missing. Original exception was: Traceback (most recent call last): File "/usr/bin/cura", line 195, in <module> from cura.CuraApplication import CuraApplication File "/usr/lib/python3.9/site-packages/cura/CuraApplication.py", line 34, in <module> from UM.Qt.Bindings.FileProviderModel import FileProviderModel ModuleNotFoundError: No module named 'UM.Qt.Bindings.FileProviderModel' Additional info: * version 4.9.1 * upstream issue: https://github.com/Ultimaker/Cura/issues/9859 * upstream maintainer confirms that it's a packaging issue Steps to reproduce: just run cura-4.9.1 |
This task depends upon
Closed by Jelle van der Waa (jelly)
Friday, 30 September 2022, 09:50 GMT
Reason for closing: Deferred
Additional comments about closing: Cura moved to the AUR
Friday, 30 September 2022, 09:50 GMT
Reason for closing: Deferred
Additional comments about closing: Cura moved to the AUR
Install the package community/uranium 4.9.1-1 corrected the issue for me.
Best regards.