Bug 1033475

Summary: [abrt] PackageKit-0.8.9-6.fc19: pk_transaction_db_defer_write_job_count_cb: Process /usr/libexec/packagekitd was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Thomas Lofgren <thomas.n.lofgren>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jonathan, lso, rdieter, rhughes, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3f9d28a845a0a3ce2e19a1a054df5e334b013e4f
Whiteboard: abrt_hash:75e7c753896f886d0b0856a7454d9fb590f89b6d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-22 10:38:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
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 Thomas Lofgren 2013-11-22 08:18:57 UTC 
Description of problem:
This happens in background. Guessing it happens whenever packagekitd is testing for updates. Sadly I don't have more information because it crashes in the middle of the night.

Version-Release number of selected component:
PackageKit-0.8.9-6.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: pk_transaction_db_defer_write_job_count_cb
executable:     /usr/libexec/packagekitd
kernel:         3.11.8-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (1 frames)
 #2 pk_transaction_db_defer_write_job_count_cb at pk-transaction-db.c:528

Potential duplicate: bug 880119
Comment 1 Thomas Lofgren 2013-11-22 08:19:05 UTC 
Created attachment 827615 [details]
File: backtrace
Comment 2 Thomas Lofgren 2013-11-22 08:19:08 UTC 
Created attachment 827616 [details]
File: cgroup
Comment 3 Thomas Lofgren 2013-11-22 08:19:12 UTC 
Created attachment 827617 [details]
File: core_backtrace
Comment 4 Thomas Lofgren 2013-11-22 08:19:16 UTC 
Created attachment 827620 [details]
File: dso_list
Comment 5 Thomas Lofgren 2013-11-22 08:19:20 UTC 
Created attachment 827622 [details]
File: environ
Comment 6 Thomas Lofgren 2013-11-22 08:19:23 UTC 
Created attachment 827624 [details]
File: limits
Comment 7 Thomas Lofgren 2013-11-22 08:19:26 UTC 
Created attachment 827627 [details]
File: maps
Comment 8 Thomas Lofgren 2013-11-22 08:19:30 UTC 
Created attachment 827629 [details]
File: open_fds
Comment 9 Thomas Lofgren 2013-11-22 08:19:34 UTC 
Created attachment 827632 [details]
File: proc_pid_status
Comment 10 Thomas Lofgren 2013-11-22 08:19:37 UTC 
Created attachment 827634 [details]
File: var_log_messages
Comment 11 Richard Hughes 2013-11-22 10:38:18 UTC 
You've got some disk corruption going on: "failed to set job id: database disk image is malformed"

This might fix it:

rm /var/lib/PackageKit/transactions.db

Then reboot. I've added this to PackageKit as we don't need to abort the daemon just because we can't log the transaction:

commit 1af9673897abc949ada9f11db33e5f152ea3c517
Author: Richard Hughes <richard>
Date:   Fri Nov 22 10:36:46 2013 +0000

    Do not abort the daemon if we can't write to the transaction database
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1033475

:100644 100644 773d041... ff16029... M  src/pk-transaction-db.c

Richard.