Description of problem: This situation can cappen when dnf repodata expires too. So I'd consider this as blocker. [root@localhost ~]# ls -tlra /var/cache/dnf/updates-testing-f2a2dc38561e43b9/repodata/ total 11068 -rw-r--r--. 1 root root 7827 Apr 1 12:19 repomd.xml drwxr-xr-x. 2 root root 4096 Apr 1 12:19 . -rw-r--r--. 1 root root 457429 Apr 1 12:19 bcefba0112ed15ffc6d705c1da018ec45f7294c31f41e63c01112bfc8cb31765-comps-Everything.x86_64.xml.zck -rw-r--r--. 1 root root 29118 Apr 1 12:19 b0c797951c6aa9fd4b859cd35ff0f10e69e7da7f253cd66e1a4651f44a65b1b4-prestodelta.xml.zck -rw-r--r--. 1 root root 634308 Apr 1 12:19 0503bb3a2333513fa21dc399ba96491e937697b2d091036036270916112d7c41-updateinfo.xml.xz -rw-r--r--. 1 root root 3303250 Apr 1 12:19 6b31e1e3a7fbd44e6e01b217b652e0503e6de174a149c499ce591c197cddf0bf-primary.xml.zck -rw-r--r--. 1 root root 6869938 Apr 1 12:19 99e3aec08c01fa08f47949959b93cfcad53fd65e478fbb0a0e9ef02fae98d320-filelists.xml.zck drwxr-xr-x. 4 root root 4096 Apr 1 12:42 .. [root@localhost ~]# rm /var/cache/dnf/updates-testing-f2a2dc38561e43b9/repodata/b0c797951c6aa9fd4b859cd35ff0f10e69e7da7f253cd66e1a4651f44a65b1b4-prestodelta.xml.zck [root@localhost ~]# dnf update dnf-4.2.2-1.fc30.noarch dnf-data-4.2.2-1.fc30.noarch dnf-plugins-core-4.0.6-1.fc30.noarch dnf-yum-4.2.2-1.fc30.noarch libdnf-0.28.1-1.fc30.x86_64 libdnf-debuginfo-0.28.1-1.fc30.x86_64 libdnf-debugsource-0.28.1-1.fc30.x86_64 python3-dnf-4.2.2-1.fc30.noarch python3-dnf-plugins-core-4.0.6-1.fc30.noarch python3-libdnf-0.28.1-1.fc30.x86_64 python3-libdnf-debuginfo-0.28.1-1.fc30.x86_64 Version-Release number of selected component: dnf-4.2.2-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/dnf update crash_function: Curl_splay executable: /usr/bin/python3.7 journald_cursor: s=e08d26839f9543fd9bdaba659ef3da25;i=b555;b=2d57fd8411dc49c29dcf810b49ff03b3;m=771786af;t=5857528214d5a;x=b0199543790116dc kernel: 5.0.5-300.fc30.x86_64 rootdir: / runlevel: N 3 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 Curl_splay at ../../lib/splay.c:51 #1 Curl_splayremovebyaddr at ../../lib/splay.c:238 #2 Curl_expire_clear at ../../lib/multi.c:3110 #3 Curl_close at ../../lib/url.c:326 #4 curl_easy_cleanup at ../../lib/easy.c:826 #5 prepare_next_transfer at /usr/src/debug/librepo-1.9.6-1.fc30.x86_64/librepo/downloader.c:1454 #6 prepare_next_transfers at /usr/src/debug/librepo-1.9.6-1.fc30.x86_64/librepo/downloader.c:1688 #7 lr_download at /usr/src/debug/librepo-1.9.6-1.fc30.x86_64/librepo/downloader.c:2572 #8 lr_download_single_cb at /usr/src/debug/librepo-1.9.6-1.fc30.x86_64/librepo/downloader.c:2781 #9 lr_yum_download_repo at /usr/src/debug/librepo-1.9.6-1.fc30.x86_64/librepo/yum.c:952
Created attachment 1550443 [details] File: backtrace
Created attachment 1550444 [details] File: cgroup
Created attachment 1550445 [details] File: core_backtrace
Created attachment 1550446 [details] File: cpuinfo
Created attachment 1550447 [details] File: dso_list
Created attachment 1550448 [details] File: environ
Created attachment 1550449 [details] File: exploitable
Created attachment 1550450 [details] File: limits
Created attachment 1550451 [details] File: machineid
Created attachment 1550452 [details] File: maps
Created attachment 1550453 [details] File: mountinfo
Created attachment 1550454 [details] File: open_fds
Created attachment 1550455 [details] File: proc_pid_status
Created attachment 1550467 [details] valgrid-1.log Log output of: [root@localhost ~]# valgrind --time-stamp=yes --trace-children=yes --log-file=vg-dnf-update-%p-%n.log --verbose dnf update Segmentation fault (core dumped)s [ === ] --- B/s | 0 B --:-- ETA
Some meaningfull packages: libcurl-7.64.0-6.fc30.x86_64 curl-7.64.0-6.fc30.x86_64 librepo-1.9.6-1.fc30.x86_64 This host is from Fedora-Workstation-netinst-x86_64-30-20190329.n.0.iso minimal install and then add some packages. You should be able to restore dnf as working by removing /var/cache/dnf and trying agian.
*** This bug has been marked as a duplicate of bug 1694411 ***
*** Bug 1699597 has been marked as a duplicate of this bug. ***