[Pkg-electronics-devel] Bug#895008: kicad: can't start pcbnew

[Carsten Schoenert]

Hello Aurelien,

On Sat, Apr 07, 2018 at 11:37:25PM +0200, Aurelien Jacobs wrote:
... 
> I've tested this new build, and I can now start pcbnew including with
> latest version python-wxgtk3.0, so this seems to fix the issue. Thanks !

excellent, thanks for testing, I also experienced no segfaulting issues
any more while starting.

> Now this has uncovered another GTK+3 related issue for me in pcbnew.
> If I enable "Modern Toolset (Accelerated)" in the Preferences menu,
> pcbnew segfaults. It looks like it might be related to using
> wxGLCanvasX11 (ie. calling libGLX and libX11) even though this GTK+3
> build is now using Wayland instead of X11.

Hmm, I've no deeper knowledge about the internals of wayland vs. X11 so
I probably can't help much here.
It's known that pcbnew will crash under Wayland and the Modern Toolset
in some cases. Please note the information on

http://kicad-pcb.org/help/known-system-related-issues/#_wayland

As you got a informative backtrace it mayed be a good idea to add this
to the bug report mentioned on the above linked section. As this is now
a different problem to the original bug report here I'd like close this
report by a upload of this rebuilded version of src:kicad and create
later a new report with the backtrace information from you.

If you could spend some time to dig into this new issue under wayland
I'd really appreciate this!

Back to the origin of this report.
Upstream is planning to release a RC2 of KiCad 5 with a string freeze.
The feature freeze was done with RC1 so only bugfixing will be done on
KiCad. I plan to upload these RC2 related version to unstable to get a
broader base for testing. 
I don't have plans to upload a rebuild for KiCad 4.0.7 in unstable.

Regards
Carsten