On 15/12/18 5:34 pm, Carsten Schoenert wrote: > I tried to reproduce this issue on several machines in preparation for > 5.0.2. But I'm unable to get catched by your reported issue on any of my > machines. Even if I forced the install the packages python-wxgtk3.0 and > libwxgtk3.0-gtk3-0v5!
For me forcing python-wxgtk3.0_3.0.2.0+dfsg-4 is the way I make things work. ... > No other user seems to be affected by the root of this report until now. > I've not seen something similar in the KiCad user forum too. Also the > backtrace shows to me that somehow functions called that should have > been disabled (CMake option KICAD_SCRIPTING_WXPYTHON=OFF) for all > versions since 5.0.0-1. > Are you really sure you are using a binary from the Debian archive? Can Yes. I just upgraded to 5.0.2+dfsg1-1 last night, and before that played around. Having a python plugin (in .kicad/scripting/plugins, and specifically InteractiveHtmlBom[1]) seems to be what triggers this. So if python is intended to be disabled it's clearly not. 1: https://github.com/openscopeproject/InteractiveHtmlBom