Comment 109 for bug 538796

(In reply to comment #40)
> By "older" moonlights, do you know which version no longer has this symbol? It
> seems that we are shipping versions 2.2 and 2.3 in our supported Ubuntu
> releases.

both 2.2 and 2.3 have the symbol. It's been removed (well, c++ namespaced) in master which is where the moonlight 4 stuff will come from. We have a potential fix in git already and should know soon if it actually fixes the problem. I'll update this bug again with revisions when we have confirmation so you can take a look and roll the changes into your packages.

We were going to push a new moonlight 2.x release in the coming days anyway, so this isn't going to cause us too much additional headache.

> I'm quite happy to provide an update for our supported releases which renames
> that symbol in our moonlight package (and we can update to the latest version
> in our development release). Would that be an alternative to blacklisting
> either plugin (assuming other distro's fix their packages too)?

That sound fine to me in the very short term, but we're going to be going through our exported symbols with a fine toothed comb and will likely have something a bit more comprehensive soon.

For people who download via go-mono.com, they will get notified of updates via firefox's extension update mechanism. Those updates should still be visible even if a plugin is blocked, I would assume.

As far as the distro packages are concerned there's no real notification outside of distribution channels that there's an update.

What exactly is the UX for a blocked plugin anyway?