Version-Release number of selected component: PackageKit-1.0.3-2.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_malloc0 executable: /usr/libexec/packagekitd kernel: 3.17.4-301.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #6 g_malloc0 at gmem.c:127 #7 g_malloc0_n at gmem.c:356 #8 g_hash_table_resize at ghash.c:542 #9 g_hash_table_maybe_resize at ghash.c:597 #10 g_hash_table_insert_node at ghash.c:923 #11 g_hash_table_insert_internal at ghash.c:1173 #12 g_key_file_add_key_value_pair at gkeyfile.c:3783 #13 g_key_file_parse_key_value_pair at gkeyfile.c:1309 #14 g_key_file_parse_line at gkeyfile.c:1147 #15 g_key_file_flush_parse_buffer at gkeyfile.c:1410
Created attachment 1012828 [details] File: backtrace
Created attachment 1012829 [details] File: cgroup
Created attachment 1012830 [details] File: core_backtrace
Created attachment 1012831 [details] File: dso_list
Created attachment 1012832 [details] File: environ
Created attachment 1012833 [details] File: limits
Created attachment 1012834 [details] File: maps
Created attachment 1012835 [details] File: open_fds
Created attachment 1012836 [details] File: proc_pid_status
Created attachment 1012837 [details] File: var_log_messages
This looks like a crash due to memory corruption that happened earlier. Unfortunately, there is not much that we can do to find out what caused it, from the information in the stacktrace.