On Sun, 26 Jan 2020 17:51:55 +0100
Carsten Schoenert <c.schoen...@t-online.de> wrote:
> > Seems to be stored there:
> > $ grep canvas_type .config/kicad/pcbnew
> > canvas_type=1
> >
> > (When switched on seems to be "=1", switched off to be "=2",
> > but not completely sure about it.)
> > And maybe which graphics driver do you use?
Mine is also
canvas_type=1
I have tried setting it to 2 but that doesn't appear to make any
difference.
> As a shot into the blue, what libwx* libraries are used by the kicad
> main application? Should look like this (Debian testing / unstable) no
> matter if you called only kicad or eeschema or pcbnew.
>
> > $ grep libwx /proc/$(pidof kicad)/maps
...
> You can also look at all libs that are used, maybe some version
> clashing due some library that's installed accidentally?
Mine are:
7f84a8ac6000-7f84a8b28000 r--p 00000000 fe:00 355482
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.5.0
7f84a8b28000-7f84a8ce4000 r-xp 00062000 fe:00 355482
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.5.0
7f84a8ce4000-7f84a8d6f000 r--p 0021e000 fe:00 355482
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.5.0
7f84a8d6f000-7f84a8d70000 ---p 002a9000 fe:00 355482
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.5.0
7f84a8d70000-7f84a8d7b000 r--p 002a9000 fe:00 355482
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.5.0
7f84a8d7b000-7f84a8d7f000 rw-p 002b4000 fe:00 355482
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.5.0
7f84a8d8a000-7f84a8d9b000 r--p 00000000 fe:00 355487
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0.5.0
7f84a8d9b000-7f84a8dc3000 r-xp 00011000 fe:00 355487
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0.5.0
7f84a8dc3000-7f84a8dd0000 r--p 00039000 fe:00 355487
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0.5.0
7f84a8dd0000-7f84a8dd1000 ---p 00046000 fe:00 355487
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0.5.0
7f84a8dd1000-7f84a8dd3000 r--p 00046000 fe:00 355487
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0.5.0
7f84a8dd3000-7f84a8dd4000 rw-p 00048000 fe:00 355487
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0.5.0
7f84a8dd5000-7f84a8fe6000 r--p 00000000 fe:00 353901
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0.5.0
7f84a8fe6000-7f84a92da000 r-xp 00211000 fe:00 353901
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0.5.0
7f84a92da000-7f84a93d8000 r--p 00505000 fe:00 353901
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0.5.0
7f84a93d8000-7f84a93d9000 ---p 00603000 fe:00 353901
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0.5.0
7f84a93d9000-7f84a944b000 r--p 00603000 fe:00 353901
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0.5.0
7f84a944b000-7f84a9453000 rw-p 00675000 fe:00 353901
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0.5.0
7f84a945f000-7f84a949f000 r--p 00000000 fe:00 353946
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0.5.0
7f84a949f000-7f84a950e000 r-xp 00040000 fe:00 353946
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0.5.0
7f84a950e000-7f84a9530000 r--p 000af000 fe:00 353946
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0.5.0
7f84a9530000-7f84a953c000 r--p 000d0000 fe:00 353946
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0.5.0
7f84a953c000-7f84a953f000 rw-p 000dc000 fe:00 353946
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0.5.0
7f84a9540000-7f84a95e9000 r--p 00000000 fe:00 353412
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0.5.0
7f84a95e9000-7f84a96bb000 r-xp 000a9000 fe:00 353412
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0.5.0
7f84a96bb000-7f84a9702000 r--p 0017b000 fe:00 353412
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0.5.0
7f84a9702000-7f84a9703000 ---p 001c2000 fe:00 353412
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0.5.0
7f84a9703000-7f84a9723000 r--p 001c2000 fe:00 353412
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0.5.0
7f84a9723000-7f84a9726000 rw-p 001e2000 fe:00 353412
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0.5.0
7f84a972a000-7f84a9759000 r--p 00000000 fe:00 353889
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0.5.0
7f84a9759000-7f84a97a6000 r-xp 0002f000 fe:00 353889
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0.5.0
7f84a97a6000-7f84a97be000 r--p 0007c000 fe:00 353889
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0.5.0
7f84a97be000-7f84a97c6000 r--p 00093000 fe:00 353889
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0.5.0
7f84a97c6000-7f84a97c7000 rw-p 0009b000 fe:00 353889
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0.5.0
Looking pretty similar to yours. I'm currently running
ii kicad 5.1.6+dfsg1-1 amd64 Electronic schematic
and PCB design software
ii libwxbase3.0-0v5:amd64 3.0.5.1+dfsg-1 amd64 wxBase library
(runtime) - non-GUI support classes of wxWidgets toolkit
ii libwxgtk3.0-gtk3-0v5:amd64 3.0.5.1+dfsg-1 amd64 wxWidgets
Cross-platform C++ GUI toolkit (GTK 3 runtime)
My issue seems to have expanded beyond the original problem. I now
can't run the "Associate Footprints" tool. The dialog opens just fine
and I can interact with it, but when I try to dismiss it "OK" or
"Cancel" the process just hangs, again in 100% CPU spin.
Having now installed the -dbgsym package to get more detailed debug
information, a gdb trace of that situation looks like:
$ gdb -p `pidof kicad`
GNU gdb (Debian 9.1-3) 9.1
...
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fee505684dc in wxClassInfo::~wxClassInfo (this=0x7fee48811520
<wxGLContext::ms_classInfo>, __in_chrg=<optimized out>) at
../src/common/object.cpp:177
177 ../src/common/object.cpp: No such file or directory.
(gdb) bt
#0 0x00007fee505684dc in wxClassInfo::~wxClassInfo() (this=0x7fee48811520
<wxGLContext::ms_classInfo>, __in_chrg=<optimized out>) at
../src/common/object.cpp:177
#1 0x00007fee4fec9e27 in __run_exit_handlers
(status=0, listp=0x7fee50048718 <__exit_funcs>,
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at
exit.c:108
#2 0x00007fee4fec9fda in __GI_exit (status=<optimized out>) at exit.c:139
#3 0x00007fee4feb2e12 in __libc_start_main (main=
0x5565fec4d880, argc=1, argv=0x7ffcd2cf1058, init=<optimized out>,
fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcd2cf1048)
at ../csu/libc-start.c:342
#4 0x00005565fec521fa in _start ()
Same style of stack trace as before, and again somewhat odd that it
appears to be trying to exit the entire process, when all I did was hit
"Cancel" on the "Associate Footprints" dialog. I was hoping to just be
returned back to eeschema.
At this point now I'm a little stuck, because being unable to associate
footprints with components, I can't actually make any new boards. With
pcbnew crashing only on exit, at least I could edit and save just fine
within one editing session, as it would only crash when I tried to exit
anyway. At the moment I can't work on new boards, so this has become a
bit more critical a failure. :(
--
Paul "LeoNerd" Evans
leon...@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
