search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
5.96k stars 2.04k forks source link

Fail to import STL files #18892

Open pogechi opened 2 months ago

pogechi commented 2 months ago

Cura Version

5.7.0

Operating System

Linux

Printer

Anycubic Kobra NEO

Reproduction steps

Open File From Disk Select STL file

Actual results

Nothing gets imported

Expected results

Import STL file

Add your .zip and screenshots here ⬇️

Nothing to show

nallath commented 2 months ago

Can you please provide the log files? You can find information where to find them here: https://github.com/Ultimaker/Cura/wiki/Reporting

nilesjohnson commented 2 months ago

I'm having a similar problem; also linux, but with a creality printer. The issue is new with some update in the past few months. Actually, after waiting ~5 minutes, the stl does finally load, and then I can load others instantly.

Searching around, I found this rambling thread that describes similar behavior in September 2023. It concludes with a cryptic comment to disable usb printing. I tried that and, it works! I don't have a printer connected by usb to the computer I use for slicing.

When I check the log files from before I had the plugin disabled, I see thousands of debug messages like the following. Note the timestamps are separated by ,001 seconds or less!?

2024-04-17 05:27:20,090 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289510>>]
2024-04-17 05:27:20,090 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb63f291b0>>]
2024-04-17 05:27:20,091 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289b40>>]
2024-04-17 05:27:20,091 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289480>>]
2024-04-17 05:27:20,091 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb63f29bd0>>]
2024-04-17 05:27:20,091 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289000>>]
2024-04-17 05:27:20,092 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb782896c0>>]
2024-04-17 05:27:20,092 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289630>>]
2024-04-17 05:27:20,092 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289750>>]
2024-04-17 05:27:20,092 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb782897e0>>]
2024-04-17 05:27:20,093 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289870>>]
2024-04-17 05:27:20,093 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289990>>]
2024-04-17 05:27:20,093 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289900>>]
2024-04-17 05:27:20,093 - DEBUG - [MainThread] cura.TaskManagement.OnExitCallbackManager.triggerNextCallback [53]: Scheduled the next on-app-exit callback [<bound method USBPrinterOutputDevice._checkActivePrintingUponAppExit of <USBPrinting.USBPrinterOutputDevice.USBPrinterOutputDevice object at 0x71eb78289a20>>]

Update about my specific version info: I'm using the flatpak version of cura 5.7.0

pogechi commented 2 months ago

Thank you Niles, your suggestion seems to have worked for me as well.

taleroangel commented 2 months ago

I am experiencing the same issue with Cura 5.7.0 (Flatpak) with Linux 6.8.6, booting from an old kernel version (6.7.9) fixes the issue. Might be a kernel compatibility issue