gvfsd-metadata crashed with SIGSEGV

[Charlie Kravetz]

Binary package hint: gvfs

Testing screen-reader installation for Natty Narwhal Beta2. image is Ubuntu-desktop-i386.iso, dated 2011-04-13.

1. start system with the cd in drive
2. hit any key after bios checks to get the cd menu
3. hit F5
4. down-arrow three times to screen-reader
5. enter two times
when desktop stops, orca starts and this error will appear shortly.

After the live desktop started, I used Alt+F1, right-arrow, right-arrow, down-arrow to select install 11.04. This error appears on screen.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gvfs 1.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Apr 13 18:43:51 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-metadata
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
ProcCmdline: /usr/lib/gvfs/gvfsd-metadata
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x804c92d: mov 0x8(%edx),%edx
 PC (0x0804c92d) 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/i386-linux-gnu/libglib-2.0.so.0
Title: gvfsd-metadata crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Charlie Kravetz (cjkgeek)]

Report made public; there is no private information, since this is a test machine only.

[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 #744836, 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.