Version-Release number of selected component: gvfs-1.18.3-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-metadata crash_function: verify_metadata_block executable: /usr/libexec/gvfsd-metadata kernel: 3.12.8-300.fc20.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 verify_metadata_block at metatree.c:186 #1 copy_tree_to_builder at metatree.c:2123 #2 meta_tree_flush_locked at metatree.c:2293 #3 meta_tree_flush at metatree.c:2315 #4 writeout_timeout at meta-daemon.c:62 Potential duplicate: bug 699109
Created attachment 857380 [details] File: backtrace
Created attachment 857381 [details] File: cgroup
Created attachment 857382 [details] File: core_backtrace
Created attachment 857383 [details] File: dso_list
Created attachment 857384 [details] File: environ
Created attachment 857385 [details] File: exploitable
Created attachment 857386 [details] File: limits
Created attachment 857387 [details] File: maps
Created attachment 857388 [details] File: open_fds
Created attachment 857389 [details] File: proc_pid_status
Created attachment 857390 [details] File: var_log_messages
Another user experienced a similar problem: Unknown reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-metadata crash_function: verify_metadata_block executable: /usr/libexec/gvfsd-metadata kernel: 3.14.7-200.fc20.x86_64 package: gvfs-1.18.3-2.fc20 reason: gvfsd-metadata killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Guys, are ever going to do something with this bug? I just see more and more people appearing in the CC list (i.e. hitting the issue) and it's been here for a while.
And the duplicate bug on Fedora 18 has been here for even much, much longer.
We know about the bug and we keep track on it, however we need a reproducer with empty metadata database. See for the detailed instruction: https://bugzilla.redhat.com/show_bug.cgi?id=699109#c74 *** This bug has been marked as a duplicate of bug 699109 ***