On Wed, Oct 10, 2018 at 09:26:17AM +1300, Olly Betts wrote:
> If we could automate "GDK_BACKEND=x11" (or equivalent via the GDK
> API) in wxwidgets that would be a neater way to address this until
> the upstream code is updated to not require X11, but that seems to
> be tricky to do because we
Control: severity -1 important
On Sat, Sep 29, 2018 at 06:16:05PM +0200, Tobias Frost wrote:
> I think we're seeing https://trac.wxwidgets.org/ticket/17702
> So I will reassign this bug to wxwidgets now...
> As wayland is the default, I increase severity to serious.
The definition of "serious"
Control: severity -1 serious
Control: retitle -1 wxwidgets3.0: wxGLCanvas doesn't work with Wayland
Control: reassign -1 wxwidgets3.0
Control: forwarded -1 https://trac.wxwidgets.org/ticket/17702
Control: affects -1 slic3r
Control: affects -1 slic3r-prusa
I've debugged into it and it seems that
Package: slic3r
Version: 1.3.0+dfsg1-2
Severity: important
Hi,
Slic3r segfaults immediatly after launching.
Triaging into it is seems that the update of wxwidgets
causes this, at least I can reproduce on my other machine
that when I update wxwidgets slic3r begins to fail.
Attached is a gdb
4 matches
Mail list logo
