KiCad

Crash (Possibly Gnome crash?)

Bug #1851231 reported by Frank Severinsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Unknown

Bug Description

Hi Guys

This might be a 19.10 and/or gnome specific issue, but there are probably some more competent people here to decide.

OBS! Dual screen setup needed to provoke this

Steps to reproduce:
Open Kicad
Open "Symbol Editor"
Open any symbol
Press "Edit symbol Properties"
Press the Footprint browse icon
Press "Select footprints to browse"
crash

If all windows are opened on the same screen, there is no crash.
If any windows are moved to the other screen, the crash occurs.

Application: KiCad
Version: 5.1.5-rc1-unknown-37f23fa~84~ubuntu19.10.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.9.0/openssl/zlib nghttp2/1.39.2 librtmp/2.3
Platform: Linux 5.3.0-19-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.65.3
    Compiler: GCC 9.2.1 with C++ ABI 1013

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

Revision history for this message
Frank Severinsen (shack) wrote :

Please see attached video.

Revision history for this message
Nick Østergaard (nickoe) wrote :

Did you update your ubuntu recently? Maybe it is a video driver issue and you may need to reboot.

But other than that could you please try to fetch the backtrace?

It looks like you are using the daily ppa for the 5.1 branch and as far as I can tell it installs the kicad binary to /usr/bin/kicad. Please try to run gdb on the executable or pcbnew or whatever fails like:

  gdb /usr/bin/kicad

1. Then type 'r' for run
2. Then do the thing that makes it crash
3. Go back to the terminal where you ran gdb, you should be able to type 'bt' for backtrace to get the backtrace.
4. Attach the backtrace to a comment here.

Michael Kavanagh (michaelkavanagh)
Changed in kicad:
status: New → Incomplete
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2579

Changed in kicad:
status: Incomplete → Expired
Bug Watch Updater (bug-watch-updater)
Changed in kicad:
importance: Undecided → Unknown
status: Expired → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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