abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: evolution component: evolution crash_function: shell_settings_pspec_for_key executable: /usr/bin/evolution kernel: 2.6.35.9-64.fc14.x86_64 package: evolution-2.32.1-1.fc14 rating: 4 reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1291980457 uid: 500 comment ----- In .xsession-errors: Electric Fence 2.2.2 Copyright (C) 1987-1999 Bruce Perens <bruce> (evolution:3198): GConf-CRITICAL **: gconf_schema_get_type: assertion `schema != NULL' failed (evolution:3198): GConf-CRITICAL **: gconf_schema_get_default_value: assertion `schema != NULL' failed (evolution:3198): GConf-CRITICAL **: gconf_value_new: assertion `GCONF_VALUE_TYPE_VALID(type)' failed evolution-shell-ERROR **: Unable to create EShellSettings property for GConf key '/apps/evolution/shell/file_chooser_folder' of type 'invalid' aborting... How to reproduce ----- 1. Evolution was ran with G_DEBUG=resident-modules,gc-friendly G_SLICE=always-malloc,debug-blocks under ElectricFence 2. Without ElectricFence, evolution didn't abort.
Created attachment 467955 [details] File: backtrace
Thanks for a bug report. The error means that Evolution failed to find a GConf scheme for "/apps/evolution/shell/file_chooser_folder" which is mandatory in 2.32.x. I see this GConf scheme in evolution source code, and it would exhibit this when run without ElectricFence too, thus I believe this is a bug of ElectricFence, preventing Evolution from reading its GConf schema definitions (or those are not installed in ElectricFence). In other words, this is not a bug in Evolution itself.
Yes, you're right, it's not a bug in evolution. I was searching this bug report to close it myself. ElectricFence seems to return memory address not aligned on 16 bytes boundaries as glibc does, and this seems to mess up gconf. I have reproduced the same problem with nautilus and gconf-editor. I will report a bug on ElectricFence and dig in gconf to see why it rely on 16 bytes alignment.
(In reply to comment #3) > I will report a bug on ElectricFence See bug 662085 on ElectricFence for more details
*** This bug has been marked as a duplicate of bug 662085 ***