Hide Forgot
Version-Release number of selected component: dnf-1.1.7-2.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/dnf -v makecache timer crash_function: solv_realloc executable: /usr/bin/python3.4 global_pid: 27569 kernel: 4.4.6-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #3 solv_realloc at /usr/src/debug/python3-libsolv-0.6.19-2.fc23/src/util.c:52 #4 solv_realloc2 at /usr/src/debug/python3-libsolv-0.6.19-2.fc23/src/util.c:63 #5 solv_extend_realloc at /usr/src/debug/python3-libsolv-0.6.19-2.fc23/src/util.c:100 #6 solv_extend at /usr/src/debug/python3-libsolv-0.6.19-2.fc23/src/util.h:57 #7 repodata_add_dirstr at /usr/src/debug/python3-libsolv-0.6.19-2.fc23/src/repodata.c:2755 #8 endElement at /usr/src/debug/python3-libsolv-0.6.19-2.fc23/ext/repo_rpmmd.c:1197 #9 doContent at lib/xmlparse.c:2532 #10 contentProcessor at lib/xmlparse.c:2105 #11 XML_ParseBuffer at lib/xmlparse.c:1651 #12 repo_add_rpmmd at /usr/src/debug/python3-libsolv-0.6.19-2.fc23/ext/repo_rpmmd.c:1366
Created attachment 1143224 [details] File: _var_log_dnf.log
Created attachment 1143225 [details] File: backtrace
Created attachment 1143226 [details] File: cgroup
Created attachment 1143227 [details] File: core_backtrace
Created attachment 1143228 [details] File: dso_list
Created attachment 1143229 [details] File: environ
Created attachment 1143230 [details] File: exploitable
Created attachment 1143231 [details] File: limits
Created attachment 1143232 [details] File: maps
Created attachment 1143233 [details] File: mountinfo
Created attachment 1143234 [details] File: namespaces
Created attachment 1143235 [details] File: open_fds
Created attachment 1143236 [details] File: proc_pid_status
Created attachment 1143237 [details] File: var_log_messages
Created attachment 1143238 [details] File: dnf-makecache.log
Can you reproduce this bug?
This happened during the weekend by something automated. But I ran 'sudo dnf upgrade' now and it does indeed crash. My colleagues have also been experiencing crashes, so this might be a duplicate of bug 1318662. As stated there, it seems to be caused by repo data generated on EL6.
Ok, bug is the same as in 1318662 *** This bug has been marked as a duplicate of bug 1318662 ***