Ubuntu
gvfs package

gvfsd-trash crashed with signal 5 in _g_dbus_oom()

Bug #871361 reported by Igor Lemos on 2011-10-09

This bug report is a duplicate of: Bug #812476: gvfsd-trash crashed with signal 5 in _g_dbus_oom(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gvfs (Ubuntu)	New	Undecided	Unassigned

Bug Description

sem detalhes

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs 1.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CheckboxSubmission: 68c348da0ce8873ebe5733bc60e23afd
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Sun Oct 9 13:28:41 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_spaw/0
Signal: 5
SourcePackage: gvfs
StacktraceTop:
_g_dbus_oom () from /usr/lib/gvfs/libgvfscommon.so
_g_dbus_append_file_attribute () from /usr/lib/gvfs/libgvfscommon.so
_g_dbus_append_file_info () from /usr/lib/gvfs/libgvfscommon.so
g_vfs_job_enumerate_add_info () from /usr/lib/gvfs/libgvfsdaemon.so
?? ()
Title: gvfsd-trash crashed with signal 5 in _g_dbus_oom()
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (15 days ago)
UserGroups: adm admin lpadmin nopasswdlogin sambashare

Tags:

Revision history for this message

Igor Lemos (l88os) wrote on 2011-10-09:

ProcEnviron.txt Edit (141 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-09: This bug is a duplicate

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 #812476, 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.