Version-Release number of selected component: PackageKit-0.9.4-4.fc22 Additional info: reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/libexec/packagekitd executable: /usr/libexec/packagekitd kernel: 3.17.0-0.rc1.git3.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #2 munmap at ../sysdeps/unix/syscall-template.S:81 #3 _dl_unmap_segments at ./dl-unmap-segments.h:32 #4 _dl_unmap at ../sysdeps/x86_64/tlsdesc.c:140 #5 _dl_close_worker at dl-close.c:641 #7 _dl_close at dl-close.c:775 #8 _dl_catch_error at dl-error.c:187 #9 _dlerror_run at dlerror.c:163 #10 __dlclose at dlclose.c:46 #11 _g_module_close at gmodule-dl.c:136 Potential duplicate: bug 1133296
Created attachment 931084 [details] File: backtrace
Created attachment 931085 [details] File: cgroup
Created attachment 931086 [details] File: core_backtrace
Created attachment 931087 [details] File: dso_list
Created attachment 931088 [details] File: environ
Created attachment 931089 [details] File: exploitable
Created attachment 931090 [details] File: limits
Created attachment 931091 [details] File: maps
Created attachment 931092 [details] File: open_fds
Created attachment 931093 [details] File: proc_pid_status
Created attachment 931094 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.