gvfsd-metadata crashed with SIGSEGV

[Chris J]

Binary package hint: gvfs

Blind crash, no user interaction involved. Let's see what the retrace pulls up.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gvfs 1.6.1-0ubuntu1build1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Sat Aug 14 15:36:15 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-metadata
ProcCmdline: /usr/lib/gvfs/gvfsd-metadata
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_GB:en
 LANG=en_GB.utf8
SegvAnalysis:
 Segfault happened at: 0x804d35a: mov 0x8(%edx),%edx
 PC (0x0804d35a) ok
 source "0x8(%edx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
Title: gvfsd-metadata crashed with SIGSEGV
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare scanner video

[Tim Croydon (timcroydon)]

I just had this problem return following upgrade from Lucid to Maverick beta. Is there any info I can provide to help?

It occurred shortly after login but didn't seem to be triggered by any sort of user interaction. There's nothing else in the logs within around the same time.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #405432, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.