Description of problem: Happened while in the overview, while looking at the weather information I believe. Version-Release number of selected component: zeitgeist-0.9.14-3.fc21 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: zeitgeist-datahub crash_function: append_value_to_blob executable: /usr/bin/zeitgeist-datahub kernel: 3.15.0-1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (1 frames) #0 append_value_to_blob at gdbusmessage.c:2182
Created attachment 910252 [details] File: backtrace
Created attachment 910253 [details] File: cgroup
Created attachment 910254 [details] File: core_backtrace
Created attachment 910255 [details] File: dso_list
Created attachment 910256 [details] File: environ
Created attachment 910257 [details] File: exploitable
Created attachment 910258 [details] File: limits
Created attachment 910259 [details] File: maps
Created attachment 910260 [details] File: open_fds
Created attachment 910261 [details] File: proc_pid_status
Created attachment 910262 [details] File: var_log_messages
Another user experienced a similar problem: Happened during boot. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/zeitgeist-datahub crash_function: append_value_to_blob executable: /usr/bin/zeitgeist-datahub kernel: 3.16.0-0.rc2.git1.1.fc21.x86_64 package: zeitgeist-0.9.14-3.fc21 reason: zeitgeist-datahub killed by SIGSEGV runlevel: unknown type: CCpp uid: 1000
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.