Registered: Feb 2013
Solved: aMule 2.3.1, Ubuntu 12.04, Firefox 18 links not working
Wake up, old Thread! It's time to wake up and smell the changes!
I started searching for this info recently when installing Ubuntu 12.04 LTS and aMule 2.3.1. FireFox is now at Version 18.xx, and a lot has changed. The last time I got aMule working was on a Fedora 10 build, aMule 2.2.6, and FireFox 2.x or 3.x (I don't remember because I've upgraded since then). The information commonly found on the web and info early in this thread was enough to get it working then. (Back then, *.amule.org was a working web site with a nice wiki, but it's been down for some time as of this writing.) Also, there is a reference to the FireMule addon. I don't remember if I used that back then, but it certainly is no longer available for Firefox 18.
Since I tend to just let stuff run if it's working, my laptop just suddenly woke up with a whole new Linux environment several years newer, and I had to remember and mostly relearn almost everything about getting my favorite software working again.
Hopefully what I've discovered today helps someone else and puts all the different clues and pieces together in one place. My environment is Ubuntu 12.04 LTS, aMule 2.3.1, and FireFox 18.x. I don't know what changed or when since my last clean Linux install (Fedora 10, then upgraded to 14), so it probably applies to other Linux versions, older FireFox versions past 3.x, and probably aMule going back to 2.2.6. Or, maybe it's just a bug specific to Ubuntu 12.04 and/or the aMule installation package that came with it.
With my versions of Ubuntu 12.04 LTS, aMule 2.3.1 and FireFox 18.x, we are STILL a long way from "plug and play" to get aMule working. (One would think after running apt-get install, everything would "just work", but alas, no.) In addition to the customization of FireFox, one must also learn about xdg, and the Ubuntu desktop environment, which is usually "automagically" set up when other software is installed.
By the way, I changed my desktop from Unity to XFCE because I came from Fedora 10 / 14, and didn't want to have to figure out a new interface on top of everything else. Hopefully the info below applies to Unity as well but I haven't tested it. Maybe this thread will come back alive and others will post their software versions, what desktop, etc., and let us know their experiences. I'd like to know if similar troubles were seen with other Linux versions, and how far back it goes.
I don't know how many of the steps I took are necessary on a "modern" (2012) installation, because I started with the FireFox 3.x instructions first:
FireFox 3.5 info, which can still be done in Version 18:
Go into about:config as mentioned earlier, and add the following values (including a couple extras I found in different places):
The first three settings are the standard ones most commonly given to get FireFox 3.x (some say 3.5 and later) to work:
Open about:config in a browser window. Click on the "I'll be careful, I promise" button.
Right click somewhere in the list, and select New, then select the type listed below.
Copy and paste the preference name, then the value. Try everything exactly as is first, then move on to the Desktop info below this section before returning to troubleshoot Firefox.
Preference Name Type Value
[Main 3 Preferences, widely publicized for Firefox 3.5]
network.protocol-handler.app.ed2k String /usr/bin/ed2k
(Some say just use "ed2k" without the path but full path works on Ubuntu 12.04 LTS and aMule from repositories)
network.protocol-handler.external.ed2k Boolean True
network.protocol-handler.expose.ed2k Boolean False
(FireFox 3 or 3.5 and higher. Some say it's needed to get FireFox to prompt for ed2k program)
[Preferences I found elsewhere, when the above wasn't enough to get working. Optional until you try the Desktop stuff below.]
network.protocol-handler.warn-external.ed2k Boolean True
(Some say it's needed to get a prompt for what program to use.)
extensions.torrentserver-handler.protocols String ed2k
(Some say newer versions need this to handle ed2k links. I don't remember where I found this or if it will break BitTorrent.)
For my installation, though, this was not enough, and I kept getting messages that FireFox didn't know how to handle ed2k links. I gave up and installed Google Chrome (Chromium) and tried to get that to work. (It didn't out of the box.) But it led me to...
Ubuntu Desktop Environment:
I stumbled upon information about xdg-open, while trying to get Chromium to work with ed2k links, though I haven't fully researched all of the xdg stuff. Chrome relies on the Operating System (OS) to decide how to open links (which is probably also true of other browsers as well as your File Manager, etc.), which led me to xdg-open, creating .desktop files (which creates a link in your desktop, at least for XFCE and probably Gnome, and provides the path and commands to open the URI). Again, I don't know when FireFox started needing this, but apparently it does now.
We first have to create a file with our favorite editor (I still use vi but most people use gedit so it depends on my mood):
sudo gedit /usr/share/applications/ed2k.desktop
Copy and paste the following text and save. (If you forget the "sudo", you won't be able to save.)
----------------- Copy Below --------------------
Comment=aMule ED2K Link Parser
------------------ Copy Above --------------------
Then, enter the following commands (in my case, I didn't need sudo, they worked from the user account):
gconftool-2 -s /desktop/gnome/url-handlers/ed2k/command '/usr/bin/ed2k %s' --type String
gconftool-2 -s /desktop/gnome/url-handlers/ed2k/enabled --type Boolean true
Then, fire up aMule or your aMule daemon plus aMule GUI, and test:
In my case, this got FireFox to work exactly how I like with single and multiple links. Chrome, however, handles single links fine, but ignores multiple links. Whatever, that's another problem, and I'm using Firefox for my aMule needs anyway.
Copy an ed2k link (ed2k://|file...)
From a terminal, type:
xdg-open "<paste your link here>" (You MUST include quotes or the shell will misinterpret "/" and "|")
If this results in a new file being queued in your aMule application, then your desktop environment plus ed2k program are working.
If not, then type:
ed2k "<paste link here>" (again, in quotes)
If it works now, at least your ed2k program and aMule are working, and you still need to get xdg-open working before you can hope for Firefox or Chrome to work.
As usual with something that takes me a couple of days to get working, some of the steps I took above may no longer be needed. If you know this, then feel free to post a reply with your findings. Or, on the next build I'll only do the desktop stuff and not the FireFox customizations, and I'll try to remember to post my findings as a reply.
Hopefully this will help the next person who Googles Amule and Firefox.