-
Notifications
You must be signed in to change notification settings - Fork 1k
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
3D view broken in own-compiled package, but the one from Debian repo is good #1291
Comments
Hi @VanessaE, The problem is introduce from pyglet as they have released version 2.0 a couple of days before. Unfortunately this version isn't compatible with version 1.xx. I hadn't the time to investigate the source code of panel.py. I have a workaround for this that works for windows and I hope this will work for you as well. Change in requirements.txt the line This take care that you stick to the latest version 1.xx Let me know if this work for you. |
Yep, Printrun has been part of the official Debian repositories since early 2016 (it is in 'main', as it is fully free software :) ). However the package is now almost two years old (early 2021) so it probably lacks a few new additions here and there. (nudge intended to push for a 2.0.0 release, got some features in the oven ready for a 2.1.0 release even :P )
Quick look at your build and runtime logs, there's clearly something going on with pyglet so @DivingDuck is probably on the right track there. The package currently in stable (a.k.a Bullseye or 11) is using Python 3.9, wxWidgets 4.0 and pyglet 1.5. These versions differ from those on your build log. Let me know if I can help you any further. |
@rockstorm101 I would suggest @DivingDuck's fix to Besides, I'm content to use the Debian package, so I won't need to test building that way myself. |
Temporary fix to deal with #1291 until full fix is implemented.
Note to future self: 8fd9b8b introduced a workaround, issue left open until Printrun supports Pyglet >= 2.0. |
Would be good to fix README where it talks about running from sources on Ubuntu/Debian |
Thanks @real-artswan for bringing our attention to this. I'm tempted to even delete the whole Ubuntu/Debian section there. Users of these distributions probably either use the official package or run from source using a virtual environment. I would say this method using a mix of system and PyPI packages is obsolete and probably should not be encouraged. Did you run Printrun using such method? |
It is maybe worth to add requirements.txt in general to the manual build instruction. We we had limit the version beside of pyglet in addition cairosvg and wxpython there as well. |
I gave my PC a much-needed clean-out and reinstall, just to wipe away years' worth of cruft and my own blunders. 😄 I went from a mixed Debian stable+testing setup to a pure install of Debian stable "Bullseye" v11.5.0. The whole reinstall, while time-consuming, went just fine -- by the book.
Of course reinstalling the OS also meant rebuilding and reinstalling my 3d printing toolchain, since underlying libraries will no doubt have changed, but that's where the problem starts.
I can build Pronterface just fine, no obvious errors... compilation Just Works™, though there *still* isn't a suitable Wx wheel that'll work for Bullseye (need v4.1.0 plus cp39), so the system had to compile it.
The whole build seemed to go without incident:
Show build log...
However, when I run it, the plater/gcode preview is only the old top-down 2d view. The program throws errors to the terminal complaining that it can't initialize the 3d view:
Show runtime errors...
(that last message is probably unrelated but I include it here because it says "critical" and repeats about a zillion times)
Googling around has provided no answers, except for some handwaving blaming
numpy
.HOWEVER, I also discovered that Pronterface is in Debian's standard repository (didn't notice if it was from
main
orcontrib
though), currently at version 2.0.0-rc8.I blew away my local Pronterface sources and
apt install
-ed the Debian package. It works completely normally, 100% fine for routine printing (I have not tried things like the excluder or gcode plater but I assume they'd work fine also).So apparently something that works within the Debian packaging environment is silently failing during my build.
One interesting detail, which I mention because it's surely related to WxWidgets being different inside the Debian package compared to what went into my old pre-OS-reinstall build:
The top row buttons ("Load File", "SD", "Print", etc.), and my custom buttons at the bottom of the window, are all a bit larger now than before. Don't change them, though -- now they're just right (they used to be a little too small for my bad eyes and poor dexterity).
@rockstorm101 I was advised to ping you about this.
The text was updated successfully, but these errors were encountered: