Re: Re: Vuze (Azureus) broken after Apt-get upgrade

Boyd Stephen Smith Jr. wrote: > Probably related to > > there's a supposed work-around in Message-Id: > <200912151551.20419.tim.rueh...@gmx.de>, which should be in the > archives. I did not test the work-around because I do not use > any

Re: Vuze (Azureus) broken after Apt-get upgrade

Boyd Stephen Smith Jr. wrote: In <4b2a6476.1000...@mbo.net>, Russ Cook wrote: I am running a 64-bit system, unstable, with kernel 2.6.31-1. Every week or so, I run apt-get update, apt-get upgrade, to keep system reasonable up to date. I am running no firewalls on my system, which is on a home

Re: Vuze (Azureus) broken after Apt-get upgrade

In <4b2a6476.1000...@mbo.net>, Russ Cook wrote: >I am running a 64-bit system, unstable, with kernel 2.6.31-1. >Every week or so, I run apt-get update, apt-get upgrade, to keep system >reasonable >up to date. >I am running no firewalls on my system, which is on a home network behind a >dsl modem/ro

Vuze (Azureus) broken after Apt-get upgrade

I am running a 64-bit system, unstable, with kernel 2.6.31-1. Every week or so, I run apt-get update, apt-get upgrade, to keep system reasonable up to date. I am running no firewalls on my system, which is on a home network behind a dsl modem/router. This week, after running apt-get update, Vuze

NAT unreachability problem in VUZE(Azureus)

choose to configure a lower value. The key is that the opening of the azureus port is not countermanded by the firewall initialisation which runs later. At the end is a *) &* which allows the script to let the rest of the boot continue, while the script waits. chmod +x /etc/init.d/iptables

Re: I need some help (Issues with amule, azureus and vlc)

Tony wrote: > The error was 'BadAlloc (insufficient resources for operation)'. You might have run out of memory. Try adding more RAM to the system and see if it works David S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: azureus

On Sat, 12 Jan 2008 19:22:58 -0500 Rick Pasotto <[EMAIL PROTECTED]> wrote: [...] > $ java -version > java version "1.4.2-03" > Java(TM) 2 Runtime Environment, Standard Edition (build > Blackdown-1.4.2-03) Java HotSpot(TM) Client VM (build > Blackdown-1.4.2-03, mixed mode) > Please try to install

Re: azureus

On Sat, Jan 12, 2008 at 05:50:48PM -0600, Michael Shuler wrote: > On 01/12/2008 05:15 PM, Rick Pasotto wrote: >> On Sun, Jan 13, 2008 at 12:01:09AM +0100, Peter Greff wrote: >>> On Sat, 12 Jan 2008 17:37:02 -0500 >>> Rick Pasotto <[EMAIL PROTECTED]> wrote: >&

Re: azureus

On 01/12/2008 05:15 PM, Rick Pasotto wrote: On Sun, Jan 13, 2008 at 12:01:09AM +0100, Peter Greff wrote: On Sat, 12 Jan 2008 17:37:02 -0500 Rick Pasotto <[EMAIL PROTECTED]> wrote: When I launch azureus I get a full-screen window with a black background in the middle of which in white l

Re: azureus

On Sun, Jan 13, 2008 at 12:01:09AM +0100, Peter Greff wrote: > On Sat, 12 Jan 2008 17:37:02 -0500 > Rick Pasotto <[EMAIL PROTECTED]> wrote: > > > When I launch azureus I get a full-screen window with a black background > > in the middle of which in white letters

Re: azureus

On Sat, 12 Jan 2008 17:37:02 -0500 Rick Pasotto <[EMAIL PROTECTED]> wrote: > When I launch azureus I get a full-screen window with a black background > in the middle of which in white letters is: "Loading...Please Wait". > > Fifteen+ minutes and there has been no ch

azureus

When I launch azureus I get a full-screen window with a black background in the middle of which in white letters is: "Loading...Please Wait". Fifteen+ minutes and there has been no change. How long am I supposed to wait? What is it I'm supposed to be waiting for? -- "The

Re: azureus: upgrade

On Sat, 2006-07-08 at 12:19 -0300, Marcelo Chiapparini wrote: > Hello, > > I am running Azureus 2.2.0.2 in sarge. Each time Azureus starts, I > receive a warning regarding new updates availables. Is it safe to > upgrade Azureus accepting the suggested upgrade? > Update will wo

Re: azureus: upgrade

On Sat, 2006-07-08 at 11:54 -0400, Roberto C. Sanchez wrote: > Marcelo Chiapparini wrote: > > Hello, > > > > I am running Azureus 2.2.0.2 in sarge. Each time Azureus starts, I > > receive a warning regarding new updates availables. Is it safe to > > upgrade Azureu

Re: azureus: upgrade

Marcelo Chiapparini wrote: > Hello, > > I am running Azureus 2.2.0.2 in sarge. Each time Azureus starts, I > receive a warning regarding new updates availables. Is it safe to > upgrade Azureus accepting the suggested upgrade? > > Thanks in advance > > Marcelo > &

azureus: upgrade

Hello, I am running Azureus 2.2.0.2 in sarge. Each time Azureus starts, I receive a warning regarding new updates availables. Is it safe to upgrade Azureus accepting the suggested upgrade? Thanks in advance Marcelo -- Marcelo Chiapparini [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to

Azureus BT client window not refreshing properly

I've just installed Azureus from Testing but I have a strange problem where the statistics (i.e. graphs and text statistics) are not refreshing properly within the app during downloads and uploads. When the app has window focus then nothing updates. If I move the mouse out of the wind

RE: Azureus and the TCP port 6881

ter. Get a manual for the router online, if necessary. There is undoubtedly a configuration page for port forwarding. You want to forward the port that you select with the proper protocol (for Azureus that's both TCP and UDP) to the local IP of your machine. If the machine uses DHCP to get an

Re: Azureus and the TCP port 6881

0, Gene Heskett wrote: >> On Monday 30 January 2006 17:59, Marcelo Chiapparini wrote: >> >Dear debianners, >> > >> >I've just installed Azureus as my .torrent client. During its >> >configuration the wizard checks for the 6881 TCP port reporting the >

Re: Azureus and the TCP port 6881

>Dear debianners, > > > >I've just installed Azureus as my .torrent client. During its > >configuration the wizard checks for the 6881 TCP port reporting the > >following message: "Testing port 6881... NAT error". I would like to > >know how to

Re: Azureus and the TCP port 6881

I wrote: > They may simply block anything they can't analyze. Chris Howie writes: > That's a recipie for disaster for any ISP -- they would have to > anticipate every application that will be used by their clients and > authorize it on their analyzer. And if something like this did happen, > chan

Re: Azureus and the TCP port 6881

Scott wrote: > Calm down. Software malfunction. > > I just discovered the problem before I got back here and saw your reply. > It wasn't intentional. Sorry, I didn't mean to come across as angry or upset, I only meant to add emphasis for the case where it might be intentional (it's happened befo

Re: Azureus and the TCP port 6881

Edward Shornock wrote: On Mon, Jan 30, 2006 at 04:54:12PM -0700, Debian-user wrote: Chris Howie wrote: >1) Don't use port 6881. Pick something random in the 49152-65535 range. What's wrong with using port 6881? Some trackers will reject any connections from clients on the default port(s).

Re: Azureus and the TCP port 6881

On Mon, Jan 30, 2006 at 04:54:12PM -0700, Debian-user wrote: > Chris Howie wrote: > > >1) Don't use port 6881. Pick something random in the 49152-65535 range. > > What's wrong with using port 6881? Some trackers will reject any connections from clients on the default port(s). signature.asc D

Re: Azureus and the TCP port 6881

Chris Howie wrote: Debian-user wrote: 1) Don't use port 6881. Pick something random in the 49152-65535 range. What's wrong with using port 6881? Please *DO NOT* set your 'From' address to the list address. It's confusing as I have no way to tell who sent the message. Adjust your mail clie

Re: Azureus and the TCP port 6881

John Hasler wrote: > Chris Howie writes: >>Watch ISPs try to filter that. The TLS/SSL wrapper keeps them from >>filtering by analyzing the protocol. > > They may simply block anything they can't analyze. That's a recipie for disaster for any ISP -- they would have to anticipate every application

Re: Azureus and the TCP port 6881

Chris Howie writes: > Watch ISPs try to filter that. The TLS/SSL wrapper keeps them from > filtering by analyzing the protocol. They may simply block anything they can't analyze. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [E

Re: Azureus and the TCP port 6881

On Monday 30 January 2006 17:59, Marcelo Chiapparini wrote: >Dear debianners, > >I've just installed Azureus as my .torrent client. During its >configuration the wizard checks for the 6881 TCP port reporting the >following message: "Testing port 6881... NAT error"

Re: Azureus and the TCP port 6881

Andrew Sackville-West wrote: >>1) Don't use port 6881. Pick something random in the 49152-65535 range. > > Are you suggesting this for a reason? or just for diagnostic purposes. I > don't do much with torrent, but once in a whileI do and it never seems to > quite work very well. and yes I port

Re: Azureus and the TCP port 6881

On Mon, 30 Jan 2006 18:28:27 -0500 Chris Howie <[EMAIL PROTECTED]> wrote: > Marcelo Chiapparini wrote: > > I've just installed Azureus as my .torrent client. During its > > configuration the wizard checks for the 6881 TCP port reporting the > > following message: &

Re: Azureus and the TCP port 6881

Debian-user wrote: >> 1) Don't use port 6881. Pick something random in the 49152-65535 range. > > What's wrong with using port 6881? Please *DO NOT* set your 'From' address to the list address. It's confusing as I have no way to tell who sent the message. Adjust your mail client settings befor

Re: Azureus and the TCP port 6881

Chris Howie wrote: 1) Don't use port 6881. Pick something random in the 49152-65535 range. What's wrong with using port 6881? Curiously, -- Scott www.angrykeyboarder.com © 2006 angrykeyboarder™ & Elmer Fudd. All Wights Wesewved

Re: Azureus and the TCP port 6881

Marcelo Chiapparini wrote: > I've just installed Azureus as my .torrent client. During its > configuration the wizard checks for the 6881 TCP port reporting the > following message: "Testing port 6881... NAT error". I would like to > know how to open this port. I'

Azureus and the TCP port 6881

Dear debianners, I've just installed Azureus as my .torrent client. During its configuration the wizard checks for the 6881 TCP port reporting the following message: "Testing port 6881... NAT error". I would like to know how to open this port. I've surfed the list, goo