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
Hi,
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
Hello,
it looks like following line should expect the Get() call returning a nullptr,
which wxWidget documentation explicitly notes.
2079
wxTranslations::Get()->SetLanguage(wxLANGUAGE_DEFAULT);
I have raised this question to upstream here:
https://github.com/prusa3d/P
Package: prusa-slicer
Version: 2.5.0+dfsg-1
Followup-For: Bug #1020702
Dear Maintainer,
I have the same issue with prusa-slicer although the backtrace looks a bot
different is seams to be a similar problem:
╰─ gdb prusa-slicer
─╯
GNU gdb (Debian 12.1-3) 12.1
Copyright (C) 2022 Free Software Foun
That seems to be a dead giveaway:
#2 0x7696e0c6 in wxTranslations::SetLanguage (this=0x0,
lang=lang@entry=wxLANGUAGE_DEFAULT) at ./src/common/translation.cpp:1384
I'd expect it to crash when *this* is a null pointer.
Have you reported the issue upstream?
Control: notfound -1 2.4.2+dfsg-1
As the backtrace hinted that direction, I yesterday did a local rebuild using
libwxgtk3.0-gtk3-dev:
This version does NOT segfault.
So I guess there is either a bug in wxwidgets 3.2, or in prusa-slicer which has
been exposed with the new
wxWidgets.
(The versio
Package: prusa-slicer
Version: 2.5.0+dfsg-1
Severity: grave
Justification: renders package unusable
Hi,
the new 2.5.0 prusa-slicer immedialty crashes for me:
tobi@isildor:~$ prusa-slicer
[2022-09-25 18:14:22.532762] [0x7f41f5a0dd40] [trace] Initializing
StaticPrintConfigs
Segmentation fau
7 matches
Mail list logo
