Bug#991642: kicad does not start several modules like eescheme
Am Montag, 2. August 2021, 15:59:59 CEST schrieb Carsten Schoenert: > > Yes, this is correct, my fault, saw only 5.99 as the version in unstable. > > > > @Seth > > Can please have a look at the full story? > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991642 > > > > The user Hans is using a NVidia card GF-8600GS and has some problems to > > use shortcuts and parts of the various parts of KiCad. My guess is that > > this is hardly related to an underlying graphic card problem and not > > basically a kicad problem within the Debian packaging. > > > > I've no NVidia cards anywhere and can't adjust anything to reproduce the > > behavior. For now I can't do something useful regarding this bug report. > > Hi Seth, > > the problem appears also on my EEEPC, which has no nvidia card, but just > an > old intel card (I945). > > I attached a picture, maybe it did not reach the bugreport, yet. > > Best > > Hans > > Hello Hans- Those icons are only active after you create a new project. Best Regards- Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com
Bug#913864: kicad: Backtraces on opening cvpcb
Am 2018-11-18 11:18, schrieb Carsten Schoenert: Hello Seth, Am 17.11.18 um 05:34 schrieb Seth Hillbrand: Hi Julien- Am 2018-11-16 22:37, schrieb Julien Goodwin: It looks to me like the python-wxgtk and wxwidgets versioning is orthogonal, it's just chance they happen to be similar. I did try doing a rebuild of the python-wxgtk source package (on my affected machine) to see if that would help, and it's the same behaviour. One thing I forgot to mention, this also affected the last build of 5.0, before 5.0.1. My apologies for the hasty response the first time. I gave a poor response. python-wxgtk3.0=3.0.2.0+dfsg-7 and higher are compiled against gtk3.0. This conflicts with the GTK2.0 versions of wxgtk3.0 that KiCad 5 is compiled against. The latest version that can be used is python-wxgtk3.0=3.0.2.0+dfsg-6. You will need to downgrade this package. now I'm really confused. I added a versioned dependency on python-wxgtk3.0 >= 3.0.2.0+dfsg-7~ to the kicad package on Apr 8 2018 in preparation for 5.0.0_rc1+dfsg1+20180318-3. That will be required for KiCad 5.1 as soon as the package works reliably with GTK3. As long as we are using the wxgtk3.0 built against GTK2, we need to maintain the python-wxgtk that is also built against GTK2. On Buster, this does not exist, so we will need to disable scripting for Buster until KiCad 5.1 is released. The maintainers of the wxWidget related packages don't build a GTK2+ version of python-wxgtk3.0 package in Debian testing anymore. And this will not change for the Buster release. So we need to deal with this. This whole wx stuff and the relations between the various packages is getting more and more worse in my eyes. I agree. The decision to change python-wxgtk3.0 from GTK2 to GTK3 but keep the same package name was a poor one. At a minimum, I wish that they would have changed the name as the functionality is definitely not equivalent. -Seth
Bug#913864: kicad: Backtraces on opening cvpcb
Hi Julien- Am 2018-11-16 22:37, schrieb Julien Goodwin: It looks to me like the python-wxgtk and wxwidgets versioning is orthogonal, it's just chance they happen to be similar. I did try doing a rebuild of the python-wxgtk source package (on my affected machine) to see if that would help, and it's the same behaviour. One thing I forgot to mention, this also affected the last build of 5.0, before 5.0.1. My apologies for the hasty response the first time. I gave a poor response. python-wxgtk3.0=3.0.2.0+dfsg-7 and higher are compiled against gtk3.0. This conflicts with the GTK2.0 versions of wxgtk3.0 that KiCad 5 is compiled against. The latest version that can be used is python-wxgtk3.0=3.0.2.0+dfsg-6. You will need to downgrade this package. Best- Seth
Bug#913864: kicad: Backtraces on opening cvpcb
Am 2018-11-16 12:39, schrieb Carsten Schoenert: So downgrading is a bit difficult and right now before the soft freeze for Buster not the right way I think. That's a fair assessment. I believe the issue is mixing versions. So an alternate solution is to upgrade both to the 3.0.4 version. I would be curious to hear if there were issues when both are running on 3.0.4 as I haven't had any issues in Buster related to this. -Seth
Bug#913864: kicad: Backtraces on opening cvpcb
Hello Carsten- Am 2018-11-16 02:00, schrieb Carsten Schoenert: Hello Seth, seems there is another issue with the RTTI implementation, now as far I see on amd64. Maybe this is already fixed in the current HEAD of the 5.x tree? As I recall, this issue is an incompatibility between 3.0.2 and 3.0.4 of the wx libraries. If Julien downgrades libwxbase and libwxgtk3.0 to the 3.0.2.0+dfsg-8, this issue should go away. Please let me know if it doesn't. -Seth You will need a DGB log? Am 16.11.18 um 05:18 schrieb Julien Goodwin: ii libwxbase3.0-0v53.0.4+dfsg-4 ii libwxgtk3.0-0v5 3.0.4+dfsg-4 ii python-wxgtk3.0 3.0.2.0+dfsg-8
Bug#911559: kicad: pcbnew crashes on reading a eeschema generated netlist
Hallo Carsten- Am 2018-11-07 11:15, schrieb Carsten Schoenert: Hi, Am 05.11.18 um 18:40 schrieb tro...@franken-online.de: I wish to supply some additional information: If I try to import the netlist into a newly generated board, pcbnew reproducibly fails as stated in my last mail.> If I remove 2 to 4 arbitrarily selected '(footprint ...)' lines from the netlist using a text editor, the partial netlist import succeeds and I can drop the incomplete block of footprints onto the board. If I then import the unmodified complete netlist the previously missing footprints appear and can also be dropped onto the board resulting in a complete bunch of footprints and networks on the board. so far I've seen and have understand the message from Seth the main problem is the code inside KiCad for i386 here. Seth, I guess the root for this report will be fixed with the upcoming release 5.0.2 of Kicad? Yes. The issue was a build flag that needed to be included for i386 machines. The default flags are fixed for 5.0.2 but I know that they get modified by the debian build, so you may check that that it keeps the extra -ffloat-store for 32-bit builds. -S
Bug#909282: Eeschema triggers wx assertion when adding text to schematic
Package: kicad Version: 5.0.0+dfsg1-2~bpo9+1 Severity: normal Dear Maintainer, Eeschema triggers an assertion. Steps: 1) Run kicad 2) Start new project 3) Open Eeschema 4) Insert text 5) The following assertion is displayed: ASSERT INFO: ../src/common/sizer.cpp(1961): assert "!IsRowGrowable( idx )" failed in AddGrowableRow(): AddGrowableRow() called for growable row BACKTRACE: [1] wxFlexGridSizer::AddGrowableRow(unsigned long, int) [2] wxDialog::Show(bool) [3] wxDialog::ShowModal() [4] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const [5] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [6] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [7] wxEvtHandler::TryHereOnly(wxEvent&) [8] wxEvtHandler::ProcessEventLocally(wxEvent&) [9] wxEvtHandler::ProcessEvent(wxEvent&) [10] wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) [11] wxEvtHandler::SafelyProcessEvent(wxEvent&) [12] g_closure_invoke [13] g_signal_emit_valist [14] g_signal_emit [15] gtk_propagate_event [16] gtk_main_do_event [17] g_main_context_dispatch [18] g_main_loop_run [19] gtk_main [20] wxGUIEventLoop::DoRun() [21] wxEventLoopBase::Run() [22] wxAppConsoleBase::MainLoop() [23] wxEntry(int&, wchar_t**) [24] __libc_start_main [25] _start -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kicad depends on: ii libc6 2.24-11+deb9u3 ii libcairo2 1.14.8-1 ii libcurl3 7.52.1-5+deb9u7 ii libfreeimage3 3.17.0+ds1-5 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libglew2.02.0.0-3+b1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libgomp1 6.3.0-18+deb9u1 ii liboce-foundation10 0.17.2-2 ii liboce-modeling10 0.17.2-2 ii liboce-ocaf-lite100.17.2-2 ii liboce-ocaf10 0.17.2-2 ii liboce-visualization100.17.2-2 ii libpixman-1-0 0.34.0-1 ii libpython2.7 2.7.13-2+deb9u2 ii libssl1.1 1.1.0f-3+deb9u2 ii libstdc++66.3.0-18+deb9u1 ii libwxbase3.0-0v5 3.0.2+dfsg-4 ii libwxgtk3.0-0v5 3.0.2+dfsg-4 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii python2.7.13-2 ii python-wxgtk3.0 3.0.2.0+dfsg-4 Versions of packages kicad recommends: ii kicad-demos 5.0.0+dfsg1-2~bpo9+1 ii kicad-libraries 5.0.0+dfsg1-2~bpo9+1 ii xsltproc 1.1.29-2.1 Versions of packages kicad suggests: pn extra-xdg-menus pn kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-d pn kicad-packages3d -- no debconf information
Bug#905221: kicad: pcbnew immediately crashes after invocation without showing a GUI (failed assertion)
Hello Carsten and Werner- I've committed a potential fix to this issue to the kicad tree ( https://git.launchpad.net/kicad/commit/?id=edbf34c2b2965f63537e485d958f00166f01bc5a). However, it has only been seen to correct the similar behavior we observed earlier and I have been unable to recreate the current issue. If you have a chance to apply/test this for the current issue, I'd greatly appreciate it. Best- Seth
