Bug 2253923
| Summary: | [abrt] setroubleshoot: _FcObjectLookupOtherTypeByName(): python3.12 killed by SIGABRT | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sylvain Arth <sylvain> | ||||||||||||||||||||||||||
| Component: | fontconfig | Assignee: | Akira TAGOH <tagoh> | ||||||||||||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||
| Version: | 39 | CC: | ajax, dwalsh, fonts-bugs, gnome-sig, i18n-bugs, mclasen, mmalik, plautrba, rstrode, sylvain, tagoh, vmojzis | ||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/0e194909d66e734ae91ff3d617419ea87209ed9 | ||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:5d415c8fd3542357049db9bce3a3d3b921473316;VARIANT_ID=server; | ||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||
| Last Closed: | 2024-04-23 03:30:51 UTC | Type: | --- | ||||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||
|
Description
Sylvain Arth
2023-12-11 00:39:57 UTC
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. |