KISYS3DMOD path variable apparently hard coded

Bug #1782708 reported by Oivind Toien on 2018-07-20
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KiCad
Medium
Wayne Stambaugh

Bug Description

In the latest Windows nightly, Version: (6.0.0-rc1-dev-93-g3c1dc9e5c), release build the KISYS3DMOD path variable appears as if it is now hard coded. The following was tested in a VM where there are no system environmental variables set in Windows. After 6.0 development version install, this variable is reset to the program folder. I have the KiCad official library files organized under my home folder, thus I would need the change this variable under Configure Paths of the main window. However after editing the path value the attached message appears, indicating that the variables have been set externally and will be overwritten next time KiCad is started (again, the system environment variables in Windows have **not** been set; they are not there when checking after install).

Moreover, in most cases Kicad get stuck on this dialog with high CPU activity, and I need to let Windows terminate KiCad. Even if I press Cancel in the Configure path Window I get this dialog, and get stuck. I have in a couple of cases I was able to get past the dialog, and next time KiCad was started the path was reset to the program folder.

If it is intentional that this variable is locked to the program folder I disagree, and it will create problems for all custom footprint libraries that had to use the KYSYS3D model variable as root for their 3D model location. It will also prevent official libraries to be installed anywhere but the program folder, so users will need administrative privileges to make any updates beyond the KiCad install.

This might be related to the following commit: https://git.launchpad.net/kicad/commit/?id=8f0aa68ab820fcd9d7ce7d5b1323b031fa9ccb21, "Fold 3D Search Paths dialog into Configure Paths."
(I am not sure what this implies, perhaps it refers to the stuck dialog?) It works fairly well under 5.0 rc3 so I am not sure why it was changed.

Application: kicad
Version: (6.0.0-rc1-dev-93-g3c1dc9e5c), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.54.1
    Compiler: GCC 7.1.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_USE_OCC=OFF
    KICAD_SPICE=ON

Changed in kicad:
milestone: none → 5.1.0

Also happens on linux, no high cpu usage though

m (easyw) wrote :

the same issue on Win10 64b

m (easyw) wrote :

Please note that is a big issue, for users that have their own 3d path.
It is not possible to load and change the 3D folder path.

Changed in kicad:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Wayne Stambaugh (stambaughw)
KiCad Janitor (kicad-janitor) wrote :

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

Changed in kicad:
status: Triaged → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers