Vuze startup segmentation fault
Hello :)
This was also posted on the Vuze forum. This issue seen with Vuze 4.3.10 and gcc-java-4.3.3-i4 running on Slackware 13.0 32-bit. Installed Vuze 4.3.10 from Vuze_4.3.1.0_linux.tar.bz2 downloaded from Sourceforge and tested OK as non-root user using ~/.azureus configuration from previous 4.2.0.8. OK. Did not use for a week. Opened the Slackware 13.0 32-bit DVD torrent using Firefox 3.5.3. Saw Vuze message advising torrent had been added but Vuze exited. Started Vuze as same non-root user in a terminal using /opt/vuze/vuze &. Saw Code:
/opt/vuze/vuze: line 188: 8468 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 "$@" Code:
root:/var/log# ln -s /usr/lib/firefox-3.5.2/libxpcom.so /usr/lib/seamonkey/libxpcom.so Code:
# A fatal error has been detected by the Java Runtime Environment: Best Charles |
Same issues here.
I guess, you will have to use Vuze_4.2.0.X until a new version with no bugs appear. May be try 'jre-6u18' ? ? ..... |
FYI, vuze 4.3.1.2 works fine with jdk-6u18
Regards |
Thanks knudfl and bathory :)
Will try suggestions and post back but don't hold your breath -- some other tasks have greater priority. |
"Other tasks with greater priority" now need a functioning torrent :cool:
I've never had more than one jre installed on Linux (and never had a jdk). Is it possible? It doesn't look so Code:
root@CW8:~# type java Are there any issues, considerations, likely breakages etc I should be aware of? |
Quote:
Regards |
Thanks (that was quick!) for correcting my ignorance, bathory :)
Code:
c@CW8:~$ /usr/lib/java/bin/java -version |
Upgraded to Vuze 4.3.1.4 and JRE 6u18 but still have a SIGSEGV error. Tried removing ~/.azureus but same. Will now try an old version of Vuze.
In case it matters, in detail, using jre-6u18-i586-1.txz from ftp://ftp.slackware.com/pub/slackwar...t/slackware/l/ and Vuze_4.3.1.4_linux.tar.bz2 from http://sourceforge.net/projects/azureus/files/vuze/: Code:
slackpkg remove jre-6u16-i586-1 |
Hi,
Could you try to delete the files /tmp/libswt*.so, or the directory /tmp/swtlib-32 (whatever exists for your setup) and restart azureus. These are created every time azureus starts if they don't exist. |
Quote:
Azureus' /tmp files may explain why 4.1.0.4 showed the 4.3.1.4 ChangeLog and displays 4.3.1.4 in Help->About ... ? (the /opt/vuze/ChangLog.txt is correct and other files in that directory have credible modification times for 4.1.0.4). Will update here after Knoppix downloaded. |
Washii pointed out in the Vuze Forum thread that libxul is in Firefox territory.
@bathory: in preparation for testing as you suggested are there any of these that I should not delete before testing a different version of azureus? Code:
root@CW8:~# ls -l /tmp/* Code:
root@CW8:~# ps -ef | grep 4601 | grep -v grep |
Quote:
The hsperfdata_c directory is used by vuze to create a file with its PID. The file is deleted when you stop vuze. Quote:
|
Quote:
1 GB per day download; you are right to ask! The answer is not simple ... The "broadband" package gives us 512 kbps "wherever technically feasible" and we do get 64 kBps at best. But I share the connection with others so must throttle back the download speed when they are using it. That would give ~10 hours of full speed equivalent per day except we are having trouble with our new ADSL modem/router (Cisco-Linksys WAG54G2 -- not a good choice in retrospect). It dropped out of service while I was torrenting at 45 kBps and would not work again, even after a 40 minute cooling period. Was OK in the morning. :confused: That lost an entire night and since then I've been edging the download speed up from 32 kBps, not wanting to loose another night. After some debate (it's not my decision) it has been agreed to take the modem back under warranty. |
Quote:
The only difference is, that the first 2 (versions 4.3.1.4 and 4.2.0.4) put the temp files in /tmp/swtlib-32 directory, while the 3rd (version 3.0.42) puts them in /tmp. |
Quote:
Re-testing 4.3.1.4 with no Vuze files in /tmp and no ~/.azureus produced the same result. Following a suggestion in the Vuze forum thread, Vuze 4.3.1.4's swt.jar (version 3.631) was replaced with swt.jar version 3.550. Testing (again with no Vuze files in /tmp and no ~/.azureus) produced the same result except with less debug output. |
All times are GMT -5. The time now is 10:03 AM. |