Bug 614296

Summary: [abrt] dconf-0.4.1-2: Process /usr/libexec/dconf-service was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Kurt Driver <kurtdriver>
Component: dconfAssignee: Matthias Clasen <mclasen>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: eblake, mclasen, richard
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:115cc66297fb571a50b3edf15841dbc881bfcef7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-26 17:41:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Kurt Driver 2010-07-14 03:37:33 UTC 
abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/dconf-service
component: dconf
executable: /usr/libexec/dconf-service
global_uuid: 115cc66297fb571a50b3edf15841dbc881bfcef7
kernel: 2.6.35-0.31.rc4.git4.fc14.x86_64
package: dconf-0.4.1-2
rating: 0
reason: Process /usr/libexec/dconf-service was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Rawhide)
time: 1279057322
uid: 500

comment
-----
I ran pinball (from the repos) and it messed up my resolution. Maybe related? 
Or to the locking up of the trackpad a few minutes prior to runnung pinball?

How to reproduce
-----
1. I don't know. I read it in ABRT.
2. 
3.
Comment 1 Kurt Driver 2010-07-14 03:37:44 UTC 
Created attachment 431664 [details]
File: backtrace
Comment 2 Kurt Driver 2010-07-14 03:58:20 UTC 
I just realized that it was unrelated to either the lockup of the touchpad or pinball as it was several hours earlier. Sorry about the mixup.
Comment 3 Eric Blake 2010-07-21 22:46:02 UTC 
But just because it was unrelated to pinball doesn't mean you should summarily close this as NOTABUG.  I got the same ABRT backtrace in running a 32-bit rawhide VM hosted by a 64-bit F13 (and ABRT added me as CC to this bug), so this deserves proof that the issue has been resolved before it is closed.
Comment 4 Bug Zapper 2010-07-30 12:34:19 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Matthias Clasen 2010-08-26 17:41:43 UTC 
I am pretty sure this was fixed with dconf 0.5