Description of problem: I just opened footprint editor, and that's not the first time, bit I noticed that whenever that happen I was adding footprint and 3D view before crashing Version-Release number of selected component: kicad-1:6.0.4-1.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-glib-kicad-66805.scope cmdline: kicad crash_function: std::__replacement_assert executable: /usr/bin/kicad journald_cursor: s=e52d416e20674e4bac4122a7f48da430;i=50aa5;b=2bf2f59ab11b4745a5f9ed3014a0a0ba;m=b43a19611;t=5de4e4cb07152;x=61b1b669fc31f423 kernel: 5.17.5-100.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 std::__replacement_assert at /usr/include/c++/11/x86_64-redhat-linux/bits/c++config.h:2660 #3 std::vector<VECTOR2<int>, std::allocator<VECTOR2<int> > >::operator[] at /usr/include/c++/11/bits/stl_vector.h:1043 #5 ZONE::HatchBorder at /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/zone.cpp:1031 #6 ZONE::SetBorderDisplayStyle at /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/zone.cpp:882 #7 PCB_PARSER::parseZONE at /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_parser.cpp:5437 #8 PCB_PARSER::parseFOOTPRINT_unchecked at /usr/include/c++/11/bits/unique_ptr.h:173 #9 PCB_PARSER::parseFOOTPRINT at /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_parser.cpp:3211 #10 PCB_PARSER::Parse at /usr/include/c++/11/bits/unique_ptr.h:185 #11 FP_CACHE::Load at /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_plugin.cpp:274 #12 PCB_PLUGIN::FootprintEnumerate at /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_plugin.cpp:2390
Created attachment 1877470 [details] File: backtrace
Created attachment 1877471 [details] File: core_backtrace
Created attachment 1877472 [details] File: cpuinfo
Created attachment 1877473 [details] File: dso_list
Created attachment 1877474 [details] File: environ
Created attachment 1877475 [details] File: limits
Created attachment 1877476 [details] File: maps
Created attachment 1877477 [details] File: mountinfo
Created attachment 1877478 [details] File: open_fds
Created attachment 1877479 [details] File: proc_pid_status
I've reported the bug upstream. We'll see if the developers can track down the cause.
Upstream thinks they know what caused this crash, and have pointed me to a potential fix - it sounds like a race condition, which is why it doesn't always happen. I'll make a build in my personal copr and I'll provide a link in case you are able to test it. It will take a few hours to build.
A test repo is here: https://copr.fedorainfracloud.org/coprs/stevenfalco/ I'll start production builds tomorrow.
Now available in the official KiCad Copr: https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/
FEDORA-2022-94a7ee7f62 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-94a7ee7f62
FEDORA-2022-94a7ee7f62 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-94a7ee7f62` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-94a7ee7f62 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I'm upgrading to Fedora 36 with KDE, I may try the copr version, that's much better than the testing repository. though I'm now convinced that flatpak is the way to distribute programs and distribution repositories are better for basic system components are cli programs. thank you for your time and effort.
You are welcome. We do have a flatpak available, but that is packaged separately, and probably won't include this specific fix until 6.0.6 rolls out. So, you should probably use the Copr version, or, if you wait 4 more days, the rpm I built will move from the testing repo into the production Fedora repo.
alright, I think I'll wait 4 more days. thank you a lot for your awesome work <3
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
FEDORA-2022-12e166d642 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-12e166d642
Moving to F35. The new package will move to "stable" in 3 days.
FEDORA-2022-a8584d360c has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a8584d360c
I'm making a bootable USB stick right now, I'm moving to fedora 36 with GNOME, I'll e using kiCAD there. thanks a lot, see you on my new installation
FEDORA-2022-a8584d360c has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-94a7ee7f62 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-12e166d642 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.