Ubuntu
gvfs package

gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()

Bug #1217652 reported by Cristian Aravena Romero on 2013-08-28

This bug report is a duplicate of: Bug #1213555: gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gvfs (Ubuntu)	New	Undecided	Unassigned

Bug Description

Connect Android and Crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.2-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Tue Aug 27 22:24:07 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationDate: Installed on 2013-07-31 (27 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.9 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANGUAGE=es_CL:es
LANG=es_CL.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fa99ce09b84 <g_object_unref+20>: cmpq $0x50,(%rax)
PC (0x7fa99ce09b84) ok
source "$0x50" ok
destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? ()
?? ()
g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2013-08-28:

Dependencies.txt Edit (8.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-28: This bug is a duplicate

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 #1213555, 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.