pcbnew segmentation fault on Ubuntu 18.04

Bug #1768174 reported by Stephen Newberry
58
This bug affects 8 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Undecided
Unassigned

Bug Description

I have a brand new install of Ubuntu 18.04 LTS, with Kicad 5.0.0 from the js-reynaud repository. Eeschema works perfect, but when I went to assign a footprint, everything crashed/closed. Attempting to run 'pcbnew' from the terminal results in "Segmentation fault (core dumped)" and nothing opens. I had tried reverting to Kicad 4.0.7, and the same problem exists, so it may be on Ubuntu's side rather than Kicad's.

Thank you,
Stephen

-------------------------------------------------------------------------
Application: kicad
Version: 5.0.0-rc1-44a33f2~62~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.0.2n 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-20-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.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=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON

Revision history for this message
Seth Hillbrand (sethh) wrote :

Are you using the correct .deb for Bionic? It looks like your build has WX_GRAPHICS_CONTEXT OFF, which I think jsreynaud turned off for Bionic.

Changed in kicad:
status: New → Incomplete
Revision history for this message
Stephen Newberry (stn8188) wrote :

I'm not sure which .deb it installed. I have the following ppa installed on my machine: http://ppa.launchpad.net/js-reynaud/kicad-5/ubuntu bionic main

Which I added using the instructions here:
https://forum.kicad.info/t/ppa-for-kicad-5/9746

Is there a way to verify that the correct .deb was installed?

Revision history for this message
Seth Hillbrand (sethh) wrote :

Interesting, it looks like Jean-Samuel has changed his build command for Bionic from the last time I looked. It is once again compiling wxpython and has graphics_context off. And it also looks like it has some very old EESCHEMA flags enabled, so I suspect there is a build hiccup going on.

Please report this to him at https://bugs.launchpad.net/~js-reynaud

See: https://lists.launchpad.net/kicad-developers/msg35387.html

Revision history for this message
Stephen Newberry (stn8188) wrote :

Seth - thanks, I've sent him a message detailing the bug. I appreciate the help.

Revision history for this message
Jean-Samuel Reynaud (js-reynaud) wrote :

I see that KiCad on bionic was still compiled with KICAD_SCRIPTING_WXPYTHON=ON. There is an issue on that with bionic (cause gtk3 and wxpython). I had launch a rebuild without this option.

Let see in few minute if it's fix your issue.

Revision history for this message
Stephen Newberry (stn8188) wrote :

Thank you for the help. I'm still getting segfaults with the following version info:

Application: kicad
Version: 5.0.0-rc1-44a33f2~64~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-20-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
    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_SPICE=ON

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Could you install kicad-dbg from the same repository and try to obtain a backtrace from the crash and post it here? Once kicad-dbg installed, the steps are following:
- run 'gdb pcbnew'
- the prompt execute 'r' command to actually run pcbnew
- once it crashes, type 'bt' to get the backtrace

Revision history for this message
Stephen Newberry (stn8188) wrote :
Download full text (5.0 KiB)

Hello, requested output is below.

Thanks,
Stephen

------------------------------------------------------------------------------

stn8188@desktop:~$ gdb pcbnew
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from pcbnew...Reading symbols from /usr/lib/debug/.build-id/79/df637877b10a3f6381c35757716fc5e5ce3001.debug...done.
done.
(gdb) r
Starting program: /usr/bin/pcbnew
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007fffdef7dbb7 in wxStatusBarBase::CalculateAbsWidths(int) const ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
(gdb) bt
#0 0x00007fffdef7dbb7 in wxStatusBarBase::CalculateAbsWidths(int) const ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#1 0x00007fffdee1da2e in wxStatusBar::DoUpdateFieldWidths() ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#2 0x00007fffdee1dd09 in wxStatusBar::OnSize(wxSizeEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#3 0x00007ffff6d914be in wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#4 0x00007ffff6d915c3 in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#5 0x00007ffff6d9198b in wxEvtHandler::TryHereOnly(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#6 0x00007ffff6d91a13 in wxEvtHandler::ProcessEventLocally(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#7 0x00007ffff6d91a75 in wxEvtHandler::ProcessEvent(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#8 0x00007ffff6d917d7 in wxEvtHandler::SafelyProcessEvent(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#9 0x00007ffff72b566e in wxWindow::DoSetSize(int, int, int, int, int) ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#10 0x00007ffff72f407d in wxStatusBar::Create(wxWindow*, int, long, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
---Type <return> to continue, or q <return> to quit---
#11 0x00007ffff73c4096 in wxFrameBase::OnCreateStatusBar(int, long, int, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#12 0x00007ffff73c4273 in wxFrameBase::CreateStatusBar(int, long, int, wxString const&) () from /usr/lib/x86_64-linux-gnu/libw...

Read more...

Revision history for this message
Seth Hillbrand (sethh) wrote :

Hmm... Something is still pulling in wx_gtk3. This is the likely culprit.

@js-reynaud: For a while you were compiling Bionic with GRAPHIC_CONTEXT=ON This is changed now?

Revision history for this message
Seth Hillbrand (sethh) wrote :

After installing bionic in a VM, I can confirm this but it looks like a build issue where the build is linked against gtk2 but still has the python shell, which pulls in gtk3.

Revision history for this message
Stephen Newberry (stn8188) wrote :

Thanks, is this just a build settings change that can be made (or I could compile myself)?

Changed in kicad:
milestone: none → 5.0.0-rc2
Revision history for this message
Dmitry Me (4x1md) wrote :

I have the same issue with KiCad 4.0.7.

Revision history for this message
Seth Hillbrand (sethh) wrote :

With 4.0.7, please submit the crash reports to Canonical (Ubuntu). This is a library conflict issue.

Revision history for this message
Dmitry Me (4x1md) wrote :

Where exactly can I do it?

Revision history for this message
Seth Hillbrand (sethh) wrote :

You can use the crash reporter that pops up when a program crashes to automatically submit it. You can also submit one here https://bugs.launchpad.net/ubuntu/bionic

Revision history for this message
Dmitry Me (4x1md) wrote :

Done. Bug #1769215. Thanks.

Revision history for this message
Seth Hillbrand (sethh) wrote :

Excellent, thanks! I also filed one against 4.0.7 (https://bugs.launchpad.net/ubuntu/+source/kicad/+bug/1769220) so we'll see if it gets any traction. Fixing either issue will fix both.

Revision history for this message
ccdisle (sim-blk) wrote :

This is also affecting my machine on Ubuntu 18.04. PCBnew and the footprint editor crash.

crash report attached.

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

ccdisle, is it about nightlies or 4.x? I have just installed 18.04 in a VM, together with KiCad nightly from js-reynaud PPA and it works fine. Are you guys still experiencing problems with the nightly builds from PPA?

Revision history for this message
ccdisle (sim-blk) wrote :

I'm running
Version: 4.0.7-e3-6376~60~ubuntu18.04.1, release build
wxWidgets 3.03 Unicode and Boost 1.65.1
Platform: Linux 4.15.0-20-generic x86_64, 64 bit

And yes I'm still getting the same problem.

Revision history for this message
ccdisle (sim-blk) wrote :

If this is not a nightly build I would appreciate instructions on how install it.

Revision history for this message
Dmitry Me (4x1md) wrote :

I run 4.0.7-e2-6376~60~ubuntu18.04.1 release build.
wxWidgets: Version 3.0.3 (debug,wchar_t,compiler with C++ ABI 1011,GCC
Linux 4.15.0-20-generic x86_64, 64 bit, Little endian, wxGTK

Revision history for this message
Stephen Newberry (stn8188) wrote :

I had tried the nightly on the day I reported this bug, and had the same issue. I will try a newer nightly later today and see if it works.

Revision history for this message
Stephen Newberry (stn8188) wrote :

Confirmed that pcbnew opens properly in the nightly listed below:

------------------------------------------------------

Application: kicad
Version: 5.0.0-rc2-dev-unknown-1f5b575~64~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-20-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
    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_SPICE=ON

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Stephen, thank you for reporting back.

ccdisle, check our website [1, "Nightly Development Builds" paragraph] for instructions on how to install nightlies.

1. http://kicad-pcb.org/download/ubuntu/

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

ccdisle, note that v5 differs a lot from v4. Once you modify a design with v5 it may become not compatible with v4. Please back up your files before any modifications.

Revision history for this message
ccdisle (sim-blk) wrote :

Thank you for the information. I will let you know how it goes.

Revision history for this message
ccdisle (sim-blk) wrote :

I just finished installing and testing the nightly build. It launches with no issues at all. This versions is quite an improvement.

I suppose the problem was with the stable version. Since I need to get going I will stick with this release. I'm happy with it.

If there is anything to watch out for I'd appreciate pointers.

Otherwise thanks for the help to everyone who assisted and all the best with fixing the problem for the stable release.

tags: added: packaging ubuntu
Revision history for this message
Jean-Samuel Reynaud (js-reynaud) wrote :

For kicad-4 packaging wxpython is now disabled by default on bionic. It should fix this issue on V4. For V5 (RC) and nightlies it should already ok.

Revision history for this message
Dmitry Me (4x1md) wrote :

~js-reynaud, how can I get the update to the stable release of V4? I tried apt-get upgrade and apt-get install kicad --reinstall and nothing helped.

Revision history for this message
Jean-Samuel Reynaud (js-reynaud) wrote : Re: [Bug 1768174] Re: pcbnew segmentation fault on Ubuntu 18.04

Le 08/05/2018 à 21:36, Dmitry Me a écrit :
> ~js-reynaud, how can I get the update to the stable release of V4? I
> tried apt-get upgrade and apt-get install kicad --reinstall and nothing
> helped.
>

Are you using ppa:js-reynaud/kicad-4
(https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-4) ?
The last version in bionic is 4.0.7+e2-6376~61~ubuntu18.04.1 .
Could you try to remove/add kicad to see what's happend...

Revision history for this message
Dmitry Me (4x1md) wrote :

Remove/add helped. Thank you very much. Now everything works.

Changed in kicad:
status: Incomplete → Fix Released
Revision history for this message
ccdisle (sim-blk) wrote :

Removing and reinstalling worked for me too.

Revision history for this message
Carl (carl-gould) wrote :
Download full text (4.1 KiB)

Just freshly installed Ubuntu 18.04 and Kicad 5 tonight, still having the segmentation fault problem with pcbnew and footprint editor. Backtrace as follows:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Gtk-Message: 22:15:33.730: Failed to load module "canberra-gtk-module"

Program received signal SIGSEGV, Segmentation fault.
0x00007fffdff42bb7 in wxStatusBarBase::CalculateAbsWidths(int) const ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
(gdb) bt
#0 0x00007fffdff42bb7 in wxStatusBarBase::CalculateAbsWidths(int) const ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#1 0x00007fffdfde2a2e in wxStatusBar::DoUpdateFieldWidths() ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#2 0x00007fffdfde2d09 in wxStatusBar::OnSize(wxSizeEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#3 0x00007ffff6b4d4be in wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#4 0x00007ffff6b4d5c3 in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#5 0x00007ffff6b4d98b in wxEvtHandler::TryHereOnly(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#6 0x00007ffff6b4da13 in wxEvtHandler::ProcessEventLocally(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#7 0x00007ffff6b4da75 in wxEvtHandler::ProcessEvent(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#8 0x00007ffff6b4d7d7 in wxEvtHandler::SafelyProcessEvent(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#9 0x00007ffff72b566e in wxWindow::DoSetSize(int, int, int, int, int) ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#10 0x00007ffff72f407d in wxStatusBar::Create(wxWindow*, int, long, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
---Type <return> to continue, or q <return> to quit---
#11 0x00007ffff73c4096 in wxFrameBase::OnCreateStatusBar(int, long, int, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#12 0x00007ffff73c4273 in wxFrameBase::CreateStatusBar(int, long, int, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#13 0x00007fffea3fe9e8 in EDA_DRAW_FRAME::EDA_DRAW_FRAME (this=0x5555574be710,
    aKiway=<optimized out>, aParent=<optimized out>,
    aFrameType=<optimized out>, aTitle=..., aPos=..., aSize=...,
    aStyle=541335104, aFrameName=...) at ./kicad/common/draw_frame.cpp:173
#14 0x00007fffea202c8e in PCB_BASE_FRAME::PCB_BASE_FRAME (this=0x5555574be710,
    aKiway=<optimized out>, aParent=<optimized out>, aFrameType=FRAME_PCB,
    aTitle=..., aPos=..., aSize=..., aStyle=541335104, aFrameName=...)
    at ./kicad/pcbnew/pcb_base_frame.cpp:108
#15 0x00007fffe9e87e94 in PCB_BASE_EDIT_FRAME::PCB_BASE_EDIT_FRAME (
    aFrameName=..., aStyle=541335104, aSize=..., aPos=..., aTitle=...,
    aFrameType=FRAME_PCB, aParent=0x0, aKiway=0x555555810140 <Kiway>, this=
    0x5555574be710) at ./kicad/pcbnew/./pcb_base_edit_frame.h:42
#16 PCB_EDIT_FRAME::PCB_EDIT_FRAME (this=0x55555...

Read more...

Revision history for this message
giuliano (syntaxb) wrote :

After reinstall from js-reynaud everything ok

Revision history for this message
Carl (carl-gould) wrote :
Download full text (3.6 KiB)

Still having problems with the following configuration on 18.04.

Application: kicad
Version: 5.0.0-rc2-dev-unknown-f73b9a5~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-20-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
    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_SPICE=ON

Starting program: /usr/bin/pcbnew
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007fffdeec7bb7 in wxStatusBarBase::CalculateAbsWidths(int) const ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
(gdb) bt
#0 0x00007fffdeec7bb7 in wxStatusBarBase::CalculateAbsWidths(int) const ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#1 0x00007fffded67a2e in wxStatusBar::DoUpdateFieldWidths() ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#2 0x00007fffded67d09 in wxStatusBar::OnSize(wxSizeEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#3 0x00007ffff6b4d4be in wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#4 0x00007ffff6b4d5c3 in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#5 0x00007ffff6b4d98b in wxEvtHandler::TryHereOnly(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#6 0x00007ffff6b4da13 in wxEvtHandler::ProcessEventLocally(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#7 0x00007ffff6b4da75 in wxEvtHandler::ProcessEvent(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#8 0x00007ffff6b4d7d7 in wxEvtHandler::SafelyProcessEvent(wxEvent&) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#9 0x00007ffff72b566e in wxWindow::DoSetSize(int, int, int, int, int) ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#10 0x00007ffff72f407d in wxStatusBar::Create(wxWindow*, int, long, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
---Type <return> to continue, or q <return> to quit---
#11 0x00007ffff73c4096 in wxFrameBase::OnCreateStatusBar(int, long, int, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#12 0x00007ffff73c4273 in wxFrameBase::CreateStatusBar(int, long, int, wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#13 0x00007fffe9383c48 in ?? () from /usr/bin/_pcbnew.kiface
#14 0x00007fffe9187efe in ?? () from /usr/bin/_pcbnew.kiface
#15 0x00007fffe8e0cd94 in ?? () from /usr/bin/_pcbnew.kiface
#16 0x00007fffe8adaf03 in ?? () from /us...

Read more...

Revision history for this message
Carl (carl-gould) wrote :

After a fresh install of Ubuntu 18.04 the nightly build works again for me.

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

As far as I can tell, KiCad already works for all people that have reported problems here.

Revision history for this message
Carl (carl-gould) wrote :

It has since broken again for me, back to segmentation faults when opening pcbnew. The only things that changed since installation are the installation of extra-xdg-menus and libcanberra-gtk-module. Uninstalled them both, uninstalled and reinstalled Kicad, still no difference.

I really don't feel like reinstalling Ubuntu for the third time in two days. Can anyone point me in a useful diagnostic direction? The GDB backtrace is identical to the previous one I posted.

Revision history for this message
Carl (carl-gould) wrote :

Solved my problem. The segfaults happen as soon as I add any third party plugins. Once I remove them from the plugins folder pcbnew works again.

Revision history for this message
Stephen Newberry (stn8188) wrote :

I appreciate the help on this bug - I finally moved back from the nightly ppa to the kicad-5 ppa tonight, and I no longer experience the issue. Unless anyone else objects I'm happy to call this one closed.

Revision history for this message
Michael McCormack (nbxmike) wrote :

I just received the a segmentation fault running pcbnew for the first time on a fresh install of 18.04 using the install from ppa.launchpad.net/js-reynaud/kicad-4/ubuntu. I did not load anything, this was my very first attempt to load a project from another machine. Got a message about changing the libraries then nothing.

I don't think its fixed.

Revision history for this message
Michael McCormack (nbxmike) wrote :

Segmentation fault (core dumped) << what was on the command line, yes ran it from the command so I could see the stdout but does the some invoked from the desktop.

kicad crashed with SIGSEGV in wxStatusBarBase::CalculateAbsWidths() << from crash report.

glad to post more if it will help...

Revision history for this message
Seth Hillbrand (sethh) wrote :

@Michael-

Do you have any plugins installed in your ~/.kicad_plugins directory?

Revision history for this message
Michael McCormack (nbxmike) wrote :

Retract my claim it is still a problem. In pawing through the crash report I find that the Kicad install and ppa reference were not updated when I migrated from 16.04 to 18.04 (FYI 18.04 won't install on and Asus UX303 so I installed 16.04 and upgraded.) After removing the updating the ppa reference and installing the problem is gone.

Revision history for this message
Element Green (jgreen-users) wrote :

This bug says that there is a fix, but I'm using the 5.0.1-stable-201810221457+33cea8e~68~ubuntu18.10.1 package on Ubuntu 18.10 and this bug is still a problem. Same backtrace to wxStatusBarBase::CalculateAbsWidths when any Python plugins are installed to ~/.kicad_plugins. Is there a way to get Python plugins working with pcbnew v5 on Ubuntu?

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Master branch, where we develop 5.1, is supposed to fix Python scripting problems, but be careful - it may contain other bugs, as this is the current development branch. Unfortunately, I cannot propose anything better, as the fix is too large to backport to 5.0 branch, but you should know that we do our best to quickly solve problems appearing in the master branch.

Revision history for this message
Element Green (jgreen-users) wrote :

Thank you for the tip. I may just give that a try, just to be able to run the replicate_layout plugin. Since that seems like a real time saver for certain projects. I'm assuming that 5.0 and 5.1 versions should be interoperable in regards to file formats.

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Yes, the two versions compatible on the file format level. The main goal of the upcoming 5.1 release is to fix Python issues on Linux.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.