For as long as I can remember, I've been able to install plugins without restarting the browser; just move the .so into the plugins directory and *poof* it works. That no longer works. I haven't looked into this any deeper at all, yet. I will soon.

The plugin also does not work after looking at about:plugins?

Hmm... it does start working after viewing about:plugins. I don't remember that ever being required before. I suppose it's *possible* I always did it before without even realizing it was required, but I don't think so.

about:plugins scans for new plugins, but yeah normally it should work without this. Are all plugins affected by this? Do you possibly have a regression range?

Okay, unless I messed up my testing... 2005-12-10 trunk: fails 2006-04-30 trunk: fails 2006-05-24 trunk: fails 2006-06-15 trunk: fails 2006-06-14 branch: works ...except I don't use branch, so where would I have seen this work in the past? I'm confused. :(

It's possibly dependant on how the page uses the plugin. If the page simply attempts to instantiate a plugin using an object tag for an unknown mimetype then the plugins will be rescanned to see if a new one has been installed. If however the page uses JS to query navigator.plugins to look for the plugin then no re-scan is performed.