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.
Created attachment 431664 [details] File: backtrace
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.
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.
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
I am pretty sure this was fixed with dconf 0.5