I know that this may not help anyone, as there are probably very few PCLOS users using Vuze or Azureus, but I want to post this fix I found for Vuze crashing on startup. I am running KDE SC version 4.6.2 on OS version Linux 2.6.33.7-pclos6.bfs. All up to date through Synaptic on a 1TB drive I installed the latest iso on about a month ago.
When I installed Vuze 4.5.1.0 about a week ago, there were no error reports and all appeared ok. When I went to start it however, it would show the application icon in the panel then just disappear. No error message, nothing.
So from Synaptic, I tried reinstalling, removing then installing and removing everything then installing. None of it seemed to work. Then I started hitting the PCLOS forums looking for answers.
The first situation I found had a similar error log to mine and it talked about reinstalling JRE.
http://www.pclinuxos.com/forum/index.php/topic,64790.0.htmlAfter a fruitless search in Synaptic, I found that JRE stuff is under java. So I removed Vuze, installed java stuff and reinstalled Vuze, but it still disappeared upon startup.
The next situation I found mentioned Vuze having a problem after updating.
http://www.pclinuxos.com/forum/index.php/topic,66287.0.htmlSo I tried replacing swt.jar and Azureus2.jar in root/usr/lib/vuze with ones from their website.
http://azureus.sourceforge.net/howto_linux.phphttp://dev.vuze.com/This also didn't fix the problem.
I tried installing and trying other torrent programs to see if they had the same problem. One at a time, I installed and removed Transmission-QT, Transmission and Deluge from Synaptic and they all worked fine, but they were slow. I tried reinstalling Vuze again, but still had the same problem.
Finally I found a thread on a Vuze forum that seemed to make sense.
http://forum.vuze.com/thread.jspa?threadID=96996&tstart=0&messageID=239347It was a much more recent forum, and the error log file listed was a close match for mine. It mentioned a fatal error in the Java Runtime Environment (JRE) involving some libxul.so file, whatever that is. They discovered that this particular Vuze crash was caused by something in the new mozilla-xulrunner20 package and suggested going back to mozilla-xulrunner192.
I checked Synapic for a Package --> Force Version option in xulrunner, but there wasn't one there. That meant that trying this suggestion would involve using CLI instead of synaptic on its own. I am always cautious of going around Synaptic, as it is such an integral part of preventing noobs like me from breaking my PCLOS installation.
The solution boils down to replacing xulrunner version 2.0-4pclos2011 with a previous version I found at
http://rpm.pbone.net/index.php3/stat/4/idpl/14906337/dir/pclinuxos/com/xulrunner-1.9.2.13-1pclos2010.i586.rpm.htmlThe trick for me was how to swap it over with the installed version. I removed xulrunner and libxulrunner version 2.0-4pclos2011 with Synaptic. Then I went into a console and typed su to become root.
I typed cd /var/cache/apt/archives to go to the directory where I had the rpm files.
I tried the RPM command with -Uvh for Update verbose hash on the xulrunner downgrade
rpm -Uvh xulrunner-1.9.2.13-1pclos2010.i586.rpm
It came up with an error:
error: Failed dependencies:
libxulrunner1.9.2.13 = 1.9.2.13-1pclos2010 is needed by xulrunner-1.9.2.13-1pclos2010.i586
So I had to find libxulrunner version 1.9.2.13-1pclos2010 and got it from
http://rpm.pbone.net/index.php3/stat/4/idpl/14906257/dir/pclinuxos/com/libxulrunner1.9.2.13-1.9.2.13-1pclos2010.i586.rpm.htmlThen I couldn't Upgrade libxulrunner, so I had to change the -U for a -i to install it
rpm -ivh libxulrunner1.9.2.13-1.9.2.13-1pclos2010.i586.rpm
Preparing... ########################################### [100%]
1:libxulrunner1.9.2.13 ########################################### [100%]
That seemed to work fine. Then I retried the original command with the xulrunner package.
rpm -Uvh xulrunner-1.9.2.13-1pclos2010.i586.rpm
Preparing... ########################################### [100%]
1:xulrunner ########################################### [100%]
Yay, success! Now I had to retry Vuze. Guess what? It worked like a dream.
So if this helps anyone, that's cool. And if any of you PCLOS Legends have words of advice for how I could have done this better, or quicker, please don't hesitate to let me know.
