gvfsd-http crashed with SIGSEGV in g_variant_unref()

Bug #816814 reported by fabrizio columbano
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs
New
Critical
gvfs (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

gvfsd-http crashed with SIGSEGV in g_variant_unref()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-backends 1.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Wed Jul 27 09:17:53 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-http
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-http --spawner :1.3 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=it_CH.UTF-8
 LANGUAGE=it_CH:it
 LANG=it_CH.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f0beb8e1ba9 <g_variant_unref+9>: lock xadd %eax,0x24(%rdi)
 PC (0x7f0beb8e1ba9) ok
 source "%eax" ok
 destination "0x24(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_settings_get_string () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
 ?? () from /usr/lib/libsoup-2.4.so.1
Title: gvfsd-http crashed with SIGSEGV in g_variant_unref()
UpgradeStatus: Upgraded to oneiric on 2011-07-27 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
fabrizio columbano (fabrizio-columbano) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_variant_unref (value=0x0) at /build/buildd/glib2.0-2.29.14/./glib/gvariant-core.c:617
 g_settings_get_string (settings=<value optimized out>, key=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./gio/gsettings.c:1770
 update_settings (proxy_resolver=<value optimized out>, uri=0x25f92d0 "http://screenshots.ubuntu.com/screenshot-with-version/canorus/0.7-3", cancellable=0x260d330, error=0x7fff7e19b4d8) at gproxyresolvergnome.c:206
 g_proxy_resolver_gnome_lookup (proxy_resolver=<value optimized out>, uri=0x25f92d0 "http://screenshots.ubuntu.com/screenshot-with-version/canorus/0.7-3", cancellable=0x260d330, error=0x7fff7e19b4d8) at gproxyresolvergnome.c:463
 g_proxy_resolver_gnome_lookup_async (proxy_resolver=0x25f20e0, uri=0x25f92d0 "http://screenshots.ubuntu.com/screenshot-with-version/canorus/0.7-3", cancellable=0x260d330, callback=<value optimized out>, user_data=0x25f4f60) at gproxyresolvergnome.c:591

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=655427

visibility: private → public
Changed in gvfs (Ubuntu):
status: New → Triaged
Changed in gvfs:
importance: Unknown → Critical
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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