Ubuntu
gvfs package

gvfsd-http crashed with SIGSEGV in g_settings_get_child()

Bug #852435 reported by Erwin van Rijsewijk
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-backends 1.9.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 12 08:04:33 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-http
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/gvfs/gvfsd-http --spawner :1.73 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=nl_NL:en_US:en
 LANG=nl_NL.utf8
SegvAnalysis:
 Segfault happened at: 0x7fdf7e5df1be: mov 0x18(%rdi),%rax
 PC (0x7fdf7e5df1be) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_child () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-http crashed with SIGSEGV in g_settings_get_child()
UpgradeStatus: Upgraded to oneiric on 2011-09-05 (11 days ago)
UserGroups: adm admin audio cdrom dialout floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.