gvfsd-archive crashed with SIGSEGV in dbus_message_get_sender()

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

Bug Description

just crashed not sure why

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.11.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Feb 5 08:15:05 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-archive
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/gvfs/gvfsd-archive file=/media/VideoGameDrive/Anomaly/AnomalyWarzoneEarth
SegvAnalysis:
 Segfault happened at: 0x7f2591a24110: mov 0x8(%rdi,%rbp,4),%esi
 PC (0x7f2591a24110) ok
 source "0x8(%rdi,%rbp,4)" (0xaaaaaaaaaaaaaae6) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_get_sender () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_new_method_return () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
Title: gvfsd-archive crashed with SIGSEGV in dbus_message_get_sender()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

Revision history for this message
TheMixtureMedia (mpmckinnon) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #816087, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-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.