After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 601723 - nautilus crashed with SIGSEGV
nautilus crashed with SIGSEGV
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: metadata
1.4.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-11-12 17:56 UTC by Pedro Villavicencio
Modified: 2015-02-20 11:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Pedro Villavicencio 2009-11-12 17:56:37 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/473002

".

+ Trace 219054

Thread 1 (process 5647)

  • #0 meta_journal_iterate
    at metatree.c line 1293
  • #1 meta_journal_reverse_map_path_and_key
    at metatree.c line 1438
  • #2 meta_tree_lookup_string
  • #3 _g_daemon_vfs_append_metadata_for_set
  • #4 g_daemon_vfs_local_file_set_attributes
  • #5 ??
    from /usr/lib/libgio-2.0.so.0
  • #6 ??
    from /usr/lib/libgio-2.0.so.0
  • #7 g_file_set_attributes_from_info
    from /usr/lib/libgio-2.0.so.0
  • #8 ??
    from /usr/lib/libgio-2.0.so.0
  • #9 ??
    from /usr/lib/libgio-2.0.so.0
  • #10 ??
    from /usr/lib/libgio-2.0.so.0
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #14 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130 






Comment 1


Tomas Bzatek





          2009-11-13 14:00:27 UTC
        



(In reply to comment #0)
> this report has been filed here:

Can you please ask the reporter for /home/sergio/.local/share/gvfs-metadata/home* files? Please note the file is being constantly rewritten so files must be picked up right after the crash happens. I'd like to see what's happening there.

Of course without proper repro steps we're unable to fix the real issue, only consequences (which I tend not to push upstream until we know what's really going on).






Comment 3


Ondrej Holy





          2015-02-20 11:48:22 UTC
        



It is an old bug and several fixes has been pushed into metadata code since this bug was reported. Closing as obsolete, because I think it was fixed with Bug 637095 and also there aren't any abrt bug reports with such backtrace recently. Please reopen if you are still facing those crashes.