Bug 536933 - Azureus 4.0.0.4-6 freezing when loading torrents
Summary: Azureus 4.0.0.4-6 freezing when loading torrents
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: azureus
Version: 11
Hardware: i386
OS: Linux
low
urgent
Target Milestone: ---
Assignee: David Juran
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-11 20:10 UTC by Ondrej Hujnak
Modified: 2010-06-28 15:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 15:27:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
this one is working OK (7.11 KB, application/x-bittorrent)
2009-11-25 22:33 UTC, Ondrej Hujnak
no flags Details
and this one not at all (7.13 KB, application/x-bittorrent)
2009-11-25 22:34 UTC, Ondrej Hujnak
no flags Details

Description Ondrej Hujnak 2009-11-11 20:10:48 UTC
Description of problem:

If I try to open any .torrent files by azureus, it does nothing for sec and then it goes "Not responding" and never starts working again. It does only when expecting to start download (when i tried it offline, everything seemed ok).

Version-Release number of selected component (if applicable):

azureus 4.0.0.4 6.fc11

How reproducible:

Always

Steps to Reproduce:
1. Download the .torrent file
2. open it with azureus

Additional info:

I had the same problem under Windows (Vista 32b) and after updating azureus it was solved.

Comment 1 Ondrej Hujnak 2009-11-25 18:06:02 UTC
OK, even in Fedora 12 with azureus 4.2.0.8-2.fc12 it happens. I have discovered that it has problems only with some torrents and other are OK. But it doesn't seem to be problem in torrent, because others can download it normally. It happens mostly with totally new torrents.

Comment 2 Ondrej Hujnak 2009-11-25 22:30:40 UTC
I tried to look into logs and this looks suspicious to me:

Debug_2.log
[20:32:12] [nwman] ConnectDisconnectManager::address exception: full=/0.66.15.121:59302, hostname=0.66.15.121, port=59302, unresolved=false, full_sub=0.66.15.121/0.66.15.121, host_address=0.66.15.121
 channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_address=/0:0:0:0:0:0:0:0, local_port=38572, remote_address=<null>, remote_port=0

Comment 3 Ondrej Hujnak 2009-11-25 22:33:18 UTC
Created attachment 373843 [details]
this one is working OK

Comment 4 Ondrej Hujnak 2009-11-25 22:34:08 UTC
Created attachment 373844 [details]
and this one not at all

Comment 5 David Juran 2009-12-15 15:35:25 UTC
Actually the torrent from comment #4 works for me even with azureus-4.0.0.4-6.fc11. But as you say updating azurues helped on windows, could you please try with azureus-4.3.0.4 from F12-testing? You'll find it at https://admin.fedoraproject.org/updates/F12/FEDORA-2009-13110

Comment 6 Ondrej Hujnak 2009-12-18 12:44:37 UTC
That new version works just fine for me. Thanks a lot.

Comment 7 Fedora Update System 2009-12-24 20:37:24 UTC
azureus-4.3.0.4-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update azureus'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-13110

Comment 8 Bug Zapper 2010-04-28 11:17:29 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2010-06-28 15:27:01 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.


Note You need to log in before you can comment on or make changes to this bug.