Azureus: Segmentation fault suddenly, caused by java?!

Olaus · 11-10-2009, 05:29 AM

When I try to run Azureus, it starts up and the aborts with this output:

Code:

Downloads/vuze/vuze: line 188:  3326 Segmenteringsfel        ${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:

java -version
java version "1.6.0_16"

Any ideas? It has worked before.
Line 188 in the vuze script reads

Code:

$START_CLASS "$@"

MS3FGX · 11-15-2009, 07:05 PM

I have had this same problem with Azureus and recent versions of JRE under Slackware. Unfortunately I have not been able to find a fix, and I'm hoping that an update to either Azureus or the JRE package addresses this sometime in the future.

Olaus · 11-16-2009, 12:55 PM

Quote:

Originally Posted by MS3FGX

I have had this same problem with Azureus and recent versions of JRE under Slackware. Unfortunately I have not been able to find a fix, and I'm hoping that an update to either Azureus or the JRE package addresses this sometime in the future.

I "solved" it by downgrading seamonkey/seamonkey-solibs to v 1.18 to get azureus v 4.2 to work, but azureus v 4.3 seems to work with seamonkey/seamonkey-solibs v 2.0. The problem was on azureus's side.

Demonos · 11-22-2009, 09:23 AM

I think I managed to resolve issue for me :-)
I had the same headache. Since version 2.4.1 of Vuze (I guess) and couldn't find solution. I started using kTorrent - nice, uTorrent resembling client, but... :-)

Today, I found this topic. I tried with upgrading seamonkey-solibs. But it didn't work.
Then I looked closer what's happenining on starting vuze from console.
And I found that Vuze is looking for libxpcom.so in seamonkey-solibs path and it isn't there.
So I symlinked libxpcom.so from firefox libs to seamonkey-solibs path.

sudo ln -s /usr/lib/firefox-3.5.2/libxpcom.so /usr/lib/seamonkey/libxpcom.so

And Vuze is working again.

I hope it will help.