Hide Forgot
I wonder why is this considered Python bug. Could you elaborate on that?
I set the component to "python" since it looks platform-python core dumped. I'm not sure if it's correct. Please feel free to reset the component. --- PID: 3684 (dnf) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Tue 2019-07-02 07:46:57 EDT (12min ago) Command Line: /usr/libexec/platform-python /usr/bin/dnf makecache Executable: /usr/libexec/platform-python3.6 Control Group: /user.slice/user-0.slice/session-4.scope Unit: session-4.scope Slice: user-0.slice Session: 4 Owner UID: 0 (root) Boot ID: aa1d6f8c7413425a81411063828194be Machine ID: 468bb364677d4186b7c0efefb990d8cc Hostname: virt-11 Storage: /var/lib/systemd/coredump/core.dnf.0.aa1d6f8c7413425a81411063828194be.3684.1562068017000000.lz4 Message: Process 3684 (dnf) of user 0 dumped core. Stack trace of thread 3684: #0 0x00007fa7c264c8af raise (libc.so.6) #1 0x00007fa7c2636cc5 abort (libc.so.6) #2 0x00007fa7c2636b99 __assert_fail_base.cold.0 (libc.so.6) #3 0x00007fa7c2644e66 __assert_fail (libc.so.6) #4 0x00007fa7bf851240 dnf_sack_load_repo (libdnf.so.2) #5 0x00007fa7b0e56919 _ZL9load_repoP11_SackObjectP7_objectS2_ (_hawkey.so) #6 0x00007fa7c34e1216 PyCFunction_Call (libpython3.6m.so.1.0) #7 0x00007fa7c3538d38 _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #8 0x00007fa7c34ca17a fast_function (libpython3.6m.so.1.0) #9 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #10 0x00007fa7c3532cfa _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #11 0x00007fa7c348443b _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #12 0x00007fa7c34ca330 fast_function (libpython3.6m.so.1.0) #13 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #14 0x00007fa7c3533c6f _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #15 0x00007fa7c348443b _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #16 0x00007fa7c34ca330 fast_function (libpython3.6m.so.1.0) #17 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #18 0x00007fa7c3532cfa _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #19 0x00007fa7c34ca17a fast_function (libpython3.6m.so.1.0) #20 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #21 0x00007fa7c3532cfa _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #22 0x00007fa7c34ca17a fast_function (libpython3.6m.so.1.0) #23 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #24 0x00007fa7c3532cfa _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #25 0x00007fa7c34ca17a fast_function (libpython3.6m.so.1.0) #26 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #27 0x00007fa7c3532cfa _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #28 0x00007fa7c34ca17a fast_function (libpython3.6m.so.1.0) #29 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #30 0x00007fa7c3532cfa _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #31 0x00007fa7c348443b _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #32 0x00007fa7c34ca330 fast_function (libpython3.6m.so.1.0) #33 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #34 0x00007fa7c3532cfa _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #35 0x00007fa7c348443b _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #36 0x00007fa7c34ca330 fast_function (libpython3.6m.so.1.0) #37 0x00007fa7c34e1582 call_function (libpython3.6m.so.1.0) #38 0x00007fa7c3533c6f _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #39 0x00007fa7c350c8c8 PyEval_EvalCodeEx (libpython3.6m.so.1.0) #40 0x00007fa7c350d79b PyEval_EvalCode (libpython3.6m.so.1.0) #41 0x00007fa7c359f4c2 run_mod (libpython3.6m.so.1.0) #42 0x00007fa7c35a0727 PyRun_FileExFlags (libpython3.6m.so.1.0) #43 0x00007fa7c35a222f PyRun_SimpleFileExFlags (libpython3.6m.so.1.0) #44 0x00007fa7c35a332b Py_Main (libpython3.6m.so.1.0) #45 0x000055d651b5fc68 main (platform-python3.6) #46 0x00007fa7c2638843 __libc_start_main (libc.so.6) #47 0x000055d651b5fdde _start (platform-python3.6) ---
Ah. I just noticed "Message: Process 3684 (dnf) of user 0 dumped core.". Maybe I should reset the component to "dnf"?
dnf_sack_load_repo() from libdnf.so.2 aborts.
Thanks for help correct the fields!
I create the patch that fix the issue. https://github.com/rpm-software-management/librepo/pull/156 . It also requires rebuild of libdnf, because the solution uses a build option.
Karel LGTM!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3583