Launching pcbnew from kicad creates graphical errors for pcbnew then freezes kicad upon close.

[Jt Whissel]

Launching pcbnew from kicad creates graphical errors for pcbnew (See attached image). Then it freezes kicad upon closing pcbnew. Opening up pcbnew externally does not cause any graphical error for pcbnew upon launch. I have purged and reinstalled kicad and the issue persists.

Application: kicad
Version: 5.0.0-rc2-unknown-ca54880~65~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-22-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[Nick Østergaard (nickoe)]

It looks the same as when using wx with gtk2 and wxpython with gtk3. I am not convinced that setting wxpython off in the kicad build config resolves this issue, although it seems to work for some people...

[Nick Østergaard (nickoe)]

I assume this is from the ppa?

[jean-pierre charras (jp-charras)]

This is really strange.

It could be, of course, a gtk3 issue.

But the issue is only if launched by Kicad manager, not as stand alone, and a gtk3 issue does not explain this difference.

[Nick Østergaard (nickoe)]

Yes, it does. That is the exact behavior I see when using wxwidgets with gtk2 and only changing wxpython with gtk2/gtk3.

[Jt Whissel (jtwhissel)]

Any suggestions on to fix this problem if it something I have configured wrong by chance?

[Nick Østergaard (nickoe)]

I think you need to make sure that the ppa is pointing at bionic and not a previous ubuntu release you may have used. Other people have fixed this and crashing issues by reinstalling for the correct target distro.

[Jeff Young (jeyjey)]

Have we concluded that this is indeed the GTK3 issue, or is there more we need to do here?

[Jt Whissel (jtwhissel)]

I have it on bionic and the problems are still there.

On Sun, Jun 3, 2018 at 1:36 PM, Nick Østergaard <email address hidden>
wrote:

> ** Changed in: kicad
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1773019
>
> Title:
> Launching pcbnew from kicad creates graphical errors for pcbnew then
> freezes kicad upon close.
>
> Status in KiCad:
> Incomplete
>
> Bug description:
> Launching pcbnew from kicad creates graphical errors for pcbnew (See
> attached image). Then it freezes kicad upon closing pcbnew. Opening up
> pcbnew externally does not cause any graphical error for pcbnew upon
> launch. I have purged and reinstalled kicad and the issue persists.
>
>
> Application: kicad
> Version: 5.0.0-rc2-unknown-ca54880~65~ubuntu18.04.1, release build
> Libraries:
> wxWidgets 3.0.4
> libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4
> libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
> Platform: Linux 4.15.0-22-generic x86_64, 64 bit, Little endian, wxGTK
> Build Info:
> wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+
> 2.24
> Boost: 1.65.1
> OpenCASCADE Community Edition: 6.9.1
> Curl: 7.58.0
> Compiler: GCC 7.3.0 with C++ ABI 1011
>
> Build settings:
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=ON
> KICAD_SCRIPTING_MODULES=ON
> KICAD_SCRIPTING_WXPYTHON=OFF
> KICAD_SCRIPTING_ACTION_MENU=ON
> BUILD_GITHUB_PLUGIN=ON
> KICAD_USE_OCE=ON
> KICAD_USE_OCC=OFF
> KICAD_SPICE=ON
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1773019/+subscriptions
>

--
From,
Jt Whissel

[Nick Østergaard (nickoe)]

But what does your apt line look like?

[Jt Whissel (jtwhissel)]

I managed to get a trace of the issue. I removed every python package on my system and removed kicad again and reinstalled. I get pcbnew to segfault not instead of just sudo work and then crash kicad.

[Jt Whissel (jtwhissel)]

P.S The "title" was "kicad crashed with SIGSEGV in wxStatusBarBase::CalculateAbsWidths()"

[jean-pierre charras (jp-charras)]

It looks really like Pcbnew has loaded wxPython build with GTK3.

if you Kicad version is built with option:
KICAD_SCRIPTING_WXPYTHON=OFF
Pcbnew does not load wxPython.

But perhaps a python script was loaded and tried to load wxPython.

Have you added some python plugin to your install?

[Jt Whissel (jtwhissel)]

I get the kicad build from the latest nightly build. I do not compile it my self. I will check my scripts folder and see if that is the issue. I attached another stack trace that is different from the last one.

[Jt Whissel (jtwhissel)]

It is my plugins. What did they change to cause this problem? This plugin was working for months and I update kicad everyday

[Seth Hillbrand (sethh)]

If you run plugins that provide a graphical interface, they will generally pull in wxPython. There's not much we can do to prevent this, I think without disable all python scripting.

Since Ubuntu 18.04 does not provide a GTK2 wxPython, it loads GTK3 wx libraries and crashes KiCad. I would guess that the difference now is that you have updated your system from a previous Ubuntu version.