Arch Linux

Can't reproduce. Do you have any gtk/qt theme engine installed and running?

Also please try to get a backtrace:
https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces

I have [gtk-engines] working fine. I don't use anything related to [qt].

I recompiled [mlt] and [mlt-python-bindings] to include debugging symbols. Strangely [qt] is a dependency in the PKGBUILD file. I installed the compiled packages, removed [qt] package afterwards and got the segmentation fault (kinda makes sense why though). Backtrace is included in the attachments (Took me some time to figure out how to debug "python + c/c++". Maybe include in the wiki?).

I also removed the [qt] dependency from the PKGBUILD file and recompiled [mlt] in hope that no errors would occur in compilation. Finally [openshot] worked without [qt].

From a quick look it think instance in mlt++/MltTractor.cpp is NULL and it's not a packaging bug, but I could be wrong.

Please ask mlt upstream to take a look.

Doesn't seem to work w/o qt.

[karol@black ~]$ pacman -Q openshot
openshot 1.3.1-2
[karol@black ~]$ openshot

------------------------- ERROR 1 ------------------------------
Failed to import 'from openshot import main'
Error Message: cannot import name main
----------------------------------------------------------------
--------------------------------
OpenShot (version 1.3.1)
--------------------------------
Process no longer exists: 2524. Creating new pid lock file.
state saved
Segmentation fault

Works for me.

Also: When reopening bugs, please update first. Current version is openshot 1.4.0-1

> Also: When reopening bugs, please update first. Current version is openshot 1.4.0-1
I requested reopening two weeks ago :-)

Oh sorry, I only looked at the date above the comment, but it seems flyspray doesn't use the correct one there.

Anyway, does it work with the newest version?

The current version works w/o qt on one of my computers, but still segfaults on the other. I need to investigate further.

I give up.
Installing qt fixes it, removing qt is like flipping a switch - openshot segfaults.
The other computer doesn't seem to care for qt (as expected). They both are 32-bit and up to date.

I don't see instructions how to debug "python + c/c++" in the wiki, so Emanuel (untseac) must have kept this info to himself.
If anyone has any ideas how to debug it, I'm listening.

Or we can kill this bug report, as I'm not using openshot and even if I have to use it, installing qt is not a problem for me.

"I don't see instructions how to debug "python + c/c++" in the wiki, so Emanuel (untseac) must have kept this info to himself."
True, because I'm kinda lazy. Here's how you do it:

bash$ gdb /usr/bin/python2
(python2 because it doesn't work with 3)
(gdb) run /usr/bin/openshot
(it should segfault in your case)
(gdb) bt
(for the backtrace)

Hope it helps.
I'm going to add it myself the info to the wiki.

(gdb) run /usr/bin/openshot
Starting program: /usr/bin/python2 /usr/bin/openshot
[Thread debugging using libthread_db enabled]

------------------------- ERROR 1 ------------------------------
Failed to import 'from openshot import main'
Error Message: cannot import name main
----------------------------------------------------------------
--------------------------------
OpenShot (version 1.4.0)
--------------------------------
Process no longer exists: 1726. Creating new pid lock file.
[New Thread 0xb623cb70 (LWP 1784)]

Detecting formats, codecs, and filters...

Program received signal SIGSEGV, Segmentation fault.
0xb64cf157 in ?? () from /usr/lib/libmlt.so.4
(gdb) bt
#0 0xb64cf157 in ?? () from /usr/lib/libmlt.so.4
#1 0xb64cf4ff in mlt_properties_set () from /usr/lib/libmlt.so.4
#2 0xb64fb1a3 in Mlt::Properties::set(char const*, char const*) () from /usr/lib/libmlt++.so.3
#3 0xb651ae28 in ?? () from /usr/lib/python2.7/_mlt.so
#4 0xb651c361 in ?? () from /usr/lib/python2.7/_mlt.so
#5 0xb7ea0eef in PyCFunction_Call () from /usr/lib/libpython2.7.so.1.0
#6 0xb7efff4f in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#7 0xb7f01552 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
#8 0xb7effbf1 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#9 0xb7f01552 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
#10 0xb7effbf1 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#11 0xb7f0027b in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#12 0xb7f01552 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
#13 0xb7e8bc57 in function_call () from /usr/lib/libpython2.7.so.1.0
#14 0xb7e64ea4 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#15 0xb7e746fc in instancemethod_call () from /usr/lib/libpython2.7.so.1.0
#16 0xb7e64ea4 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#17 0xb7efa3eb in PyEval_CallObjectWithKeywords () from /usr/lib/libpython2.7.so.1.0
#18 0xb7e754b9 in PyInstance_New () from /usr/lib/libpython2.7.so.1.0
#19 0xb7e64ea4 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#20 0xb7efe35c in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#21 0xb7f0027b in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#22 0xb7f01552 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
#23 0xb7f016c3 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0
#24 0xb7f1b19c in run_mod () from /usr/lib/libpython2.7.so.1.0
#25 0xb7f1c0ed in PyRun_FileExFlags () from /usr/lib/libpython2.7.so.1.0
#26 0xb7f1cc99 in PyRun_SimpleFileExFlags () from /usr/lib/libpython2.7.so.1.0
#27 0xb7f1d95c in PyRun_AnyFileExFlags () from /usr/lib/libpython2.7.so.1.0
#28 0xb7f2e977 in Py_Main () from /usr/lib/libpython2.7.so.1.0
#29 0x080484e7 in main ()
(gdb)

Had same problem and installing these packages fixed it: pacman -S xdg-utils qt swig ladspa

maybe the dependencies of the mlt package need to be updated

Can it be reproduced now? I can not.

I tried 'pacman -Rdd qt', but openshot starts.

Also I tried 'pacman -Rdd xdg-utils swig ladspa', but it works too.