Your message dated Sun, 29 Nov 2020 07:34:01 +0100 with message-id <[email protected]> and subject line Re: Bug#948626: kicad: Closing pcbnew hangs main kicad process has caused the Debian Bug report #948626, regarding kicad: Closing pcbnew hangs main kicad process to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 948626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948626 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: kicad Version: 5.1.5+dfsg1-2 Severity: normal I can open, use and close eeschema just fine. I can open and use pcbnew just fine, but when I attempt to close it and return back to the main toplevel kicad window, the entire process hangs at 100% CPU usage, not drawing any windows (existing onscreen content gets corrupted). It remains in this state until SIGINT or SIGTERM. If run from the terminal there is no printed output of any kind. Connecting to a process in this state with gdb shows: $ gdb --pid 309563 ... Attaching to process 309563 [New LWP 309564] [New LWP 309565] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007fec889fa4bc in wxClassInfo::~wxClassInfo() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 (gdb) bt #0 0x00007fec889fa4bc in wxClassInfo::~wxClassInfo() () at /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #1 0x00007fec88352720 in __run_exit_handlers (status=0, listp=0x7fec884cf718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #2 0x00007fec8835285a in __GI_exit (status=<optimized out>) at exit.c:139 #3 0x00007fec8833cbc2 in __libc_start_main (main= 0x562cef17a880, argc=1, argv=0x7fff6f8f9548, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6f8f9538) at ../csu/libc-start.c:342 #4 0x0000562cef17f12a in _start () -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kicad depends on: ii libc6 2.29-7 ii libcairo2 1.16.0-4 ii libcurl4 7.67.0-2 ii libgcc1 1:9.2.1-22 ii libgl1 1.1.0-1+b1 ii libglew2.1 2.1.0-4+b1 ii libglu1-mesa [libglu1] 9.0.1-1 ii libngspice0 31.3-2 ii libocct-data-exchange-7.3 7.3.3+dfsg1-1 ii libocct-foundation-7.3 7.3.3+dfsg1-1 ii libocct-modeling-algorithms-7.3 7.3.3+dfsg1-1 ii libocct-modeling-data-7.3 7.3.3+dfsg1-1 ii libocct-ocaf-7.3 7.3.3+dfsg1-1 ii libpixman-1-0 0.36.0-1 ii libpython3.7 3.7.6-1 ii libstdc++6 9.2.1-22 ii libwxbase3.0-0v5 3.0.4+dfsg-15 ii libwxgtk3.0-gtk3-0v5 3.0.4+dfsg-15 ii python3 3.7.5-1 ii python3-wxgtk4.0 4.0.7+dfsg-2 Versions of packages kicad recommends: ii kicad-demos 5.1.5+dfsg1-2 ii kicad-libraries 5.1.5+dfsg1-2 ii xsltproc 1.1.32-2.2 Versions of packages kicad suggests: ii extra-xdg-menus 1.0-4 pn kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-d <none> pn kicad-packages3d <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hello Paul, Am Thu, Jun 04, 2020 at 07:02:14PM +0100 schrieb Paul "LeoNerd" Evans: > Some further investigation and help from `nickoe` on the #kicad ... > I think this bug can be closed now. so we do. Regards Carsten
--- End Message ---
