Created attachment 1282541 [details] ABRT problem dir from dnf crash Description of problem: I just ran `dnf upgrade --exclude khelpcenter --exclude kde-l10n-de` on Fedora 26 (updates-testing) Version-Release number of selected component (after dnf crashed): dnf-2.5.0-1.fc26.noarch dnf-2.5.0-2.fc26.noarch libdnf-0.9.0-1.fc26.x86_64 python3-dnf-2.5.0-1.fc26.noarch python3-dnf-2.5.0-2.fc26.noarch python3-3.6.1-6.fc26.x86_64 glib2-2.52.2-2.fc26.x86_64 How reproducible: Unclear, untested. Actual results: DNF crashed with signal 11 (Segmentation fault) Expected results: No crash Additional info: Full ABRT problem dir is attached. It seems like the crash was from dnf-makecache running at the same time though. Truncated backtrace: Core was generated by `/usr/libexec/system-python /usr/bin/dnf makecache timer'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __env_in_api (env=0x55ff3438d9e0) at ../../src/env/env_failchk.c:328 328 if (ip->dbth_state == THREAD_SLOT_NOT_IN_USE || Thread 1 (Thread 0x7f17c52e4700 (LWP 6843)): #0 0x00007f17b2419683 in __env_in_api (env=0x55ff3438d9e0) at ../../src/env/env_failchk.c:328 dbenv = 0x55ff343c57e0 thread = 0x7f17ae9fb330 i = 4 ret = <optimized out> htab = 0x7f17ae9fb378 ip = 0xfeb716da8ab8 renv = <optimized out> infop = <optimized out> unpin = 0 env = 0x55ff3438d9e0 ret = <optimized out> #1 0x00007f17b2419683 in __env_failchk_int (dbenv=dbenv@entry=0x55ff343c57e0) at ../../src/env/env_failchk.c:82 env = 0x55ff3438d9e0 ret = <optimized out> #2 0x00007f17b241a228 in __env_failchk_pp (dbenv=0x55ff343c57e0, flags=<optimized out>) at ../../src/env/env_failchk.c:58 ip = 0x7f17aea22170 env = 0x55ff3438d9e0 ret = <optimized out> #3 0x00007f17b2d22c2f in db_init (dbhome=0x55ff343c57c0 "/var/lib/rpm", rdb=0x55ff3439d370) at backend/db3.c:504 dbenv = 0x55ff343c57e0 xx = <optimized out> eflags = 1153 rc = 0 retry_open = <optimized out> lockfd = 3 cfg = 0x55ff3439d3f0 dbhome = 0x55ff343c57c0 "/var/lib/rpm" dbi = <optimized out> rc = 0 retry_open = <optimized out> verifyonly = <optimized out> db = 0x0 dbtype = DB_UNKNOWN oflags = 1024 _lockdbfd = 0 #4 0x00007f17b2d22c2f in db3_dbiOpen (rdb=<optimized out>, rpmtag=0, dbip=0x7fff8c081098, flags=<optimized out>) at backend/db3.c:841 dbhome = 0x55ff343c57c0 "/var/lib/rpm" dbi = <optimized out> rc = 0 retry_open = <optimized out> verifyonly = <optimized out> db = 0x0 dbtype = DB_UNKNOWN oflags = 1024 _lockdbfd = 0
*** This bug has been marked as a duplicate of bug 1443415 ***
Mai 26 12:28:27 chstpc-2 systemd-coredump[6909]: Process 6843 (dnf) of user 0 dumped core. Stack trace of thread 6843: #0 0x00007f17b2419683 __env_failchk_int (libdb-5.3.so) #1 0x00007f17b241a228 __env_failchk_pp (libdb-5.3.so) #2 0x00007f17b2d22c2f db_init (librpm.so.7) #3 0x00007f17b2d2959e pkgdbOpen (librpm.so.7) #4 0x00007f17b2d29e50 openDatabase (librpm.so.7) #5 0x00007f17b2d54935 rpmtsOpenDB (librpm.so.7) #6 0x00007f17b056dc98 rpmts_Match (_rpm.cpython-36m-x86_64-linux-gnu.so) #7 0x00007f17c4d0e076 PyCFunction_Call (libpython3.6m.so.1.0) #8 0x00007f17c4d58655 _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #9 0x00007f17c4ca35c1 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #10 0x00007f17c4cd8101 fast_function (libpython3.6m.so.1.0) #11 0x00007f17c4d1523e call_function (libpython3.6m.so.1.0) #12 0x00007f17c4d5268a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #13 0x00007f17c4cd7eda fast_function (libpython3.6m.so.1.0) #14 0x00007f17c4d1523e call_function (libpython3.6m.so.1.0) #15 0x00007f17c4d5268a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #16 0x00007f17c4ca35c1 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #17 0x00007f17c4cd8101 fast_function (libpython3.6m.so.1.0) #18 0x00007f17c4d1523e call_function (libpython3.6m.so.1.0) #19 0x00007f17c4d5268a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #20 0x00007f17c4ca35c1 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #21 0x00007f17c4cd8101 fast_function (libpython3.6m.so.1.0) #22 0x00007f17c4d1523e call_function (libpython3.6m.so.1.0) #23 0x00007f17c4d5268a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #24 0x00007f17c4cd7eda fast_function (libpython3.6m.so.1.0) #25 0x00007f17c4d1523e call_function (libpython3.6m.so.1.0) #26 0x00007f17c4d5268a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #27 0x00007f17c4ca35c1 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #28 0x00007f17c4cd8101 fast_function (libpython3.6m.so.1.0) #29 0x00007f17c4d1523e call_function (libpython3.6m.so.1.0) #30 0x00007f17c4d5268a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #31 0x00007f17c4ca35c1 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #32 0x00007f17c4cd8101 fast_function (libpython3.6m.so.1.0) #33 0x00007f17c4d1523e call_function (libpython3.6m.so.1.0) #34 0x00007f17c4d53616 _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #35 0x00007f17c4d22208 PyEval_EvalCodeEx (libpython3.6m.so.1.0) #36 0x00007f17c4d22f7b PyEval_EvalCode (libpython3.6m.so.1.0) #37 0x00007f17c4daaf72 run_mod (libpython3.6m.so.1.0) #38 0x00007f17c4dabc3d PyRun_FileExFlags (libpython3.6m.so.1.0) #39 0x00007f17c4dadec7 PyRun_SimpleFileExFlags (libpython3.6m.so.1.0) #40 0x00007f17c4daeed3 Py_Main (libpython3.6m.so.1.0) #41 0x000055ff32c0ecf5 main (system-python) #42 0x00007f17c3e9e5fe __libc_start_main (libc.so.6) #43 0x000055ff32c0ee6a _start (system-python) That was the first crash. Then I get a few of these: Mai 26 12:38:21 chstpc-2 systemd-coredump[27416]: Process 27414 (rpm) of user 0 dumped core. Stack trace of thread 27414: #0 0x00007f56e2da0683 __env_failchk_int (libdb-5.3.so) #1 0x00007f56e2da1228 __env_failchk_pp (libdb-5.3.so) #2 0x00007f56e368bc2f db_init (librpm.so.7) #3 0x00007f56e369259e pkgdbOpen (librpm.so.7) #4 0x00007f56e3692e50 openDatabase (librpm.so.7) #5 0x00007f56e36bd935 rpmtsOpenDB (librpm.so.7) #6 0x00007f56e36bdbcc rpmtsInitIterator (librpm.so.7) #7 0x00007f56e36bde6b loadKeyringFromDB (librpm.so.7) #8 0x00007f56e36bdbb5 rpmtsInitIterator (librpm.so.7) #9 0x00007f56e36aaac7 initQueryIterator (librpm.so.7) #10 0x00007f56e36ab477 rpmcliArgIter (librpm.so.7) #11 0x00007f56e36ab647 rpmcliQuery (librpm.so.7) #12 0x000055de1ec878f1 main (rpm) #13 0x00007f56e11bf5fe __libc_start_main (libc.so.6) #14 0x000055de1ec87d6a _start (rpm) So it looks like dnf-makecache crashed first, corrupting something, which in turn broke dnf while it was installing updates. Due to a bug in abrt, https://bugzilla.redhat.com/show_bug.cgi?id=1411497, I cannot get abrt to report these bugs.
(In reply to Igor Gnatenko from comment #1) > > *** This bug has been marked as a duplicate of bug 1443415 *** Are you sure this is a duplicate? My crash did not happen during F25→F26 update. It also did not happen on ppc64le, but on x86_64. If you are sure, please change the details of bug #1443415.