gvfsd-metadata crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gvfs
right after reboot (after update)
this is reproducable and occurs on every reboot
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gvfs 1.6.3-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Sat Sep 25 14:15:06 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x804ccae: mov 0x8(%ecx,
PC (0x0804ccae) ok
source "0x8(%ecx,%eax,8)" (0xb77da000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: gvfsd-metadata crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
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 #643618, 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.