[feisty]azureus wont open after update of java

[Fernando Miguel]

the title is self explainable.
after todays update by synaptic I cant open azureus.
I notice that updates included some java lib packages.

[Tim Fuchs (tim-fuchs)]

Could you post the output when starting Azureus in a terminal?

To do this open a terminal, enter 'azureus' (without the ') and press Enter.

[Fernando Miguel (fernandomiguel)]

$ azureus
DEBUG::Tue Feb 06 17:17:40 GMT 2007::org.gudy.azureus2.core3.security.impl.SESecurityManagerImpl::initialise::140:
  No SSL provider available
    SESecurityManager::initialise::52,ConfigurationChecker::setSystemProperties::145,ConfigurationManager::initialise::138,ConfigurationManager::getInstance::71,LoggerImpl::init::90,Logger::<clinit>::48,Class::initializeClass::-1,StartServer::<init>::70,Main::<init>::56,Main::main::162
changeLocale: *Default Language* != en (US). Searching without country..
changeLocale: Searching for language en in *any* country..
changeLocale: no message properties for Locale 'en (US)' (en_US), using 'English (default)'
DEBUG::Tue Feb 06 17:17:41 GMT 2007::org.gudy.azureus2.core3.security.impl.SESecurityManagerImpl::initialise::140:
  No SSL provider available
    SESecurityManager::initialise::52,CryptoManagerImpl::<init>::73,CryptoManagerImpl::getSingleton::60,CryptoManagerFactory::getSingleton::33,AzureusCoreImpl::<init>::155,AzureusCoreImpl::create::92,AzureusCoreFactory::create::46,Main::<init>::143,Main::main::162
DEBUG::Tue Feb 06 17:17:50 GMT 2007::com.aelitis.azureus.core.networkmanager.impl.tcp.VirtualChannelSelectorImpl::select::528:
  VirtualChannelSelector: No progress for op 1: listener = class com.aelitis.azureus.core.clientmessageservice.impl.NonBlockingReadWriteService$2, count = 10, socket: open = true, connected = true
    VirtualChannelSelector::select::272,NonBlockingReadWriteService$1::runSupport::79,AEThread::run::69
Aborted

[Áron Sisak (asisak)]

Thanks for reporting this issue. I tried to run Azureus (Feisty, x86) with all GIJ, GCJ and Sun Java, and no problems for me. I suspect this might be a fault in your Java Runtime Environment.

Please run 'update-alternatives --display java' (without '-s) in a terminal window and paste its result.

[Fernando Miguel (fernandomiguel)]

$ update-alternatives --display java
java - status is auto.
 link currently points to /usr/lib/jvm/java-gcj/jre/bin/java
/usr/bin/gij-wrapper-4.1 - priority 41
 slave java.1.gz: /usr/share/man/man1/gij-wrapper-4.1.1.gz
/usr/lib/jvm/java-1.5.0-sun/jre/bin/java - priority 53
 slave java.1.gz: /usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/man/man1/java.1.gz
/usr/lib/jvm/java-gcj/jre/bin/java - priority 1041
 slave java.1.gz: /usr/lib/jvm/java-gcj/man/man1/java.1.gz
Current `best' version is /usr/lib/jvm/java-gcj/jre/bin/java.

[Áron Sisak (asisak)]

Any changes since? Please try to run with other JVMs, please, if gcj is still not working.

[Fernando Miguel (fernandomiguel)]

I've track down the prob:
the version available on the repositories is 2.5.0.0, and the last on the website is 2.5.0.4.
The java version available on the repositories is the latest, and unsupported by 2.5.0.0.
I downloaded the last version from the site, and it works just fine.
I'll have to wait for the repositories to update to place this as fixed.

[Áron Sisak (asisak)]

The last version available upstream supports JVM in the repositories.
Thanks BUGabundo for tracking that down.

[Ilmari Vacklin (wolverian)]

Is this really fixed? It still crashes here, and the version number is certainly not 2.5.0.4.

[DrMnis (mnis)]

Still a problem here, occurred about one week ago. When using java-gcj, configured like this:

$ sudo update-alternatives --config java

There are 3 alternatives which provide `java'.
  Selection Alternative
-----------------------------------------------
          1 /usr/lib/jvm/java-6-sun/jre/bin/java
          2 /usr/bin/gij-wrapper-4.1
*+ 3 /usr/lib/jvm/java-gcj/jre/bin/java

Press enter to keep the default[*], or type selection number:

azureus starts up, but torrents are extremely slow. The same with gij!

My default configuration though is to use java-6-sun, but an update destroyed this last week. When I start Azureus using java-6-sun, this is displayed:
$ azureus
java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
Aborted (core dumped)

[Fernando Miguel (fernandomiguel)]

Just a few days from Final Release of Feisty and still no one uploaded to the repositories azureus version 2.5.0.4 to fix this problem??
is that so difficult?

[DaanS (daanschulpen)]

Confirming that the current (post-feisty-release) repository version does not work with the current sun-java-6 repository package.

Workaround:
 - Download Azureus2.5.0.4.jar from http://azureus.sourceforge.net/download.php
 - Copy the downloaded .jar to /usr/share/java/Azureus2.jar

[Thangalin (thangalin-deactivatedaccount)]

Remove GIJ and install Sun's JVM.

It seems GIJ, which is the Java Virtual Machine installed by Feisty, cannot handle the connection load required for Azureus to perform properly.

1. sudo apt-get remove gij
2. rm /usr/bin/java
3. Download Sun's JVM (http://java.sun.com); try "Java Runtime Environment (JRE) 6u1"
4. Install Sun's JVM into /opt/jdk1.6.0
5. Set your PATH to include /opt/jdk1.6.0/bin
6. Close your shell window.
7. Open a new shell window.
8. Run Azureus.
9. Help -> About
10. You should see "Java 1.6.0" in the "System" pane.

[Fernando Miguel (fernandomiguel)]

I already have Sun Java JRE 1.6 from the Ubuntu repositorie and still
have this problem.

On 4/25/07, Thangalin wrote:
>
> Remove GIJ and install Sun's JVM.
>
> It seems GIJ, which is the Java Virtual Machine installed by Feisty,
> cannot handle the connection load required for Azureus to perform
> properly.
>
> 1. sudo apt-get remove gij
> 2. rm /usr/bin/java
> 3. Download Sun's JVM (http://java.sun.com); try "Java Runtime Environment (JRE) 6u1"
> 4. Install Sun's JVM into /opt/jdk1.6.0
> 5. Set your PATH to include /opt/jdk1.6.0/bin
> 6. Close your shell window.
> 7. Open a new shell window.
> 8. Run Azureus.
> 9. Help -> About
> 10. You should see "Java 1.6.0" in the "System" pane.
>
> --
> [feisty]azureus wont open after update of java
> https://bugs.launchpad.net/bugs/83594
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
BUGabundo :o)
))))(``-_-
GPG key 1024D/00967685
Linux user #443786

http://BUGabundo.net
http://BrinKadeiraS.BUGabundo.net

http://host.BUGabundo.net -- http://alojamento.BUGabundo.net
From / month1

Crazy Domain Insane (200GB disk, 2TB bw, 6. ($7.95)/month)00

at http://www.dreamhost.com/r.cgi?249195/signup
50$ discount with promo code "BUG50" on all plans
Free lifetime domain with promo code "BUGDOMAIN"

[Cameron Braid (cameron-braid)]

same thing happens to me after installing a fresh feisty and azureus.

The above workaround worked for me :

Workaround:
 - Download Azureus2.5.0.4.jar from http://azureus.sourceforge.net/download.php
 - Copy the downloaded .jar to /usr/share/java/Azureus2.jar

[Pascal Vandeputte (pascal-vdp)]

I think Thangalin hits the nail on the head. Apart from sometimes not being able to start Azureus, and needing to restart it often because of stalls, running it from the CLI and viewing the debug output was rather worrying as well (many exceptions being thrown). This fixed it perfectly for me (solid transfers, zero exceptions):

Install Sun JRE (I have excellent results with 1.5):
$ sudo apt-get install sun-java5-jre

Start Azureus with the Sun java binaries as follows:
$ JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun-1.5.0.11 azureus

(if you have a look at the /usr/bin/azureus script you see that $JAVA_HOME/bin/java will be used if $JAVA_HOME is set)

I also used the Azureus2.jar file from the 2.5.0.4 download, but I feel this didn't matter much.

[Sam Brightman (sambrightman)]

I find it likely that this bug is a duplicate of bug 68020 or one of the other Azureus startup bugs. Without a full Hotspot crash report it is hard to tell. A lot of those bugs are worked around by using upstream's jar file - this is not a fix in Ubuntu as it is not clear whether other users would still experience this on a default install. However, if it is a duplicate, they are being worked on/are fixed anyway, so it hardly matters. An attachment of the hs_err_pidXXXX.log file from your ~/.azureus directory would help clear things up.

[Jonas Björk (jonasbjork)]

Camerons workaround (https://bugs.launchpad.net/ubuntu/+source/azureus/+bug/83594/comments/14 ) works for me too, Ubuntu 7.04.

[Matti Lindell (mlind)]

Closing the upstream task, this is Ubuntu specific issue.

[Saivann Carignan (oxmosys)]

Thanks for this bug report and for your contribution to ubuntu.

This bug is a duplicate of bug 57875 so I mark it as such. You can install the latest azureus version 2.5.0.4-1ubuntu3~gutsy1 which fix that problem in Linux Ubuntu Gutsy with backports repositories enabled.

If you still experience problems with this new version of azureus, please mark this bug as not a duplicate anymore.