[3dprinter-general] Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)

Scott Talbert swt at techie.net
Wed Dec 28 17:55:20 GMT 2022

On Tue, 27 Dec 2022, Chow Loong Jin wrote:

> On Wed, Dec 21, 2022 at 06:34:40PM +1300, Olly Betts wrote:
>> On Wed, Dec 21, 2022 at 11:21:03AM +0800, Chow Loong Jin wrote:
>>> I've fixed the segfault by applying the patch from [1], but there's one
>>> issue remaining -- PrusaSlicer fails to initialize GLEW due to [2],
>>> resulting in the plater screen not showing up, same as this SuperSlicer
>>> issue[3].
>>> I've also attempted to roll PrusaSlicer back to wxwidgets3.0
>> Please don't do that.  We're really close to eliminating wxwidgets3.0
>> now, and we're not planning to include it in the bookworm release.
>> We're going to switch to --disable-glcanvasegl in wxwidgets3.2 which
>> should solve the incompatibilities with GLEW which seem to be the
>> problem here.  However that's an ABI breaking change affecting any
>> packages using wxwidgets3.2's OpenGL APIs so it needs coordinating
>> with the release team - Scott is currently working on that.
> Alright, I'll leave the slic3r-prusa as-is then. I'm guessing that a
> binNMU will take care of things when we get there.

wxwidgets3.2 has been rebuilt in unstable with EGL support disabled.  The 
release team skipped the binNMU of slic3r-prusa due to bug #1025827.  If 
you upload the (already merged) fix for that bug, that should take care of 
this rebuild for slic3r-prusa too.


More information about the 3dprinter-general mailing list