Red Hat Bugzilla – Bug 835620
Local debugging initialization can't be stopped
Last modified: 2014-01-21 18:22:51 EST
Created attachment 594523 [details]
Description of problem:
See screenshot. I have an extremely slow network so I decided to stop the process. But the stop button ("Zastavit") didn't work. I pressed it several times, nothing happened. The progress bar was still moving and it seemed like it's still examining the repositories. I had to close the whole window, then it probably finally stopped.
I would expect Abrt to stop the process and move me back to previous form.
Version-Release number of selected component (if applicable):
Can you please check if it really stopped when you closed the window? I'm bit suspicious it didn't... yum is extremelly persistent when you try to kill it.. (it's something with urlgrabber if I remember it..)
There is no yum process when the debuginfo packages are being downloaded, so I don't know how to check it has stopped when the window is closed.
But even if I hit Stop during the debuginfo download and installation, it doesn't stop. So the button is completely non-functional.
OK, so, the Stop button works only when generating backtrace (this action itself takes about 5 seconds). The button doesn't work when you want to stop repository initialization or debuginfo package download.
I think this one happnes because of this:
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Seems fixed in F19.