Version-Release number of selected component: tracker-0.14.4-1.fc18 Additional info: libreport version: 2.0.18 abrt_version: 2.0.17 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: magazine_chain_pop_head kernel: 3.6.6-3.fc18.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 magazine_chain_pop_head at gslice.c:532 : #1 thread_memory_magazine1_alloc at gslice.c:835 : #2 g_slice_alloc at gslice.c:994 : #3 g_slist_prepend at gslist.c:265 : #4 g_strsplit at gstrfuncs.c:2268 : #5 g_file_attribute_matcher_new at gfileinfo.c:2294 : #6 g_local_file_query_info at glocalfile.c:1208 : #7 query_info_async_thread at gfile.c:4989 : #8 run_in_thread at gsimpleasyncresult.c:869 : #9 io_job_thread at gioscheduler.c:162 Potential duplicate bug: 717852
Created attachment 654436 [details] File: core_backtrace
Created attachment 654437 [details] File: environ
Created attachment 654438 [details] File: backtrace
Created attachment 654439 [details] File: limits
Created attachment 654440 [details] File: cgroup
Created attachment 654441 [details] File: smolt_data
Created attachment 654442 [details] File: executable
Created attachment 654443 [details] File: maps
Created attachment 654444 [details] File: dso_list
Created attachment 654445 [details] File: build_ids
Created attachment 654446 [details] File: proc_pid_status
Created attachment 654447 [details] File: open_fds
Created attachment 654448 [details] File: var_log_messages
Program chrashed while extracting big rar archive. backtrace_rating: 4 Package: tracker-0.14.4-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Checked out a large source tree using Subversion. So, presumably, many file changes in a short period of time. backtrace_rating: 4 Package: tracker-0.14.4-1.fc18 Architecture: i686 OS Release: Fedora release 18 (Spherical Cow)
Happened while running git clone on Linux kernel sources. F18 too...
I was moving some folder. Suddenly a "Cannot remove XX folder" appeared ( don't know if this is related though ), and then the "Report bug" dialog appered. backtrace_rating: 4 Package: tracker-0.14.4-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
I was transferring huge amounts of data from my external HDD to the HD of the computer when a message from ABRT for tracker-store crash appeared. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: magazine_chain_pop_head executable: /usr/libexec/tracker-miner-fs kernel: 3.6.10-4.fc18.x86_64 package: tracker-0.14.5-2.fc18 reason: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV) runlevel: N 5 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.