firebug says "debugger not activated" even when script panel is activated...

[titiyoyo]

Hi,

when i click on the script panel i get the message 'debugger not
activated' even though it's activated...
i tried to reboot, reinstall firebug, then reinstall firefox and
firebug, delete all other modules and disable all plugins, but nothing
worked...

any idea for this ?

i'm using firebug 1.7 in firefox 4

[John J Barton]

My suggestion is a new Firefox profile, reinstall almost never solves
any problem because Firefox retains the configuration information when
you uninstall.

See also
http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!

jjb

[titiyoyo]

it worked !
thanks !

On 29 mar, 16:33, John J Barton <johnjbar...@johnjbarton.com> wrote:
> My suggestion is a new Firefox profile, reinstall almost never solves
> any problem because Firefox retains the configuration information when
> you uninstall.
>

> See alsohttp://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!

[bugrain]

I'm getting this issue too, as of today.

Haven't installed any new add-ons since it was working as far as I remember - don't use Firebug daily on this PC so can't be 100% sure.

Have tried a new Firefox profile with no other add-ons too.

If script panel is disabled, I get the normal 'Script Panel is disabled' message and a link to enable it. As soon as I enable it I get the "Debugger not activated" message in the script panel.

Firefox 4.0
Firebug 1.7.0

[John J Barton]

Try Firebug Icon Menu > Options > reset all
Does it help?

Try Firebug 1.8a1 on FF4: http://getfirebug.com/releases/firebug/1.8
does that help?

(1.8a1 has fixes that will be in 1.7.1).

jjb

[bugrain]

Neither of those suggestions help.

FYI - no "options" on menu activated by right click on Firebug icon if you are referring to the icon in the Add-on bar (Windows XP here - does that make a difference?). But, did the reset via Tools > Firebug > etc. which I'm sure is what you were asking.

Tried reset before and after installing 1.8a1 too.

[bugrain]

Sorry, forget the no options menu issue - just noticed the Firebug icon in top left of Firebug window pane - never used it before :)

[John J Barton]

Ok please install 1.7.0 on FF4 using a new Firefox profile.

http://getfirebug.com/wiki/index.php/FAQ

If you still have the problem please open a bug report.

http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!

jjb

[bugrain]

Hi John

Tried the re-install (again, had tried it before). This time it worked! Maybe first time I did something wrong, it was late at night!

Anyway, armed with a working version I decided to try some digging - very crude as I don;t have the right tools/knowledge for this environment but, it turns out, quite fruitful.

I've narrowed down my problem to the following line in prefs.js:

   user_pref("extensions.firebug.DBG_FBS_FUNCTION", true);

With this, I get the problem. Delete it and script panel works again.

Hope this helps with a fix for others.

[John J Barton]

Perhaps we have a bug in a tracing call that throws an exception. But
without a test case its hard to say.
jjb

[Honza (Jan Odvarko)]

On Apr 8, 5:28 am, John J Barton <johnjbar...@johnjbarton.com> wrote:
> Perhaps we have a bug in a tracing call that throws an exception.

Yes, LogFunctionStepper constructor calls this.intitialize(), which is
not defined.
Removed at R9974

Do we need that function?

(should be ported into 1.7)

Honza

[John J Barton]

On Apr 8, 12:19 am, "Honza (Jan Odvarko)" <odva...@gmail.com> wrote:
> On Apr 8, 5:28 am, John J Barton <johnjbar...@johnjbarton.com> wrote:> Perhaps we have a bug in a tracing call that throws an exception.
>
> Yes, LogFunctionStepper constructor calls this.intitialize(), which is
> not defined.
> Removed at R9974
>
> Do we need that function?

No, I'll write it over again. It was an attempt to trace function
calls using the new stepper objects, but it did not work well enough.
I did not realize the tracing option still used it.

jjb

[Aiur]

Disabling greasemonkey fixed this issue for me

[Abcmeister]

I had this problem twice, and it worked without reinstalling firefox oder plugins.

I don't know what of these steps did it, but after i played around wild it worked.

* Deactivate Firebug
* Activate Firebug
* Delete Firebug Preferences
* Deactivate Scripts
* Activate Scripts
* Edit Css in Live Mode
* ! Wild clicking in the Dom-Model
* ! Open Firebug in extra Window
* ! Reload Page with Strg+Shift+R
* ! Restart Firefox

I think it must be one of the steps i marked with a !.

Maybe someone will test it and have success.

[Tsyren Ochirov]

* ! Restart Firefox works for me

[kentr]

Quick and easy fix that worked for me:

* Go to configuration (with about:config in location bar. details
here: http://kb.mozillazine.org/About:config).
* Search for "FINDDEBUGGER".
* Double-click the entry to change "value" to "true"
* Close the window / tab and reload your page. Debugger should
appear.

[Jan Honza Odvarko]

On Apr 30, 9:18 pm, kentr <k...@kentrichards.net> wrote:
> Quick and easy fix that worked for me:
>
> * Go to configuration (with about:config in location bar. details
> here:http://kb.mozillazine.org/About:config).
> * Search for "FINDDEBUGGER".
> * Double-click the entry to change "value" to "true"
> * Close the window / tab and reload your page.  Debugger should
> appear.

This is interesting. Do you know why it helps?

Honza

[Sebastian Zartner]

There are two issues I know of that can cause this message to appear:

• Issue 5646
• Issue 5118

Sebastian

On Wednesday, December 19, 2012 4:08:01 PM UTC+1, Arthur Shpakov wrote:

Hi,
The same problem happened to me recently. I've cleared cache and cookies and it worked fine. Not sure, probably clearing cache only will be enough.
In Firefox choose Tools -> Clear Recent Hisotry -> Cache(checkbox)
Reload the page or restart Firefox and it should work fine.

[Hars Saraf]

try this

firebug options > enable all panels
it should do the job.

[Sebastian Zartner]

That shouldn't do any difference since the Script panel is already activated in that case, as the subject already says. See the test case for issue 5118.
If you had a case, in which that option helped fixing the problem, then please try to find a test case with steps to reproduce it.

Sebastian

[Bruce Holm]

I tried various options and nothing worked until I did the following:

Open the Firebug window
Click on the Firebug icon in the upper-left corner of the window and go to the menu item:
   Options > Reset All Firebug Options
Activate Firebug

Then it worked.

[Prabakaran V]

Click firebug menu - > Enable All panels.

Cheers