Bug 683251

Summary: [abrt] dconf-0.7.2-3: dconf_state_init_session: Process /usr/libexec/dconf-service was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Andrew Gormanly <a.gormanly>
Component: dconfAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dlelliott99, mclasen, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fcf5f9f1fca266336246ec8f83fda3e260a1736b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:47:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Andrew Gormanly 2011-03-08 22:16:02 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 5567 bytes
cmdline: /usr/libexec/dconf-service
component: dconf
Attached file: coredump, 561152 bytes
crash_function: dconf_state_init_session
executable: /usr/libexec/dconf-service
kernel: 2.6.38-0.rc6.git6.1.fc15.x86_64
package: dconf-0.7.2-3
rating: 4
reason: Process /usr/libexec/dconf-service was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1299622433
uid: 500

How to reproduce
-----
1. Logged in
2.
3.
Comment 1 Andrew Gormanly 2011-03-08 22:16:04 UTC 
Created attachment 483043 [details]
File: backtrace
Comment 2 dlelliott99 2011-03-17 02:54:58 UTC 
Package: dconf-0.7.2-3
Architecture: i686
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1.Not sure
2.
3.


Comment
-----
See above
Comment 3 abrt-bot 2012-03-21 14:47:00 UTC 
Backtrace analysis found this bug to be similar to bug #668322, closing as duplicate.

Bugs which were found to be similar to this bug: bug #654557, bug #668322, bug #702949

This comment is automatically generated.

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