Open SIeeepy opened 2 years ago
chunter1
commented
2 years ago Had the same issue and in my case the "Ultimaker-Cura.exe" file was missing after installation. I resolved the problem by choosing a different installation directory (e.g. ...\Ultimaker Cura 5.0.0_test) during the installation process. Hope it helps ;)
SIeeepy
commented
2 years ago Thanks for the help chunter. I've checked, the "Ultimaker-Cura.exe" is not missing and I also have tried different installation locations. To no avail. :( As mentioned the .exe will be executed and the new bright blue loading screen appears and lists all the things it's loading, but the final UI window freezes ("Ultimaker Cura is not responding").
I think your problem was an aggressiv antivirus reaction. I'm using just the internal Windows antivirus. I've also tried to open Cura with deactivated "real time protection" of this Windows antivirus app, without success.
FransBothma
commented
2 years ago Ihave the same Problem on Windows 11. also tried all of the points mentioned above to no avail.
ISHaDoW6I
commented
2 years ago Me as well. Using Windows 11 Home and also have the above issues. Installs just fine but after loading everything it just hangs. Need help, was really looking forward to trying it.
DaveCarrera4
commented
2 years ago Same issue with Windows 11 - new Alienware core i9 32 Gb laptop. Splash screen finishes, main Cura window opens a couple seconds and the message; (Not Responding). Then fan goes all the way to 100% and nothing happens, blank window.
SIeeepy
commented
2 years ago I found out the starting problem for my case (but still have no satisfying solution). Cura 5 seems to have a problem with a multi monitor setup. If I disable output to my second monitor, I can start Cura 5 and run it stable. I did not observe this monitor problem with any other Cura Version. The work around is also not a practical solution, as I’m not willing to sacrifice my second screen just to get an app started. There are some tips, e.g. to uncheck the box in the settings “Restore window position on start”. But this doesn’t help. Checked or unchecked, Cura 5 doesn’t start with a second monitor, previous versions showed no issue.
TheTabe
commented
2 years ago I found out the starting problem for my case (but still have no satisfying solution). Cura 5 seems to have a problem with a multi monitor setup. If I disable output to my second monitor, I can start Cura 5 and run it stable. I did not observe this monitor problem with any other Cura Version. The work around is also not a practical solution, as I’m not willing to sacrifice my second screen just to get an app started. There are some tips, e.g. to uncheck the box in the settings “Restore window position on start”. But this doesn’t help. Checked or unchecked, Cura 5 doesn’t start with a second monitor, previous versions showed no issue.
Same issue here on Windows 11. Just a large white window when I launch it with an external monitor connected to my laptop but when I disconnect/disable the 2nd monitor it launches into the UI as expected.
ISHaDoW6I
commented
2 years ago Can we get this dual monitor glitch fixed? I am not willing to loose my second screen.
FransBothma
commented
2 years ago I found out the starting problem for my case (but still have no satisfying solution). Cura 5 seems to have a problem with a multi monitor setup. If I disable output to my second monitor, I can start Cura 5 and run it stable. I did not observe this monitor problem with any other Cura Version. The work around is also not a practical solution, as I’m not willing to sacrifice my second screen just to get an app started. There are some tips, e.g. to uncheck the box in the settings “Restore window position on start”. But this doesn’t help. Checked or unchecked, Cura 5 doesn’t start with a second monitor, previous versions showed no issue.
Thanks !! Same thing on my windows 11. At least now I can use it an start playing.
DaveCarrera4
commented
2 years ago I found out the starting problem for my case (but still have no satisfying solution). Cura 5 seems to have a problem with a multi monitor setup. If I disable output to my second monitor, I can start Cura 5 and run it stable. I did not observe this monitor problem with any other Cura Version. The work around is also not a practical solution, as I’m not willing to sacrifice my second screen just to get an app started. There are some tips, e.g. to uncheck the box in the settings “Restore window position on start”. But this doesn’t help. Checked or unchecked, Cura 5 doesn’t start with a second monitor, previous versions showed no issue.
Same here. Disconnected 2nd monitor and it loaded on Win 11 Alienware laptop.
ghost
commented
2 years ago Maybe related. My Cura 5 opens then freezes on the working page. I discovered if I press the Maximize button on the top right of the page it starts working.
nallath
commented
2 years ago Can we get this dual monitor glitch fixed? I am not willing to loose my second screen.
We are going to do our best, but we've had little luck getting it to reproduce.
evtrados
commented
2 years ago In case you are using a docking station which connects to your laptop via a USB cable the issue could be because the GPU used on your native screen is NVIDIA and on the monitors connected to the docking station it is defaulting to the default GPU. At least that was the issue I was facing. If that's your setup too, I can add some steps that fix this (hopefully - because I was getting a crash instead of a non-responsive window).
rburema
commented
2 years ago To everyone: Can you also please include your log files? It'll maybe help us pinpoint the problem (or ascertain we're dealing with multiple superficially similar but unrelated problems).
For example, in the original logs attached, these could be 'red herrings' or vital clues:
Could not restore to previous location on screen, since the sizes or number of monitors have changed since thenSIeeepy
commented
2 years ago To everyone: Can you also please include your log files? It'll maybe help us pinpoint the problem (or ascertain we're dealing with multiple superficially similar but unrelated problems).
For example, in the original logs attached, these could be 'red herrings' or vital clues:
- I've noticed that the block with OpenGL vendor / GLSL version doesn't get printed, even though the log says it otherwise detected 4.1 (of OpenGL) -- that is very strange
- Also in the original log is a(/that) line about
Could not restore to previous location on screen, since the sizes or number of monitors have changed since then
Thanks rburema! Here's a current log: sleeepy_cura.log 1) I'm not sure I understand. AFAIK OpenGL is part of the graphic card driver. For testing I switched back to an older Nvidia driver (it didn't help) 2) As mentioned I've experimented also with single monitor setup. So the "sizes or numbers of montitors have changed" seems to be a correct statement.
SIeeepy
commented
2 years ago In case you are using a docking station which connects to your laptop via a USB cable the issue could be because the GPU used on your native screen is NVIDIA and on the monitors connected to the docking station it is defaulting to the default GPU. At least that was the issue I was facing. If that's your setup too, I can add some steps that fix this (hopefully - because I was getting a crash instead of a non-responsive window).
Thanks for the tip. In my case it's just two identical monitors plugged into a standard Geforce GTX 3090. Old Cura thinks this is as very fine setup, new Cura thinks it can't work under these circumstances.
DaveCarrera4
commented
2 years ago Samsung U28E570 monitor via HDMI cable direct into back of Alienware Core i9 laptop w built in NVIDIA GeForce RTX 3070 graphic card. Unplug monitor cable, works. Plug in monitor cable, freezes after splash screen.
rburema
commented
2 years ago @DaveCarrera4 Thanks for the info, could you also please attach the log file.
DaveCarrera4
commented
2 years ago this is from today's load - no monitor plugged in:
2022-05-05 11:43:15,254 - INFO - [MainThread] UM.Qt.QtApplication.init [87]: Adding QT6 plugin path: C:\Program Files\Ultimaker Cura 5.0.0\PyQt6\plugins
2022-05-05 11:43:15,255 - INFO - [MainThread] UM.Qt.QtApplication.init [97]: Adding QT5 plugin path: C:\Program Files\Ultimaker Cura 5.0.0\PyQt6\plugins
2022-05-05 11:43:15,255 - DEBUG - [MainThread] UM.Application.initialize [161]: Initializing Ultimaker Cura
2022-05-05 11:43:15,255 - DEBUG - [MainThread] UM.Application.initialize [162]: App Version 5.0.0-beta+1
2022-05-05 11:43:15,255 - DEBUG - [MainThread] UM.Application.initialize [163]: Api Version 8.0.0
2022-05-05 11:43:15,255 - DEBUG - [MainThread] UM.Application.initialize [164]: Build type None
2022-05-05 11:43:15,255 - WARNING - [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:\Program Files\lib\uranium must be a folder.
2022-05-05 11:43:15,255 - WARNING - [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:\Program Files\lib64\uranium must be a folder.
2022-05-05 11:43:15,255 - WARNING - [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:\Program Files\lib32\uranium must be a folder.
2022-05-05 11:43:15,256 - WARNING - [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:\Program Files\Ultimaker Cura 5.0.0\plugins must be a folder.
2022-05-05 11:43:15,256 - WARNING - [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:\Program Files\Resources\uranium\plugins must be a folder.
2022-05-05 11:43:15,256 - WARNING - [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:\Program Files\Resources\cura\plugins must be a folder.
2022-05-05 11:43:15,256 - DEBUG - [MainThread] UM.Resources.initializeStoragePaths [447]: Initializing storage paths
2022-05-05 11:43:15,256 - DEBUG - [MainThread] UM.Resources.initializeStoragePaths [457]: Config storage path is C:\Users\dcoop\AppData\Roaming\cura\5.0
2022-05-05 11:43:15,256 - DEBUG - [MainThread] UM.Resources.initializeStoragePaths [465]: Data storage path is C:\Users\dcoop\AppData\Roaming\cura\5.0
2022-05-05 11:43:15,256 - DEBUG - [MainThread] UM.Resources.initializeStoragePaths [477]: Cache storage path is C:\Users\dcoop\AppData\Local\cura\5.0\cache
2022-05-05 11:43:15,256 - INFO - [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:\Program Files\Ultimaker Cura 5.0.0\UM..\share\uranium\resources\bundled_packages\uranium.json
2022-05-05 11:43:15,256 - INFO - [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:\Program Files\Ultimaker Cura 5.0.0\share\cura\resources\bundled_packages\cura.json
2022-05-05 11:43:15,256 - INFO - [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:\Program Files\Ultimaker Cura 5.0.0\cura..\share\cura\resources\bundled_packages\cura.json
2022-05-05 11:43:15,257 - INFO - [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:\Program Files\Ultimaker Cura 5.0.0\share\uranium\resources\bundled_packages\uranium.json
2022-05-05 11:43:15,257 - DEBUG - [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [124]: Trying OpenGL context 4.1...
2022-05-05 11:43:15,257 - DEBUG - [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [132]: Yay, we got at least OpenGL 4.1 core: 4.1 Core profile
2022-05-05 11:43:15,257 - DEBUG - [MainThread] UM.Qt.QtApplication.initialize [180]: Detected most suitable OpenGL context version: 4.1 Core profile
2022-05-05 11:43:15,257 - INFO - [MainThread] UM.Qt.QtApplication.initialize [187]: Initializing job queue ...
2022-05-05 11:43:15,257 - INFO - [MainThread] UM.Qt.QtApplication.initialize [191]: Initializing version upgrade manager ...
2022-05-05 11:43:15,257 - INFO - [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:\Program Files\Ultimaker Cura 5.0.0\UM..\share\uranium\resources\bundled_packages\uranium.json
2022-05-05 11:43:15,257 - INFO - [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:\Program Files\Ultimaker Cura 5.0.0\share\cura\resources\bundled_packages\cura.json
2022-05-05 11:43:15,257 - INFO - [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:\Program Files\Ultimaker Cura 5.0.0\cura..\share\cura\resources\bundled_packages\cura.json
2022-05-05 11:43:15,257 - INFO - [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:\Program Files\Ultimaker Cura 5.0.0\share\uranium\resources\bundled_packages\uranium.json
2022-05-05 11:43:15,258 - INFO - [MainThread] UM.PackageManager._loadManagementData [201]: Loaded user packages management file from C:\Users\dcoop\AppData\Roaming\cura\5.0\packages.json
2022-05-05 11:43:15,258 - INFO - [MainThread] UM.PackageManager._removeAllScheduledPackages [280]: Attempting to remove the following scheduled packages: -
2022-05-05 11:43:15,258 - INFO - [MainThread] UM.PluginRegistry.initializeBeforePluginsAreLoaded [121]: Loading plugin configuration file 'C:\Users\dcoop\AppData\Roaming\cura\5.0\plugins.json'
2022-05-05 11:43:15,258 - WARNING - [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:\Program Files\lib\cura must be a folder.
2022-05-05 11:43:15,259 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin FileLogger
2022-05-05 11:43:15,277 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin LocalContainerProvider
2022-05-05 11:43:15,298 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin LocalFileOutputDevice
2022-05-05 11:43:15,314 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CameraTool
2022-05-05 11:43:15,333 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin MirrorTool
2022-05-05 11:43:15,354 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin RotateTool
2022-05-05 11:43:15,375 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin ScaleTool
2022-05-05 11:43:15,392 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SelectionTool
2022-05-05 11:43:15,412 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin TranslateTool
2022-05-05 11:43:15,446 - INFO - [MainThread] UpdateChecker.UpdateChecker.checkNewVersion [68]: Checking for new version
2022-05-05 11:43:15,449 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UpdateChecker
2022-05-05 11:43:15,563 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SimpleView
2022-05-05 11:43:15,644 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin 3MFReader
2022-05-05 11:43:15,670 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin 3MFWriter
2022-05-05 11:43:16,304 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin AMFReader
2022-05-05 11:43:16,339 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraDrive
2022-05-05 11:43:16,454 - INFO - [MainThread] CuraEngineBackend.CuraEngineBackend.init [96]: Found CuraEngine at: C:\Program Files\Ultimaker Cura 5.0.0\CuraEngine.exe
2022-05-05 11:43:16,455 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraEngineBackend
2022-05-05 11:43:16,473 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [188]: Socket state changed to Listening
2022-05-05 11:43:16,490 - INFO - [MainThread] UM.Backend.Backend.startEngine [91]: Started engine process: C:\Program Files\Ultimaker Cura 5.0.0\CuraEngine.exe
2022-05-05 11:43:16,491 - DEBUG - [MainThread] UM.Backend.Backend._backendLog [111]: [Backend] Calling engine with: ['C:\Program Files\Ultimaker Cura 5.0.0\CuraEngine.exe', 'connect', '127.0.0.1:49674', '']
2022-05-05 11:43:16,508 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraProfileReader
2022-05-05 11:43:16,528 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraProfileWriter
2022-05-05 11:43:16,570 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,571 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] Cura_SteamEngine version 5.0.0-beta+1
2022-05-05 11:43:16,572 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] Copyright (C) 2021 Ultimaker
2022-05-05 11:43:16,572 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,572 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] This program is free software: you can redistribute it and/or modify
2022-05-05 11:43:16,573 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] it under the terms of the GNU Affero General Public License as published by
2022-05-05 11:43:16,573 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] the Free Software Foundation, either version 3 of the License, or
2022-05-05 11:43:16,573 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] (at your option) any later version.
2022-05-05 11:43:16,574 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,574 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] This program is distributed in the hope that it will be useful,
2022-05-05 11:43:16,574 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] but WITHOUT ANY WARRANTY; without even the implied warranty of
2022-05-05 11:43:16,575 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2022-05-05 11:43:16,575 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] GNU Affero General Public License for more details.
2022-05-05 11:43:16,575 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,576 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] You should have received a copy of the GNU Affero General Public License
2022-05-05 11:43:16,576 - DEBUG - [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] along with this program. If not, see http://www.gnu.org/licenses/.
2022-05-05 11:43:16,664 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin DigitalLibrary
2022-05-05 11:43:16,664 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [192]: Socket state changed to Connected
2022-05-05 11:43:16,664 - DEBUG - [MainThread] UM.Backend.Backend._onSocketStateChanged [181]: Backend connected on port 49674
2022-05-05 11:43:16,692 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin FirmwareUpdateChecker
2022-05-05 11:43:16,707 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin FirmwareUpdater
2022-05-05 11:43:16,721 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeGzReader
2022-05-05 11:43:16,736 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeGzWriter
2022-05-05 11:43:16,750 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeProfileReader
2022-05-05 11:43:16,777 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeReader
2022-05-05 11:43:16,799 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeWriter
2022-05-05 11:43:16,819 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin ImageReader
2022-05-05 11:43:16,836 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin LegacyProfileReader
2022-05-05 11:43:16,850 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin MachineSettingsAction
2022-05-05 11:43:16,925 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin Marketplace
2022-05-05 11:43:16,942 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin ModelChecker
2022-05-05 11:43:16,957 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin MonitorStage
2022-05-05 11:43:16,979 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PerObjectSettingsTool
2022-05-05 11:43:16,995 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PostProcessingPlugin
2022-05-05 11:43:17,009 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PrepareStage
2022-05-05 11:43:17,024 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PreviewStage
2022-05-05 11:43:17,048 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin RemovableDriveOutputDevice
2022-05-05 11:43:17,080 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SimulationView
2022-05-05 11:43:17,098 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SliceInfoPlugin
2022-05-05 11:43:17,114 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SolidView
2022-05-05 11:43:17,129 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SupportEraser
2022-05-05 11:43:17,143 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin TrimeshReader
2022-05-05 11:43:17,159 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UFPReader
2022-05-05 11:43:17,174 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UFPWriter
2022-05-05 11:43:17,191 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UltimakerMachineActions
2022-05-05 11:43:17,410 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [448]: Plugin [UM3NetworkPrinting] has been disabled. Skip loading it.
2022-05-05 11:43:17,455 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [448]: Plugin [USBPrinting] has been disabled. Skip loading it.
2022-05-05 11:43:17,483 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade21to22
2022-05-05 11:43:17,498 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade22to24
2022-05-05 11:43:17,515 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade25to26
2022-05-05 11:43:17,530 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade26to27
2022-05-05 11:43:17,545 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade27to30
2022-05-05 11:43:17,562 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade30to31
2022-05-05 11:43:17,577 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade32to33
2022-05-05 11:43:17,590 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade33to34
2022-05-05 11:43:17,605 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade34to35
2022-05-05 11:43:17,618 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade35to40
2022-05-05 11:43:17,631 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade40to41
2022-05-05 11:43:17,647 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade411to412
2022-05-05 11:43:17,661 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade413to50
2022-05-05 11:43:17,675 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade41to42
2022-05-05 11:43:17,689 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade42to43
2022-05-05 11:43:17,705 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade43to44
2022-05-05 11:43:17,719 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade44to45
2022-05-05 11:43:17,733 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade45to46
2022-05-05 11:43:17,749 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade460to462
2022-05-05 11:43:17,765 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade462to47
2022-05-05 11:43:17,779 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade47to48
2022-05-05 11:43:17,793 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade48to49
2022-05-05 11:43:17,808 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade49to410
2022-05-05 11:43:17,827 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin X3DReader
2022-05-05 11:43:17,855 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin XmlMaterialProfile
2022-05-05 11:43:17,869 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin XRayView
2022-05-05 11:43:17,902 - ERROR - [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module CuraFreeCADPlugin
2022-05-05 11:43:17,903 - ERROR - [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:17,904 - ERROR - [MainThread] UM.PluginRegistry._findPlugin [729]: File "UM\PluginRegistry.py", line 727, in _findPlugin
2022-05-05 11:43:17,904 - ERROR - [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:17,904 - ERROR - [MainThread] UM.PluginRegistry._findPlugin [729]: File "imp.py", line 245, in load_module
2022-05-05 11:43:17,904 - ERROR - [MainThread] UM.PluginRegistry._findPlugin [729]: File "imp.py", line 217, in load_package
2022-05-05 11:43:17,904 - ERROR - [MainThread] UM.PluginRegistry._findPlugin [729]: File "
ISHaDoW6I
commented
2 years ago My case as well, using 2 identical 32” Samsung smart 4K monitors
Sent from my iPhone
On May 5, 2022, at 11:16 AM, Remco Burema @.***> wrote:
@DaveCarrera4 Thanks for the info, could you also please attach the log file.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
FransBothma
commented
2 years ago To everyone: Can you also please include your log files? It'll maybe help us pinpoint the problem (or ascertain we're dealing with multiple superficially similar but unrelated problems).
I would like to help, where do I find the Log File ?\
SIeeepy
commented
2 years ago To everyone: Can you also please include your log files? It'll maybe help us pinpoint the problem (or ascertain we're dealing with multiple superficially similar but unrelated problems).
I would like to help, where do I find the Log File ?\
for me the path in Win10 is: C:\Users[Username]\AppData\Roaming\cura\5.0 and the file name is cura.log
FransBothma
commented
2 years ago To everyone: Can you also please include your log files? It'll maybe help us pinpoint the problem (or ascertain we're dealing with multiple superficially similar but unrelated problems).
I would like to help, where do I find the Log File ?\
for me the path in Win10 is: C:\Users[Username]\AppData\Roaming\cura\5.0 and the file name is cura.log
ScruffR
commented
2 years ago The issue still persists with the official release and I am not using a secondary monitor (MS Surface Pro 6 and Thinkpad Yoga 17 on Win 10 Pro 64bit) cura.log
nallath
commented
2 years ago The issue still persists with the official release and I am not using a secondary monitor (MS Surface Pro 6 and Thinkpad Yoga 17 on Win 10 Pro 64bit) cura.log
You have an entirely different issue.
2022-06-03 16:23:39,619 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [606]: file:///C:/Program Files/Cura/share/cura/plugins/ModelChecker/ModelChecker.qml:8:1: Type UM.SimpleButton unavailable
2022-06-03 16:23:39,619 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [606]: file:///C:/Program Files/Cura/qml/UM/SimpleButton.qml:28:5: Type RecolorImage unavailable
2022-06-03 16:23:39,619 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [606]: file:///C:/Program Files/Cura/qml/UM/RecolorImage.qml:5:1: The plugin 'C:/Program Files/Cura/qml/QtGraphicalEffects/qtgraphicaleffectsplugin.dll' uses incompatible Qt library. (5.15.0) [release]
2022-06-03 16:23:39,619 - DEBUG - [MainThread] ModelChecker.ModelChecker._createView [127]: Model checker view created.
2022-06-03 16:23:39,619 - DEBUG - [MainThread] SliceInfoPlugin.SliceInfo._createDialog [76]: Creating dialog [MoreInfoWindow.qml]
2022-06-03 16:23:39,635 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [606]: file:///C:/Program Files/Cura/share/cura/plugins/SliceInfoPlugin/MoreInfoWindow.qml:64:13: UM.Label is not a typeThis pretty much looks like you install went wrong somehow. It's almost as if you're mixing two installs of Cura.
Did you perhaps install Cura in the exact same location as where you had Cura 4.13 installed?
ScruffR
commented
2 years ago @nallath, thanks for the reply and you are correct - I did :blush:
I never had an issue with doing that with any of the previous versions - additionally all the previous installs also noticed the fact and asked whether I want the previous version uninstalled before installing the new one, but the 5.0.0 installer did not.
jldavis1969
commented
2 years ago I have this same issue except I have 6 monitors, 3 on a RTX 2060 Super, 3 on a GTX 960.
I have found on another forum (Cura github here) that if you unplug one monitor so that Cura 5.0.0 is moved to another monitor it will work.
In my case, Cura 5.0.0 was on my righthand lower monitor and would go not responding there.
I disconnected said monitor and got Cura 5.0.0 to fully load and work on my middle monitor.
My righthand monitor is connected via the DVI port (Maybe and issue with DVI), My middle and lefthand monitors are connected via the DisplayPort connector. All three monitors are connected to my RTX 2060 Super video card.
I would try my fix if you are using multiple monitors and getting the Not Responding issued described in the above message.
I have added this comment to the Ultimaker forum (Cura 5 Multi Monitor Crash)
majormer
commented
2 years ago For what it is worth, if I change my primary monitor to the monitor Cura has been failing to load on, it will launch fine (Windows 11). Geforce RTX 3070 video card. I run with a 4 monitor setup. Otherwise, I have the same symptoms with a white, non-responsive window as described above. Since having my secondary monitor running as primary is a non-sustainable solution except for maybe quickly klicking off a print job to my OctoPrint server, I'm hoping there is a solution in the future.
Joeydelarago
commented
2 years ago One of our team members have managed to reproduce this bug. We will discuss it.
Specifically the bug caused by trying to display Cura when using the GPU (Nvidia cards it seems). If you can plug you monitor into your motherboards HDMI slot (Not using GPU) and it works normally then this is the same issue you are having.
Thanks for attaching all the logs, they help a lot!
pedrolamas
commented
2 years ago Thanks for following up on this, @Joeydelarago!
Your findings do match my own setup as I use a Dell XPS 15 laptop (with an Intel integrated GPU and a NVIDIA GeForce RTX 3050 discrete GPU).
This has made me wonder if it would make any difference to force Cura to run on either of these GPUs instead of letting Windows automatically handle it...
In my own system, it seems I have it set to use the Nvidia GPU:
pedrolamas
commented
2 years ago ~FWIW, changing from "high performance" (Nvidia GPU) to "power saving" (integrated graphics) has solved the problem for me: Cura 5 has not crashed a single time (nor cause the graphics driver to crash as it did) for the past few days!~
Spoke too soon: just had a crash of the app a few minutes ago...
rburema
commented
2 years ago We're still investigating this. (So it we couldn't fix this in 5.1 yet unfortunately.) At present moment, we have two (other) leads, bot largely outside of our sphere of direct influence:
wiwa5369
commented
2 years ago I've also this problem with dual monitors NVIDIA RTX3060 in Cura V 5.0 and 5.1. My solution for this moment was to edit the cura.cfg found in Windows %APPDATA%\Roaming\cura\5.0 or ...\5.1 Using any Textedit-tool search the line content "windows_left =" and set the value to a x-coord near the outer left side of total screen coordinates, may be 10 or so. While my 2nd monitor is the left one starting coordinates with x=0, shown in NVIDIA Devicesoftware. This works and cura starts on the left (2nd) Screen/monior well.
Programmers may read the cura.cfg anyway on start. Why not put a quick for-the-moment-workaround in the code that forces the start on windows_left = 10 i.e. I.e. C#: Screen.AllScreens[0] ??? (dont know this in py)
Cura freezes if I move it to the right monitor (whatever number it was) and do some essential changes i.e. change the print-density (high to normal or draft). Leave it on the left screen it works. As soon as it touches the second screen it freezes.
Regards
wiwa5369
commented
2 years ago Try this (my workaround in Powershell):
->$line = Get-Content "C:\Users\xxxxx\AppData\Roaming\cura\5.1\cura.cfg" | Select-String "windowleft = " | Select-Object -ExpandProperty Line ->$content = Get-Content "C:\Users\xxxxx\AppData\Roaming\cura\5.1\cura.cfg" ->$content | ForEach-Object {$ -replace $line,"window_left = 1"} | Set-Content "C:\Users\xxxxx\AppData\Roaming\cura\5.1\cura.cfg" ->[System.Diagnostics.Process]::Start("D:\Ultimaker Cura 5.1.0\Ultimaker-Cura.exe")
Cura 5.xxx may start allways with coordinate "windows_left = 1"
regards
MostHostLA
commented
2 years ago Was having very similar issues. Deleting the roaming/cura folder got cura to open again same as disconnecting input from other monitors.
Safe to say the issue is very much still an issue.
wiwa5369
commented
2 years ago Same to me. So I start Cura with my workaround now very fine until solution was implemented.
elradlako
commented
2 years ago Hello. Did any of you find solution? I've used cura 5.1 for a week and then i didn't use it for 2 days. When i tried to launch it got blue loading window then opened to white screen and closed after 3 seconds. Was looking for help online tried to rebooting PC reinstalling cura reinstalling it to other location then tried to install previous version of cura then tried to install prusa slicer, slic3r etc. No slicer works anymore on my PC. And i just have only one display. I really hope someone can help me with this one
wiwa5369
commented
2 years ago Sorry, no idea. Try again deinstall, delete all from %appdata%\Roaming\Cura\5.xx and try an previous Cura version (4.3-4.13 maybe works better?!).
elradlako
commented
2 years ago Sorry, no idea. Try again deinstall, delete all from %appdata%\Roaming\Cura\5.xx and try an previous Cura version (4.3-4.13 maybe works better?!).
Already done that. Uninstalled removed %appdata then installed again not even a bit better. Uninstalled deleted %appdata installed 4.13 didnt work either. Uninstalled installed prusa slicer didnt work etc.
wiwa5369
commented
2 years ago Did you have a System Recovery Point from times before you get this problems then reactivate it. If this not helps or it's not true my ideas are at the end except a full restore or new Winsetup. Maybe you find in other forums some help - Good luck...
wiwa5369
commented
2 years ago I'm not a Cura programmer so I can't help with that. (Seems to be a corrupt install, cause folders and files are missed and printer was not found. Please wait for a spezialist answeres here or post into another or new thread. )
elradlako
commented
2 years ago Okay so i just forced my pc to look for windows update and it found something updated and cura magically started to work after reinstall
elradlako
commented
2 years ago okay so it worked for one day and today got same scenario. However i got no more updates from windows, already reinstalled it few times and cleared all cache. any ideas?
peterashuk
commented
1 year ago Does anyone have a solution to running Cura 5.2.2 with dual monitors ?
TheTabe
commented
1 year ago Stopping the Nahimic service (and setting it to not auto start) worked for me.
MariMakes
commented
1 year ago Quick update on our side for those who are still stuck.
We might have a fix for some of the issues reported here. 🎉 It's a bit hard for us to test, but we have a nightly build available. Can you please try it out and let us know if it resolves your issue?
Application Version
5.0.0 Beta +1
Platform
Windows 10, GeForce RTX 3090
Printer
None (program doesn't start)
Reproduction steps
Install Cura, open Cura.
Actual results
The installation process seems to be successful. After starting Cura the loading screen appears ("loading machines", "loading UI"...), but after Cura switches to the actual larger working window, it stays completely white and does no longer work/respond.
Expected results
Starting Cura
Checklist of files to include
Additional information & file uploads
cura.log
What I've tried to do so far (to no avail): Reinstall to different locations, uninstalling all previous versions, disabling antivirus (Windows defender), deleting all configuration folders under %APPDATA%\cura\, update graphic card driver, update vc_redist x64, installing and opening as administrator.
Previous versions of Cura did work just fine.