piroxxi
commented
3 years ago Hi, I have the exact same issue.
Open gdampf opened 3 years ago
piroxxi
commented
3 years ago Hi, I have the exact same issue.
konskarm
commented
3 years ago Hi @gdampf. From a clean install of 4.7 I am unable to reproduce this. The Creality Ender 3-Pro profile loads whitout issues for me. When you were uninstalling 4.6.2 did you keep your configurations? Could you try deleting 4.6 and 4.7 configurations (assuming you won't lose your data) and then try loading Cura 4.7 again?
gdampf
commented
3 years ago No, I selected to purge them. But, what I found is, that not all profiles were deleted this way. One added for DaVinci Printer, which wasn't included in the clean install, remained and caused this kind of trouble, I guess. Interesting is, that the Version 4.6.2 just ignored the faulty printer description, the 4.7.1 crashed instead. Maybe this is the only issue. I didn't test it completely. I will keep the older version, which is more reliable for a while and may give 4.7.2 a chance, when released.
Von meinem iPad gesendet
Am 14.09.2020 um 11:31 schrieb Konstantinos Karmas notifications@github.com:
Hi @gdampf. From a clean install of 4.7 I am unable to reproduce this. The Creality Ender 3-Pro profile loads whitout issues for me. When you were uninstalling 4.6.2 did you keep your configurations? Could you try deleting 4.6 and 4.7 configurations (assuming you won't lose your data) and then try loading Cura 4.7 again?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Ghostkeeper
commented
3 years ago Hmm, the stack trace indicates pretty much nothing. The Qt GUI framework is getting a segfault, which should never happen unless there is a bug in Qt somewhere.
The window after the anonymous data collection screen is the log-in prompt. So it would appear there is something there that is causing the crash? Only, that screen is basically just an SVG image, some text, two buttons referring to a website when clicked, and a "skip" button. Nothing really special and pretty much a subset of the very first "welcome" screen.
If you purge your profiles, be sure to do that while all versions of Cura are closed. Otherwise it'll indeed re-save some of them when Cura is closed or you change a profile.
ShuzzDE
commented
3 years ago Hi! I'm getting the exact same behaviour with a virtually identical logfile. Funny thing is: The machine I'm getting the error on has been freshly installed from scratch. Empty hard drive, fresh win10 install, fresh Cura download + install --> Crashes at the exact same point.
RickUsingGitHub
commented
3 years ago Same deal. Cleaned out all old versions emptying profiles from %appdata%Cura.
Crashes sometimes at that OP location sometimes next page after that. Subset of my log. `2020-10-04 13:26:23,683 - DEBUG - [MainThread] cura.AutoSave._onTimeout [59]: Autosaving preferences, instances and profiles 2020-10-04 13:26:31,487 - INFO - [MainThread] cura.CuraApplication.writeToLog [595]: User accepted the User-Agreement. Fatal Python error: Segmentation fault
Thread 0x00000e98 (most recent call first): File "C:\Program Files\Ultimaker Cura 4.7\plugins\USBPrinting\USBPrinterOutputDeviceManager.py", line 79 in _updateThread File "threading.py", line 862 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x00002e70 (most recent call first): File "C:\Program Files\Ultimaker Cura 4.7\plugins\RemovableDriveOutputDevice\RemovableDrivePlugin.py", line 61 in _updateThread File "threading.py", line 862 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x00001178 (most recent call first): File "threading.py", line 297 in wait File "zeroconf__init.py", line 2117 in wait File "zeroconf\init__.py", line 1434 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x0000203c (most recent call first): File "threading.py", line 297 in wait File "threading.py", line 549 in wait File "C:\Program Files\Ultimaker Cura 4.7\plugins\UM3NetworkPrinting\src\Network\ZeroConfClient.py", line 81 in _handleOnServiceChangedRequests File "threading.py", line 862 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x000033a4 (most recent call first): File "threading.py", line 297 in wait File "zeroconf__init.py", line 2117 in wait File "zeroconf\init__.py", line 1262 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x00001528 (most recent call first): File "zeroconf__init__.py", line 1183 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x000017c4 (most recent call first): File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\Backend\Backend.py", line 165 in _storeStderrToLogThread File "threading.py", line 862 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x00001eb8 (most recent call first): File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\Backend\Backend.py", line 153 in _storeOutputToLogThread File "threading.py", line 862 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x00000cb4 (most recent call first): File "threading.py", line 293 in wait File "threading.py", line 424 in acquire File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 98 in _nextJob File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 123 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x00001ee8 (most recent call first): File "threading.py", line 293 in wait File "threading.py", line 424 in acquire File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 98 in _nextJob File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 123 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x0000269c (most recent call first): File "threading.py", line 293 in wait File "threading.py", line 424 in acquire File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 98 in _nextJob File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 123 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Thread 0x00001dc4 (most recent call first): File "threading.py", line 293 in wait File "threading.py", line 424 in acquire File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 98 in _nextJob File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\JobQueue.py", line 123 in run File "threading.py", line 914 in _bootstrap_inner File "threading.py", line 882 in _bootstrap
Current thread 0x00000b7c (most recent call first):
File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\UM\Qt\QtApplication.py", line 378 in exec_
File "X:\4.7-exe\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 844 in run
File "X:\4.7-exe\build\inst\bin\cura_app.py", line 234 in
awb95
commented
3 years ago Hi,
I'm having the same problem, but running Cura with my second Graphic Card instead the integrated one solved the problem for me.
doc-Seltsam
commented
3 years ago Hi,
I have the exact same issue, with Cura 4.70 and also 4.71
Win10 64Bit
"Fatal Python error: Segmentation fault"
during initial startup after "help us improving .." screen and before the screen to choose a printer appears.
Cura 4.61 works fine, before the update and after roll back everything.
I tried al lot, cleaning %appdata%, cleaning registry, paused my pi-hole, uninstalled driver, switched off network, ...
But I'm happy with 4.61 so far. I had an backup of my materials and profiles.
doc-Seltsam
commented
3 years ago More or less by chance I found a solution to the problem. Maybe it is just a solution of my problem!
The crash is apparently caused by a problem with my OpenGL driver for the internal Intel HD3000 graphics. The Intel drivers are too old. To fix this, install the "Application Compatibility Tools" from the Microsoft Windows ADK package.
In this tool you give Cura the compatibility fix WIN81RTMVersionLie. Then you start Cura the first time from this tool. This will run it through the initialization. The next times you start Cura as normal.
I have tested with Cura 4.8.
3dmakertech1
commented
3 years ago Outstanding. Works just fine now. Thanks Doc!
cyberws
commented
3 years ago For me this issue was fixed quite easily (given the hints above at to the GPU issue)
I have a laptop with an Intel HD3000 on motherboard and additional 2GB Ram Nvidia GeForce GPU.
Navigate to the location of the Application exe file, most likely C:\Program Files\Ultimaker Cura 4.8.0
When I right click on the Application there is a Run with Graphic Process pop-out menu. Once I have run the program once using the "High Performance NVIDIA processor" option. It seems to run thereafter without issue (not tested following a reboot at this time).
Hope this helps.
Regards,
Phil - I don't have 3D Printer yet, Ender 3 Pro on order, but getting up to speed before it arrives.
tonyctp
commented
3 years ago I had occupied the same issues. It works fine in my linux debian 11 AppImage but win10 workstation failed. After several test, it works fine under my administrator account in win10, it may be caused by specisal account name (I had used chinese as my user name) I hope it will be helpful for you Logs as below, the path is invalid not existed in my disk. 2021-07-18 23:41:29,728 - ERROR - [JobQueueWorker [2]] UM.Logger.logException [116]: File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-exe\build\inst\lib\python3.8\site-packages\UM\Mesh\MeshData.py", line 220, in getExtents 2021-07-18 23:41:29,733 - CRITICAL - [MainThread] cura.CrashHandler.init [66]: An uncaught error has occurred!
Application version 4.7.1
Platform Windows 10 pro 64bit
Printer Crealitiy Ender 3
Reproduction steps
Screenshot(s) Last step
Actual results Crash
Expected results Don't crash
Project file None
Log file
Additional information None