So what will I do now? Any way I can downgrade? I have lots of torrents on Vuze. On 1/15/11, Thomas Dziedzic <gostrc@xxxxxxxxx> wrote: > On Sat, Jan 15, 2011 at 10:02 AM, Thomas Dziedzic <gostrc@xxxxxxxxx> wrote: >> On Sat, Jan 15, 2011 at 9:47 AM, Madhurya Kakati <mkakati2805@xxxxxxxxx> >> wrote: >>> HI, >>> I just updated Vuze bittorrent client to its latest version and now it >>> doesn't run. I am using 64 bit arch and openjdk6. The output when I >>> run vuze on the terminal is: >>> >>> $ vuze >>> Starting Azureus... >>> Suitable java version found [java = 1.6.0_20] >>> Configuring environment... >>> Java exec found in PATH. Verifying... >>> Browser check failed with: Cannot load 32-bit SWT libraries on 64-bit JVM >>> 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/lib/xulrunner-devel-1.9.2 for GRE >>> Can not use GRE from /usr/lib/xulrunner-devel-1.9.2 because >>> it's missing libxpcom.so. >>> checking /usr/lib/xulrunner-1.9.2 for GRE >>> GRE found at /usr/lib/xulrunner-1.9.2. >>> Browser check failed with: Could not initialize class >>> org.eclipse.swt.widgets.Display >>> Can't create browser. Will try to set LD_LIBRARY_PATH and hope Vuze >>> has better luck. >>> setting LD_LIBRARY_PATH to: /usr/lib/xulrunner-1.9.2 >>> setting MOZILLA_FIVE_HOME to: /usr/lib/xulrunner-1.9.2 >>> Loading Azureus: >>> java -Xmx128m -cp "./Azureus2.jar:./swt.jar" >>> -Djava.library.path="/usr/share/vuze" >>> -Dazureus.install.path="/usr/share/vuze" >>> -Dazureus.script="/usr/bin/vuze" -Dazureus.script.version=2 >>> org.gudy.azureus2.ui.swt.Main >>> file:/usr/share/vuze/Azureus2.jar ; file:/usr/share/vuze/swt.jar ; >>> file:/usr/share/vuze/ >>> changeLocale: *Default Language* != English (United States). Searching >>> without country.. >>> changeLocale: Searching for language English in *any* country.. >>> changeLocale: no message properties for Locale 'English (United >>> States)' (en_US), using 'English (default)' >>> java.lang.reflect.InvocationTargetException >>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native >>> Method) >>> at >>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) >>> at >>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) >>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532) >>> at org.gudy.azureus2.ui.swt.Main.<init>(Main.java:114) >>> at org.gudy.azureus2.ui.swt.Main.main(Main.java:292) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:616) >>> at >>> com.aelitis.azureus.launcher.MainExecutor$1.run(MainExecutor.java:37) >>> at java.lang.Thread.run(Thread.java:636) >>> Caused by: java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT >>> libraries on 64-bit JVM >>> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:197) >>> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:174) >>> at org.eclipse.swt.internal.C.<clinit>(C.java:21) >>> at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63) >>> at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54) >>> at org.eclipse.swt.widgets.Display.<clinit>(Display.java:132) >>> at >>> org.gudy.azureus2.ui.swt.mainwindow.SWTThread.<init>(SWTThread.java:84) >>> at >>> org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(SWTThread.java:63) >>> at >>> com.aelitis.azureus.ui.swt.Initializer.<init>(Initializer.java:163) >>> ... 12 more >>> Exit from Azureus complete >>> No shutdown tasks to do >>> Azureus TERMINATED. >>> >> >> This is a known issue: >> https://bugs.archlinux.org/task/22432 >> FS#22432 - [vuze] 4.6 fails to start on x86_64 >> >> What's interesting is that I can't find a 64bit version of vuze >> anymore like there was with the older version. and what's more >> interesting is that I downloaded the file on a 64bit computer and >> still got the 32bit version. Is this an upstream problem? >> > > BTW, I would like to continue this discussion on the bug webpage, not > on the ml please. & thanks. > -- Sent from my mobile device
