Bug 1480351

Summary: [abrt] PackageKit: _g_log_abort(): packagekitd killed by signal 5
Product: [Fedora] Fedora Reporter: Erik Lentz <dev>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: daniel, jonathan, klember, kondor6c, nicolegossettm, rdieter, rhughes, smparrish, tmerz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3ceb111c2b12ababe827bdb1b2ab8ecc00a9c5c4
Whiteboard: abrt_hash:cf2a227223f0569674f468c3ad5545bd7d760142;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:46:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Erik Lentz 2017-08-10 19:47:00 UTC
Description of problem:
A packager from copr repo tcg/discord fails to run.

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: _g_log_abort
executable:     /usr/libexec/packagekitd
journald_cursor: s=4ca7547f09334919a7f6bf5fcabebbe5;i=9ccddd;b=b1cdc145e37b490f843f4e24d095e76e;m=997159;t=555b3b091437f;x=4641fbcf7a9c5e5a
kernel:         4.11.11-300.fc26.x86_64+debug
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 _g_log_abort at gmessages.c:549
 #1 g_log_default_handler at gmessages.c:3036
 #4 pk_backend_initialize at pk-backend-dnf.c:249
 #5 pk_backend_load at pk-backend.c:601
 #6 pk_engine_load_backend at pk-engine.c:1048

Potential duplicate: bug 1398429

Comment 1 Erik Lentz 2017-08-10 19:47:05 UTC
Created attachment 1311866 [details]
File: backtrace

Comment 2 Erik Lentz 2017-08-10 19:47:06 UTC
Created attachment 1311867 [details]
File: cgroup

Comment 3 Erik Lentz 2017-08-10 19:47:07 UTC
Created attachment 1311868 [details]
File: core_backtrace

Comment 4 Erik Lentz 2017-08-10 19:47:08 UTC
Created attachment 1311869 [details]
File: cpuinfo

Comment 5 Erik Lentz 2017-08-10 19:47:09 UTC
Created attachment 1311870 [details]
File: dso_list

Comment 6 Erik Lentz 2017-08-10 19:47:10 UTC
Created attachment 1311871 [details]
File: environ

Comment 7 Erik Lentz 2017-08-10 19:47:11 UTC
Created attachment 1311872 [details]
File: limits

Comment 8 Erik Lentz 2017-08-10 19:47:12 UTC
Created attachment 1311873 [details]
File: maps

Comment 9 Erik Lentz 2017-08-10 19:47:13 UTC
Created attachment 1311874 [details]
File: open_fds

Comment 10 Erik Lentz 2017-08-10 19:47:14 UTC
Created attachment 1311875 [details]
File: proc_pid_status

Comment 11 Erik Lentz 2017-08-10 19:47:15 UTC
Created attachment 1311876 [details]
File: var_log_messages

Comment 12 Erik Lentz 2017-08-14 13:18:05 UTC
Similar problem has been detected:

Trying to build package at system startup.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: _g_log_abort
executable:     /usr/libexec/packagekitd
journald_cursor: s=4ca7547f09334919a7f6bf5fcabebbe5;i=9d0843;b=f59bbb30f3d14cc79310cb069b1bd690;m=6662a7c57;t=55673301fe765;x=d9f5a034f564ab0b
kernel:         4.11.11-300.fc26.x86_64+debug
package:        PackageKit-1.1.6-2.fc26
reason:         packagekitd killed by signal 5
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 Erik Lentz 2017-08-18 13:13:00 UTC
Similar problem has been detected:

1. Building package on bootup

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: _g_log_abort
executable:     /usr/libexec/packagekitd
journald_cursor: s=4ca7547f09334919a7f6bf5fcabebbe5;i=9d414e;b=b0cb7b07f65147b3afa9eb3972d5c933;m=dbac8478d;t=556d7c54b45d7;x=e4862de5a8ef6657
kernel:         4.12.5-300.fc26.x86_64+debug
package:        PackageKit-1.1.6-2.fc26
reason:         packagekitd killed by signal 5
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 14 Thorsten 2017-09-08 19:52:30 UTC
*** Bug 1489961 has been marked as a duplicate of this bug. ***

Comment 15 daniel-wtd 2017-09-25 17:34:57 UTC
Similar problem has been detected:

The exact cause seems unknown.

Neither "systemctl restart packagekit.service" not other software like Gnome-Software or Deja-Dup are able to connect to the service.

Removing 
/var/lib/PackageKit/*.db 
or
//var/cache/PackageKit/26/hawkey/@System.solv

seems to help.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: _g_log_abort
executable:     /usr/libexec/packagekitd
journald_cursor: s=6a94cc533bb4434ca995fe88ffda9717;i=13999;b=f03746c2c22745c6b7751d35ed11d452;m=2378251a36;t=559f654b8d805;x=99025fb905bd21b7
kernel:         4.12.12-300.fc26.x86_64
package:        PackageKit-1.1.6-2.fc26
reason:         packagekitd killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 16 daniel-wtd 2017-09-25 18:06:59 UTC
Similar problem has been detected:

After editing a repofile from:
metadata_expire=0
to
metadata_expire=1d

the problem was fixed.

Seems like a change in package kit or unwanted behaviour here.

Have informed the repo-maintainer, too.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: _g_log_abort
executable:     /usr/libexec/packagekitd
journald_cursor: s=6a94cc533bb4434ca995fe88ffda9717;i=152d7;b=645a9badf23840a187d4aabab542f9b9;m=6a74a0c4;t=55a070f6ba4d5;x=f420f96a5eb79bba
kernel:         4.12.13-300.fc26.x86_64
package:        PackageKit-1.1.6-2.fc26
reason:         packagekitd killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 17 unixinskie 2017-10-01 04:04:46 UTC
*** Bug 1497497 has been marked as a duplicate of this bug. ***

Comment 18 Fedora End Of Life 2018-05-03 08:21:14 UTC
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.

Comment 19 Fedora End Of Life 2018-05-29 11:46:42 UTC
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.