Hi! I see two regressions in gwibber-3.1.0-4.fc16 compared to .3 version: - gwibber-service is launched four times, each of these instances forks 4 child processes, which makes 20 gwibber-service processes running. Previous version only used 5 processes. - the F-5 (refresh) function seems to be always disabled in the GUI.
*sigh* Gwibber 3.1 is effectively a dead branch. The newer code doesn't look at all like it, but because of deps, the newer code can only go into f17+ (gwibber-3.3.2-1.fc17). So, fixing these sorts of issues is a very low priority for me, but I will try to look at it. If you can come up with patches, I will happily review and apply them.
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.