Was using KTorrent and the built-in client in Opera, they worked OK. Decided to install and try out Vuze. Vuze installs but won’t open, it trys but then times out and stops after showing a brief splash screen of Vuze. Uninstalled and tried a reinstall of Vuze again with the same results…it won’t open.
Any idea what it wrong and why it won’t open?
from a terminal type:
vuze
see if there are errors…
Did that, here’s the output:
tt@linux-9swh:~> vuze
using MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9b5 and MOZ_PLUGIN_PATH=/usr/lib/br
owser-plugins
GRE/XULRunner automatically found
java virtual machine used: /usr/lib/jvm/jre/bin/java
classpath used: /usr/share/java/Azureus/Azureus3.jar:/usr/share/java/Azureus/swt
.jar
main class used: org.gudy.azureus2.ui.swt.Main
flags used:
options used: -Xms16m -Xmx128m -Djava.library.path=/usr/lib64/Azureus:/usr/lib/A
zureus -Dazureus.install.path=/var/lib/Azureus -Dazureus.script.version=2 -Dazur
eus.script=/usr/bin/vuze
arguments used:
file:/usr/share/java/Azureus/Azureus3.jar ; file:/usr/share/java/Azureus/swt-3.5
-I20080702-0939.jar ; file:/home/tt/
changeLocale: Default Language != English (United States). Searching without c
ountry…
changeLocale: Searching for language English in any country…
changeLocale: no message properties for Locale ‘English (United States)’ (en_US)
, using ‘English (default)’
Locale Initializing took 648ms
32787: Core: 541ms for activity between ‘Loading Plugin: azemp’ and ‘Loading
Plugin: azrating’
33148: Core: 440ms for activity between ‘Loading Plugin: azrating’ and ‘Loadi
ng Torrents’
33218: Core: 56ms for activity between ‘Initializing Global Torrent Manager’
and ‘Loading Plugin: azupnpav’
33971: Core: 728ms for activity between ‘Loading Plugin: azupnpav’ and ‘Loadi
ng Plugin: azplugins’
34373: Core: 390ms for activity between ‘Loading Plugin: azplugins’ and ‘Load
ing Plugin: azupdater’
34556: Core: 167ms for activity between ‘Loading Plugin: azupdater’ and ‘Load
ing Plugin: Start/Stop Rules’
34778: Core: 206ms for activity between ‘Loading Plugin: Start/Stop Rules’ an
d ‘Loading Plugin: Torrent Removal Rules’
34843: Core: 66ms for activity between 'Loading Plugin: Torrent Removal Rules
’ and ‘Loading Plugin: Share Hoster’
34927: Core: 56ms for activity between ‘Loading Plugin: Share Hoster’ and ‘Lo ading Plugin: Plugin Update Checker’
35228: Core: 300ms for activity between ‘Loading Plugin: UPnP’ and ‘Loading P lugin: DHT’
35387: Core: 150ms for activity between ‘Loading Plugin: DHT’ and ‘Loading Pl ugin: DHT Tracker’
35520: Core: 109ms for activity between ‘Loading Plugin: DHT Tracker’ and ‘Lo ading Plugin: Magnet URI Handler’
35560: Core: 60ms for activity between ‘Loading Plugin: Magnet URI Handler’ a nd ‘Loading Plugin: Core Update Checker’
35639: Core: 56ms for activity between ‘Loading Plugin: Core Update Checker’ and ‘Loading Plugin: Core Patch Checker’
35710: Core: 73ms for activity between ‘Loading Plugin: Core Patch Checker’ a nd ‘Loading Plugin: Platform Checker’
35829: Core: 110ms for activity between ‘Loading Plugin: Network Status’ and ‘Loading Plugin: Buddy’
37587: Core: 1737ms for activity between ‘Loading Plugin: Buddy’ and ‘Initial izing Plugin: Embedded Media Player’
37637: Core: 51ms for activity between ‘Initializing Plugin: Rating’ and ‘Ini tializing Plugin: UPnP Media Server’
37694: Core: 51ms for activity between ‘Initializing Plugin: UPnP Media Serve r’ and ‘Initializing Plugin: Tracker Static Pages’
38910: Core: 1187ms for activity between ‘Initializing Plugin: Tracker Static Pages’ and ‘Initializing Plugin: Azureus Update Support’
38959: Core: 27ms for activity between ‘Initializing Plugin: Azureus Update Support’ and ‘Initializing Plugin: Start/Stop Rules’
39026: Core: 35ms for activity between ‘Initializing Plugin: Start/Stop Rules’ and ‘Initializing Plugin: Download Remove Rules’
39108: Core: 78ms for activity between ‘Initializing Plugin: Download Remove Rules’ and ‘Initializing Plugin: Share Hoster’
39197: Core: 84ms for activity between ‘Initializing Plugin: PluginUpdate’ and ‘Initializing Plugin: Distributed DB’
39400: Core: 196ms for activity between ‘Initializing Plugin: Distributed DB’ and ‘Initializing Plugin: Universal Plug and Play (UPnP)’
39423: Core: 27ms for activity between ‘Initializing Plugin: Universal Plug and Play (UPnP)’ and ‘Initializing Plugin: Distributed Tracker’
39493: Core: 56ms for activity between ‘Initializing Plugin: Distributed Tracker’ and ‘Initializing Plugin: Magnet URI Handler’
39566: Core: 29ms for activity between ‘Initializing Plugin: Magnet URI Handler’ and ‘Initializing Plugin: CoreUpdater’
39590: Core: 18ms for activity between ‘Initializing Plugin: CoreUpdater’ and ‘Initializing Plugin: CorePatcher’
39824: Core: 268ms for activity between ‘Initializing Plugin: LAN Peer Finder’ and ‘Initializing Plugin: Network Status’
39929: Core: 84ms for activity between ‘Initializing Plugin: Network Status’ and ‘Initializing Plugin: Friends’
Core Initializing took 9625ms
UIFunctions/ImageLoad took 101ms
new shell took 145ms
new shell setup took 751ms
skinlisteners init took 220ms
skin init took 2492ms
MainMenu init took 1902ms
createWindow init took 0ms
skin layout took 376ms
pre skin widgets init took 272ms
hooks init took 411ms
WARNING: already added UIUpdatable com.aelitis.azureus.ui.swt.views.skin.sidebar.SideBar@1613b53
skin widgets (1/2) init took 1310ms
skin widgets init took 2414ms
pre SWTInstance init took 5ms
Init Core Columns took 434ms
SWTInstance init took 1208ms
shell.layout took 1542ms
Aborted
tt@linux-9swh:~>
Are you using the Packman version of Vuze?
Make sure you have the latest ver of this
Vuze-libswt3-gtk2 (formerly Azureus-libswt3-gtk2)
If that doesn’t work
go and download this
SourceForge.net: Downloading …
Now navigate to your /usr/share/java/Azureus
copy your new Azureus3.jar here (you might want to make a copy of the old one - but it’s not really necessary, as all will be changed when you update via Yast in the future)
There is no Packman version anymore, or it can’t be found in the Packman Rep.
I went into Software install>yast2 then put Vuze in the search box and installed the 5 Vuze components that came up.
Since Vuze won’t open I have no idea what version it is.
I went and downloaded at SourceForge.net: Downloading … and tried doing what you posted but frankly haven’t got a clue how to do what you suggest below…
Now navigate to your /usr/share/java/Azureus
copy your new Azureus3.jar here (you might want to make a copy of the old one - but it’s not really necessary, as all will be changed when you update via Yast in the future)
Well there is a Vuze in my packman repo when I search Vuze
and this is from Packman web, though listed as Azureus
PackMan :: Informationen zum Paket Azureus
Open Yast - Software Management
filter by repo
select packman
scroll the list, which for me is in two sections of A-Z
Vuze is in the first section
if it is highlighted with blue text, then it needs updating.
Try this first and report back.
Did that.
For some reason neither Vuze nor Azureus is in my Packman repo. I updated the repos and still can’t find either in Packman. Vuze is only found in the other general repos.
Tried that also.
It looked like it was installing then stopped and kicked out this error:
Software installation
The installation has failed. For more information, see the log file at /var/log/YaST2/y2log. Failure stage was: Adding Repositories
Error Message
An error occurred while attempting to subscribe to the required repositories. Review the yast2 logs for more information.
in a terminal type
zypper lr
and post it here
Here’s the output:
tt@linux-9swh:~> zypper lr
| Alias | Name | Enabled | Refresh
–±--------------------------±--------------------------±--------±-------
1 | openSUSE-11.0-Non-Oss | openSUSE-11.0-Non-Oss | Yes | No
2 | openSUSE-11.0-Oss | openSUSE-11.0-Oss | Yes | No
3 | Main Repository (OSS) | Main Repository (OSS) | Yes | Yes
4 | Packman Repository | Packman Repository | Yes | Yes
5 | Main Repository (NON-OSS) | Main Repository (NON-OSS) | Yes | Yes
6 | openSUSE-11.0-Updates | openSUSE-11.0-Updates | Yes | Yes
tt@linux-9swh:~>
Go to repo manager
delete all but packman then add these back
OSS:
Index of /distribution/11.0/repo/oss
Non OSS:
Index of /distribution/11.0/repo/non-oss
Updates:
Index of /update/11.0
finish then exit yast
as su
run
zypper up
then
zypper in vuze*
OK, here’s what I got:
tt@linux-9swh:~> su
Password:
linux-9swh:/home/tt # zypper up
Reading installed packages…
Nothing to do.
linux-9swh:/home/tt # zypper in vuze*
Reading installed packages…
‘Vuze-libswt3-gtk2’ is already installed.
‘Vuze-libswt3-gtk2-debuginfo’ is already installed.
‘Vuze-libswt3-gtk2-debugsource’ is already installed.
‘Vuze’ is already installed.
‘Vuze-console’ is already installed.
Nothing to do.
linux-9swh:/home/tt #
Ok.
so now go back to this
If that doesn’t work
go and download this
SourceForge.net: Downloading …
Now navigate to your /usr/share/java/Azureus
copy your new Azureus3.jar here (you might want to make a copy of the old one - but it’s not really necessary, as all will be changed when you update via Yast in the future)
The file you download will be an archive. extract it and copy the Azureus3.jar file to replace the one in /usr/share/java/Azureus
you may need to be using file manager super user mode
When I extract it, it opens up into so many files I can’t find that Azureus3.jar file, to copy it over…
My mistake
it’s not an archive
the file you have downloaded is the file- no need to extract
just copy and paste - re-name the old one first to oldAzureus3.jar
Konqueror will not let me re-name the file to oldAzureus3.jar.
It kicks out an error saying access denied, to /usr/share/java/Azureus/oldAzureus3.jar…
Same error pops up when trying to copy the new Azureus 3.1.1.0.jar file over.
Are you doing this with super user file manager??
First time I didn’t.
Then I saw your intstructions and did it with super user file manager.
It then allowed a re-naming of that jar file.
Then I copied over the new jar file which went through with no error.
Tried Vuze and it still won’t open.
Even did a reboot and Vuze is the same, it looks like it is loading but times out and won’t open.
First, go to repository manager
make sure all your repo’s are enabled and refresh.
Now go to Software Management
filter by repo and select Packman
Scroll to Vuze, it’s in the first section A-Z
click on the tick of Vuze and Vuze-libswt3
this should mark them for update and will restore it back from the changes we just made.
I suggest now you go here: PackMan :: Informationen zum Paket Azureus
click on the Packager name: Tony Graffy
this will start an email to Him and Packman
Give a brief explanation of your problem
Start vuze from a terminal again
and post the output in your email
wait for a reply. It’s usually quite quick.
For the time being use ktorrent - it’s good.