Unfortunetly this does not help. No changes after removing my two plugins: MeshTools and OctoPrintPlugin.
My installed python version (most recent for Fedora 38) is: 3.11.6-1.fc38
Edited by Pulsar07
Okay, so it's in the config folder, not a problem with Python, and nothing to do with a plugin.
The obvious next to thing to try is to empty the materials folder and see if that helps, but I've also got an inkling it could be in the main config file (cura.cfg). Open that up and search for "material_name" and delete it (and the semicolon delimiting it from other properties) if it appears anywhere.
the curious is: I have search for it with:
find ~/.local/share/cura -type f -print0 | xargs -0 grep material_name
and the result was NOTHING FOUND
maybe this snippet of the cura.log helps to identify the area:
2023-11-23 13:03:30,072 - DEBUG - [MainThread] UM.Qt.QtRenderer._initialize [211]: Support for Vertex Array Objects: True
2023-11-23 13:03:30,076 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [121]: Initialized OpenGL subsystems.
2023-11-23 13:03:30,076 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [122]: OpenGL Version: 4.6 (Core Profile) Mesa 23.1.9
2023-11-23 13:03:30,076 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [123]: OpenGL Vendor: Intel
2023-11-23 13:03:30,077 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [124]: OpenGL Renderer: Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2)
2023-11-23 13:03:30,077 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [125]: GLSL Version: 4.60.0
2023-11-23 13:03:30,077 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/uranium/resources/shaders/default.shader]...
2023-11-23 13:03:30,078 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/uranium/resources/shaders/selection.shader]...
2023-11-23 13:03:30,079 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/uranium/resources/shaders/select_face.shader]...
2023-11-23 13:03:30,079 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/uranium/resources/shaders/default.shader]...
2023-11-23 13:03:30,080 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/uranium/resources/shaders/composite.shader]...
2023-11-23 13:03:30,081 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/cura/resources/shaders/overhang.shader]...
2023-11-23 13:03:30,082 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/cura/resources/shaders/striped.shader]...
2023-11-23 13:03:30,083 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/cura/resources/shaders/transparent_object.shader]...
2023-11-23 13:03:30,084 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/cura/resources/shaders/striped.shader]...
2023-11-23 13:03:30,085 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [/usr/share/uranium/resources/shaders/platform.shader]...
2023-11-23 13:03:30,108 - DEBUG - [MainThread] cura.Machines.Models.IntentSelectionModel._update [91]: Updating IntentSelectionModel.
2023-11-23 13:03:30,109 - DEBUG - [MainThread] cura.Machines.Models.IntentSelectionModel._update [91]: Updating IntentSelectionModel.
2023-11-23 13:03:30,112 - DEBUG - [MainThread] cura.Machines.Models.IntentSelectionModel._update [91]: Updating IntentSelectionModel.
2023-11-23 13:03:30,147 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [66]: An uncaught error has occurred!
2023-11-23 13:03:30,147 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: Traceback (most recent call last):
2023-11-23 13:03:30,147 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: File "/usr/lib/python3.11/site-packages/UM/Qt/ListModel.py", line 54, in data
2023-11-23 13:03:30,147 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: return self._items[index.row()][self._role_names[role].decode("utf-8")]
2023-11-23 13:03:30,148 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2023-11-23 13:03:30,148 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: KeyError: 'material_name'
2023-11-23 13:03:30,157 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [66]: An uncaught error has occurred!
2023-11-23 13:03:30,158 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: Traceback (most recent call last):
2023-11-23 13:03:30,158 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: File "/usr/lib/python3.11/site-packages/UM/Qt/ListModel.py", line 54, in data
2023-11-23 13:03:30,158 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: return self._items[index.row()][self._role_names[role].decode("utf-8")]
2023-11-23 13:03:30,158 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2023-11-23 13:03:30,158 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: KeyError: 'material_name'
2023-11-23 13:03:30,161 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [66]: An uncaught error has occurred!
2023-11-23 13:03:30,162 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: Traceback (most recent call last):
2023-11-23 13:03:30,162 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: File "/usr/lib/python3.11/site-packages/UM/Qt/ListModel.py", line 54, in data
2023-11-23 13:03:30,162 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: return self._items[index.row()][self._role_names[role].decode("utf-8")]
2023-11-23 13:03:30,162 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That definitely looks like a problem starting up OpenGL... updated your graphics drivers recently?... but that doesn't really explain why getting rid of the config folder fixes it... did you try getting rid of the contents of the materials folder like I suggested?
Cause it might just be time for Whack-A-Mole: Create a copy of the complete config folder. Try deleting one part of the folder, if Cura still doesn't load, restore the original copy (removing some things will mess up other things in the process) and try the next bit.
Sorry I can't be more help but this has got me rather vexated too. About the only thing I've had to learn to get Cura running in Linux (openSUSE Tumbleweed being my distro of choice) is don't try running it as root.
And FWIW, what happens if you try the current version (either 5.5 or the 5.6 beta)? They automatically copy config files over from previous versions.
deleting/emptying the materials folder does not help. After removing all files from the .local/share/cura/5.3/user
folder Cura is starting and asking to setup an new printer.
When I select my printer (a Creality "Ender 5 Pro") Cura immediately crashs with the above shown error traceback!
... and it dosn't matter which printer I try to add. Trying a Anycubic or a UltiMakter printer always the same result: crash with the above shown traceback.
I think this is where I have to bow out and hope @Dustin hears this call for help.
This kind exceeds what I can help with.. I would recommend reporting as bug on github for best support.
You're not alone having this issue, if you get a resolution or post it to another forum could you please post a link here?
Did you look at the log file? There's tons of known issues with simple fixes related to things as diverse as operating system, graphics drivers, bad configuration files, etc.
Please post your log file.
I did look at the log file. I'm running the same OS, the same version of the OS and the same version of Cura. My error message and log file match this almost verbatim. I did a meld between his posted log file and mine and only the time stamps are different.
Finally, I didn't want to hijack someone else's thread.
Sorry that I don't know much about Cura not starting. I'm using ubuntu and it's fine for me. There are 2 different appImage's for linux - did you try them both? One has "modern" in the name, the other doesn't.
14 minutes ago, gr5 said:There are 2 different appImage's for linux - did you try them both? One has "modern" in the name, the other doesn't.
This thread might be about Cura 5.3, but for what it's worth, 5.4 was the last version to have two different AppImages available. 5.5 and up ditched the older one and only has the modern one - now with no need for "modern" in the name - available.
Still think it's worth trying a newer version to see if it has the same problem.
Edited by Slashee_the_Cow-
1
I'm also experiencing this problem with the Fedora RPM version of Cura 5.3.0 on Fedora 38.
I've reported the bug here:
-
1
Thanks for reporting this bug to RedHat.
To get things working (I have to slice some part for my printer ;-)) I use the 5.3 or 5.5 AppImages (UltiMaker-Cura-5.3.0-linux-modern.AppImage / UltiMaker-Cura-5.5.0-linux-X64.AppImage).
Some progress has been made.
https://bugzilla.redhat.com/show_bug.cgi?id=2252195#c18
I think we'll see a fix soon.
- Solution
The new RPMs mentioned at the end of the bugzilla report fix the problem for me. Yippee!
-
1
- gr5 changed the title to Cura 5.3 crashs at startup (linux)
-
Our picks
-
.png.790188cb2d32e3558395d7e5fbc992f3.png)
UltiMaker Cura 5.9 stable released!
ArunC posted a topic in UltiMaker Cura,
Here comes Cura 5.9 and in this stable release we have lots of material and printer profiles for UltiMaker printers, including the newly released Sketch Sprint. Additionally, scarf seams have been introduced alongside even more print settings and improvements. Check out the rest of this article to find out the details on all of that and more-
-
- 5 replies
Picked By
MariMakes, -
-
Introducing the UltiMaker Factor 4
ArunC posted a topic in UltiMaker 3D printers,
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications-
-
- 7 replies
Picked By
MariMakes, -
-
.png.790188cb2d32e3558395d7e5fbc992f3.png)
Recommended Posts
Slashee_the_Cow 541
Try removing just the plugins from the config directory. If that works, then you can put them back in one by one until you find the problem.
Also: have you had any software updates lately that deal with Python? Fedora is the sort of distro which might have upgraded to Python 3.12, but you need to make sure your Python 3.11 packages are still present and working (can't hurt too much to reinstall them just in case)
Link to post
Share on other sites