gvfsd-metadata crashed with SIGSEGV

Bug #641061 reported by Marco Simonelli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

simply i played a youtube video

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gvfs 1.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 17 07:58:58 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-metadata
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100816)
ProcCmdline: /usr/lib/gvfs/gvfsd-metadata
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=it_IT.utf8
SegvAnalysis:
 Segfault happened at: 0x405796: mov 0x8(%rsi),%esi
 PC (0x00405796) ok
 source "0x8(%rsi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%esi" 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 cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.