Package Details: vuze

Git Clone URL: (read-only, click to copy)
Package Base: vuze
Description: A feature-rich Java-based BitTorrent client (previously called 'Azureus')
Upstream URL:
Licenses: GPL
Submitter: td123
Maintainer: joshuarosato
Last Packager: patlefort
Votes: 120
Popularity: 0.27
First Submitted: 2011-07-31 04:31 (UTC)
Last Updated: 2021-09-26 14:50 (UTC)

Dependencies (5)

Sources (1)

Latest Comments

micwoj92 commented on 2021-03-16 20:51 (UTC)

Please update links to https.

rafaelff commented on 2020-01-14 16:45 (UTC)

@GraveDigger: which folder?

GraveDigger commented on 2020-01-14 16:41 (UTC)

i've noticed that every version of vuse for manjaro has a issue with a particular folder not being writable. please take a look at how you complied your version. thanks

Det commented on 2017-12-26 17:33 (UTC)

There :).

moham_96 commented on 2017-12-26 04:53 (UTC)

@Det can you package Biglybt which is based on azureus and actively developed by former azeureus developers

gkun commented on 2017-11-02 21:45 (UTC)

Thank you :-)

Det commented on 2017-11-02 21:40 (UTC)


gkun commented on 2017-11-02 21:37 (UTC)

Today the package was updated, but apparently it fails the validity check: ERROR: One or more files did not pass the validity check!

raspher commented on 2017-05-01 21:32 (UTC)

# BUG white tools>>options... window, after some use....

capoeira commented on 2016-12-17 21:07 (UTC)

@Det nice, because it is very confusing when you first start it. Actualy the program was unusable until I disabled the auto-update. Unclosable also lol

Det commented on 2016-12-17 21:03 (UTC)

Added a mention in the .install for future. Thanks.

rafaelff commented on 2016-12-17 20:55 (UTC)

@capoeira: de nada ;)

capoeira commented on 2016-12-17 20:53 (UTC)

@rafaelff thanks. Did so

capoeira commented on 2016-12-17 20:50 (UTC)

It happens again. screenshot: The moment it starts it says it downloaded an update and wants to restart. after restart same window appears.

rafaelff commented on 2016-12-17 20:48 (UTC)

I recommend disabling Vuze autoupdate. In order to do so: 1- Go to Tools>Options>Interface>Start and uncheck all checkboxes in it; 2- Go to Tools>Options>Plugins>Plugin Update and uncheck the only checkbox.

capoeira commented on 2016-12-17 20:45 (UTC)

yes I had. I'm compiling it again now

Det commented on 2016-12-17 20:44 (UTC)

Ok, but I'm still not sure whether you have the or not? If not, you can just update the package. No need to uninstall anything.

capoeira commented on 2016-12-17 20:41 (UTC) (edited on 2016-12-17 20:42 (UTC) by capoeira)

@Det it happened automaticly. It wanted to update itself the first time I started it. And the error pop up had a link, which I followed: I think I just uninstall and try it again.

Det commented on 2016-12-17 20:36 (UTC) (edited on 2016-12-17 20:37 (UTC) by Det)

You shouldn't use the builtin updater. Use makepkg or an AUR tool (packer, yaourt, etc.) and update the _package_ the same way you installed it in the first place. If you insist, you'd need to run the thing as root or chmod/chown the install dir (hacky, and also, why then use a package in the first place?). I don't know which Wiki are you talking about.

capoeira commented on 2016-12-17 20:32 (UTC)

@Det I just installed this and it tried to update itself complaining not to have write access to opt. closing the software caused a endless loop of restarts. Had to kill it and update manualy like I found in the wiki

Det commented on 2016-12-17 20:26 (UTC)

Update the package as any other.

capoeira commented on 2016-12-17 19:29 (UTC)

well. this could include a script to update. or how s it supposed to work?

moham_96 commented on 2016-08-23 00:21 (UTC)

Vuze dies after a while of normal operation throwing the following error /usr/bin/vuze: line 198: 2288 Segmentation fault (core dumped) ${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. what is the cause of this problem ?

Det commented on 2016-02-12 16:28 (UTC)

Wha... okay?

Scimmia commented on 2016-02-12 16:27 (UTC)

I don't even use this package, so i don't really care. I'm just pointing on problems with your methods. I should have known better than to try reason.

Det commented on 2016-02-12 16:17 (UTC)

I get that you don't like it, but what did you want to change?

Scimmia commented on 2016-02-12 16:16 (UTC)

Just because you do it in a lot of packages doesn't make it right. Ideally, nothing in $srcdir should be changed after build().

Det commented on 2016-02-12 16:03 (UTC)

Hmm, I wasn't asking you, but I'll do that. :)

rafaelff commented on 2016-02-12 16:02 (UTC)

Well, since you asked, you could add "..." after "Fixing paths", to fit another msg2 ... :P

Det commented on 2016-02-12 15:56 (UTC)

I'm curious what did you need to change in the package anyway?

rafaelff commented on 2016-02-12 15:54 (UTC)

What Scimmia said is true when running 'makepkg -R'. But this flag is useful only when the compilation of a source code is too much time consuming, which is not the case here... IMHO no problem moving in this package.

Det commented on 2016-02-12 15:43 (UTC)

I do that with quite a lot of packages. Do you mean makepkg(8) -R?:

Scimmia commented on 2016-02-12 15:41 (UTC)

Moving things out of $srcdir in the package function is a bad idea. It breaks repackaging.

Det commented on 2015-07-21 13:31 (UTC)


toropisco commented on 2015-07-21 13:24 (UTC)

Hahahaha! Det, Det my child! You crack me up. Not only call me "my friend" but quote falconindy and myself out of context. I am sure you saved that bookmark sulking and bode your time to be able to show off smugly. That only demonstrate the fact that you are a poorly socialized individual. And that email nymshifting? You are not even capable of owning up when relating to others. Please don't contact me again.

toropisco commented on 2015-07-21 13:24 (UTC)

Hahahaha! Det, Det my child! You crack me up. Not only call me "my friend" but quote falconindy and myself out of context. I am sure you saved that bookmark sulking and bode your time to be able to show off smugly. That only demonstrate the fact that you are a poorly socialized individual. And that email nymshifting? You are not even capable of owning up when relating to others. Please don't contact me again.

toropisco commented on 2015-07-21 13:24 (UTC)

Hahahaha! Det, Det my child! You crack me up. Not only call me "my friend" but quote falconindy and myself out of context. I am sure you saved that bookmark sulking and bode your time to be able to show off smugly. That only demonstrate the fact that you are a poorly socialized individual. And that email nymshifting? You are not even capable of owning up when relating to others. Please don't contact me again.

toropisco commented on 2015-07-21 13:24 (UTC)

Hahahaha! Det, Det my child! You crack me up. Not only call me "my friend" but quote falconindy and myself out of context. I am sure you saved that bookmark sulking and bode your time to be able to show off smugly. That only demonstrate the fact that you are a poorly socialized individual. And that email nymshifting? You are not even capable of owning up when relating to others. Please don't contact me again.

toropisco commented on 2015-07-21 13:23 (UTC)

Hahahaha! Det, Det my child! You crack me up. Not only call me "my friend" but quote falconindy and myself out of context. I am sure you saved that bookmark sulking and bode your time to be able to show off smugly. That only demonstrate he fact that you are a poorly socialized individual. And that email nymshifting? You are not even capable of owning up when relating to others. Please don't contact me again.

Det commented on 2015-07-21 11:09 (UTC)

Just uploaded vuze You might get a conflict with "/usr/bin/azureus", which was previously added from the .install, and now included in the package. To fix it, either: $ rm /usr/bin/azureus or: # pacman -U --force <path> (see pacman(8):

Det commented on 2015-07-21 09:29 (UTC)

OK, @vorbote, my friend, but not _every time_ somebody tells you what doesn't work in your package does it translate into an "insult" :D. The report you're talking about is pretty funny and people who weren't already mad at me for our talk in 'cower-git' (apparently, falconindy, you know, you never replied to me privately, either), make up your own conclusions: Full quotes: <falconindy>: [Det]'s not a very well-socialized individual. Sorry, there's not much we can do about fixing that. <vorbote>: *Sigh* The kid needs a thourough dusting in public. Let's see who gets there first. :-) Thanks anyway. So maybe it's time you let go of your beef with me when I said almost a year ago that your package was "replaced". It really wasn't an insult. ps. If you think 97 packages is too much, you just gave me a 98th. pps. "Daniel Davis" is not my real name. :)

toropisco commented on 2015-07-20 16:20 (UTC)

josephgbr, you can say whatever you want, but you haven't been insulted by the person in question in the past, and there is a flyspray report to back it up (that I won't dig up for you, look it up if you care). You know what? I don't care about vuze anymore. I'm adding you and Det as comaintainers and signing off myself. Have fun.

rafaelff commented on 2015-07-20 16:10 (UTC)

Well, that's some attitude... Just say SourceForge is having storage problems. No need for this response on other maintainer's feedback.

toropisco commented on 2015-07-20 15:57 (UTC)

Hi Daniel Davis aka "Det", you simply can't stop being your antisocial self! Can you? For your information, SourceForge is presently having storage problems that started Monday, July 13 2015 and that, if you weren't so busy maintaining 97 packages, you'd have time to actually be informed about. Your comment has value, but your form is pathetic. What does has to do with anything?

Det commented on 2015-07-20 13:22 (UTC)

The homepage should be or doesn't exist (just like and is wrongly reported to be a problem with the entire SourceForge.

Det commented on 2014-10-20 20:41 (UTC)

By the way, since we now have .AURINFOs, you could probably revert to the _ver=${pkgver//./} versioning, and remove all that pretty unnecessary talk on "whining", including the sentence "Don't whine, send a patch". Thanks. E: Also, the dependency 'java-environment-common' is wrong. It's meant for Java Environment packages (jdk8-openjdk, jdk), and Vuze only needs 'java-runtime' anyway.

toropisco commented on 2014-08-25 11:32 (UTC)

Hmm... I think this is a bug in AUR. My canonical reference is:

rafaelff commented on 2014-08-25 02:41 (UTC)

Weird, because I had vuze installed which seems to be exactly the one recorded on Aug 18 00:00:09 UTC 2014 in GIT repo. Anyway, don't want to argue with you. It is working just fine for me in the pkgrel=3. Thanks a lot @vorbote.

toropisco commented on 2014-08-24 00:18 (UTC)

@josephgbr But your idea of generalizing the runtime path beyond java-common is fine with me.

toropisco commented on 2014-08-24 00:00 (UTC)

@josephgbr You are not using the latest version of the PKGBUILD. And before you say I'm moving the goalpost; it was updated at 2014-08-17 22:03GMT.

rafaelff commented on 2014-08-23 17:39 (UTC)

'/usr/bin/vuze' has java fullpath set to '/usr/lib/jvm/java-default-runtime/bin/java', resulting in the fatal error message: /usr/bin/vuze: line 119: /usr/lib/jvm/java-default-runtime/bin/java: No such file or directory Please sed JAVA_PROGRAM_DIR from "/usr/lib/jvm/java-default-runtime/bin/" to '$JAVA_HOME/bin'. FWIW, I have 'jdk' version 8u20 installed. full log:

toropisco commented on 2014-02-22 00:33 (UTC)

@cro > What's that gconf stuff good for?? For desktop environments that still use GTK+ 2 such as XFCE and I believe MATE. > It doesn't work as root without display: Obviously you don't use such type of DEs. > Also it's strange that you change PKGEXT. Don't confuse practicality with conformity. You see, not everybody has the latest Core i7 and 16 GB RAM. XZ compression consumes high quantities of RAM and CPU resources. There is no point in compressing something that will be repacked, installed and most likely thrown away immediately after. If you want to store it somewhere, you can compress it yourself.

cro commented on 2014-02-21 02:13 (UTC)

What's that gconf stuff good for?? It doesn't work as root without display: (gconftool-2:6648): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Also it's strange that you change PKGEXT.

toropisco commented on 2013-09-29 15:24 (UTC)

@jcasper Thanks for bringing this to my attention. I have uploaded an updated set of files without increasing the package version as not to disturb the people who already have done the manual upgrade.

jcasper commented on 2013-09-29 03:00 (UTC)

Might want to put a note about the swt update in the .install. I didn't see the instructions in the comments until I got annoyed with it always trying to update itself.

toropisco commented on 2013-09-01 16:24 (UTC)

I have uploaded a new update because after I managed to update swt, there came an azrating update that's uninstallable as well. *sigh* I took the opportunity to do further name cleanup so now swt{$CARCH} is installed as swt.jar. Now the instructions are simpler: Step 4: Extract swt.jar and copy it over /usr/lib/vuze/swt.jar @josephgbr Thanks for the comments! Very appreciated.

rafaelff commented on 2013-09-01 16:00 (UTC)

@vorbote: many thanks for the effort you put to rearrange the files in FHT. I looks awesome! And thanks for the instructions. It worked just fine for me. As suggestion, here the command lines to apply the steps 3, 4 and 5 (obviously, replace CARCH with your architecture, i686 or x86_64): mv /tmp/swt-4403-gtk-linux-${CARCH}.zip $HOME sudo rm /usr/lib/vuze/swt64.jar sudo unzip swt-4403-gtk-linux-${CARCH}.zip -d /usr/lib/vuze/swt64.jar rm -rf ~/.swt/

toropisco commented on 2013-09-01 15:49 (UTC)

I haven't found a way to divine the direct download links for the latest SWT update, if someone discovers how to pull those files from some server at Vuze's it is much appreciated. As some of you may have discovered yet, Vuze uses a development version of SWT that is not available in the repos nor the AUR. So I will outline here a procedure to *update manually* Vuze's private SWT copy: 0. VERY IMPORTANT: Update your installation to as I have, finally, updated the PKGBUILD to install binaries in their proper FHS location, namely /usr/lib. Previously binaries where installed in /usr/share, which I should have corrected when I inherited this package. My bad. 1. Run Vuze. When it start up it asks you to download an updated SWT. Let it do its thing. 2. When Vuze restarts, it will ask again to download SWT. Ignore it and quit Vuze instead. 3. Go to /tmp, there you will find a ZIP file called swt-4403-gtk-linux-{$CARCH}.zip. Copy it somewhere safe. 4. Extract the swt.jar file from the ZIP file and overwrite /usr/lib/vuze/swt64.jar 5. Delete $HOME/.swt And you are done. 4.

Etzos commented on 2013-08-18 02:03 (UTC)

I don't think it's a good idea to change the PKGEXT in a PKGBUILD like you do. I'm pretty sure that's supposed to be more of a user choice.

toropisco commented on 2013-08-16 22:10 (UTC)

@willemw **Sigh** That's the reality of taking care of inherited loot. :-) Thanks for spotting it. Fixed.

willemw commented on 2013-08-16 08:12 (UTC)

/usr/sbin in the .install file is obsolete now. Should be: /usr/bin.

toropisco commented on 2013-07-11 13:31 (UTC)

@evilxel Fixed. BTW, your patched file is unnecesary and the proper fix was to edit a line in the PKGBUILD file. Would you mind removing your comment below? It may lead people to donwload an unneeded file and try to "fix" their installation by hand when the PKGBUILD is already working fine. And another BTW, I like the idea behind your ordered download plugin. Why don't you upload a PKGBUILD to the AUR? You can use one of my other vuze-related PKGBUILDs as a guide.

commented on 2013-07-11 12:11 (UTC)

Please add this in pkgbuild. Rename to Azureus2.jar Copy to /usr/share/vuze/ Also Vuze won't start... thanks.

rafaelff commented on 2013-05-10 21:51 (UTC)

Guys, both of you, let's try to keep the courtesy, and avoid attacking each other. Please. @Vorbote, allow me to partially agree with @zozi56 comments. Sometimes it happens all the that developers do a terrible job, and I agree with you of being mad at that. But, in the end, who will read your PKGBUILD is not the developer, but the AUR user who might feel offended by the comments, which I know is not your intention. My suggestion: Keep it clean, with relevant comments (e.g.: # This is bugged, won't work without the following workaround) and done - it will be flawless. Except for that incident, keep up with the good work

toropisco commented on 2013-05-10 16:01 (UTC)

@zozi56 So I'm unprofessional for expressing my "emotional state"? I appreciate your politeness but not the speciousness of your affirmations. I'm not expressing "emotional state", I'm stating my contempt towards unprofessional (lack of) release engineering. Why don't you remove the comments yourself? I'll be very happy to transfer the git repos ownership to you. When you have control of those, I'll orphan the package here in AUR. Else, the comments will remain until upstream fixes its package.

toropisco commented on 2013-05-10 15:44 (UTC)

@josephbgr I was wondering about the relationship of the plugins and vuze myself. I think your solution is the cleanest and will implement it asap. On separating the plugins, I doubt it is possible. They are system plugins and there is a bug in the patcher that throws the application into a loop as snoxu rightly complained.

rafaelff commented on 2013-05-10 14:55 (UTC)

btw, about vuze-plugin-i2p and vuze-plugin-mldht, don't you think that 'vuze' optdepends these two plugins, instead of them depending on 'vuze'?

zozi56 commented on 2013-05-10 14:54 (UTC)

Excerpts from the PKGBUILD: # Java and Ruby people are IDIOTS when it comes to creating proper releases. # Truly blabbering, stuttering MORONS. # Did I mention, again, I have lost all respect for these people? # Now, kids... Don't try this at home or much grief will ensue. These comments are not funny. They are a sign of immaturity. Documenting the maintainer's actual emotional state is not a professional attitude. Please consider getting rid of them.

rafaelff commented on 2013-05-10 14:52 (UTC)

@vorbote, I was wondering if it is possible separate these plugins from the main package, adding them (e.g. vuze-azrating and vuze-azupnpav) to 'vuze's depends array. This way, you can avoid that users have to update all of it everytime, reducing bandwidth and CPU usage, and reduce your headache as maintainer.

rafaelff commented on 2013-05-10 02:25 (UTC)

Ignore these attempts to update plugins, as you don't have permission to this folder. Just ignore it.

snoxu commented on 2013-05-10 02:16 (UTC)

Just updated and the new Vuze tries to update some and fails: Version 0.4.7 of plugin 'azupnpav/UPnP Media Server' failed to install - /usr/share/vuze/plugins/azupnpav/ (Permission denied)

toropisco commented on 2013-05-09 21:55 (UTC)

Sorry for the short burst of PKGBUILD updates. Vuze people have created their *shoddiest* release ever. There goes the proof: Java lobotomizes people.

toropisco commented on 2013-04-17 20:32 (UTC)

@phoenixlzx Glad to know you are back and with a vengeance. :-)

phoenixlzx commented on 2013-04-17 11:50 (UTC)

Hi, I'm back again. @vorbote, vuze is now in [archlinuxcn], Our package list is here: I will follow your update and build this package on our build machine in Las Vegas(No network block anymore). :-D

toropisco commented on 2013-03-12 01:38 (UTC)

@xvoprsalek I've tested Oracle's Java7 SDK from AUR with Vuze (latest PKGBUILD from AUR) and it works flawlessly. You have worse problems than a vuze install. I recommend a full OS reinstall. If you have a recent install: 1) Made the /usr/lib transition cleanly, 2) you are using systemd and not sysv init with rc.conf, 3) whatnot (check arch-announce for the glaring ones); then you don't need to reinstall but rather review carefully your shell initialization files in your account's home directory.

rafaelff commented on 2013-03-11 19:06 (UTC)

@xvorsalek: I don't know, but maybe it looks for "$JAVA_HOME/bin", which normally is also in $PATH

xvoprsalek commented on 2013-03-11 18:18 (UTC)

I have quite old machine and Webstorm with openjdk7 was VERY slow -- almost unusable. When I got some spare time, I will dig into it, try figure out pros and cons and why... So far, my head is just not taking the idea that Vuze can not find a java executable even it's in my $PATH, is properly installed and working likecharm with other applications.

toropisco commented on 2013-03-11 18:12 (UTC)

As far as I know, according to the news that I read last year in the tech press—no java developer here—, Oracle java7 releases are basically OpenJDK7 re-branded and sprinkled with some proprietary bits, namely fonts, midi drivers and other exotic things that are scheduled to be replaced by open source software AFAIK. Furthermore, apart from a nasty FUDmmercial pushing Oracle's binaries when starting it on the console, webstorm worked well here in the short time I installed it this past weekend.

rafaelff commented on 2013-03-11 13:50 (UTC)

Not an option? I use jdk7-openjdk.

xvoprsalek commented on 2013-03-11 13:39 (UTC)

Using OpenJDK or OpenJRE is not an option here. Also this is long term state, after many reboots and poweroffs. Reainstalling Java my my first step ofcourse, didn't help. Vuze is just stupid to use executable that is in $PATH. command -v java /opt/java/bin/java

toropisco commented on 2013-03-09 20:22 (UTC)

Forgot to mention this: Log out and log in again after reinstalling java. To make sure that vuze's launch script is finding the executable, open a terminal emulation window and type "command -v java". Assuming you use bash as your shell, it should output the path to the executable.

toropisco commented on 2013-03-09 19:45 (UTC)

My suggestion is to reinstall java7 (not 6, much less 5). In fact, I strongly suggest you use OpenJRE7 available in the official repos.

xvoprsalek commented on 2013-03-09 10:24 (UTC)

I can not start it for "missing jre". Starting Azureus... OOPS, you don't seem to have a valid JRE [java = Picked] You need to upgrade to JRE 1.4.x or newer from Java exec not found in PATH, starting auto-search... ls: cannot access /usr/java/latest: No such file or directory ls: cannot access /usr/java: No such file or directory ls: cannot access /usr/lib/jvm/latest: No such file or directory ls: cannot access /usr/lib/jvm: No such file or directory Re-checking with GCJ (Sun Java recommended).. OOPS, you don't seem to have a valid JRE [java = Picked] You need to upgrade to JRE 1.4.x or newer from Java exec not found in PATH, starting auto-search... ls: cannot access /usr/java/latest /usr/java /usr/lib/jvm/latest /usr/lib/jvm: No such file or directory OOPS, unable to locate java exec in /usr/java/latest /usr/java /usr/lib/jvm/latest /usr/lib/jvm/ hierarchy You need to upgrade to JRE 1.4.x or newer from I would appreaciate some pointers from you guys. I have jdk installed from aur. Working fine (I use webstorm for example) My PATH also includes java path: echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/java/bin:/opt/java/db/bin:/opt/java/jre/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/qt4/bin

toropisco commented on 2013-02-04 17:05 (UTC)

Playing catch up with new packages without version changes. The heathens.

j_r0dd commented on 2013-02-01 22:23 (UTC)

Got it thanks! Working beautifully now!

toropisco commented on 2013-02-01 21:32 (UTC)

Check the version of the PKGBUILD you used. I have already fixed that (last night).

j_r0dd commented on 2013-02-01 21:23 (UTC)

@vorbote the only location I have a vuze.desktop file is in /usr/share/applications. With the %U option magnets work fine. With %f magnet links work and open vuze but then vuze throws an error and doesn't begin download.

toropisco commented on 2013-02-01 00:47 (UTC)

@eugf Well, compiling xulrunner is taxing and not all paople want to compile such a big package. What I may do is review that binary PKGBUILD and upload a new version to AUR.

eugf commented on 2013-02-01 00:41 (UTC)

@vorbote I did that, works like a charm. Why not use xulrunner192 or xulrunner by default in PKGBUILD?

toropisco commented on 2013-02-01 00:38 (UTC)

@eugf I just noticed there is binary PKGBUILD of xulrunner 192 in AUR. It is outdated, but you can edit the PKGBUILD and update it to the latext version.

toropisco commented on 2013-02-01 00:26 (UTC)

@eugf. You need to install xulrunner192 from AUR. Or configure vuze to use the classic interface, that's always my first choice. BTW, please don't use but one of the many alternatives, see for the reasons why.

eugf commented on 2013-02-01 00:16 (UTC)

When I installed this package, i got this message error: The program runs fine, but this missing lib ('') can affect some feature (I don't know what feature is). So, I solve this problem installing 'xulrunner' from pacman and the message goes out. Is 'xulrunner' a dependency? PS: I don't have 'firefox' installed.

toropisco commented on 2013-01-31 21:31 (UTC)

@j_r0dd Are you sure? It works here as expected. If you are having trouble, clean up the contents of $HOME/.local/share/applications/mimeapps.list and check if you have a local vuze.desktop file in that directory as well.

j_r0dd commented on 2013-01-31 21:23 (UTC)

@vorbote Thanks! You missed the change in the Exec line. It won't work otherwise. Exec=vuze %U

toropisco commented on 2013-01-31 21:09 (UTC)

@j_r0dd done. Need new reading glasses. :-)

j_r0dd commented on 2013-01-31 20:52 (UTC)

@vorbote Thanks! You missed the change in the Exec line. It won't work otherwise. Exec=vuze %U

toropisco commented on 2013-01-31 01:13 (UTC)

@j_r0dd done.

j_r0dd commented on 2013-01-30 18:44 (UTC)

@vorbote is there any chance you can have the vuze.desktop file updated to the following so it will properly handle magnet links? [Desktop Entry] Encoding=UTF-8 Categories=Java;Network;FileTransfer;P2P Comment=Multimedia Bittorrent Client Exec=vuze %U GenericName=Multimedia Bittorrent Client Icon=vuze.png MimeType=application/x-bittorrent;x-scheme-handler/magnet; Name=Vuze Type=Application

toropisco commented on 2012-12-27 11:35 (UTC)

@josephgbr did you check the change history in the git repo?

rafaelff commented on 2012-12-27 04:58 (UTC)

pkgrel=5 ? Did you reset to 1 the pkgrel in this new version ? If not, leave as it is, but please remember too reset it in future upstream releases of this software.

toropisco commented on 2012-12-26 13:08 (UTC)

@phoenixlzx I'm sad to see the GFC is causing you and your fellow citizens so much trouble. @josephgbr I've adopted the package. You are welcome to rattle my chain if I don't stay on top of things.

rafaelff commented on 2012-12-26 03:03 (UTC)

@vorbote: Would you mind adopt this package? @phoenixlzx: That's sad. Anyway, thanks for your contribution.

phoenixlzx commented on 2012-12-26 02:51 (UTC)

Hi guys, sorry for the late reply. However, due to something nasty in China network, i can't download the source files correctly -- I even can't reach the site now. I think i shouldnt take this package any more, the god damn network will ruin our community. Thank you @vorbote @josephgbr and so many people for the help.

toropisco commented on 2012-12-26 01:01 (UTC)

Caught myself doing something pointless. So... I think this is ready for merging into master, what do you think @phoenixlzx ?

toropisco commented on 2012-12-26 00:56 (UTC)

@josephgbr Well, yes, that would make things even simpler, it can be automated too. Yup it works nicely.

rafaelff commented on 2012-12-26 00:45 (UTC)

@vorbote: ah, I read it before, but didn't notice the change in version. Thanks for the warning me. Well, in my suggestions, second one would need to be "_ver=4812".

toropisco commented on 2012-12-26 00:40 (UTC)

Simplified the PKGBUILD even more and updated it to

toropisco commented on 2012-12-26 00:25 (UTC)

@josephgbr, as a first stab at simplifyng the PKGBUILD you may want to check the pkgbuild at out.

rafaelff commented on 2012-12-25 23:18 (UTC)

@phoenixlzx: Are you willing to abandon this package? Wednesday already passed, and my yaourt still complains about this md5 error. And just my 2 cents: Instead of the source URL have the current workaround, I suggest two options: 1) use ${pkgver//./} as variable substitution (much more clean) or 2) "_ver=4810", which won't mess the displayed URL in the AUR web interface (cause AUR won't parse shell scripts).

phoenixlzx commented on 2012-12-17 07:53 (UTC)

The keyboard of my laptop broken down... I have to wait until Wedsday to get a new keyboard. Shall I let @vorbote maintain this package or I find someone else to do this?

toropisco commented on 2012-12-16 00:59 (UTC)

There is a corrected PKGBUILD in

commented on 2012-12-16 00:58 (UTC)

There seems to be an error in the md5 sum for .jar file. Using yaourt to upgrade throws up this error. i downloaded the jar file seperately and it gives the md5 sum to be 88696519b464fb1262c778fdf4f21bd0 i have successfully built vuze with the changed md5.

commented on 2012-10-26 07:23 (UTC)

@phoenixlzx: will do that next time :)) (you sould have the link in the description :)

phoenixlzx commented on 2012-10-26 07:03 (UTC)

@tukan thankyou for reminding! If you wanna contribute, just send pull request to this repo:

commented on 2012-10-26 06:59 (UTC)

I don't know how to submit a change to pkgbuild but the solution is to change: install -Dm644 plugins/azupnpav/azupnpav_0.4.1.jar "$pkgdir/usr/share/vuze/plugins/azupnpav/azupnpav_0.4.1.jar" to install -Dm644 plugins/azupnpav/azupnpav_0.4.3.jar "$pkgdir/usr/share/vuze/plugins/azupnpav/azupnpav_0.4.3.jar"

commented on 2012-10-26 06:56 (UTC)

The new version does not install correctly. The problem is with the azupnpav_0.4.1.jar. With this version comes azupnpav_0.4.3.jar! ... ==> Building and installing package ==> Making package: vuze (Fri Oct 26 08:29:10 CEST 2012) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving Sources... -> Found Vuze_4800.jar -> Found Vuze_4800_linux.tar.bz2 ==> Validating source files with md5sums... Vuze_4800.jar ... Passed Vuze_4800_linux.tar.bz2 ... Passed ==> Extracting Sources... -> Extracting Vuze_4800_linux.tar.bz2 with bsdtar ==> Removing existing pkg/ directory... ==> Entering fakeroot environment... ==> Starting package()... install: cannot stat ‘plugins/azupnpav/azupnpav_0.4.1.jar’: No such file or directory ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build vuze. ==> Restart building vuze ? [y/N] ==> -----------------------------

toropisco commented on 2012-10-02 16:40 (UTC)

Oops, forgot to mention that I added libwebkit as an optdepend. Feel free to make it a hard depend.

toropisco commented on 2012-10-02 16:39 (UTC)

@phoenixlzx I keep polishing this baby. I have confirmed that libwebkit web enables vuze fully. Here is the corrected PKGBUILD: (that repo has to be useful somehow :-)).

phoenixlzx commented on 2012-10-02 15:32 (UTC)

@vorbote Thank you for your help, my Arch's Xorg(it really sucks) and KDE crashed so I visit your PKGBUILD and get things done in TTY1 with w3m. XD Again, thank you very much. And a great plugin for vuze.

toropisco commented on 2012-10-02 15:02 (UTC)

Guys (and gals) an apology for my mistake, I've uploaded the mlDHT plugin to the AUR. Enjoy!!!

toropisco commented on 2012-10-02 14:41 (UTC)

OK, a PKGBUILD that works or I'll eat my hat. ::ashamed:: The link:

toropisco commented on 2012-10-02 14:04 (UTC)

*Sigh* I'm wrong about not having to download an updated jar file to have the real It did work the first time. I wonder what I did wrong that time.

toropisco commented on 2012-10-02 12:10 (UTC)

@phoenixzx This is how to fix it: Drop the external swt dependency and install swt/swt32.jar or swt/swt64.jar in /usr/share/vuze without renaming it, depending on the architecture. Drop the extra Azureus.jar download as it is not needed anymore. Here is a working PKGBUILD for those that want a quick fix. Use the same vuze install contained in the tarball.

phoenixlzx commented on 2012-10-02 01:43 (UTC)

@fernando_ccs17 Hmmm... It seems to be something wrong with swt libraries, or upstream binary? Thank you for your report, I will check it out as soon as possible (Sorry for my Arch crashes this morning, I have to repair it first).

fernando_ccs17 commented on 2012-10-01 22:29 (UTC)

Starting Azureus... Suitable java version found [java = 1.7.0_07] Configuring environment... Java exec found in PATH. Verifying... Browser check failed with: Could not load SWT library. Reasons: no swt-gtk-4233 in java.library.path no swt-gtk in java.library.path Can't load library: /home/fernando/.swt/lib/linux/x86_64/ Can't load library: /home/fernando/.swt/lib/linux/x86_64/ 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/firefox for GRE GRE found at /usr/lib/firefox. Browser check failed with: Could not initialize class org.eclipse.swt.widgets.Display Can't create browser. Will try to set LD_LIBRARY_PATH and hope Vuze has better luck. setting LD_LIBRARY_PATH to: /usr/lib/firefox setting MOZILLA_FIVE_HOME to: /usr/lib/firefox 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=3 org.gudy.azureus2.ui.swt.Main file:/usr/share/vuze/Azureus2.jar ; file:/usr/share/java/swt-4.2.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)' java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance( at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( at java.lang.reflect.Constructor.newInstance( at org.gudy.azureus2.ui.swt.Main.<init>( at org.gudy.azureus2.ui.swt.Main.main( at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at com.aelitis.azureus.launcher.MainExecutor$ at Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-gtk-4233 in java.library.path no swt-gtk in java.library.path Can't load library: /home/fernando/.swt/lib/linux/x86_64/ Can't load library: /home/fernando/.swt/lib/linux/x86_64/ at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.C.<clinit>(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source) at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.<init>( at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance( at com.aelitis.azureus.ui.swt.Initializer.<init>( ... 12 more Exit from Azureus complete No shutdown tasks to do Azureus TERMINATED. What i`m doing wrong?

phoenixlzx commented on 2012-09-20 09:40 (UTC)

@kevku updated, thx!

kevku commented on 2012-09-19 20:03 (UTC)

hmm seems like the 4720 tar contains 4712 so made a pkgbuild that gets the proper jar

jbj commented on 2012-07-19 12:11 (UTC)

@Kalinda Vuze works for me after installing the xulrunner192 package from AUR. The problem seems to be that Vuze uses an old version of xulrunner (i.e., Firefox) to display its donation-begging popup. Once it decides that it's time to ask for donations, it will crash every time because it fails to display that screen. The issue has been reported upstream almost a year ago:

phoenixlzx commented on 2012-06-23 04:38 (UTC)

@Kalinda Me too. But this is bug of the program, we can do nothing but report it to the developers.

Kalinda commented on 2012-06-22 17:39 (UTC)

Hi, guys - Every time I go to save a torrent and start a download, Vuze crashes. This is what it says in the terminal: vuze/vuze: line 188: 14887 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.

phoenixlzx commented on 2012-05-17 08:58 (UTC)

@vorbote My username is phoenixlzx. Let's get start :-)

toropisco commented on 2012-05-16 23:34 (UTC)

@phoenixlzx ping me with your username and I'll add you as a collaborator. :-)

phoenixlzx commented on 2012-05-16 15:14 (UTC)

@vorbote Okay then, happy collaborating! :D but time to sleep now.. You can create a repository in github and leave me a link. I will join you tomorrow.

toropisco commented on 2012-05-16 15:11 (UTC)

@phoenixizx Don't think I'm that good of a packager myself but two heads are better than one and we can always ask for help in -dev :-)

phoenixlzx commented on 2012-05-16 14:40 (UTC)

@vorbote Thank you very much for your effort. I have updated the PKGBUILD as you suggested. I'm glade to work with you, but I have some problem such as I'm not so good at packaging and other things like that. However I would like to learn if you would give me a hand. Thank you again for your help :)

toropisco commented on 2012-05-16 14:08 (UTC)

@phoenixizx Sorry for the delay in getting back to you, I've been short on time. I managed to set up a slate-clean test box last weekend and I came to these conclusions: 1. The only real depends are java-runtime *and* libgnomeui. The latter pulls in all needed dependencies includding libgnome and gnome-vfs. 2. The start up script always calls the local SWT copy, therefore installing a system-wide copy is futile. 3. There is a basic library incompatibility: while vuze's SWT, libgnome and libgnome-ui depend on gtl+2, gnome-vfs depends on gtk+3. 4. The crashes with firefox/xulrunner are due to changes in ABI that in fact cause vuze to die with a segmentation fault. 5. The library version clash due to 3 makes webkitgtk useless as well. Solution: I think the most straightforward solution would be to stop depending on upstream-supplied binaries and compile native Arch binaries instead. In this case we could rely on the swt and xulrunner libraries in extra. I'm willing to lend a hand on this, may be collaborate in Github?

phoenixlzx commented on 2012-05-10 09:02 (UTC)

@vorbote @nienhs ARE YOU SURE that removes gnome-vfs libgnomeui and libgnome wont cause any problem?There are someone else have configured a light-weight and simple os that could not have all the libraries it needs. Please check the old comments again.Thank you for your report.

toropisco commented on 2012-05-09 21:59 (UTC)

Ahh and even if using the official java 6 JRE/JDK, vuze channel browsing has not worked with Firefox/Xulrunner since the times of FF5 or FF6 if memory serves.

toropisco commented on 2012-05-09 21:54 (UTC)

I agree with nienhs. The GNOME libraries are, in fact, not needed as SWT is a GTK+2-only library framework---run ldd on a local copy of the SWT libraries and see for yourselves---, that is, it has no GNOME library dependencies. phoenixlzx, if you still want to keep them to be on the safe side, they should be moved to optdepends. Furthermore, I don't have a system copy of SWT, the ones supplied with Vuze have worked fine all the time. Requiring SWT as a depends is a red herring. The problem that zozi56 reported is caused by vuze using some Java classes that *do not* work well with OpenJDK 1.6 because 1.6 is *very* broken compared to the official Oracle binaries. I use OpenJDK 1.7 and I have never had vuze crash on me.

nienhs commented on 2012-05-09 21:25 (UTC)

Could it be that the GNOME dependencies are only required if you are actually running GNOME? I don't need them under Xfce. Maybe they should be moved to optdepends. Thanks for the package.

zozi56 commented on 2012-05-02 09:09 (UTC)

Thank you, it works now.

phoenixlzx commented on 2012-05-02 08:08 (UTC)

@zozi56 OK, I updated with swt as a dependency. I make a fresh install in my virtualbox, and I get the same error. Luckily I installed swt from official source,then it started successfully. Maybe there are some problem with its own swt. Good luck.

zozi56 commented on 2012-05-02 07:57 (UTC)

Firefox is installed, xulrunner wasn't (is is in conflict with Eclipse). Temporarily, I removed Eclipse and installed xulrunner, but the result was a crash again: the only difference seems to be that now the problematic frame in the error log is not in libc, but in libxul (in the SWT thread, same as before).

phoenixlzx commented on 2012-05-02 05:34 (UTC)

@zozi56 It seems not a program error because I run it without error... Check you have everything installed correctly? Or you can install firefox / xulrunner and try again.

zozi56 commented on 2012-05-01 17:55 (UTC)

When starting Vuze, it crashes immediately after the GUI is shown. Console output: Error log:

phoenixlzx commented on 2012-03-08 09:13 (UTC)

@dedopalomera,fixed,thanks for your report. It seems to have some errors with those who have configured a simple and light system.otherwise it just need a java-runtime.

commented on 2012-03-08 00:28 (UTC)

Please add libgnomeui, libgnome and gnome-vfs as dependencies. Otherwise I have problems like; Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-gnome-gtk-3802 in java.library.path no swt-gnome-gtk in java.library.path /home/daniel/.swt/lib/linux/x86_64/ cannot open shared object file: No such file or directory Can't load library: /home/daniel/.swt/lib/linux/x86_64/ ... Exit from Azureus complete No shutdown tasks to do Azureus TERMINATED.

haawda commented on 2012-01-07 11:41 (UTC)

No need to late the users change the PKGBUILD. We have the dummy dependency "java-runtime" just for that.

phoenixlzx commented on 2012-01-07 09:42 (UTC)

@blovemaple The preferred Java VM is openjdk,also oracle java vm works fine.You can edit the PKGBUILD if you want to use oracle jre. @vorbote Thank you for your kind observation,but someone else may complain why it depends on this or that...I will test vuze on a newly installed archlinux to decide which should be depend on.Thank you again for your advice.

blovemaple commented on 2012-01-07 07:01 (UTC)

Why does it depend on jre7-openjdk but not java-runtime(>=7)? I am using jre(oracle) from aur but not jre7-openjdk.

toropisco commented on 2012-01-06 12:33 (UTC)

Another observation. :-) Upstream binaries do not depend on SWT because they already have a copy embedded in them. If you were building a native copy, yeah, you'd need them as a dependency.

toropisco commented on 2012-01-05 13:51 (UTC)

A couple of observations: 1) Vuze works perfectly fine without the obsolete gnome libraries as it uses GTK+ only through the SWT widget kit. 2). Vuze works fine with jre7-openjdk or jdk7-openjdk. This should be the preferred java vm out of licensing considerations (and making openjdk better, it is the future for linux as per Oracle).

phoenixlzx commented on 2011-11-03 04:08 (UTC)

@Det fixed.thx

Det commented on 2011-11-02 08:20 (UTC)

Please fix the depends=() line: depends=('java-runtime' 'gnome-vfs' 'libgnome' 'libgnomeui')

mrbit commented on 2011-10-07 17:37 (UTC)

ok, Thx.

phoenixlzx commented on 2011-10-07 01:04 (UTC)

Java-runtime,all right.

mrbit commented on 2011-10-06 18:17 (UTC)

jre and openjdk6 are in conflict (java runtime). Want to remove openjdk6?

rafaelff commented on 2011-10-06 14:47 (UTC)

@phoenixlzx: yep, looks good now, Thanks!

phoenixlzx commented on 2011-10-06 14:34 (UTC)

@josephgbr:Sorry..when i download it from the official binary and it updated to 4.7.0...But now everything is ok:I changed to the sourceforge one and it is,ARCH i686/x86_64 was aparted. @archtux:do you have xulrunner installed?

rafaelff commented on 2011-10-02 15:33 (UTC)

@phoenixlzx: I'm trying to undestand why when I do a fresh install of vuze with the provided source ( I have Vuze in about option, instead of the 4.7.0 set in pkgver. This is annoying: vuze keeps trying to update and will always restart (to apply updates) when I want to exit/close it.

BertiBoeller commented on 2011-09-27 21:53 (UTC)

This is a package build for i686 system which circumvents the following error: java.lang.UnsatisfiedLinkError: Cannot load 64-bit SWT libraries on 32-bit JVM

kellerman commented on 2011-09-26 13:06 (UTC)

works with openjdk6 only if you modify /usr/bin/vuze with proper java path. doesnt work with sun java 7 at all and with openjdk6 by default too...

phoenixlzx commented on 2011-09-01 15:33 (UTC)

OK,changed to the sourceforge one.Thx for suggestion.

kevku commented on 2011-09-01 12:31 (UTC)

you need to use the system swt instead of the bundeled one to prevent it from crashing.

mrbit commented on 2011-08-25 14:19 (UTC)

ok, Thx.

phoenixlzx commented on 2011-08-25 10:30 (UTC)

Changed to Java-runtime,Thx.

mrbit commented on 2011-08-25 08:59 (UTC)

jre e openjdk6 vanno in conflitto (java-runtime). Vuoi rimuovere openjdk6? [s/N] ????

mrbit commented on 2011-08-25 08:59 (UTC)

jre e openjdk6 vanno in conflitto (java-runtime). Vuoi rimuovere openjdk6? [s/N] ????

dax commented on 2011-08-11 12:05 (UTC)

i'm having trouble with this one