gvfsd-fuse crashed with SIGSEGV in malloc()

[Michal Hruby]

No details...

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-fuse 1.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 1 01:13:12 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-fuse
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120923)
ProcCmdline: /usr/lib/gvfs//gvfsd-fuse -f /home/username/.gvfs
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7f1a6fe23c5f: mov 0x10(%r14),%r8
 PC (0x7f1a6fe23c5f) ok
 source "0x10(%r14)" (0x65722d6576697274) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 g_malloc (n_bytes=n_bytes@entry=31) at /build/buildd/glib2.0-2.34.0/./glib/gmem.c:159
 g_strdup (str=str@entry=0x7f1a64010c30 "drive-removable-media-symbolic") at /build/buildd/glib2.0-2.34.0/./glib/gstrfuncs.c:364
 g_themed_icon_set_property (object=0x7f1a68004410, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at /build/buildd/glib2.0-2.34.0/./gio/gthemedicon.c:120
Title: gvfsd-fuse crashed with SIGSEGV in malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1057090, 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.