Comment 8 for bug 1619933

> First you don't test with the command line you provided...
As already mentioned there are no build instructions for mediainfo so I can't test properly (with git bisect)

> so it is not possible to know if your issue is related to Matroska; you also don't provide the content of $F; when the output is empty, this usually means that the file is not accessible by MediaInfo, not related to Matroska.
As already shown with the ffprobe example, every other application thinks the file is a valid matroska.

> Second this issue is not related to this ticket (again: before or after this ticket is handled, it changes nothing)
As already stated the mediainfo change log leads me to believe otherwise; upstream might fix it.

>, so it is complicated to manage it. If you want your issue, not related to this ticket, to be resolved, please open a new ticket dedicated to this issue on Launchpad or on the upstream tracker https://github.com/MediaArea/MediaInfoLib/issues because I think that it is not related to how it is packaged in Ubuntu (if you want to be sure that the issue is from upstream, you can test https://mediaarea.net/MediaInfo/Download/Ubuntu packages)
That link dose not have builds for the architecture I'm using.

>No quotes around $F
That is not the issue though it brings up 2 mediainfo shortcomings: the exit code is 1 if it's given a bad path or a file it can't decode when it should be using more than one exit code. And all non-zero exits should really have a text error message on stderr.

> Here, you pollute a ticket with something not related to it and it prevents both issues (the reason of the ticket + your issue) to be resolved.
Sorry I thought I was adding reasons for Ubutnu to sync with upstream. I'll stop polluting your ticket.