>Hmmm, it could be related to the switch to gcc 4.1. Does it produce >any errors at all?
No there is no output of the browser. The extension may check the library internals by its own. So you are redirected to the error page mentioned above. I checked it up with the beta version (0.83) but the extension fails too. Should I report this to the upstream developer (though I do not use a vanilla browser)?
