firefox-2 plugins unable to be re-enabled

[Dennis Ta]

Binary package hint: firefox-2

Firefox 2 plugins are disabled after upgrading to hardy RC from latest gutsy. When I try to re-enable them, certain plugins cannot be re-enabled. The button is not greyed out, it simply does not respond to clicks.

The same is true after an aptitude reinstall.
(I didn't try purging and reinstalling firefox-2)

Some plugins can be re-enabled, I really can't tell if there is a pattern (i seem to be able to use all the plugins that i don't *need*)

It is important that users are able to fallback to firefox-2 since otherwise, firefox 3 is forced and compromises usability.

***apt-cache policy firefox-2 firefox***

firefox-2:
  Installed: 2.0.0.14+2nobinonly-0ubuntu1
  Candidate: 2.0.0.14+2nobinonly-0ubuntu1
  Version table:
 *** 2.0.0.14+2nobinonly-0ubuntu1 0
        500 http://us.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status
firefox:
  Installed: 3.0~b5+nobinonly-0ubuntu2
  Candidate: 3.0~b5+nobinonly-0ubuntu2
  Version table:
 *** 3.0~b5+nobinonly-0ubuntu2 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

[Savvas Radevic (medigeek)]

confirming, this should assigned to desktop bugs in my opinion

[Savvas Radevic (medigeek)]

Just to mention that during an upgrade from gutsy -> hardy, firefox-2 is kept and not removed, people will want to use it and will face problems with plugins

[Alexander Sack (asac)]

On Mon, Apr 21, 2008 at 08:27:38AM -0000, Dennis Ta wrote:
> Public bug reported:
>
> Binary package hint: firefox-2
>
> Firefox 2 plugins are disabled after upgrading to hardy RC from latest
> gutsy. When I try to re-enable them, certain plugins cannot be re-
> enabled. The button is not greyed out, it simply does not respond to
> clicks.

1st. backup your $HOME/.mozilla directory ... then

as a workaround you can stop firefox, remove any extensions.* file in
your profile

 e.g. rm $HOME/.mozilla/firefox/*/extensions.*

and start firefox again ...

further this most likely is a dupe of "bad installLocation" bug ...

 tag likely-dup
 status incomplete

 - Alexander

[Patricio Gonzalez (pagondel)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!