Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 221176 bytes cmdline: dconf-editor component: dconf Attached file: coredump, 13991936 bytes crash_function: g_type_check_instance_is_a executable: /usr/bin/dconf-editor kernel: 2.6.38-0.rc4.git0.2.fc15.x86_64 package: dconf-editor-0.7.2-3 rating: 4 reason: Process /usr/bin/dconf-editor was killed by signal 11 (SIGSEGV) release: Fedora release 15 (Rawhide) time: 1297853576 uid: 500 How to reproduce ----- 1. start dconf-editor 2. click on 'apps' 3. Crash
Created attachment 479103 [details] File: backtrace
This is Fedora 15 Alpha TC2 with to latest updates from f15 repositories
Created attachment 479105 [details] console output
Package: dconf-editor-0.7.2-3 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Execute dconf-editor.
Package: dconf-editor-0.7.2-3 Architecture: x86_64 OS Release: Fedora release 16 (Rawhide) How to reproduce ----- 1. Open any category on the left. 2. Wait for a second.
For current F15 including updates-testing, dconf-editor-0.7.2-3 does not crash anymore, thus, the culprit hid elsewhere.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.