Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slicing hangs indefinitely for some printer models #1547

Closed
phile314-fh opened this issue Mar 16, 2017 · 10 comments
Closed

Slicing hangs indefinitely for some printer models #1547

phile314-fh opened this issue Mar 16, 2017 · 10 comments
Labels
Type: Bug The code does not produce the intended behavior.

Comments

@phile314-fh
Copy link

Application Version: 2.4.0
Platform: Linux NixOS 17.03
Qt: 5.7.1
PyQt: 5.8.1
Display Driver: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2), Mesa 17.0.0

Steps to Reproduce:
Start Cura, add Printer "Ultimaker 2+", Load stl model.

Actual Results:
"Preparing to slice..." text appears in lower right status field, stays there forever.

Expected results:
Slicing should finish.

Additional Information:
Bug seems to be only triggered by certain printers:
Working:

  • Ultimaker Original+
  • Ultimaker 2

Broken:

  • Ultimaker 2+
  • Ultimaker 3

Suspicious log entry:

2017-03-16 17:21:05,608 - CRITICAL - cura.CrashHandler.show [35]: TypeError: unorderable types: NoneType() > int()
2017-03-16 17:21:05,622 - CRITICAL - cura.CrashHandler.show [32]: An uncaught exception has occurred!
2017-03-16 17:21:05,623 - CRITICAL - cura.CrashHandler.show [35]: Traceback (most recent call last):
2017-03-16 17:21:05,623 - CRITICAL - cura.CrashHandler.show [35]:   File "/nix/store/mk9gdgfgwy1q5ydympwwrpy2w9ghr41k-uranium-2.4.0/lib/python3.5/site-packages/UM/Qt/Bindings/MainWindow.py", line 178, in _render
2017-03-16 17:21:05,624 - CRITICAL - cura.CrashHandler.show [35]:     view.beginRendering()
2017-03-16 17:21:05,624 - CRITICAL - cura.CrashHandler.show [35]:   File "/nix/store/jx09rfihvaxg9myx0rsq8wzk97agp2xg-cura-2.4.0/lib/cura/plugins/SolidView/SolidView.py", line 49, in beginRendering
2017-03-16 17:21:05,624 - CRITICAL - cura.CrashHandler.show [35]:     multi_extrusion = global_container_stack.getProperty("machine_extruder_count", "value") > 1

Full Log: https://gist.github.com/phile314-fh/33f013ffacb105c11521a7fb4eebef45
Original NixOS issue: NixOS/nixpkgs#23951

@hroncok
Copy link
Contributor

hroncok commented May 3, 2017

Reproduced.

Application Version: 2.5.0
Platform: Linux Fedora 25
Qt: 5.7.1
PyQt: 5.7.4
Display Driver: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2)

Steps to Reproduce:
Start Cura, add Printer "Ultimaker 3", click "Finish". Try to select Ultimaker form the list of printers on the right.

Actual Results:
The "platform" is gone, the printer name does not show up. Loading STL file does not show it.

Expected results:
Should show the Ultimaker 3 platform, should say "Ultimaker 3" in the select box. Should render STLs.

Additional Information:
Switching back to "Ultimaker 2" works.

Keep repeating in the log:

2017-05-03 17:38:21,419 - CRITICAL - cura.CrashHandler.show [36]: An uncaught exception has occurred!
2017-05-03 17:38:21,419 - CRITICAL - cura.CrashHandler.show [39]: Traceback (most recent call last):
2017-05-03 17:38:21,419 - CRITICAL - cura.CrashHandler.show [39]:   File "/usr/lib/python3.5/site-packages/UM/Qt/Bindings/MainWindow.py", line 183, in _render
2017-05-03 17:38:21,420 - CRITICAL - cura.CrashHandler.show [39]:     view.beginRendering()
2017-05-03 17:38:21,420 - CRITICAL - cura.CrashHandler.show [39]:   File "/usr/lib/cura/plugins/SolidView/SolidView.py", line 53, in beginRendering
2017-05-03 17:38:21,420 - CRITICAL - cura.CrashHandler.show [39]:     multi_extrusion = global_container_stack.getProperty("machine_extruder_count", "value") > 1
2017-05-03 17:38:21,420 - CRITICAL - cura.CrashHandler.show [39]: TypeError: unorderable types: NoneType() > int()

A gif explaining what's happening:

output

@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented May 5, 2017

I can't reproduce this.

My reproduction steps are:

  • Clear all settings.
  • Start Cura.
  • Add Ultimaker 2.
  • Add Ultimaker 3. Click "Finish" on the printer connection menu.

It switches to an Ultimaker 3 as expected. The build volume renders fine. It slices. Everything looks normal.

What reproduction steps are you using? Could you try clearing your settings before you try?

@hroncok
Copy link
Contributor

hroncok commented May 5, 2017

What is the best way to clear all settings?

When I delete .config/cura/cura.cfg and .config/Unknown Organization/cura.cfg, it asks me to add a printer on startup, but I still see the old printers in the selection box.

@hroncok
Copy link
Contributor

hroncok commented May 5, 2017

Ah, .local/share/cura/.

@hroncok
Copy link
Contributor

hroncok commented May 5, 2017

Repeated:

  • Clear all settings.
  • Start Cura.
  • Add Ultimaker 2.
  • Add Ultimaker 3. Click "Finish" on the printer connection menu.
  • Select Ultimaker 3 from the select box on top right.
  • Symptoms as described before are repeated.
2017-05-05 14:54:35,003 - CRITICAL - cura.CrashHandler.show [39]: Traceback (most recent call last):
2017-05-05 14:54:35,003 - CRITICAL - cura.CrashHandler.show [39]:   File "/usr/lib/python3.5/site-packages/UM/Qt/Bindings/MainWindow.py", line 183, in _render
2017-05-05 14:54:35,003 - CRITICAL - cura.CrashHandler.show [39]:     view.beginRendering()
2017-05-05 14:54:35,004 - CRITICAL - cura.CrashHandler.show [39]:   File "/usr/lib/cura/plugins/SolidView/SolidView.py", line 53, in beginRendering
2017-05-05 14:54:35,004 - CRITICAL - cura.CrashHandler.show [39]:     multi_extrusion = global_container_stack.getProperty("machine_extruder_count", "value") > 1
2017-05-05 14:54:35,004 - CRITICAL - cura.CrashHandler.show [39]: TypeError: unorderable types: NoneType() > int()

@hroncok
Copy link
Contributor

hroncok commented May 30, 2017

I can also reproduce this on Fedora 26, Qt 5.8.0, PyQt 5.8, Python 3.6.1.

@Ghostkeeper
Copy link
Collaborator

The reproduce steps couldn't be more clear, but it's still not happening on my side. After adding the Ultimaker 3, it is already selected. I can select it again but nothing happens then because it's already selected, and I get no errors. 😞

@hroncok
Copy link
Contributor

hroncok commented Jun 28, 2017

I cannot longer reproduce this on 2.6.1 🎉

@Ghostkeeper
Copy link
Collaborator

It's still happening sometimes. I just got a report of it today from the System Testing team. But we still don't know how to reproduce it and it seems to happen only 2% of the time or so.

@BagelOrb BagelOrb added the Type: Bug The code does not produce the intended behavior. label Jul 21, 2017
@ianpaschal
Copy link
Contributor

Based on that ^ I don't believe this is significant enough to keep open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

5 participants