Hide Forgot
Description of problem: I think since F16 Azureus is a pain in the neck to run. Not only does it have a very long startup time, but it also closes itself if you don't press the "don't restart now" button quickly enough. Because if you don't it tries to restart but never comes up again. I tried to mv ~/.azureus/app/plugins/azupdater/ ~/.azureus/updates/ ~/.azureus/update.properties /tmp/ to no avail Version-Release number of selected component (if applicable): How reproducible: It's very reproducible. Steps to Reproduce: 1. start azureus 2. wait for 5 minutes or so for it load everything up 3. see a popup with two buttons asking whether it should restart now (or automatically in a minute or so) or later. Actual results: Expected results: I expected to be able to just run and leave it w/o having to babysit it to keep it running. Additional info:
First, my apologies for ignoring this bug so long. Second, this bug is really a side-effect (or regression) from fixing bug 540638. The core of the problem is that Vuze insists of auto-upgrading itself, which is not consistent fedora packaging, so this auto-upgrade functionality need to be disabled. I've already tried commenting out the entire upgrade manager but it turned out that this made it impossible to install plugins. So what needs to be done is to modify azureus in such a way that it a) Does not try to upgrade the parts that are provided by fedora b) Still allows users to install plugins c) Still updates those user-installed plugins Since this is non-trivial, I'm moving this bug to rawhide. And patches are welcome (-:
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
*** Bug 912280 has been marked as a duplicate of this bug. ***
This bug applies also to F20 and Rawhide, not just F19.
I have done mv ~/.azureus/app/plugins/azupdater/ ~/.azureus/updates/ ~/.azureus/update.properties /tmp/ and with rpm -q azureus azureus-5.2.0.0-1.fc20.noarch I can't see this bug , now I "just" see one message that complains that can't update SWT because is loaded from /usr/lib64/SWT , which btw I don't understand what exactly azureus want
The message I meant is this : [alert] Alert:3:SWT library loaded from "/usr/lib64/eclipse" can't be automatically updated from version 4333 to 4403 (must be loaded from "/home/sergio/.azureus/app")
http://wiki.vuze.com/w/SWT_Cant_Auto_Update it says : Some packaged distributions however use a shared SWT installation that can't be automatically updated. In this case you will need to obtain a newer packaged distribution from your supplier
(In reply to Tobias Mueller from comment #0) > Description of problem: > Not only does it > have a very long startup time, but it also closes itself if you don't press > the "don't restart now" button quickly enough. Because if you don't it tries > to restart but never comes up again. > > I tried to > mv ~/.azureus/app/plugins/azupdater/ ~/.azureus/updates/ > ~/.azureus/update.properties /tmp/ > to no avail I can't reproduce this .... and never saw a behavior like this. but about duplicated bug #912280 , yes every time that azureus have one update version , if we should upgrade , azureus will not upgrade , ask for restart and next time I got message again , the problem is fixed when we got a azureus package update. in options -> interface -> start , we can disable check for last version version when azureus start. I haven't found yet, how change default options ..
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.