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: _IO_file_doallocate executable: /usr/libexec/packagekitd journald_cursor: s=c7f80a679ba84813b37c67a051a0364d;i=201a;b=4d81969dad9b42ed8915c41e1571eaf0;m=34b9b162;t=55410587d1cad;x=5468364307f76f74 kernel: 4.11.9-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Potential duplicate: bug 1416601
Created attachment 1296569 [details] File: backtrace
Created attachment 1296570 [details] File: cgroup
Created attachment 1296571 [details] File: core_backtrace
Created attachment 1296572 [details] File: cpuinfo
Created attachment 1296573 [details] File: dso_list
Created attachment 1296574 [details] File: environ
Created attachment 1296575 [details] File: limits
Created attachment 1296576 [details] File: maps
Created attachment 1296577 [details] File: open_fds
Created attachment 1296578 [details] File: proc_pid_status
Created attachment 1296579 [details] File: var_log_messages
Similar problem has been detected: Started apper clicked check-for-updates and this happened. Straight after upgrade to F26. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: _IO_file_doallocate executable: /usr/libexec/packagekitd journald_cursor: s=f70cc7f16501449eb7b8c16ae9d20325;i=6941;b=5095c0fcbd3342eabfa45dd7098e8ed4;m=7eb3a6ee;t=554835bbf4235;x=dc9201366a66ad4b kernel: 4.11.9-300.fc26.x86_64 package: PackageKit-1.1.6-2.fc26 reason: packagekitd killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1478945 has been marked as a duplicate of this bug. ***
*** Bug 1479597 has been marked as a duplicate of this bug. ***
*** Bug 1482797 has been marked as a duplicate of this bug. ***
*** Bug 1499187 has been marked as a duplicate of this bug. ***
*** Bug 1507199 has been marked as a duplicate of this bug. ***
*** Bug 1508634 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I have run updates by 'dnf upgrade'. This occurred later. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: _IO_file_doallocate executable: /usr/libexec/packagekitd journald_cursor: s=00ac1063acb84be6ba50504dcb36d802;i=350d1;b=52958d2dc46946c3823fe176c44b259a;m=35305c234;t=55f9614ec3613;x=a88213170416850e kernel: 4.13.16-200.fc26.x86_64 package: PackageKit-1.1.6-2.fc26 reason: packagekitd killed by SIGABRT 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.