Red Hat Bugzilla – Full Text Bug Listing
|Summary:||[abrt] dnf: __env_size_insert(): python3.4 killed by SIGSEGV|
|Product:||[Fedora] Fedora||Reporter:||Craig Robson <craig>|
|Component:||libdb||Assignee:||Matej Mužila <mmuzila>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||23||CC:||craig, hhorak, jorton, jplesnik, jsilhan, jstanek, jsynacek, jzeleny, mdomonko, mluscon, novyjindrich, packaging-team-maint, paul, pknirsch, pnemade, ppisar, psabata, steve, vmukhame|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2016-12-20 14:07:55 EST||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Craig Robson 2016-02-29 12:16:34 EST
Version-Release number of selected component: dnf-1.1.6-2.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/python3 /bin/dnf upgrade crash_function: __env_size_insert dnf-makecache.log: Error was encountered while opening journal files: No data available executable: /usr/bin/python3.4 global_pid: 13765 kernel: 4.3.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 __env_size_insert at ../../src/env/env_alloc.c:599 #1 __memp_mf_discard at ../../src/mp/mp_fopen.c:1137 #2 __memp_fclose at ../../src/mp/mp_fopen.c:1034 #3 __db_refresh at ../../src/db/db.c:1028 #4 __db_close at ../../src/db/db.c:747 #5 __db_close_pp at ../../src/db/db_iface.c:261 #6 db3_dbiClose at backend/db3.c:735 #7 dbiForeach at rpmdb.c:441 #8 rpmdbClose at rpmdb.c:468 #9 rpmtsCloseDB at rpmts.c:78
Comment 1 Craig Robson 2016-02-29 12:16:39 EST
Created attachment 1131645 [details] File: _var_log_dnf.log
Comment 4 Craig Robson 2016-02-29 12:16:42 EST
Created attachment 1131648 [details] File: core_backtrace
Comment 7 Craig Robson 2016-02-29 12:16:44 EST
Created attachment 1131651 [details] File: exploitable
Comment 10 Craig Robson 2016-02-29 12:16:46 EST
Created attachment 1131654 [details] File: mountinfo
Comment 11 Craig Robson 2016-02-29 12:16:47 EST
Created attachment 1131655 [details] File: namespaces
Comment 13 Craig Robson 2016-02-29 12:16:49 EST
Created attachment 1131657 [details] File: proc_pid_status
Comment 14 Michal Domonkos 2016-03-07 09:04:48 EST
Hi Craig, Can you still reproduce this issue, or was it just a random crash that never happened again? Thank you
Comment 15 Craig Robson 2016-03-07 12:23:07 EST
I think this only happened once.
Comment 16 Michal Domonkos 2016-03-09 09:48:29 EST
We don't know the exact reason for this crash but it happens in the berkleydb so moving it over.
Comment 17 Petr Pisar 2016-03-09 10:55:42 EST
In BerkleyDB, not in the Perl binding. Moving there.
Comment 18 Fedora End Of Life 2016-11-24 10:50:49 EST
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 19 Fedora End Of Life 2016-12-20 14:07:55 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.