Kicad breaks while creating a new footprint

Hi, I am just creating a simple footprint and Kicad breaks (using the last nightly build on Ubuntu).
Does someone have the same problem?

Steps to Reproduce it:

  1. Launch Footprint Library Editor (from Kicad main window)
  2. File > Set Active Library > “My current library”
  3. New Footprint (from the icon on the toolbar)
  4. Enter Footprint Name (on the New Footprint popup)
  5. ENTER or Ok
    Kicad suddenly closes

Actually, steps 1, 3, 4 and 5 are enough to make it break.


Application: kicad
Version: 5.0.0-rc2-dev-unknown-c867de5~63~ubuntu17.10.1, release build
wxWidgets 3.0.3
libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 (+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-37-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.62.0
Curl: 7.55.1
Compiler: GCC 7.2.0 with C++ ABI 1011

Build settings:

Please report this to the bug tracker

Right, so it is better to put there instead of here, right? Last time i did the opposite, and the guys said to put the issue here first.

Can you give a link to that so I can see who the “gyus” are and what they literally said? Just out of interest…

Doesn’t happen to me. Try opening KiCad from commandline (terminal window) with the command “kicad” and see the output. Is it a segmentation fault? If yes, you can get a core dump and attach it to the report. Otherwise, if nobody is able to reproduce it, it can’t be fixed because nobody has an idea what could be the reason. Usually just going through the source code trying to see if there is a problem doesn’t help.

Edit: I just noticed from another thread that you already now about core dumps.

The name you give the footprint, the name of the library and the path to the lib (in the fp-lib-table. Including what the environment variables are set to if you use one.) might also be of interest.

The issue should be fixed now, than you for the report. It is better to report problems on the bug tracker, as it gives the right means to manage the issues and makes them less likely to become forgotten. Not to mention that the developers get instant e-mail notifications about the problems reported on the bug tracker.

1 Like

Of course, the problem for the average user is to know whether it is a real problem with KiCad, user error or support issue.

In order to avoid noise on the bug tracker, I think it is a good idea to post issues here first, the fact is a lot of issues are known about an frequently encountered. Quite often someone knows a fix or workaround.

Although there is currently a lot of attention paid to new issues, there are lot of old issues on the bug tracker which apparently have never been looked at. I occasionally tried to help out with triaging issues, but Wayne indicated he doesn’t like non-devs responding to bugs, so I stopped doing that.

In the cases of crashes, they should always be reported, but they may already be known. Problems with very recent nightlies are likely to be less well known.

We already have an FAQ entry I found a bug. What now?. I think the suggested practice is to post a quick question here, then if it looks like a new and real issue it can be raised on the bug tracker to hopefully get the attention of devs.

1 Like

Right, I know how to do core dumps and extract the information developers need. But sometimes I don’t have enough time om my day to put all the information ASAP. So, I prefer to say something to avoid forget to report the issue. I believe more reports are better. But you are completely right, I have to add more information.

Oh, I don’t think I have it the same settings anymore. But this gives me a good idea of the problem. I started building my library and everything was ok then after some hours of work the issue appeared. Probably I’ve changed some filenames. I’ve also upgraded my Kicad. I don’t have the issue anymore.

I agree with you and this approach is appreciated, thank you. I just wanted to point out that bugs which are reported exclusively here have a lesser chance to become fixed.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.