gvfsd-metadata crashed with SIGSEGV

Bug #410308 reported by Michael Sinchenko
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Aug 7 07:04:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gvfs/gvfsd-metadata
NonfreeKernelModules: nvidia
Package: gvfs 1.3.3-0ubuntu1
ProcCmdline: /usr/lib/gvfs/gvfsd-metadata
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x804d2ea <g_get_current_dir@plt+8738>: mov 0x8(%edx),%edx
 PC (0x0804d2ea) 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 /usr/lib/libglib-2.0.so.0
Title: gvfsd-metadata crashed with SIGSEGV
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

visibility: private → public
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.