Description of problem: To reproduce: - Start KiCad - Create a new project with File | New... - Specify a project directory - Open the project schematic by double-clicking the .sch file - The program crashes immediately A crash also occurs with opening existing projects created with KiCad 7.x and 8.x. I don't have any 9.x projects to test with. Version-Release number of selected component: kicad-1:9.0.5-1.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: kicad killed by SIGABRT journald_cursor: s=f76b974f98a94c119ef557ae44724bea;i=1abb344;b=1da03dc0811c470bb31d896e733edc83;m=11b81f972;t=64210ca39f8bf;x=4eb27c72bb0b707 executable: /usr/bin/kicad cmdline: /usr/bin/kicad cgroup: 0::/user.slice/user-501.slice/user/app.slice/app-gnome-org.kicad.kicad-92140.scope rootdir: / uid: 501 kernel: 6.17.1-300.fc43.x86_64 package: kicad-1:9.0.5-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found xsession_errors: backtrace_rating: 4 crash_function: fatal_error_exit Truncated backtrace: Thread no. 1 (34 frames) #4 fatal_error_exit at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/pylifecycle.c:3155 #5 fatal_error at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/pylifecycle.c:3301 #6 _Py_FatalErrorFunc at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/pylifecycle.c:3387 #7 _Py_CheckRecursiveCall at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/ceval.c:491 #8 _Py_EnterRecursiveCallTstate at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Include/internal/pycore_ceval.h:216 #9 method_enter_call at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/descrobject.c:300 #10 method_vectorcall_NOARGS at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/descrobject.c:444 #11 _PyObject_VectorcallTstate at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Include/internal/pycore_call.h:169 #12 PyObject_VectorcallMethod at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/call.c:856 #13 PyObject_CallMethodNoArgs at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Include/cpython/abstract.h:65 #14 _PyFile_Flush at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/fileobject.c:542 #15 flush_std_files at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/pylifecycle.c:1820 #16 fatal_error at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/pylifecycle.c:3364 #17 _Py_FatalErrorFunc at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/pylifecycle.c:3387 #18 _Py_CheckRecursiveCall at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/ceval.c:491 #19 _Py_EnterRecursiveCallTstate at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Include/internal/pycore_ceval.h:216 #20 cfunction_enter_call at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/methodobject.c:428 #21 cfunction_vectorcall_FASTCALL_KEYWORDS at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/methodobject.c:461 #22 _PyObject_VectorcallTstate at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Include/internal/pycore_call.h:169 #23 _PyObject_CallFunctionVa at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/call.c:552 #24 PyObject_CallFunction at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Objects/call.c:574 #25 PyImport_Import at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/import.c:4000 #26 PyImport_ImportModule at /usr/src/debug/python3.14-3.14.0-1.fc43.x86_64/Python/import.c:3423 #27 pybind11::module_::import at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/thirdparty/pybind11/include/pybind11/pybind11.h:1201 #28 pybind11::globals at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/thirdparty/pybind11/include/pybind11/pybind11.h:1290 #29 SCRIPTING::IsWxAvailable at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/scripting/python_scripting.cpp:119 #30 SCH_EDIT_FRAME::ReCreateHToolbar at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/eeschema/toolbars_sch_editor.cpp:127 #31 SCH_EDIT_FRAME::SCH_EDIT_FRAME at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/eeschema/sch_edit_frame.cpp:193 #32 SCH::IFACE::CreateKiWindow at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/eeschema/eeschema.cpp:169 #33 KIWAY::Player at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/common/kiway.cpp:447 #34 KICAD_MANAGER_CONTROL::ShowPlayer at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/kicad/tools/kicad_manager_control.cpp:803 #35 std::function<int(TOOL_EVENT const&)>::operator() at /usr/include/c++/15/bits/std_function.h:593 #36 COROUTINE<int, TOOL_EVENT const&>::callerStub at /usr/src/debug/kicad-9.0.5-1.fc43.x86_64/include/tool/coroutine.h:513 #37 make_fcontext
Created attachment 2110940 [details] File: proc_pid_status
Created attachment 2110941 [details] File: maps
Created attachment 2110942 [details] File: limits
Created attachment 2110943 [details] File: environ
Created attachment 2110944 [details] File: open_fds
Created attachment 2110945 [details] File: mountinfo
Created attachment 2110946 [details] File: os_info
Created attachment 2110947 [details] File: cpuinfo
Created attachment 2110948 [details] File: core_backtrace
Created attachment 2110949 [details] File: dso_list
Created attachment 2110950 [details] File: backtrace
*** This bug has been marked as a duplicate of bug 2401327 ***
So a python 3.14 rc got into F43 and broke KiCad. There is nothing I can do about that right now. Hopefully in a few months I'll be able to put a KiCad dev build into F43 and Rawhide. Only options for users right now: a flatpak incorporating an older python version or staying with F42. I'll personally be choosing to stay on F42 until things settle down.
Ah. Thanks for the update. I'll give the flatpak a try.
I recommend the flatpak produced by the KiCad project itself as it is known to have ab older version of python that is suitable. It is available from flathub, and the upstream page about its status is at https://www.kicad.org/download/linux/ about 1/2 way down the page.