Bug 632963 - [abrt] GConf2-2.31.91-1.fc14: impl_ConfigDatabase_set: Process /usr/libexec/gconfd-2 was killed by signal 11 (SIGSEGV)
Summary: [abrt] GConf2-2.31.91-1.fc14: impl_ConfigDatabase_set: Process /usr/libexec/g...
Keywords:
Status: CLOSED DUPLICATE of bug 688300
Alias: None
Product: Fedora
Classification: Fedora
Component: GConf2
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8be1d325a4ccbfdfd8fc3a68599...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-12 09:16 UTC by Kjartan Maraas
Modified: 2011-12-14 19:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-14 19:43:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (10.46 KB, text/plain)
2010-09-12 09:16 UTC, Kjartan Maraas
no flags Details

Description Kjartan Maraas 2010-09-12 09:16:27 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gconfd-2
component: GConf2
crash_function: impl_ConfigDatabase_set
executable: /usr/libexec/gconfd-2
kernel: 2.6.35.4-12.fc14.i686.PAE
package: GConf2-2.31.91-1.fc14
rating: 4
reason: Process /usr/libexec/gconfd-2 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1284245434
uid: 500

comment
-----
I think this happened while compiling GNOME using jhbuild. I've noticed error messages from
gconfd-2 sometimes when jhbuild is in the make install stage and installas schemas.

Comment 1 Kjartan Maraas 2010-09-12 09:16:30 UTC
Created an attachment (id=446727)
File: backtrace

Comment 2 Kjartan Maraas 2010-10-24 16:35:05 UTC
Package: GConf2-2.31.91-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. compiled hamster-applet in jhbuild
2. gconfd-2 crashed during make install
3.

Comment 3 Kjartan Maraas 2011-12-14 19:43:09 UTC

*** This bug has been marked as a duplicate of bug 688300 ***


Note You need to log in before you can comment on or make changes to this bug.