Description of problem: Crash happens when KDE SW Updater checks for updates via packagekit. Version-Release number of selected component: PackageKit-1.1.5-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: get_vertical_data executable: /usr/libexec/packagekitd global_pid: 2113 kernel: 4.9.6-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 get_vertical_data at /usr/src/debug/libsolv-0.6.24/src/repodata.c:489 #1 dataiterator_step at /usr/src/debug/libsolv-0.6.24/src/repodata.c:1619 #2 filter_dataiterator at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/hy-query.c:308 #3 hy_query_apply at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/hy-query.c:970 #4 hy_query_run_set at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/hy-query.c:1369 #5 running_kernel at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/hy-iutil.c:368 #6 dnf_sack_running_kernel at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/dnf-sack.c:1569 #7 allow_uninstall_all_but_protected at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/hy-goal.c:266 #8 construct_job at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/hy-goal.c:346 #9 hy_goal_run_all_flags at /usr/src/debug/PackageKit-1.1.5/libdnf-fe5a08bca7e2599798af7778917da2cc31f1460e/libdnf/hy-goal.c:966
Created attachment 1246575 [details] File: backtrace
Created attachment 1246576 [details] File: cgroup
Created attachment 1246577 [details] File: core_backtrace
Created attachment 1246578 [details] File: dso_list
Created attachment 1246579 [details] File: environ
Created attachment 1246580 [details] File: exploitable
Created attachment 1246581 [details] File: limits
Created attachment 1246582 [details] File: maps
Created attachment 1246583 [details] File: mountinfo
Created attachment 1246584 [details] File: namespaces
Created attachment 1246585 [details] File: open_fds
Created attachment 1246586 [details] File: proc_pid_status
Created attachment 1246587 [details] File: var_log_messages
Looks like a crash in libsolv. Reassigning.
Can you archive repo metadata from /var/cache/PackageKit which contains following packages? * flash-plugin-24.0.0.194 * Kflash-player-properties
Can you reproduce this? If yes, can you please attach a core file to this bug?
Created attachment 1250717 [details] Tar file of /var/cache/PackageKit/25/metadata/adobe-linux-x86_64
@Igor Gnatenko I am sorry for the late reply. Attached please find the Tar file (#c17) of: /var/cache/PackageKit/25/metadata/adobe-linux-x86_64 It is the repository where the flash-plugin package is. In the mean time, it got updated to a newer version: flash-plugin.x86_64 24.0.0.221-release @adobe-linux-x86_64 Hope it still can help. If this this is not the metadata you need, please let me know how to get the correct one. I am not a Linux expert, just a long time advanced user. There is no Kflash-player-properties package in any of my attached repositories. The closest one is: flash-player-ppapi.x86_64 24.0.0.221-release adobe-linux-x86_64 which is not installed.
@Michael Schröder I cannot reproduce it, it happened once. Moreover it seems that I inadvertently deleted the matching /var/spool/abrt/<dir>, or it got garbage collected, thus the coredump is gone too. However, I got a new crash yesterday. I could not report it, I am getting the following error from the ABRT (GUI): --- Running report_uReport --- The server at 'https://retrace.fedoraproject.org/faf' encountered an internal error (got error 500) reporter-ureport failed with exit code 1 ('report_uReport' exited with 1) I will try reporting it again later. Its coredump has 158MB, any idea where can I upload it, bugzila has 20M limit. I am attaching the core_backtrace file from the new crash, hope, it helps to determine if it is related.
Created attachment 1250723 [details] core_backtrace file from the new crash
This time it died because someone messed up glibc's memory handling (i.e. some out-of-bound write). I'm not sure if this is related or not. Btw, is the libsolv version at least 0.6.25? That version has some extra checks against bad solv files, which could help in your case.
Yes, I have libsolv.x86_64 0.6.25-1.fc25.
I tried to report the crash from two days ago. It was already reported: https://bugzilla.redhat.com/show_bug.cgi?id=1403573 This bug is Denied for me.
*** This bug has been marked as a duplicate of bug 1382900 ***