Thanks. My best guess on this right now is that the bug is an architecture-specific amd64 bug in seamonkey, with seamonkey providing a correct environment for plugins on i386 but not on amd64. Seamonkey isn't a Debian package, so I can't really reassign this bug, or (without more information from you, like full seamonkey version details etc) even reproduce it without a lot of guesswork.
I'm therefore going to: - leave this bug open for now until I'm not just *guessing*, but actually sure about what the underlying problem is. - try to find someone who actually knows a lot about how mozilla plugins are supposed to work to discuss this with. You might want to bring the issue up with the seamonkey people; they may be in a better position to deal with it appropriately. Thanks again for the bug report, -- Barak A. Pearlmutter Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
