From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4 Description of problem: If I install the Venkman JS Debugger in Firefox as an extension and then attemp to start it from the Tools menu I get the following error: An exception occurred while initializing, please file a bug. BadMojo 4: JS Debugger Service is not installed. @ <chrome://venkman/content/venkman-debugger.js> line 126 (initDebugger) The JS Debugger does then start but not in the state it is meant to start in. According to this: http://extensionroom.mozdev.org/more-info/venkman comments 17, 18, and 19 indicate that this is because the FC3 builds of Firefox are built with the option --disable-jsd. Version-Release number of selected component (if applicable): firefox-1.0.4-1.3.1 How reproducible: Always Steps to Reproduce: 1. Install Venkman as an extension. 2. Start JS Debugger from Tools menu. Actual Results: Error Expected Results: No error Additional info:
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Distribution against which this bug was reported is no longer supported; could you please reproduce this with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. Thanks in advance.
We haven't got any reply to the last question about reproducability of the bug with Fedora Core 6, Fedora 7, or Fedora devel. Mass closing this bug, so if you have new information that would help us fix this bug, please reopen it with the additional information.