[Bug 192138] Re: dom-inspector doesn't work with ff beta3

2008-03-31 Thread Alexander Jones
*** This bug is a duplicate of bug 201984 *** https://bugs.launchpad.net/bugs/201984 ** This bug has been marked a duplicate of bug 201984 xulrunner-1.9-dom-inspector does not work in Firefox 3.0b4 -- dom-inspector doesn't work with ff beta3 https://bugs.launchpad.net/bugs/192138 You

[Bug 192138] Re: dom-inspector doesn't work with ff beta3

2008-02-27 Thread Alexander Sack
please stop firefox and touch /usr/lib/xulrunner-1.9b3/.autoreg if that doesn't help, please do the same for /usr/lib/firefox-3.0b3/.autoreg if that still doesn't help: 1. backup your $HOME/.mozilla/ directory (IMPORTANT) 2. rm $HOME/.mozilla/firefox/*/extensions.* (so everything extension

[Bug 192138] Re: dom-inspector doesn't work with ff beta3

2008-02-27 Thread Bogdan Butnaru
I'm not sure what happened, but the DOM inspector was working today when I checked. I didn't notice when it became active again. -- dom-inspector doesn't work with ff beta3 https://bugs.launchpad.net/bugs/192138 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 192138] Re: dom-inspector doesn't work with ff beta3

2008-02-16 Thread Wowbagger
I see this as well. I then tried the following: 1) Removed the DOM inspector from within Synaptic. 2) edited extensions.rdf and removed the entry for DOM inspectors 3) Started FF, confirmed that DOM inspector was no longer listed. 4) Shut down FF 5) Installed DOM inspector via Synaptic 6) Started

[Bug 192138] Re: dom-inspector doesn't work with ff beta3

2008-02-15 Thread Fabien Tassin
** Changed in: xulrunner-1.9 (Ubuntu) Importance: Undecided = Medium Status: New = Confirmed -- dom-inspector doesn't work with ff beta3 https://bugs.launchpad.net/bugs/192138 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 192138] Re: dom-inspector doesn't work with ff beta3

2008-02-15 Thread Bogdan Butnaru
I have looked around a bit, and noticed two fun facts: 1) In my default profile, which I have been using for a long time, the dom-inspector is marked as not working (which I reported above), and the uninstall button is disabled, which is weird. 2) I created a few new profiles, and the dom