gvfsd-metadata crashed with SIGSEGV

Bug #549599 reported by LordPhoenix
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gvfs

Since upgrade from Karmic to Lucid I'v got many crash of gvfs-metadata. It's difficult to know what is making this crash but I think it occurs when There is an application wich is making important access to disks.
For example download with bit-torrent client or in web browser.

Sorry for my bad English I don't speak it very often. If necessary I can give you more details but in French :)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Mar 27 15:20:39 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gvfs/gvfsd-metadata
Package: gvfs 1.5.5-0ubuntu2
ProcCmdline: /usr/lib/gvfs/gvfsd-metadata
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.utf8
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
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
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
LordPhoenix (lorphoenix) wrote :
visibility: private → public
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 copy_tree_to_builder (tree=0x98c83b0, dirent=0x0, builder_file=0x98c85f0)
 meta_tree_flush_locked (tree=<value optimized out>)
 meta_tree_flush (tree=0x98c83b0) at metatree.c:2378
 writeout_timeout (data=0x98c8430) at meta-daemon.c:61
 ?? () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: removed: need-i386-retrace
Revision history for this message
Tim Croydon (timcroydon) wrote :

Since upgrading to Lucid I usually get this bug occur shortly after logging in after starting system. It occasionally happens after the system has been running for a while too but can't identify the trigger.

Happy to help trace/debug this but I'm a bit of a Linux n00b so don't know where to start. Let me know if I can do anything to help.

T

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.