Version-Release number of selected component: zeitgeist-0.9.14-2.fc21 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/zeitgeist-datahub crash_function: g_variant_lock executable: /usr/bin/zeitgeist-datahub kernel: 3.14.0-0.rc7.git0.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 g_variant_lock at gvariant-core.c:221 #1 g_variant_n_children at gvariant-core.c:929 #2 g_variant_get_child_value at gvariant-core.c:975 #3 g_variant_iter_next_value at gvariant.c:3074 #4 append_value_to_blob at gdbusmessage.c:2421
Created attachment 878582 [details] File: backtrace
Created attachment 878583 [details] File: cgroup
Created attachment 878584 [details] File: core_backtrace
Created attachment 878585 [details] File: dso_list
Created attachment 878586 [details] File: environ
Created attachment 878587 [details] File: exploitable
Created attachment 878588 [details] File: limits
Created attachment 878589 [details] File: maps
Created attachment 878590 [details] File: open_fds
Created attachment 878591 [details] File: proc_pid_status
Created attachment 878592 [details] File: var_log_messages
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.