Description of problem: Just logging in to a gnome3 session triggers this, it likely does not like one of my files. Version-Release number of selected component: tracker-0.16.1-1.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/tracker-extract crash_function: g_mutex_get_impl executable: /usr/libexec/tracker-extract kernel: 3.9.3-301.fc19.x86_64 runlevel: N 5 uid: 500 Truncated backtrace: Thread no. 1 (10 frames) #0 g_mutex_get_impl at gthread-posix.c:121 #1 g_mutex_lock at gthread-posix.c:210 #2 bin_element_is_sink at gstbin.c:1674 #3 filter_next at gstiterator.c:480 #4 gst_iterator_next at gstiterator.c:357 #5 gst_iterator_fold at gstiterator.c:611 #6 gst_bin_query at gstbin.c:3827 #7 gst_element_query_duration at gstutils.c:2186 #8 discoverer_collect at gstdiscoverer.c:1161 #9 gst_discoverer_discover_uri at gstdiscoverer.c:1755 Potential duplicate: bug 828777
Created attachment 752669 [details] File: backtrace
Created attachment 752670 [details] File: cgroup
Created attachment 752671 [details] File: core_backtrace
Created attachment 752672 [details] File: dso_list
Created attachment 752673 [details] File: environ
Created attachment 752674 [details] File: limits
Created attachment 752675 [details] File: maps
Created attachment 752676 [details] File: open_fds
Created attachment 752677 [details] File: proc_pid_status
Created attachment 752678 [details] File: var_log_messages
Happened on my system just now. Abrt doesn't upload traces since the bug is already filed.
This problem occurrs every time right after logging in to Gnome/Cinnamon reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/tracker-extract crash_function: g_mutex_get_impl executable: /usr/libexec/tracker-extract kernel: 3.10.11-200.fc19.i686 package: tracker-0.16.2-1.fc19 reason: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hi, thank you for this bug. Now we have in repos 1.0.2 so I think you can't reproduce this bug. If you can - please re-open!