Created attachment 411334 [details]
Description of problem:abrt is not functioning as it should. This is the first crash generated report since upgrading to abrt.x86_64 1.0.9-1.fc12
Version-Release number of selected component (if applicable):abrt.x86_64 1.0.9-1.fc12
How reproducible:try to report bug
Steps to Reproduce:
1.select report bug
Actual results:program hangs
Expected results:should login, check for duplicates ... and log out.
Additional info:from report selector:
Logging into bugzilla...
Checking for duplicates...
Bug is already reported: 586055
Add email@example.com to CC list
Add new comment into bug(586055)
This is the first bug report since abrt was updated. When it updated it trashed the existing config file. I modified abrt.conf as best I could, however, it still will not cooperate. I received the following message:
Unable to finish current task!
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. attached is the abrt.conf file
I had to use 'control C' to close abrt
please attach modified abrt.conf
run under root:
$ service abrtd stop
$ abrtd -dvvv
and than try to report bug
After that attach output from abrtd -dvvv
Created attachment 411628 [details]
- abrt -dvvv
attached requested info. abrt updated yesterday afternoon. This may have solved the problem! Items updated are:
attachment is not full or you don't try report bug.
The config file is already attached. The abrt -dvvv attachment is all the info that was given. Still unable to complete bug report, as reported above.
I am a graphic designer/photographer, not a developer so if something is not what you expected, I have not been given complete steps to accomplish what you requested.
It was abrt that wanted the bug reported! If you want, I can disable abrt and not waste my time with bugs. That would apply to all the other bugs I have open. I am just trying to be helpful!
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
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 prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.
Thank you for reporting this bug and we are sorry it could not be fixed.