gvfsd-metadata crashed with SIGSEGV

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

Bug Description

Binary package hint: gvfs

When i moved full disc backup to a new computer or virtualbox, i got this error.

My ubuntu and other sofwares are up to date.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gvfs 1.6.1-0ubuntu1build1
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Mon Sep 13 14:49:45 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-metadata
InstallationMedia: Scaleworks Ubuntu 1.0 - Release i386
LiveMediaBuild: Scaleworks Ubuntu 1.0 - Release i386
ProcCmdline: /usr/lib/gvfs/gvfsd-metadata
ProcEnviron:
 SHELL=/bin/bash
 LANG=tr_TR.utf8
SegvAnalysis:
 Segfault happened at: 0x8052aa6: movl $0xffffffff,0x8(%eax)
 PC (0x08052aa6) ok
 source "$0xffffffff" ok
 destination "0x8(%eax)" (0x00000007) not located in a known VMA region (needed writable region)!
SegvReason: writing 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
Osman Tosun (rainman-neu) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_builder_write (builder=0x8515020,
 meta_tree_flush_locked (tree=<value optimized out>)
 meta_tree_flush (tree=0x85154e0) at metatree.c:2378
 writeout_timeout (data=0x8513ae8) at meta-daemon.c:61
 g_timeout_dispatch (source=0x85159a8, callback=0xffffffff,

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
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.