Re: NOW IN CURRENT: shotcut

On Mon, Jun 01, 2020 at 03:20:34PM +0200, prx wrote:
> Hi,
> after trying the new shotcut port, I wonder if there is any tip to read
> video files with it. Do you convert to any format befort importing into
> shotcut?
>
> Find attached messages printed by shotcut recorded with script(1).
>
> It always crash when I import a file on my machine. Below a few lines
> that may be relevant.
>
> $ sysctl -n kern.version
> OpenBSD 6.7-current (GENERIC.MP) #234: Sun May 31 23:53:53 MDT 2020
> deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> $ gdb -q shotcut shotcut.core
> [...]
> #0 0x000001df2d3928c1 in mlt_consumer_stop () from
> /usr/local/lib/libmlt.so.3.2
>
> bt full
> #0 0x000001df2d3928c1 in mlt_consumer_stop () from /usr/local/lib/libmlt.so.3.2
> No symbol table info available.

You will need to "pkg_add debug-mlt debug-shotcut gdb" and run egdb (not
gdb) to make this backtrace more useful.

I saw similar symptoms with a crash in mlt_consumer_stop() (espie has
the details). The crash was an obvious null dereference whenever I tried
to open a movie file in any format, but what's unclear is why it happens
on some systems and not on others. Working around the null deref didn't
make shotcut work, so we are still as wise as before.

I suspected it was due to a missing dbus, but unfortunately running
shotcut under a dbus didn't help in my case.

I looked at the ktrace as well but that didn't really show anything
obviously suspicious either.