gvfsd-metadata crashed with SIGSEGV

Bug #642681 reported by mathieg2
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gvfs

Not sure what is causing this. Disks are a bit full

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gvfs 1.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sun Sep 19 11:00:35 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-metadata
ProcCmdline: /usr/lib/gvfs/gvfsd-metadata
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x804cb7a: mov 0x8(%edx),%edx
 PC (0x0804cb7a) 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 disk fax floppy fuse lpadmin mach mythtv netdev plugdev powerdev sambashare scanner tape vboxusers video

Revision history for this message
mathieg2 (graeme-salsaholics) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 copy_tree_to_builder (tree=0x951faf0, dirent=0x0, builder_file=0x9516be0)
 meta_tree_flush_locked (tree=<value optimized out>)
 meta_tree_flush (tree=0x951faf0) at metatree.c:2378
 writeout_timeout (data=0x9512c78) 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
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
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.