nautilus crashed with SIGSEGV in dconf_engine_read()

[Akshat Jain]

Binary package hint: brasero

I was opening a CD using natty in Virtualbox

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
Date: Mon Jan 31 02:09:39 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2a29e85188: cmpb $0x1,(%rdi)
 PC (0x7f2a29e85188) ok
 source "$0x1" ok
 destination "(%rdi)" (0x7f2a36b1f000) in non-writable VMA region: 0x7f2a36b1f000-0x7f2a36b20000 r--s /home/akshat/.cache/dconf/user
SegvReason: writing VMA /home/akshat/.cache/dconf/user
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /usr/lib/gio/modules/libdconfsettings.so
 dconf_engine_read () from /usr/lib/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV in dconf_engine_read()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1288): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:1288): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
 (nautilus:1531): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[Apport retracing service (apport)]

StacktraceTop:
 dconf_engine_refresh_user (engine=0x11dfc00)
 dconf_engine_read (engine=0x11dfc00,

[Pedro Villavicencio (pedro)]

Thanks for the report, are you still able to reproduce this bug? Please test again and comment back, thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.