gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #1218560 reported by Joel Salas on 2013-08-29
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Undecided
Unassigned

Bug Description

Docked Thinkpad T530, opened screen and got this error.

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
CrashCounter: 1
Date: Thu Aug 29 10:44:41 2013
ExecutablePath: /usr/lib/gvfs/gvfs-afc-volume-monitor
InstallationDate: Installed on 2013-08-27 (2 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfs-afc-volume-monitor
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f4f28c79c9c <g_type_check_instance_is_a+60>: testb $0x4,0x16(%r8)
 PC (0x7f4f28c79c9c) ok
 source "$0x4" ok
 destination "0x16(%r8)" (0x7f4f2000ae8016) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Joel Salas (joel-w) 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 #1214204, 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-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers