Version-Release number of selected component: tracker-0.14.4-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs core_backtrace: crash_function: tracker_file_notifier_init executable: /usr/libexec/tracker-miner-fs kernel: 3.7.9-205.fc18.i686 uid: 29364 var_log_messages: Mar 20 17:31:39 swan abrt[2347]: Saved core dump of pid 1327 (/usr/libexec/tracker-miner-fs) to /var/spool/abrt/ccpp-2013-03-20-17:31:38-1327 (18604032 bytes) Truncated backtrace: Thread no. 1 (10 frames) #4 tracker_file_notifier_init at tracker-file-notifier.c:1265 #5 g_type_create_instance at gtype.c:1890 #6 g_object_constructor at gobject.c:1854 #8 g_object_new_valist at gobject.c:1835 #10 tracker_file_notifier_new at tracker-file-notifier.c:1321 #11 tracker_miner_fs_init at tracker-miner-fs.c:584 #12 g_type_create_instance at gtype.c:1882 #13 g_object_constructor at gobject.c:1854 #15 g_object_new_valist at gobject.c:1835 #16 g_initable_new_valist at ginitable.c:224 Potential duplicate: bug 837667
Created attachment 714289 [details] File: backtrace
Created attachment 714290 [details] File: cgroup
Created attachment 714291 [details] File: dso_list
Created attachment 714292 [details] File: environ
Created attachment 714293 [details] File: limits
Created attachment 714294 [details] File: maps
Created attachment 714295 [details] File: open_fds
Created attachment 714296 [details] File: proc_pid_status
Installed fedora installed mate installed cinnamon logged out logged in with cinnamon got message something went wrong logged out logged in with mate got error reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: tracker_file_notifier_init executable: /usr/libexec/tracker-miner-fs kernel: 3.11.4-101.fc18.x86_64 package: tracker-0.14.5-2.fc18 reason: Process /usr/libexec/tracker-miner-fs was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
*** Bug 951717 has been marked as a duplicate of this bug. ***
*** Bug 1064426 has been marked as a duplicate of this bug. ***
For some reason tracker_sparql_connection_get did not return a connection leading to an assertion: 'Tracker-CRITICAL **: Could not get SPARQL connection: The connection is closed'
*** Bug 879826 has been marked as a duplicate of this bug. ***
*** Bug 1013268 has been marked as a duplicate of this bug. ***
*** Bug 1004140 has been marked as a duplicate of this bug. ***