Comment 73 for bug 428884

Fermulator, I think on a high level, everybody would agree. But I think the problem is that nobody is "responsible" for fixing this issue.

GNOME guys decided to clean up their API. We can't blame them for doing so. Of course, "users" of their APIs (i.e. VLC media player here) were not notified. But then again, the GNOME guys have no way to know who is using this API anyway.

On the VLC side, we did not know about the problem until it was too late. And I suspect the architectural changes that a proper fix won't be feasible before the next VLC release series. I mean VLC 1.1, and that probably will go to Ubuntu 10.10 (Ubuntu 10.04 if we are really fast and lucky).

On the Ubuntu side, VLC is only in universe (or was it even multiverse). That does mean there is no support promise. And of course, the Ubuntu GNOME guys have no incentives to take a patch that makes them drift from their upstream, only to support non-GNOME non-Ubuntu-main components.

Ultimately, you get what you pay for, and you probably paid nothing.

Complaining about the problem does not advance the resolution. What we need is someone taking action. Then (s)he can:
 - craft a proper patch for VLC 1.1,
 - then try to figure out how to backport the fix to VLC 1.0,
 - then fix it in VLC 1.0.