FS#24486 - [vuze] Crashing when starting vuze 4.6.0.2-2
Attached to Project:
Community Packages
Opened by Semyon (s3my0n) - Saturday, 28 May 2011, 09:46 GMT
Last edited by Thomas Dziedzic (tomd123) - Sunday, 31 July 2011, 05:07 GMT
Opened by Semyon (s3my0n) - Saturday, 28 May 2011, 09:46 GMT
Last edited by Thomas Dziedzic (tomd123) - Sunday, 31 July 2011, 05:07 GMT
|
Details
Description:
When I start vuze it startsup normally for about 3 seconds and then closes. Additional info: * vuze 4.6.0.2-2 * java version "1.6.0_25" Java(TM) SE Runtime Environment (build 1.6.0_25-b06) Java HotSpot(TM) Server VM (build 20.0-b11, mixed mode) Steps to reproduce: [s3my0n@arch ~]$ sudo pacman -Ss vuze community/vuze 4.6.0.2-2 [installed] BitTorrent client with GUI, written in Java. [s3my0n@arch ~]$ vuze Starting Azureus... Suitable java version found [java = 1.6.0_25] Configuring environment... Java exec found in PATH. Verifying... Browser check failed with: InvocationTargetException, No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)] 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-2.0 for GRE Can not use GRE from /usr/lib/xulrunner-devel-2.0 because it's missing libxpcom.so. checking /usr/lib/xulrunner-2.0 for GRE GRE found at /usr/lib/xulrunner-2.0. Browser check failed with: InvocationTargetException, XPCOM error -2147467261 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-2.0 setting MOZILLA_FIVE_HOME to: /usr/lib/xulrunner-2.0 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)' UIFunctions/ImageLoad took 25ms new shell took 100ms new shell setup took 50ms skin init took 76ms MainMenu init took 75ms pre skin widgets init took 25ms WARNING: already added UIUpdatable com.aelitis.azureus.ui.swt.views.skin.sidebar.SideBar@1d33a6b skin widgets (1/2) init took 101ms skin widgets (2/2) init took 75ms pre SWTInstance init took 0ms Init Core Columns took 75ms SWTInstance init took 0ms shell.layout took 25ms ---------SHOWN AT 1306574956116;1463ms # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xa39b7b42, pid=10236, tid=2798529392 # # JRE version: 6.0_25-b06 # Java VM: Java HotSpot(TM) Server VM (20.0-b11 mixed mode linux-x86 ) # Problematic frame: # C [libxul.so+0xc6cb42] NS_UTF16ToCString_P+0x195cb # # An error report file with more information is saved as: # /tmp/hs_err_pid10236.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # /usr/bin/vuze: line 188: 10236 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. |
This task depends upon
Closed by Thomas Dziedzic (tomd123)
Sunday, 31 July 2011, 05:07 GMT
Reason for closing: Won't fix
Additional comments about closing: moved vuze to the aur
Sunday, 31 July 2011, 05:07 GMT
Reason for closing: Won't fix
Additional comments about closing: moved vuze to the aur
Also, this is most likely an upstream issue, but I will take a look at it anyway.
https://bbs.archlinux.org/viewtopic.php?pid=936477
https://bbs.archlinux.org/viewtopic.php?id=115543
also note a similar eclipse bug was reported:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344665
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344270
So I think the next step for you to do is to report this upstream (vuze) and get it fixed.
So can I have both xulrunner 2.0 and 1.9.2 on arch? If so how do I go about doing that?