Ubuntu
gvfs package

gvfsd-trash crashed with signal 5 in _g_dbus_oom()

Bug #982099 reported by malonee on 2012-04-15

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

gvfsd-trash crashes when trying to open trash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-daemons 1.12.0-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
Date: Sun Apr 15 00:28:29 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_US:en
LANG=en_US.UTF-8
Signal: 5
SourcePackage: gvfs
StacktraceTop:
_g_dbus_oom () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
_g_dbus_append_file_attribute () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
_g_dbus_append_file_info () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
?? ()
?? ()
Title: gvfsd-trash crashed with signal 5 in _g_dbus_oom()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

malonee (malon-gpm) wrote on 2012-04-15:

Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-16: 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 #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.