"STL/OBJ file loading takes too long on Linux" Affected: 5.3.0 to 5.7.2

[kafufafu]

Cura Version

5.3.0 to 5.7.2

Operating System

Ubuntu 24.04 / Dell 5459 core i5 6200u

Printer

AnetA8 and old printers

Reproduction steps

I have discovered a way to replicate the issue:

1. Run any AppImage (from 5.3.0 to 5.7.2).
2. Set AnetA8 as the default printer.
3. Try to open any file using any possible method.
4. Files take up to 3.5 minutes to load.

---

The issue does not occur if the default printer before opening the program is different. (for example, Ultimaker S5).

I'm unaware if the issue affects Mac versions. I don't have any means to verify it. However, it definitely affects the AppImage versions used in Linux.

---

1. I was able to determine that the issue starts in some of the versions 5.3.0.
   (Curiously, the issue does not affect version 5.3.0-alpha+xmas.)

A) 5.3.0 Beta 1 (undetermined as I couldn't run it)
B) 5.3.0 Beta 2 (the issue appears from this version onwards)

Actual results

It takes up to 3.5 minutes to open any type of file.

Expected results

The expected result would be, for example, what version 5.2.2 does ((an instant opening)).

Additional Information/Updates

1. I have just determined through my virtual machine that the issue does not affect Windows 10 or Windows 11 versions. Apparently, the problem is exclusive to Linux users in general.

2. I still don't know if MAC operating systems are affected as well.

[GregValiant]

Thanks for the report and the extra information.
I tried to duplicate this on my Win10 system and it doesn't happen.

Someone from the Cura team will take a look.

[bbczeuz]

Duplicate of #19104; issue is still open.
Workaround: Ultimaker 5.2.2 on Ubunut 24.04 does indeed load STL instantly. As this is a quite old release, possibly export printer profiles from more recent releases and import them to 5.2.2

[sausix]

Sounds like the USB printing issue. Didn't it make into the issues here yet?

Someone found out the USB printing plugin blocks the loading process. You do not need that plugin if you print from a USB drive, Octo or similar anyway.

[gtollini]

This was linked on another issue. Here's the workaround I had found:

I fixed this by disabling USB printing altogether (I've never had an USB printer to begin with). To do that:

* Go to the “Installed” tab of the Marketplace.

* Scroll down to USB Printing and click "disable".

* Restart Cura.

[gtollini]

Thanks for the report and the extra information. I tried to duplicate this on my Win10 system and it doesn't happen.

Someone from the Cura team will take a look.

@GregValiant it isn't duplicable on Windows because the problematic code only runs if Platform.isWindows() returns False. See my fix for this problem, which just skips the problematic code altogether by changing the Platform.isWindows() check to a hard-coded True.

[kafufafu]

This was linked on another issue. Here's the workaround I had found:

I fixed this by disabling USB printing altogether (I've never had an USB printer to begin with). To do that:

* Go to the “Installed” tab of the Marketplace.

* Scroll down to USB Printing and click "disable".

* Restart Cura.

@gtollini
Indeed, that worked (deactivating the USB printing plugin). Thank you for the information; I am truly grateful for the simple solution to this annoying problem ;)

[PeterM7]

Tried your solution on Kubuntu 24.04 running Cura 5.8.1. Cura seemed to load faster but my printing obj. still hasn't loaded.