I was updating an Oneiric i386 system when this crash occurred. The crash in bug 839286 also occurred (first), as well as a crash in oneconf-service which occurred before that and almost certainly triggered that crash, but I don't know if they are at all related to this. I suspect they are not.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-backends 1.9.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sun Sep 25 09:05:35 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-http
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/gvfs/gvfsd-http --spawner :1.1 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x1b00b8 <g_settings_schema_get_string+40>: mov 0xc(%eax),%eax
PC (0x001b00b8) ok
source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
g_settings_schema_get_string (schema=0x0, key=0x9272590 "http/") at /build/buildd/glib2.0-2.29.92/./gio/gsettingsschema.c:254
g_settings_get_child (settings=0x926eb68, name=0x3b6ae5 "http") at /build/buildd/glib2.0-2.29.92/./gio/gsettings.c:2275
?? () from /usr/lib/i386-linux-gnu/gio/modules/libgiognomeproxy.so
g_type_create_instance (type=153606688) at /build/buildd/glib2.0-2.29.92/./gobject/gtype.c:1885
g_object_constructor (type=153606688, n_construct_properties=0, construct_params=0x0) at /build/buildd/glib2.0-2.29.92/./gobject/gobject.c:1629
Title: gvfsd-http crashed with SIGSEGV in g_settings_schema_get_string()
UpgradeStatus: Upgraded to oneiric on 2011-06-18 (98 days ago)
UserGroups: adm admin dialout lpadmin plugdev sambashare
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.