Red Hat Bugzilla – Bug 869833
Can't report a problem with evolution-alarm-notify because it requires GConf directory /apps/evolution-alarm-notify
Last modified: 2012-12-20 11:10:00 EST
Description of problem:
Can't report a problem with evolution-alarm-notify because it requires GConf directory /apps/evolution-alarm-notify:
--- Running collect_GConf ---
GConf directory /apps/evolution-alarm-notify does not exist
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. pkill -SEGV evolution-alarm-notify
2. Try to report a bug
See error message above
I expected it to be able to report a bug.
Should be fixed in git revision afe6b6dceeb7278fde8a6a004d97e4ef47d46d4a. Thanks for the report!
*** Bug 871798 has been marked as a duplicate of this bug. ***
Is the fix going to be released as an update? When? Will this also fix bug 807807 and bug 754756?
I'm not sure, but it seems like maybe somebody commenting in bug 754756 seems to think that every application is responsible for making collect_GConf work properly, and if that hasn't been done, it's OK for ABRT to simply fail. That's absurd. If ABRT can't collect GConf data, it should still submit the bug report without it.
*** Bug 807807 has been marked as a duplicate of this bug. ***
abrt-2.0.18-1.fc17,libreport-2.0.18-1.fc17,btparser-0.22-1.fc17 has been submitted as an update for Fedora 17.
Package abrt-2.0.18-1.fc17, libreport-2.0.18-1.fc17, btparser-0.22-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.18-1.fc17 libreport-2.0.18-1.fc17 btparser-0.22-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
abrt-2.0.18-1.fc17, libreport-2.0.18-1.fc17, btparser-0.22-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.