Comment 9 for bug 327872

Geekkit <email address hidden> writes:

> I'm confused as to the status of this bug report. Here are the steps
> AFAIU them:
>
> 1) When I filed this bug with details of what the problem was and how to
> circumvent it, it was originally filed against Nautilus.

Which is clearly wrong, as nautilus does not decode any media files.

> 2) Then the bug got reassigned to gstreamer where its state went from
> "new" to "confirmed"

which is more correct, because nautilus is using the gstreamer framework
for media files.

> 3) Then (still in gstreamer) "new" to "unknown"
>
> 4) Then (still in gstreamer) "unknown" to "new"

upstream tasks are generally tracked upstream.

> 5) Suggestion of FFMPEG supporting these files

gstreamer does TTBOMK have no AVCHD decoder, but uses ffmpeg for this.

> 6) ffmpeg changed from "new" to "fix released"
>
> Does this mean Ubuntu developers are now considering this bug now fixed?

I with my ffmpeg package maintainer in debian&ubuntu hat on, changed the
ffmpeg upstream bug-task's status, with the rationale given in comment
#6. As the ffmpeg developers do not follow nor even notice bugs
launchpad, and additionally have clear instructions for reporting such
bugs (which are clearly not followed here), I don't see what we as
ubuntu developers can do about this bug other than asking the submitters
to follow the ffmpeg upstream's bug submission guidelines
(i.e. submitting a proper example file).

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4