gvfsd-http crashed with SIGSEGV in g_error_to_daemon_reply()

Bug #1162416 reported by Nathan Williams on 2013-03-31
58
This bug affects 9 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Medium
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.16.0-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 30 23:29:40 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-http
InstallationDate: Installed on 2013-03-01 (29 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130227.1)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-http --spawner :1.8 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f40a2b98505 <g_error_to_daemon_reply+37>: mov (%rdi),%edi
 PC (0x7f40a2b98505) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_error_to_daemon_reply () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 g_vfs_channel_send_error () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-http crashed with SIGSEGV in g_error_to_daemon_reply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

information type: Private → Public

StacktraceTop:
 g_error_to_daemon_reply (error=0x0, seq_nr=0, len_out=len_out@entry=0x7fff4fe7b058) at gvfsdaemonutils.c:51
 g_vfs_channel_send_error (channel=0xde90d0, error=<optimized out>) at gvfschannel.c:691
 _g_closure_invoke_va (closure=0xdb3310, return_value=0x0, instance=0x7f4090003ab0, args=0x7fff4fe7b338, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x7f4090003ab0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff4fe7b338) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3234
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3384

Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in gvfs (Ubuntu):
status: New → Confirmed

Also happened to me, in a random fashion.

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

Other bug subscribers