Azureus crashes on startup
Posted September 29th, 2007 in Applications
Azureus is a cross browser bittorrent client, and after upgrading openSUSE from 10.2 to 10.3 Azureus wouldn't start. I would get the splash screen flash up but then it would crash without actually running.
I opened up a console and ran Azureus from there, and got the following error message, attempting to run Azureus version 2.5:
Starting Azureus...
Suitable java version found [java = 1.5.0_10]
Configuring environment...
Java exec found in PATH. Verifying...
GRE/XULRunner automatically found
Loading Azureus:
java -Xmx128m -cp "./Azureus2.jar:./swt.jar" -Djava.library.path="/opt/azureus" -Dazureus.install.path="/opt/azureus" -Dazureus.script="/opt/azureus/azureus" -Dazureus.script.version=2 org.gudy.azureus2.ui.swt.Main
java: xcb_xlib.c:52: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
/opt/azureus/azureus: line 188: 15370 Aborted ${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.
Having had a number of other issues after upgrading openSUSE, I decided it would be best to reinstall Azureus, so I downloaded Azureus version 3 and installed that. Again, I got the same sort of error with the splash screen flashing up and then the application crashing, so again ran it from the command line to see what errors I would see. This time I got this:
Starting Azureus...
Suitable java version found [java = 1.5.0_10]
Configuring environment...
Java exec found in PATH. Verifying...
Browser check failed with: memmove
Auto-scanning for GRE/XULRunner. You can skip this by appending the GRE path to LD_LIBRARY_PATH and setting MOZILLA_FIVE_HOME.
checking /usr/lib64/xulrunner-1.8.1 for GRE
Can not use GRE from /usr/lib64/xulrunner-1.8.1 because it's missing components/libwidget_gtk2.so.
checking /usr/lib64/xulrunner-1.8.1.4 for GRE
Can not use GRE from /usr/lib64/xulrunner-1.8.1.4 because it's missing components/libwidget_gtk2.so.
checking /usr/lib/firefox for GRE
Can not use GRE from /usr/lib/firefox because it's missing components/libwidget_gtk2.so.
Browser check failed with: NoClassDefFoundError
Can't create browser. Will try to set LD_LIBRARY_PATH and hope Azureus has better luck.
GRE/XULRunner automatically found
Loading Azureus:
java -Xmx128m -cp "./Azureus2.jar:./swt.jar" -Djava.library.path="/home/chris/install/azureus" -Dazureus.install.path="/home/chris/install/azureus" -Dazureus.script="./azureus" -Dazureus.script.version=2 org.gudy.azureus2.ui.swt.Main
Exception in thread "main" java.lang.UnsatisfiedLinkError: memmove
at org.eclipse.swt.internal.C.memmove(Native Method)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:67)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
at org.eclipse.swt.widgets.Display.(Display.java:128)
at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.(SWTThread.java:89)
at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(SWTThread.java:68)
at org.gudy.azureus2.ui.swt.mainwindow.Initializer.(Initializer.java:101)
at org.gudy.azureus2.ui.swt.Main.(Main.java:80)
at org.gudy.azureus2.ui.swt.Main.main(Main.java:203)
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.
Hmm, those were even worse errors than the first time. I started up Yast and did a search on gtk2, because that had popped up in the error messages a fair bit. At the top of the application list was was Azureus, so installed the version from the SUSE installation source.
Once again, I got the splash screen, a quick flash up of the application, and then Azureus crashed. So the command line again, this time revealing:
java virtual machine used: /usr/lib64/jvm/jre/bin/java
classpath used: /usr/share/java/Azureus/Azureus3.jar:/usr/share/java/Azureus/swt.jar
main class used: org.gudy.azureus2.ui.swt.Main
flags used:
options used: -Xms16m -Xmx128m -Djava.library.path=/usr/lib64/Azureus:/usr/lib/Azureus
arguments used:
Well that wasn't very useful! I was beginning to wonder if maybe the openSUSE upgrade had caused some issues with the Azureus configuration, so I issued the following command:
mv ~/.azureus ~/.azureus~
Azureus's settings are stored in a directory under the home folder called .azureus, so what I did above was to rename it to .azureus~. When Azureus starts up, there are no existing configuration settings, so it will recreate the directory with default settings.
Having done the above, I started Azureus up again and this time it worked, so there was clearly something wrong the configuration files. I didn't bother trying to work out what the problem might have been and deleted the backed up old version of the settings directory.
Subscribe!
If you found this post interesting and would like to be notified the next time something is posted, please subscribe to my RSS Feed. Thanks for visiting!


