Firefox 8.0.1 FG won't launch JDownloader

[jmorlan]

I normally use the Flashgot extension to enable JDownloader, but after upgrading to Firefox 8.0.1 it no longer worked as expected. I tried enabling the Flashgot interface within the current JDownloader but Firefox refused saying that this version of Flashgot is incompatible with Firefox 8.0.1.

However I was able to update Flashgot within Firefox to a version (1.3.4) which is apparently compatible, but it no longer launches JDownloader when I right click links and download via Flashgot. Instead nothing happens. I have to open JDownloader manually. I tried to see if the latest release candidate 1.3.5rc1 would help, but it did not.

So all works fine after JDownloader is running. The problem is that I have to do it manually. It no longer launches automatically as before. I asked in the JDownloader forum and they said it's a Flashgot issue.

Please advise.

[therube]

What version of JDownloader?


See if anything mentioned in these helps:

[RESOLVED] Integration with JDownloader on Linux

JDownloader Not Automatically Launching in Certain Cases

[jmorlan]

JDownloader Version is 0.9.581

The second link in you post describes my symptoms exactly, except that I'm on Win32 SP1.

http://forums.informaction.com/viewtopic.php?f=6&t=6084

As described, JDownloader will launch if "FlashGot All" is selected, but it will not launch if "FlashGot Link" is selected. If JDownloader is already running, then FlashGot Link works as expected. No resolution to the issue was found in the previous thread. Here are some logs:

FlashGot Link

Code: Select all

Preprocessing done in ms529
Starting dispatch
Dispatch done in ms29
Total processing time: ms558
JDownloader response:
200

FlashGot All

Code: Select all

Sorting again 276 links
Preprocessing done in ms535
Starting dispatch
Dispatch done in ms2088
Total processing time: ms2623
JDownloader response:
0

Running C:\Program Files\JDownloader\JDownloader.exe  -- async
Native execution time 42

JDownloader seems to launch after a response of 0 which occurs when FlashGot All is selcted, but not after a response of 200 which happens in the first instance when FlashGot Link is selected.

[Timur]

Windows 7 SP1 64bit, Firefox 8.0.1, FlashGot 1.3.4, JD 0.9.581 - all fine.

[jmorlan]

Windows 7 SP1 64bit, Firefox 8.0.1, FlashGot 1.3.4, JD 0.9.581 - all fine.

Thank you, but how does that help me with my issue?

[Giorgio Maone]

JDownloader seems to launch after a response of 0 which occurs when FlashGot All is selcted, but not after a response of 200 which happens in the first instance when FlashGot Link is selected.

That's correct. If the response from JDownloader's web interface ( http://127.0.0.1:9666/flashgot ) is 200 (HTTP OK), FlashGot assumes JDownloader is already up and running, therefore it doesn't launch it.

Your log suggests that when you tried with a single link JDownloader was already running, while when you tried with 276 links JDownloader was off (response 0).

If JDownloader was actually not running, the only plausible explanation is that something else is responding at http://127.0.0.1:9666/flashgot on your machine (which doesn't sound very likely, though).

[jmorlan]

If JDownloader was actually not running, the only plausible explanation is that something else is responding at http://127.0.0.1:9666/flashgot on your machine (which doesn't sound very likely, though).

I can assure you that JDownloader was not actually running. However, FG evidently thought it was and that is a perfect explanation of why FG would not launch JD. To make the point clearer, the two logs were run in succession. The first attempt, grabbing a single link failed. The second attempt, grabbing multiple links worked. If in fact JD was already running the first time, then it would not have been able to be launched the second time. I believe this proves that JD was not running without my knowledge.

Here is what I did to fix the issue.

1. Completely removed both FG and JD.
2. Installed the latest nightly build of JD.
3. Went into about:config in Firefox and set all of the legacy "user set" FG entries which remained after the uninstall to "reset"
4. Restarted Firefox to ensure all the FG config entries were gone.
5. Installed the latest release of FG.
6. Allowed FG to auto-detect JD.

Now all works as expected. Perhaps this will help somebody as it appears this issue has come up before, although evidently it is rare. Why this fixed the problem, and why FG may have thought JD was already running, I cannot say. But I suspect it was a bad FG "user set" configuration setting which remained after uninstalling and reinstalling FG.