Unable to open eagle footprint lib, No error message just empty footprint editor

Bug #1731802 reported by Rene Poeschl
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Medium
Unassigned

Bug Description

In a recent nightly i can not open a eagle test lib of mine. (Created with eagle 6)
I can open the same lib in kicad 4.0.6 (So it might be related to the new eagle import stuff.)

More details can be found on the user forum (The user originally asked about importing old kicad files until we discovered he tried to convert eagle libs. Then we found out that this does not work for him as well.): https://forum.kicad.info/t/importing-converting-old-mod-footprints/8444

Attached the lib i used to test it.

Kicad version info:
Application: kicad
Version: no-vcs-found-f3908bd~61~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.10.0-38-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

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

Tags: eagle
Revision history for this message
Rene Poeschl (poeschlr) wrote :
tags: added: eagle
Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

I confirmed that this is indeed broken. It look like some of the recent Eagle project import changes broke something. @Russell, please take a look at this when you get a chance.

Changed in kicad:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Russell Oliver (roliver8143) wrote :

This removes a line that deletes the templates created from the eagle library every time EAGLE_PLUGIN::init( const PROPERTIES* aProperties ) is called, which seems quite often. The templates are deleted though if the library path for the plugin is changed or the file has been modified.

Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 8f07da7953f0cebd3e25ab44f984b3b2f4eb6599
https://git.launchpad.net/kicad/patch/?id=8f07da7953f0cebd3e25ab44f984b3b2f4eb6599

Changed in kicad:
status: Triaged → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
Revision history for this message
Igor Petrović (paradajz) wrote :

This still happens in latest KiCad. I've tried with my personal EAGLE library as well as the attached one. When added through "Manage Footprint Libraries" it seems like the library is imported correctly (plugin type is set to "Eagle"). When I try to view the footprints using the "Edit PCB footprints > Library browser" nothing shows under both imported libraries.

Application: kicad
Version: (5.0.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

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_USE_OCC=OFF
    KICAD_SPICE=ON

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

Can you please attach the eagle library for which this happens?

Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

This is indeed broken in 5.0.2 but has been fixed in the dev branch as well as the latest changes in the 5.0 branch (5.0.2-19-g025578fee). I'm not sure what happened to 5.0.2.

Revision history for this message
jean-pierre charras (jp-charras) wrote :

This is a old bug, already fixed in 5.02

A second bug creating a similar issue (#1807629) was fixed after the 5.02 was out.

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

Other bug subscribers

Remote bug watches

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