Bug#542392: azureus: Refuses to start
Adrian Perez wrote: You don't need to do the extra steps (although they don't hurt at all), you need to investigate is your JAVA_HOME is persistant, then who's setting it. Check your ~/.bash* files, /etc/bash.bashrc, the like, you know. Yes!! It was set in /etc/profile. I must have put it in there myself, but cannot remember why or when. After I commented it out, the new azureus worked perfectly. Perhaps a warning about this in README.Debian would be good idea: Make sure that you don't have JAVA_HOME or JAVA_CMD environment variables defined, otherwise the new version of Azureus may FAIL. Check by means of env | grep JAVA . Or something. Thanks very much, Jan ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#542392: azureus: Refuses to start
Package: azureus Version: 4.2.0.4-1 Severity: grave Justification: renders package unusable I have openjdk-6-jre installed, because azureus used to depend on it. openjdk works fine with other java applications as well, so no complaints here. But (see bug report #515015) some users found it annoying that other jre's, like Sun's, could not be used. Now the latest azureus version corrects this, I believe by means of the script java-wrappers.sh. I suppose sun jre users are now happy. But I am very UNhappy, because now azureus refuses to start at all. The error messages are: /usr/lib/java-wrappers/java-wrappers.sh: line 243: /usr/lib/java/bin/java: / No such file or directory /usr/lib/java-wrappers/java-wrappers.sh: line 243: exec: / /usr/lib/java/bin/java: cannot execute: No such file or directory Why can't azureus simply use the /etc/alternatives mechanism? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages azureus depends on: ii java-wrappers 0.1.15 wrappers for java executables ii libcommons-cli-java 1.2-2 API for working with the command l ii liblog4j1.2-java 1.2.15-7 Logging library for java ii libswt-gtk-3.4-java 3.4.2-2Standard Widget Toolkit for GTK+ J ii openjdk-6-jre 6b16-4 OpenJDK Java runtime, using Hotspo Versions of packages azureus recommends: ii vuze 4.2.0.4-1 Multimedia BitTorrent client azureus suggests no packages. -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#542392: azureus: Refuses to start
Adrian Perez wrote: tag + unreproducible moreinfo Well, I've tested it on openjdk, otherwise I wouldn't released it. I've attached the output from my machine, after update-java-alternatives --set java-6-openjdk and it's working fine. I think it's something wrong with your installation. As Onkar pointed please provide debug information. Can you please try this? Modify the azureus launcher script (/usr/bin/azureus), and add DEBUG_WRAPPER=1 just before run_java. i.e. DEBUG_WRAPPER=1 run_java -Dazureus.install.path=$HOME/.azureus $UI \ org.gudy.azureus2.ui.common.Main $@ Try launching azureus from command line then and paste the output in the bug. OK; the output doesn't look at all like yours: j...@vega:~$ azureus [1] 24821 j...@vega:~$ [debug] /usr/bin/azureus: Environment variable CLASSPATH is '' [debug] /usr/bin/azureus: Runnning /usr/lib/java/bin/java -classpath /usr/lib/jni:/usr/lib/java:/usr/share/java/Azureus2.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/commons-cli.jar:/usr/share/java/swt.jar -Dazureus.install.path=/home/jws/.azureus org.gudy.azureus2.ui.common.Main /usr/lib/java-wrappers/java-wrappers.sh: line 243: /usr/lib/java/bin/java: No such file or directory /usr/lib/java-wrappers/java-wrappers.sh: line 243: exec: /usr/lib/java/bin/java: cannot execute: No such file or directory [1]+ Exit 126azureus BTW ls -al in /etc/alternatives gives: java - /usr/lib/jvm/java-6-openjdk/jre/bin/java java.1.gz - /usr/lib/jvm/java-6-openjdk/jre/man/man1/java.1.gz javaws - /usr/lib/jvm/java-6-openjdk/jre/bin/javaws javaws.1.gz - /usr/lib/jvm/java-6-openjdk/jre/man/man1/javaws.1.gz libswt-3.4-java - /usr/share/java-config/libswt-gtk-3.4-java mozilla-javaplugin.so - /usr/lib/jvm/java-6-openjdk/jre/lib/i386/IcedTeaPlugin.so And I CAN start azureus from command line by JAVA_CMD=/etc/alternatives/java azureus or by exporting JAVA_CMD=/etc/alternatives/java before starting X. The output in such a case is: j...@vega:~$ JAVA_CMD=/etc/alternatives/java azureus [debug] /usr/bin/azureus: Environment variable CLASSPATH is '' [debug] /usr/bin/azureus: Runnning /etc/alternatives/java -classpath /usr/lib/jni:/usr/lib/java:/usr/share/java/Azureus2.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/commons-cli.jar:/usr/share/java/swt.jar -Dazureus.install.path=/home/jws/.azureus org.gudy.azureus2.ui.common.Main file:/usr/lib/jni/ ; file:/usr/lib/java/ ; file:/usr/share/java/Azureus2.jar ; file:/usr/share/java/log4j-1.2-1.2.15.jar ; file:/usr/share/java/commons-cli-1.2.jar ; file:/usr/lib/java/swt-gtk-3.4.2.jar ; file:/home/jws/ Core Start Completed Unfortunately, this works only from the command line. Clicking on a torrent link in a web page does not start azureus. Regards, Jan ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#542392: Extra info
Extra info: downgrading to 3.1.1.0-4 restored functionality at once. Regards, Jan ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#542392: azureus: Refuses to start
Adrian Perez wrote: I think we both agree the problem is related to your environment and not the packaging. That's very likely. It seems the java-wrapper script it's not finding your java runtime, which may be caused by a wrong environment configuration. Make sure you have no environment variables like JAVA_HOME or JAVA_CMD set, since the script may be able to find them properly, and set them locally for the script. Also, their use it's deprecated by the new java policy. JAVA_HOME is set, to /usr/lib/java. I do not know where this is set. JAVA_CMD is not normally set. As to your other suggestions, I'll answer tomorrow (I have to get up very early, so must hit the sack about now). BTW my previous message must have crossed yours. Where can I read more about the new java policy? Regards, Jan ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
