gvfsd-trash crashed with signal 5 in g_main_context_new()

[Cristian Aravena Romero]

Hello,

I do not know how this happened.

Regards,
--
Cristian

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-daemons 1.33.91-0ubuntu1
Uname: Linux 4.13.1-041301-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 13 11:53:40 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationDate: Installed on 2017-07-05 (69 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/0
Signal: 5
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-trash crashed with signal 5 in g_main_context_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_wakeup_new () at ../../../../glib/gwakeup.c:161
 g_main_context_new () at ../../../../glib/gmain.c:658
 initable_init (initable=0x5633ea0afc20, cancellable=0x0, error=0x0) at ../../../../gio/gdbusproxy.c:1938
 g_initable_new_valist (object_type=<optimized out>, first_property_name=0x7fb566249a08 "g-flags", var_args=0x7ffe67588850, cancellable=0x0, error=0x0) at ../../../../gio/ginitable.c:248
 g_initable_new (object_type=<optimized out>, cancellable=cancellable@entry=0x0, error=error@entry=0x0, first_property_name=first_property_name@entry=0x7fb566249a08 "g-flags") at ../../../../gio/ginitable.c:162

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

Is that still an issue in newer Ubuntu series?
The problem here is 'Creating pipes for GWakeup' which is sign that something on the system is leaking fds, gvfs is just hitting an error due to the lack of resources on the system so it's not really a gvfs bug (unless it's the one having the leak, but that's not likely)

[Tom Reynolds (tomreyn)]

It is an issue for me on 18.04.2, see my recent duplicate reports.

What happened to the upstream bug report?

[Nathaniel Beaver (nathanielmbeaver)]

Upstream is here:

https://bugzilla.gnome.org/show_bug.cgi?id=787633

Was closed "as no further information has been provided", so didn't make the migration to Gitlab.

Potentially related upstream bugs:

https://gitlab.gnome.org/GNOME/gvfs/issues/261

https://gitlab.gnome.org/GNOME/gvfs/issues/400

https://gitlab.gnome.org/GNOME/gtk/issues/1010

https://bugzilla.gnome.org/show_bug.cgi?id=792331

https://bugzilla.gnome.org/show_bug.cgi?id=792335

Potentially related bugs elsewhere:

https://bugzilla.redhat.com/show_bug.cgi?id=1323079

The only workaround I've seen is "kill gvfsd-trash". I don't think anyone has been able to reliably reproduce it. If I had to guess, I think it might have to do with mounting and deleting files on USB flash drives.