D-Link router javascript login broken

[Lev]

Binary package hint: firefox-3.0

My router, a D-Link DIR-655, no longer will allow me access to its admin panel after the latest Firefox 3 patch updates that I installed today.

I can confirm that it was working prior to installing these patches, since I accessed it just earlier this morning. I tried to access the admin panel again later on this evening, after applying all software updates through Synaptic, and it no longer works.

This renders the entire admin panel for the router unusable since an error is given while attempting to login.

The error given is a D-Link error reading:

"The network connection seems to be down. Press 'Ok' to try again."

I realize this is a D-Link error that has been coded for a time out, as I've examined their HTML source, however, this is not a coding error.

It worked on Firefox 3 prior to this recent patch, and works on my girlfriend's Firefox 2 machine, which is also running Ubuntu.

Because of the numerous issues I've been encountering with Firefox 3 lately, I recently installed Opera, and can confirm that the login utility works flawlessly there as well.

Something in the latest Firefox patch (on the Ubuntu repositories at least) is causing certain Javascripts to operate incorrectly.

ProblemType: Bug
Architecture: i386
Date: Mon Aug 4 21:07:51 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
Package: firefox-3.0 3.0.1+build1+nobinonly-0ubuntu0.8.04.3
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-19-generic i686

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[Lev (lev-taintedthoughts)]

First of all, thank you for responding to the issue - I appreciate it! :)

As I should have done long ago, but failed to after forgetting about the bug report, was to inform you that this issue may be closed.

It turns out that it was most likely a result of the use of "FireBug" with Firefox. After performing numerous tests with all extensions enabled and then going one by one, I have come to believe that this was caused from having FireBug enabled.

[Victor Vargas (kamus)]

According to your last message, I will close this report because was solved with a config change, if you encounter that this issue is still occurring please reopen it or change status to new again, Thanks in advance.