Created attachment 520224 [details]
screenshot of smolt gui
Description of problem:
I´ve installed smolt gui in fedora 16 alpha, and run smolt from there.
It get frozen at 99% progrss and get not finished(more than 1h runtime-> nearly no CPU use).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install the smolt gui and run it-> smolt get frozen
In openSUSE 12.1 MS there is the same problem-> so it is more to smolt itself and not a system wide problem -> see also:
I´s fixed with the latest updates for fedora 16.
I can´t find the closed-> fixed option for closing this ticket.
What is usual on fedora bugtracker? -> Can you do?
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.
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 16'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 16 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 to click on
"Clone This Bug" and open it against that version of Fedora.
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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.