Ubuntu
gvfs package

gvfsd-trash crashed with signal 5 in _g_dbus_oom()

Bug #812476 reported by (J)Aloittelija
266
This bug affects 54 people
Affects Status Importance Assigned to Milestone
gvfs
Expired
Critical
gvfs (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I was updating system and the crash reports appeared.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs 1.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
Architecture: i386
Date: Mon Jul 18 21:34:41 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
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-07-15 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
(J)Aloittelija (jari-aho) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _g_dbus_oom () at gvfsdbusutils.c:35
 _g_dbus_append_file_attribute (iter=0xbfac34fc, attribute=0x865a0d0 "standard::display-name", status=G_FILE_ATTRIBUTE_STATUS_UNSET, type=G_FILE_ATTRIBUTE_TYPE_STRING, value_p=0x863b360) at gvfsdaemonprotocol.c:266
 _g_dbus_append_file_info (iter=0x865a894, info=0x861db90) at gvfsdaemonprotocol.c:303
 g_vfs_job_enumerate_add_info (job=0x865a810, info=0x861db90) at gvfsjobenumerate.c:202
 trash_backend_enumerate_root (vfs_backend=0x862c410, job=0x865a810, filename=0x8642f68 "/", attribute_matcher=0x8643a38, flags=G_FILE_QUERY_INFO_NONE) at gvfsbackendtrash.c:577

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=655138

visibility: private → public
Changed in gvfs (Ubuntu):
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
importance: Unknown → Critical
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
status: New → Confirmed
Apport retracing service (apport)
tags: added: bugpattern-needed
Brian Murray (brian-murray)
tags: added: precise
Revision history for this message
Jakob Unterwurzacher (jakobunt) wrote :

Once this happens you can't open the trash applet any more.
Emptying ~/.local/share/Trash is not enough to get it working again, suggestions? (without rebooting or logging off)

Revision history for this message
Ari (ari-lp) wrote :

I can confirm this bug on Ubuntu 12.04.3 LTS. Like Jakob said after the crash the trash can't be accessed any more. What works for me though is manually deleting ~/.local/share/Trash/files and ~/.local/share/Trash/info.

Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
status: Confirmed → Expired
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Has this been a problem in xenial or later?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.