Oleg, As far as I know, this fix can't be backported. I don't think it's possible to properly support GstMiniObject because it wasn't designed with introspection in mind (remember, the GStreamer 0.10 API is almost 7 years old now). I don't believe it's possible to fix this without breaking the 0.10 API. And this is just one of many issues that make it impossible to fully use GStreamer 0.10 from PyGI.
However, I imagine that GStreamer 1.0 will be made available through at least precise-backports. As it's parallel installable with GStreamer 0.10, it's quite safe to backport as it wont effect any existing 0.10 using applications. I think a case could be made for even backporting GStreamer 1.0 packages into Universe, but I don't know what the policy is there. Anyway, I agree it's a bummer that Python + Gtk3 + GStreamer isn't usable in Precise. But g-i and PyGI are big transitions, and these things just take time. If you want to start porting your app, there are GStreamer 1.0 packages in Quantal and there are packages for Precise in the GStreamer dev PPA (also in the Novacut stable PPA now): https://wiki.ubuntu.com/Novacut/GStreamer1.0 Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873712 Title: Lack of GstMiniObject means Gst.Message is broken, can't get EOS signal To manage notifications about this bug go to: https://bugs.launchpad.net/novacut/+bug/873712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
