Cura hangs completely during "add printer" wizard #15263
Labels
Status: Under Investigation
The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion.
Type: Bug
The code does not produce the intended behavior.
Comments
faern
added
Status: Triage
|
I tried the flatpak install on two other machines now. One with Fedora 36 and one with fedora 37. It works fine on both. So not sure what's broken on my main desktop machine. Could it be something regarding GPU drivers? Because the desktop has a dedicated AMD graphics card, but the other two machines just have intel graphics. |
|
I think I have same issue. It is quite possible that it get stuck in USB printing. Because after deleting config I managed to get it working once. But after one reboot I get this message and right after that it get stuck. That one time that it worked I could see that it was trying different baud rates on /dev/ttyS0 After I run |
2 tasks
|
Same for me. Systeminfo: |
|
Try run |
|
I have tried this already but did not work.. also when I run cura as sudo it's not working. Further my printer is not connected to my PC |
|
Hey @faern, Thanks for your super detailed report 👍 |
MariMakes
added
Status: Under Investigation
|
@MariMakes It really a shame that the Linux support is that bad for Cura. |
This does not work for me. But I'm not ruling out the possibility that it's a USB issue in some way. One of the differences between my working and my non-working computer is the hardware/connected peripherals. |
|
Same here. |
|
Hey @piontec, I recognize your Ubuntu version 🤔 Can you let us know if installing this library works for you? |
|
I had it installed all the time - unfortunately, this changes nothing :| |
|
Still not working with 5.4.0-beta.1-linux-modern.AppImage system: manjaro logs from fresh (no ~/.config/cura and ~/.local/share/cura dirs) |
|
@MariMakes any updates here? |
|
My best guess is that it is related to the USB printing plugin, since it only seems to trigger for machines that have the "supports_usb_connection" as far as I can tell. To validate my suspicion, can people check if adding an Ultimaker 3, s3 or s5 also cause the issue? Since I don't have the issue myself, i can't check it myself :( |
|
@nallath you're the best! it really looks like this is the issue! i have added to my printers profile so please guys... fix the usb printing plugin or at least give an option to disable the broken plugin! |
Well, you can disable it in the marketplace. The problem is that I can't reproduce it (but I'm on Ubuntu, so maybe that's it?), which makes it very hard to figure out what is going on and how to fix it. I've created a PR with some extra logging, i hope that will provide the info we need to fix it. |
|
The PR with the extra debugging statements are merged to main and I started a build for Linux such that you guys can run with this version. Sharing these logs would help @nallath out with figuring out what goes wrong. You can download these artifacts here: https://github.com/Ultimaker/Cura/actions/runs/5552874115 |
|
@jellespijker @nallath and the screen is stuck at "initialize engine..." |
|
but so far workaround: Disable "USB Printing" in marketplace |
|
Can you run And share the output? |
FYI: i don't have my printer connected using USB... i use octoprint, so the printer was and will never be connected using usb |
|
Yeah, i figured. But I'm trying to figure out why the auto detect is hanging itself up on some machines and not others. |
|
@nallath maybe it would be enough to set a timeout for the autodetect to just a few seconds |
|
I can confirm that adding ultimaker 3 worked without issues, only adding my networked ender 3 with octorpint seems to be an issue |
It already has a timeout. The auto-detect also happens in a separate thread, so it shouldn't block the application itself. I'm at a bit of a loss what is exactly causing it to hang... |
|
So, one more thing that people might be able to try. It does require changing a part of the code. Can people check if removing these lines try:
programmer.connect(self._serial_port)
serial = programmer.leaveISP()
except ispBase.IspError:
programmer.close()make the problem go away. |
|
Yes it does work when commented. |
|
I narrowed it down to the flush statement here: Cura/plugins/USBPrinting/avr_isp/stk500v2.py Line 142 in bb79282 If the flush is removed, cura does not hang. cura.working.log Maybe related? |
|
Hi @MarcoCLA, Would you mind sharing the output of the following commands : For the record, we have added a ticket to the backlog with the intent to improve this. |
|
Two devices cause it to hang on my system.
Looks like some IPMI interface. |
|
Hi @MarcoCLA, Thanks for the report ! You do have some serial devices on your system, which may be linked to your problem, depending on how they react to what Cura is doing at startup. I still have to find the best way to fix this without breaking the USB printing support. In the meantime, can you try starting cura with the following environment variable :
That should completely stop opening the USB ports, and hopefully allow you to use Cura normally. |
|
Well, from what I can tell, @MarcoCLA your theory really seems to make sense. The method Now there are many possibles ways for us to fix this. I'll discuss them with the team to find the most appropriate one. |
|
Hey @MarcoCLA, could you please test this AppImage ? It should fix your issue without breaking USB support. If you can't start it with your distribution, just tell me and I'll make a new one with different options. |
|
Sorry, the link won't work for you.. You can download the file here |
|
Do you also happen to have a patch file for me? Then I can apply it locally. |
|
Oh sure, you may want to apply it manually, it is just somes lines of code removed : 8f4dec2 |
|
This patch solves this issue. |
|
Great, thanks for the feedback ! It will be included in the next Cura release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Application Version
5.3.0 (and 5.4.0-alpha)
Platform
Fedora Linux 37
Printer
Voron 2.4 350mm (and many others)
Reproduction steps
Actual results
Cura will lock up completely at this stage. Or if lucky it will add the printer, go back to show the print bed and then lock up a few seconds later.
Expected results
I should be able to add printers without issue.
Checklist of files to include
Additional information & file uploads
I'm on Fedora 37. I have tried:
QT_QPA_PLATFORM=xcb.There is no
cura.logstored at~/.local/share/cura/5.3/cura.log. I don't know what happened. I had one, but then I deleted it to get a new fresh log to upload. But now no new logs are generated.When running from a terminal I have the following output from Cura. But all this output is printed long before the lockup:
The text was updated successfully, but these errors were encountered: