Version-Release number of selected component: PackageKit-1.1.6-7.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_malloc0 executable: /usr/libexec/packagekitd journald_cursor: s=aae25dad289e4eecb537ed270b1cdb88;i=74cce;b=89ffd98f8f084790ada8f9765203affc;m=cfa7af3;t=55899453e03a9;x=e53de62db4098229 kernel: 4.13.0-0.rc7.git0.1.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0
Created attachment 1323178 [details] File: backtrace
Created attachment 1323180 [details] File: cgroup
Created attachment 1323181 [details] File: core_backtrace
Created attachment 1323182 [details] File: cpuinfo
Created attachment 1323183 [details] File: dso_list
Created attachment 1323184 [details] File: environ
Created attachment 1323185 [details] File: limits
Created attachment 1323186 [details] File: maps
Created attachment 1323187 [details] File: open_fds
Created attachment 1323188 [details] File: proc_pid_status
Created attachment 1323189 [details] File: var_log_messages
Similar problem has been detected: PackageKit crashed when started with: sudo /usr/libexec/packagekitd --verbose and tried to refresh metadata through Gnome Software. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd --verbose crash_function: g_malloc0 executable: /usr/libexec/packagekitd journald_cursor: s=1f8069dcfb7b4d5a8656231c92ea28b6;i=22d18;b=4719a94961054d95860c8e259a6ae5e2;m=673454da98;t=55e063c70c14d;x=52adf0e3490e881e kernel: 4.13.11-300.fc27.x86_64 package: PackageKit-1.1.7-1.fc27 reason: packagekitd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1524712 has been marked as a duplicate of this bug. ***
Similar problem has been detected: DESDE QUE ACTUALICE EL SISTEMA SE DESCONECTA EL WIFI Y NO RECONOCE YA NINGUNA RED reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_malloc0 executable: /usr/libexec/packagekitd journald_cursor: s=855bfd45841b4aea97bc40068158220d;i=214d;b=26f0bb79fd704a22a9dafc4be5c9aa23;m=b917bd50;t=56594567129ba;x=3e53851142a4f55a kernel: 4.14.18-300.fc27.x86_64 package: PackageKit-1.1.8-1.fc27 reason: packagekitd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1572015 has been marked as a duplicate of this bug. ***
*** Bug 1578074 has been marked as a duplicate of this bug. ***
*** Bug 1597421 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.