Version-Release number of selected component: zeitgeist-datahub-0.9.5-1.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: /usr/bin/zeitgeist-datahub crash_function: g_str_hash kernel: 3.5.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (9 frames) : #0 g_str_hash at ghash.c:1730 : #1 g_hash_table_lookup_node at ghash.c:401 : #2 g_hash_table_lookup at ghash.c:1074 : #3 zeitgeist_interpretation_for_mimetype at zeitgeist-mimetypes.c:167 : #4 recent_documents_kde_parse_file_co at kde-recent-document-provider.c:1000 : #5 g_simple_async_result_complete at gsimpleasyncresult.c:767 : #6 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:835 : #11 data_hub_run at zeitgeist-datahub.c:1270 : #12 data_hub_main at zeitgeist-datahub.c:1492
Created attachment 618902 [details] File: core_backtrace
Created attachment 618903 [details] File: environ
Created attachment 618904 [details] File: backtrace
Created attachment 618905 [details] File: limits
Created attachment 618906 [details] File: cgroup
Created attachment 618907 [details] File: maps
Created attachment 618908 [details] File: dso_list
Created attachment 618909 [details] File: open_fds
Created attachment 618910 [details] File: var_log_messages
It occurred just when I log in. backtrace_rating: 4 Package: zeitgeist-datahub-0.9.5-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle)
(In reply to comment #10) > It occurred just when I log in. Same problem here, first time after a long usage of F17.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.
This happened to me on Fedora 18 after a reboot. This still needs to be fixed.