Version-Release number of selected component: setroubleshoot-3.3.32-7.fc39 Additional info: reporter: libreport-2.17.11 type: CCpp reason: python3.12 killed by SIGABRT journald_cursor: s=646c9283f3204a7eb1690fe6886ba825;i=103032;b=89dc3d6899d84f5b95a7370bf8086c4e;m=1498b98942;t=60c1c8b303c32;x=a7b100b520310380 executable: /usr/bin/python3.12 cmdline: /usr/bin/python3 -Es /usr/bin/seapplet cgroup: 0::/user.slice/user-1000.slice/session-33.scope rootdir: / uid: 1000 kernel: 6.6.3-200.fc39.x86_64 package: setroubleshoot-3.3.32-7.fc39 runlevel: N 5 backtrace_rating: 4 crash_function: _FcObjectLookupOtherTypeByName Truncated backtrace: Thread no. 1 (94 frames) #4 _FcObjectLookupOtherTypeByName at /usr/src/debug/fontconfig-2.14.2-5.fc39.x86_64/src/fcobjs.c:93 #5 FcObjectLookupIdByName at /usr/src/debug/fontconfig-2.14.2-5.fc39.x86_64/src/fcobjs.c:130 #7 FcObjectFromName at /usr/src/debug/fontconfig-2.14.2-5.fc39.x86_64/src/fcname.c:109 #8 IA__FcPatternAdd at /usr/src/debug/fontconfig-2.14.2-5.fc39.x86_64/src/fcpat.c:745 #9 IA__FcPatternBuild at /usr/src/debug/fontconfig-2.14.2-5.fc39.x86_64/src/fcpat.c:1239 #10 pango_fc_make_pattern at ../pango/pangofc-fontmap.c:1884 #11 pango_fc_fontset_key_make_pattern at ../pango/pangofc-fontmap.c:2127 #12 pango_fc_font_map_get_patterns at ../pango/pangofc-fontmap.c:2142 #13 pango_fc_font_map_load_fontset at ../pango/pangofc-fontmap.c:2245 #14 pango_context_get_metrics at ../pango/pango-context.c:713 #15 gtk_image_get_baseline_align at ../gtk/gtkimage.c:1686 #16 gtk_image_get_content_size at ../gtk/gtkimage.c:1731 #17 gtk_css_custom_gadget_get_preferred_size at ../gtk/gtkcsscustomgadget.c:124 #18 gtk_css_gadget_get_preferred_size at ../gtk/gtkcssgadget.c:683 #19 gtk_image_get_preferred_height_and_baseline_for_width at ../gtk/gtkimage.c:1948 #20 gtk_widget_query_size_for_orientation at ../gtk/gtksizerequest.c:215 #21 gtk_widget_compute_size_for_orientation at ../gtk/gtksizerequest.c:399 #22 gtk_widget_get_preferred_height at ../gtk/gtksizerequest.c:527 #23 gtk_window_get_preferred_height at ../gtk/gtkwindow.c:9009 #24 gtk_widget_query_size_for_orientation at ../gtk/gtksizerequest.c:219 #25 gtk_widget_compute_size_for_orientation at ../gtk/gtksizerequest.c:399 #26 gtk_widget_get_preferred_height_and_baseline_for_width at ../gtk/gtksizerequest.c:642 #27 _gtk_widget_get_preferred_size_and_baseline.constprop.0 at ../gtk/gtksizerequest.c:703 #28 gtk_window_compute_hints at ../gtk/gtkwindow.c:10334 #29 gtk_window_compute_configure_request at ../gtk/gtkwindow.c:9646 #30 gtk_window_move_resize at ../gtk/gtkwindow.c:9855 #31 _g_closure_invoke_va at ../gobject/gclosure.c:895 #32 signal_emit_valist_unlocked at ../gobject/gsignal.c:3516 #35 gtk_window_show at ../gtk/gtkwindow.c:6208 #37 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3813 #38 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612 #41 gtk_widget_show at ../gtk/gtkwidget.c:4852 #43 g_object_new_internal at ../gobject/gobject.c:2296 #45 g_object_new_valist at ../gobject/gobject.c:2584 #47 ffi_call_unix64 at ../src/x86/unix64.S:104 #48 ffi_call_int at ../src/x86/ffi64.c:673 #49 ffi_call at ../src/x86/ffi64.c:710 #50 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684 #51 _function_cache_invoke_real at ../gi/pygi-cache.c:783 #52 _constructor_cache_invoke_real at ../gi/pygi-cache.c:929 #53 pygi_function_cache_invoke at ../gi/pygi-cache.c:862 #54 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727 #55 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764 #56 _callable_info_call at ../gi/pygi-info.c:548 #58 _PyObject_MakeTpCall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:240 #59 _PyEval_EvalFrameDefault at Python/bytecodes.c:2711 #60 _PyFunction_Vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:419 #61 _PyObject_VectorcallTstate at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_call.h:92 #62 method_vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/classobject.c:91 #63 PyCFunction_Call at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:387 #64 _PyEval_EvalFrameDefault at Python/bytecodes.c:3259 #65 _PyFunction_Vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:419 #66 _PyObject_VectorcallTstate at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_call.h:92 #67 method_vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/classobject.c:91 #68 PyCFunction_Call at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:387 #69 _PyEval_EvalFrameDefault at Python/bytecodes.c:3259 #70 _PyFunction_Vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:419 #71 _PyObject_VectorcallTstate at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_call.h:92 #72 method_vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/classobject.c:91 #73 PyCFunction_Call at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:387 #74 _PyEval_EvalFrameDefault at Python/bytecodes.c:3259 #75 _PyFunction_Vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:419 #76 _PyObject_VectorcallTstate at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_call.h:92 #77 method_vectorcall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/classobject.c:91 #78 _pygi_closure_handle at ../gi/pygi-closure.c:582 #79 ffi_closure_unix64_inner at ../src/x86/ffi64.c:899 #80 ffi_closure_unix64 at ../src/x86/unix64.S:303 #81 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:3802 #84 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284 #85 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349 #87 ffi_call_unix64 at ../src/x86/unix64.S:104 #88 ffi_call_int at ../src/x86/ffi64.c:673 #89 ffi_call at ../src/x86/ffi64.c:710 #90 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684 #91 pygi_function_cache_invoke at ../gi/pygi-cache.c:862 #92 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727 #93 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764 #94 _callable_info_call at ../gi/pygi-info.c:548 #96 _PyObject_MakeTpCall at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/call.c:240 #97 _PyEval_EvalFrameDefault at Python/bytecodes.c:2711 #98 PyEval_EvalCode at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/ceval.c:570 #99 run_eval_code_obj at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pythonrun.c:1693 #100 run_mod at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pythonrun.c:1714 #101 pyrun_file at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pythonrun.c:1614 #102 _PyRun_SimpleFileObject at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pythonrun.c:433 #103 _PyRun_AnyFileObject at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pythonrun.c:78 #104 pymain_run_file_obj at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:360 #105 pymain_run_file at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:379 #106 pymain_run_python at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:610 #107 Py_RunMain at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:689 #108 Py_BytesMain at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:743 #109 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58 #110 __libc_start_main_impl at ../csu/libc-start.c:360 #111 _start
Created attachment 2003683 [details] File: proc_pid_status
Created attachment 2003684 [details] File: maps
Created attachment 2003685 [details] File: limits
Created attachment 2003686 [details] File: environ
Created attachment 2003687 [details] File: open_fds
Created attachment 2003688 [details] File: mountinfo
Created attachment 2003689 [details] File: os_info
Created attachment 2003690 [details] File: cpuinfo
Created attachment 2003691 [details] File: core_backtrace
Created attachment 2003692 [details] File: dso_list
Created attachment 2003693 [details] File: machineid
Created attachment 2003694 [details] File: backtrace
According to the backtrace it seems to be something deep in the fontconfig
how to reproduce this reported issue?
I'd like to answer, to the question "How to reproduce" because I really can't. Nowadays; all my Fedora OS machines are running as virtual machines on two different Windows servers. The main purpose of those instances is to act as servers for mails, DNS, NTP and many other usual servers like that. Punctually, I use them for comparison about possibly different behaviour about "mock-up software" of my personal coding in Ada complied with GNAT. In other words, I usually just check by emails that all those V-machines and servers are still in good health. I very rarely fall into the bug I reported, whilst I'm currently doing anything on. Most of the time, It's after reboot-startup (clean or dirty because of some failure of the hosting PC), at login time I get the warning about bugs detected by Fedora. I could ignore them, but my thought is that it could help bug solving, with providing more data, even "raw" ones. I very know this is not quite at all the best bug reporting way. But I also know (I was famous about that prior I retired) my "bug catcher" reputation. In other words, I tend to fall into bug traps other people never fall in. I ignore why about this, I just know it's a fact. I just suspect it's because I've my own way to do things that is often not the "most common way to do things". But if my reports are rather totally useless, just tell me that's the actual case. If so, I will totally stop top sending such kind of reports, to only report those I'm able to tell something like a clue about "how to reproduce, possibly". Regards
Thanks for your comment. Please do keep reporting bugs as and when you find them. But good to add one more comment to bug about what were you doing when that bug occurred. This will help us to follow same steps to reproduce reported bug. Bugs detected by Fedora shows how many times its detected. So if you find count more than 1 time bug is detected then you can try to remember what were you doing that might have caused that bug detected by Fedora on your system. Right now I am closing this bug as there is not much information available on how to reproduce this bug.