Schematic changes not fully transferred to pcbnew unless eeschema is closed

Bug #1823497 reported by Oleg Endo
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Committed
Medium
Jon Evans

Bug Description

I have noticed this started happening a few days ago.

When using the "Update PCB from schematic" button in pcbnew some changes to the schematic are not reflected until eeschema is closed. Closing eeschema and re-running the update-from-schematic will reflect all the changes.

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

Hi Oleg- Please add the version information for which this is happening. It may be a while before someone looks at it, at which point the "a few days ago" reference is hard to track down.

Also, is this the same as lp:1823177 ?

Revision history for this message
Oleg Endo (oleg.endo) wrote :

Sorry, I'm only using the nightly builds so I always forget to mention that I'm using the nightly builds on Ubuntu ;)

So, this started happening on the nightly builds sometime during this week. I guess it's related to the changes of the connectivity netlist thingy that's been going on.

Maybe it's related to lp:1823177 but for me, hitting the "update from schematic" button multiple times doesn't have any effect. Only closing eeschema will do the trick it seems.

Revision history for this message
Michael Kavanagh (michaelkavanagh) wrote :

@Oleg, please can you copy the exact version information from Help -> About KiCad -> Copy Version Info

Changed in kicad:
status: New → Incomplete
Revision history for this message
Oleg Endo (oleg.endo) wrote :

Sure

Application: kicad
Version: 5.1.0-unknown-615c493~82~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-47-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.22
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

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

Seth Hillbrand (sethh)
Changed in kicad:
status: Incomplete → Triaged
importance: Undecided → Medium
milestone: none → 6.0.0-rc1
Revision history for this message
tistructor (tistructor) wrote :

The same happens in the windows version too.

Application: kicad
Version: (5.1.0-173-g27e6f5b9e), 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_PYTHON3 = OFF
     KICAD_SCRIPTING_WXPYTHON = ON
     KICAD_SCRIPTING_WXPYTHON_PHOENIX = OFF
     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
Jon Evans (craftyjon) wrote :

This is probably because real time connectivity is currently disabled. I can put in a workaround.

Changed in kicad:
assignee: nobody → Jon Evans (craftyjon)
Revision history for this message
Jon Evans (craftyjon) wrote :

This should be working now, please re-open if you see any issues

Changed in kicad:
status: Triaged → Fix Committed
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.