This actually recently started happening to me if I had KICAD_SCRIPTING
turned on, the only way I could find to fix it was by disabling scripting.
I was going to dig in to what was going on, but then I upgraded to Ubuntu
20.04 today and the problem went away, so it was probably some kind of
I should have said "wxPython" on gtk2. Usually this pops up in gdb when
the library directory ordering changes.
-Seth
Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372
On 2020-04-23 09:53, Seth Hillbrand wrote:
That usually pops up when you
Yah, maybe you nedd to create a new buid dir, if it is really really old.
Otherwise, show us your cmake config. ;)
tor. 23. apr. 2020 18.53 skrev Seth Hillbrand :
> That usually pops up when you are loading GTK2 from wx and pcbnew is
> compiled for GTK3
>
> -Seth
>
> Seth Hillbrand
> KiCad
That usually pops up when you are loading GTK2 from wx and pcbnew is
compiled for GTK3
-Seth
Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372
On 2020-04-23 09:50, Mário Luzeiro wrote:
Hello all,
I'm trying to run KiCad on debug mode (from
Hello all,
I'm trying to run KiCad on debug mode (from latest development branch).. it
used to work.. but now it crashes when I try to run pcbnew.
Has anyone seen this before? any idea how to solve it?
../src/common/object.cpp(251): assert "classTable->Get(m_className) == NULL"
failed in
5 matches
Mail list logo
