Description of problem:
plugins for firefox are installed.
If the system is restarted with firefox running and a couple of tab are active (this may not be relevant). After logining in and firefox (re) starts, doing "about:plugins" produces a message that plugins are not loaded.
If you quit that firefox and then start it up again, this doing "about:plugins" shows the list of loaded plugins.
Apparently, mozilla-plugin-config is not run if firefox is "restored" rather than just started.
As a guess I'd say that the way that firefox gets restored by the session manager loses the mozilla directory.
Perhaps this is because what the session manager registers to restart firefox isn't the same thing as is used to start firefox from the command line or menu
This is an annoying "fit and finish" desktop bug.
Because firefox is an application that will very commonly be left on the entire desktop session and hence be saved on logout.
So when it starts at the beginning of the next session but doesn't correctly display content that it displayed without error the previous session (say youtube) one is left puzzled, and feeling that the desktop is unreliable.
However remembering to quit firefox before logging just so that it doesn't start automatically but without all it features is equally annoying when one realises what the bug is.
Can the priority of this bug be increased? Hopefully it's not terribly hard to fix?
I'm constantly running into this firefox issue in F11, which compounds already poor session management capabilities in GNOME. This is basic functionality that should just work.
I noticed that I have one locally installed plugin in ~/.mozilla/plugins and this is the only one that shows up in about:plugins after a session restore.
The patch has to be approved by upstream (mozilla.org). It may be included in some next 3.5 update.
*** This bug has been marked as a duplicate of bug 437596 ***