gvfsd-trash crashed with SIGSEGV in g_vfs_job_emit_finished()

Bug #837193 reported by Alessandro Losavio
96
This bug affects 20 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Ubuntu 11.10 amd64 Beta1

Steps to reproduce it:

1) Open the trash via Launcher

Suddenly a crash appears to me

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs 1.9.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 30 08:54:09 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110812)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_spaw/0
SegvAnalysis:
 Segfault happened at: 0x7fe3c0dad6d4 <g_vfs_job_emit_finished+4>: movzbl 0x28(%rdi),%eax
 PC (0x7fe3c0dad6d4) ok
 source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_vfs_job_emit_finished () from /usr/lib/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/gvfs/libgvfsdaemon.so
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gvfsd-trash crashed with SIGSEGV in g_vfs_job_emit_finished()
UpgradeStatus: Upgraded to oneiric on 2011-08-27 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alessandro Losavio (alo21) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_vfs_job_emit_finished (job=0x0) at gvfsjob.c:323
 send_reply_cb (source_object=0x1bb85e0, res=<optimized out>, user_data=0x1bb94f0) at gvfschannel.c:613
 g_simple_async_result_complete (simple=0x1bcae40) at /build/buildd/glib2.0-2.29.16/./gio/gsimpleasyncresult.c:749
 complete_in_idle_cb (data=0x1bcae40) at /build/buildd/glib2.0-2.29.16/./gio/gsimpleasyncresult.c:761
 g_main_dispatch (context=0x1bb58f0) at /build/buildd/glib2.0-2.29.16/./glib/gmain.c:2439

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-amd64-retrace
Changed in gvfs (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Ian Nicholson (imnichol) wrote :

Occurred for me when I attempted to empty the trash by right clicking on the trash icon in the launcher and selecting "empty"

Revision history for this message
dazza5000 (darran-kelinske) wrote :

Happened to me too on 12.04 doing the same as Ian:

Occurred for me when I attempted to empty the trash by right clicking on the trash icon in the launcher and selecting "empty"

Running latest packages on precise

Revision history for this message
Redmar (redmar) wrote :

Happened to me on 12.04:

Used nautilus to navigate to the trash, and clicked 'empty trash' there. The crash occurred after I accepted the warning that the files would be permanently deleted.

Revision history for this message
Doug Fisherman (dougfishermancanada) wrote :

Same here, Rt click trash file folder to empty it. After I click empty trash..... boom. This new bug to me.
12.04b2 with daily updates.
Reboot confirms that the trash did indeed empty. It did not show as emptied until the file manager was closed and restarted.

Changed in gvfs (Ubuntu):
importance: Medium → High
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.