gvfsd-afc crashed with SIGSEGV in g_vfs_job_try()

Bug #859306 reported by Michael Gratton
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Medium
Unassigned

Bug Description

Tried adding a contact using gnome-contacts.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-backends 1.9.5-0ubuntu2
Uname: Linux 3.0.0-b43+ x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sun Sep 25 16:45:20 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/gvfs/gvfsd-afc
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-afc --spawner :1.1 /org/gtk/gvfs/exec_spaw/0
ProcCwd: /
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 g_vfs_job_try () from /usr/lib/gvfs/libgvfsdaemon.so
 g_vfs_daemon_queue_job () from /usr/lib/gvfs/libgvfsdaemon.so
 g_closure_invoke (closure=0x20a1510, return_value=0x0, n_param_values=2, param_values=0x20aa700, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.29.92/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x20ae010, emission_return=0x0, instance_and_params=0x20aa700) at /build/buildd/glib2.0-2.29.92/./gobject/gsignal.c:3272
Title: gvfsd-afc crashed with SIGSEGV in g_vfs_job_try()
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (2 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Michael Gratton (mjog) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_vfs_job_try (job=0x20af880) at gvfsjob.c:216
 g_vfs_daemon_queue_job (daemon=0x2099640, job=0x20af880) at gvfsdaemon.c:462
 g_closure_invoke (closure=0x20a1510, return_value=0x0, n_param_values=2, param_values=0x20aa700, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.29.92/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x20ae010, emission_return=0x0, instance_and_params=0x20aa700) at /build/buildd/glib2.0-2.29.92/./gobject/gsignal.c:3272

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
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 811049, so it 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.

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.