However i do agree that an activation through the amule gui means that both clients are on the same machine, and checking that both work would save such troubles.
A very simple sanity check could be to warn the user that amuleweb will not start unless you have `external connections' set and also make sure that amuleweb process won't start either during the startup-sequence of amule, especially if it stays there waiting for a password, which you don't see when starting it from gnome, and which does not affect the proper running of amuleweb, even if you give it there through console.)
The way it is, you expect it to run, you see it running (ps -u user|grep amule), and you start checking firewall rules to see what's wrong and it doesn't connect. It's kind of a trap for the unsuspecting user, which if it comes after a less-than-smooth-installation (*), becomes upsetting.
(*) Regarding installation:
before I removed that:
wxGTK-2.6.3-2.6.3.2.2.fc4
and put these:
wx-base-unicode-2.6.3-1.i586.rpm
wx-gtk2-unicode-2.6.3-1.i586.rpm
the rpm's of amule et friends were properly installed, but when it was about to start, I was given a message that `the library' (question `which one?') was not compatible, although the program required 2.6 compatible with 2.4 and I had 2.6 compatible with 2.4 and 2.2 by its own admission (and installer's infuriation.)
Then, the instructions in the forum were mentioning a download and yum install of working wx files, which was not possible at first, because the rpms were not signed. Eventually (after some ranting) it worked with rpm -ivh (posted the `solution' there too).
Ok, I got there, because I really like your program and I had the time and I'm not entirely useless with Linux, but were that to be the first application a windows-to-linux-converted would install, he'd jump back into Gates arms shouting: "OHMG" half the way there. (Especially if there is no wiki entry for fedora that points to wx files and no rpm install howto, leaving it hanging in the air that you might have to compile the whole thing, in which case you might get all sort of errors, which although they have to do with wx, for the end-user they are attributed to amule, rendering it a `bad program').
How about contacting the packager of wxGTK-2.6.3-2.6.3.2.2.fc4 and make sure that what he bottles works with amule? I mean, how many more applications on a desktop linux using wxGTK they get installed on their FC, that they put amule aside as a second priority? If amule is not one of the top 5 check items on the list of a converted to linux, what is?
Of course, they do offer the previous version (I got it yum installed from the freshrpms repository I think), but they do not offer the amuleweb and friends (I installed the whole amule 2.1.3 et friends, because I could not find 2.1.2 amuleweb to add to my existing amule. BTW, did you realise that the previous versions of amule point to the rpm of the latest one?)
The way things are in Fedora (and here), they really spoil the fun with your program and this unfair, because it is a good program. If I were you, I'd go there kick the r's (well, that's considered suggesting violence, isn't it? :] ) and tidy up my installation instructions and the installation packages.
Still, very good program, keep up the good work.
