Description of problem: 1. sudo dnf update ... bla bla bla ... Transaction Summary ================================================================================ Install 3 Packages Upgrade 52 Packages Remove 3 Packages Total download size: 69 M Is this ok [y/N]: y Downloading Packages: ... bla bla... (14-16/55): gwyddion 11% [== ] 382 kB/s | 8.3 MB 02:42 ETA this is where is crashed Version-Release number of selected component: dnf-0.4.16-2.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/python /bin/dnf update crash_function: lr_headercb executable: /usr/bin/python2.7 kernel: 3.13.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 lr_headercb at /lib64/librepo.so.0 #1 Curl_client_write at sendf.c:476 #2 Curl_http_readwrite_headers at http.c:3491 #3 readwrite_data at transfer.c:459 #4 Curl_readwrite at transfer.c:1022 #5 multi_runsingle at multi.c:1478 #6 curl_multi_perform at multi.c:1751 #7 lr_download at /lib64/librepo.so.0 #8 lr_download_packages at /lib64/librepo.so.0 #9 py_download_packages at /usr/lib64/python2.7/site-packages/librepo/_librepomodule.so
Created attachment 871747 [details] File: backtrace
Created attachment 871748 [details] File: cgroup
Created attachment 871749 [details] File: core_backtrace
Created attachment 871750 [details] File: dso_list
Created attachment 871751 [details] File: environ
Created attachment 871752 [details] File: exploitable
Created attachment 871753 [details] File: limits
Created attachment 871754 [details] File: maps
Created attachment 871755 [details] File: open_fds
Created attachment 871756 [details] File: proc_pid_status
Created attachment 871757 [details] File: var_log_messages
trying to run "sudo dnf update" right after that resulted in a crash while downloading a kernel, actually Downloading Packages: [SKIPPED] kernel-modules-extra-3.13.5-202.fc20.x86_64.rpm: Already downloaded [SKIPPED] kmod-VirtualBox-3.13.5-202.fc20.x86_64-4.3.6-2.fc20.11.x86_64.rpm: Already downloaded [SKIPPED] Judy-1.0.5-8.fc20.x86_64.rpm: Already downloaded [SKIPPED] crda-1.1.3_2013.11.27-4.fc20.x86_64.rpm: Already downloaded [SKIPPED] gnutls-3.1.20-4.fc20.x86_64.rpm: Already downloaded [SKIPPED] gnutls-devel-3.1.20-4.fc20.x86_64.rpm: Already downloaded [SKIPPED] gnutls-dane-3.1.20-4.fc20.x86_64.rpm: Already downloaded [SKIPPED] gnutls-c++-3.1.20-4.fc20.x86_64.rpm: Already downloaded [SKIPPED] gnutls-3.1.20-4.fc20.i686.rpm: Already downloaded [SKIPPED] greybird-gtk2-theme-1.3.1-1.fc20.noarch.rpm: Already downloaded [SKIPPED] greybird-gtk3-theme-1.3.1-1.fc20.noarch.rpm: Already downloaded [SKIPPED] greybird-xfce4-notifyd-theme-1.3.1-1.fc20.noarch.rpm: Already downloaded [SKIPPED] greybird-xfwm4-theme-1.3.1-1.fc20.noarch.rpm: Already downloaded (14-16/55): kernel-3 7% [=- ] 207 kB/s | 5.3 MB 05:15 ETA
passing on to librepo.
Hi aten, have you ever experienced the problem again? Unfortunately, I cannot reproduce it. Can you please install the librepo-debuginfo package by: $ debuginfo-install librepo Your original report has missing symbol table for librepo, which can be useful for debugging such kind of problem.
Tomas, That time was my first attempt with dnf and I have never tried to use it after that crash. I have installed "librepo-debuginfo's", like you suggested, unfortunately my system is up to date at the moment (using yum), so I'll wait couple days until something shows up in repos.
It will be awesome if you can try the dnf again with the librepo-debug info installed :) Thank you!
Tomas, I just ran "sudo dnf update" and it went smoothly (kernel was updated among other packages as well), so it seems I cant reproduce the bug anymore either.
Glad to hear that. I am closing the bug now, feel free to reopen it or fill a new one if you meet the problem again. Thanks for cooperation.
librepo-1.7.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/librepo-1.7.2-1.fc20
librepo-1.7.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.