Prusa Slicer 2.5.0+dfsg-2 still SIGSEGV's during startup on Bookworm
with some sid.
A local rebuild does also runs into Segfault. However, it also reports
that it is unable to init glew.
I'm quite sure it is a different issue, but the result is quite the
same. So i was unsure if I should open a new Bug.
It *is* a different issue, but related.
Upstream has stated that they're not supporting wxWidgets 3.2 yet:
https://github.com/prusa3d/PrusaSlicer/issues/8299#issuecomment-1236874810
It's probably best to open a new issue covering other wx 3.2
crashes/issues, since a fix for the segfault was already released.
That being said, the comments on the upstream bug report make it sound
like fixes for wx 3.2 will take some time, so it may be best to classify
the new bug report as serious, so it will block the transition of the
broken 2.5.0 package to testing?
