gvfsd-http crashed with SIGSEGV in g_error_to_daemon_reply()

Bug #1130820 reported by Gleidson Galindo on 2013-02-20
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Undecided
Unassigned

Bug Description

Não sei ao certo o que ocorreu. Penso que foi ao tentar retomar uma transferência usando o SteadyFlow.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Wed Feb 20 14:50:54 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-http
InstallationDate: Installed on 2013-02-06 (13 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130206)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-http --spawner :1.11 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb772f18e <g_error_to_daemon_reply+30>: mov (%edi),%eax
 PC (0xb772f18e) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_error_to_daemon_reply () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 g_vfs_channel_send_error () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 g_cclosure_marshal_VOID__VOIDv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-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

Gleidson Galindo (omggalindo) wrote :

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

information type: Private → Public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers