Version-Release number of selected component: PackageKit-1.1.6-2.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=b3bbd312c761438c87e81e82762c1553;i=f916;b=7a5602882a3248c9a1e38b0e924fa165;m=1bf05879;t=5547a838d9996;x=b1a7fa2d97303743 kernel: 4.11.9-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #0 repo_internalize_trigger at /usr/src/debug/libdnf-0.9.2/libdnf/hy-repo.c:59 #1 lookup_num at /usr/src/debug/libdnf-0.9.2/libdnf/hy-package.c:138 #2 dnf_package_get_size at /usr/src/debug/libdnf-0.9.2/libdnf/hy-package.c:805 #3 backend_get_details_thread at pk-backend-dnf.c:1820 #4 pk_backend_job_thread_setup at pk-backend-job.c:813 #5 g_thread_proxy at gthread.c:784 Potential duplicate: bug 1375895
Created attachment 1299624 [details] File: backtrace
Created attachment 1299625 [details] File: cgroup
Created attachment 1299626 [details] File: core_backtrace
Created attachment 1299627 [details] File: cpuinfo
Created attachment 1299628 [details] File: dso_list
Created attachment 1299629 [details] File: environ
Created attachment 1299630 [details] File: exploitable
Created attachment 1299631 [details] File: limits
Created attachment 1299632 [details] File: maps
Created attachment 1299633 [details] File: open_fds
Created attachment 1299634 [details] File: proc_pid_status
Created attachment 1299635 [details] File: var_log_messages
*** Bug 1475041 has been marked as a duplicate of this bug. ***
Similar problem has been detected: no clue reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=e6445160a55c4470a68e24b4487221bf;i=948355;b=632a00b771494a79891e2b5c3984f666;m=6260a79e8;t=5568d8268d582;x=200df21bc9f34a2 kernel: 4.11.11-300.fc26.x86_64 package: PackageKit-1.1.6-2.fc26 reason: packagekitd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1485771 has been marked as a duplicate of this bug. ***
*** Bug 1486833 has been marked as a duplicate of this bug. ***
*** Bug 1489218 has been marked as a duplicate of this bug. ***
*** Bug 1490065 has been marked as a duplicate of this bug. ***
*** Bug 1491047 has been marked as a duplicate of this bug. ***
*** Bug 1496570 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Updating / Manipulating extensions via Tweak Tool or the webpage causes some issues. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=6a94cc533bb4434ca995fe88ffda9717;i=36e06;b=6894944418434f6eab8d9793a2c94df0;m=72f1aaa7a;t=55a928f8b8648;x=d04837ec8f9d01a4 kernel: 4.12.14-300.fc26.x86_64 package: PackageKit-1.1.6-2.fc26 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1499766 has been marked as a duplicate of this bug. ***
*** Bug 1505067 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I updated some packages through gpk-application. After the cleanup step, gpk-application tried to load the updates list. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=e2adaf96cdf44803b5de609a4e08888a;i=116d457;b=24e402a3f6bd485188c0202ab3a212f9;m=6dd0031f7f3;t=562b0cef4da17;x=f8422168bea8b4ab kernel: 4.13.5-200.fc26.x86_64 package: PackageKit-1.1.6-2.fc26 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
*** This bug has been marked as a duplicate of bug 1375895 ***