Your message dated Sun, 10 Jul 2022 07:01:56 +0200
with message-id <[email protected]>
and subject line Re: Bug#913864: KiCad is not usable, because cvpcb is not
working
has caused the Debian Bug report #913864,
regarding kicad: Backtraces on opening cvpcb
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.)
--
913864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913864
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kicad
Version: 5.0.1+dfsg1-3
Severity: important
On opening cvpcb there's many (408) backtraces, bypassing them does allow
cvpcb to work, but closing it crashes kicad.
This seems similar to several other reported crashes, but this machine
is straight testing.
A full log from one of the backtraces is below, all are the same basic
erorr just for different classes.
ASSERT INFO:
../src/common/object.cpp(251): assert "classTable->Get(m_className) == NULL"
failed in Register(): Class "wxCommandEvent" already in RTTI table - have you
used IMPLEMENT_DYNAMIC_CLASS() multiple times or linked some object file twice)?
BACKTRACE:
[1] wxClassInfo::Register()
[2] _dl_catch_exception
[3] _dl_catch_exception
[4] _dl_catch_error
[5] dlopen
[6] _PyImport_GetDynLoadFunc
[7] _PyImport_LoadDynamicModule
[8] PyImport_ImportModuleLevel
[9] PyObject_Call
[10] PyEval_CallObjectWithKeywords
[11] PyEval_EvalFrameEx
[12] PyEval_EvalCodeEx
[13] PyEval_EvalCode
[14] PyImport_ExecCodeModuleEx
[15] PyImport_ImportModuleLevel
[16] PyObject_Call
[17] PyEval_CallObjectWithKeywords
[18] PyEval_EvalFrameEx
[19] PyEval_EvalCodeEx
[20] PyEval_EvalCode
[21] PyImport_ExecCodeModuleEx
[22] PyImport_ImportModuleLevel
[23] PyObject_Call
[24] PyEval_CallObjectWithKeywords
[25] PyEval_EvalFrameEx
[26] PyEval_EvalCodeEx
[27] PyEval_EvalCode
[28] PyImport_ExecCodeModuleEx
[29] PyImport_ImportModuleLevel
[30] PyObject_Call
[31] PyEval_CallObjectWithKeywords
[32] PyEval_EvalFrameEx
[33] PyEval_EvalCodeEx
[34] PyEval_EvalCode
[35] PyImport_ExecCodeModuleEx
[36] PyImport_ImportModuleLevel
[37] PyEval_EvalFrameEx
[38] PyEval_EvalFrameEx
[39] PyEval_EvalCodeEx
[40] PyEval_EvalFrameEx
[41] PyEval_EvalCodeEx
[42] PyEval_EvalCode
[43] PyRun_StringFlags
[44] PyRun_SimpleStringFlags
[45] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&)
[46] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[47] wxEvtHandler::TryHereOnly(wxEvent&)
[48] wxEvtHandler::ProcessEventLocally(wxEvent&)
[49] wxEvtHandler::ProcessEvent(wxEvent&)
[50] wxEvtHandler::ProcessPendingEvents()
[51] wxAppConsoleBase::ProcessPendingEvents()
[52] wxApp::DoIdle()
[53] g_main_context_dispatch
[54] g_main_loop_run
[55] gtk_main
[56] wxGUIEventLoop::DoRun()
[57] wxEventLoopBase::Run()
[58] wxAppConsoleBase::MainLoop()
[59] wxEntry(int&, wchar_t**)
[60] __libc_start_main
[61] _start
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kicad depends on:
ii libc6 2.27-8
ii libcairo2 1.16.0-1
ii libcurl4 7.61.0-1
ii libfreeimage3 3.17.0+ds1-5+b5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.2.0-9
ii libgl1 1.1.0-1
ii libglew2.0 2.0.0-6
ii libglu1-mesa [libglu1] 9.0.0-2.1
ii libice6 2:1.0.9-2
ii libngspice0 29-1
ii liboce-foundation11 0.18.2-3
ii liboce-modeling11 0.18.2-3
ii liboce-ocaf-lite11 0.18.2-3
ii liboce-ocaf11 0.18.2-3
ii liboce-visualization11 0.18.2-3
ii libpixman-1-0 0.34.0-2
ii libpython2.7 2.7.15-4
ii libsm6 2:1.2.2-1+b3
ii libssl1.1 1.1.1-2
ii libstdc++6 8.2.0-9
ii libwxbase3.0-0v5 3.0.4+dfsg-4
ii libwxgtk3.0-0v5 3.0.4+dfsg-4
ii libx11-6 2:1.6.7-1
ii libxext6 2:1.3.3-1+b2
ii python 2.7.15-3
ii python-wxgtk3.0 3.0.2.0+dfsg-8
Versions of packages kicad recommends:
ii kicad-demos 5.0.1+dfsg1-3
ii kicad-libraries 5.0.1+dfsg1-3
ii xsltproc 1.1.32-2
Versions of packages kicad suggests:
ii extra-xdg-menus 1.0-4
ii kicad-doc-en 5.0.1+dfsg1-3
ii kicad-packages3d 5.0.1-1
-- no debconf information
--- End Message ---
--- Begin Message ---
The main version this report ist about isn't under support by upstream
since a long time.
Also no new information was contributed to the report.
I'll close this report now.
Am Sun, Nov 29, 2020 at 02:49:38AM +0100 schrieb Karsten:
> Am 28.11.20 um 20:51 schrieb Carsten Schoenert:
> > Hi,
> >
> > I can't reproduce this behavior. Seems to me you didn't use CvPcb the way
> > it is intended.
> >
> > And btw., your message about your potential problem is completely wrong in
> > this report.
> >
>
> Hello Carsten,
>
> i am talking about the features behind the button "Assign PCB footprints to
> schematic symbols" (see screenshot).
> How this simple part of KiCad cannot be used as intended?
> Using the wrong hand for the mouse? :-)
>
> Fact is that this part of KiCad seems to be very buggy.
> I did not open a new bug report for it, because i thought the problems of the
> described problem are to similar.
> One time this part crashed, but this was really not reproducible.
>
> It's fine that it is running stable on your system.
> But this is no explanation that it must be stable everywhere.
> On the other hand i think that you can't do anything to solve this bugs.
>
> We must wait until this bugs are solved in newer versions of Kicad.
> Version 5.1.8 seems to be on the way ...
>
> Regards
> karsten
>
>
--- End Message ---
