Comment 11 for bug 1067328

Not sure what is meant by 'file isn't added to Openshot ' , but...

1. is it possible to verify that your test machine has the same characteristics as mine, in terms of 64/32 bit, Python library versions, etc...

2. is there a way to get this test case tried out on a number of different machines with different characteristics ??

CPU I am using is:

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Celeron(R) CPU 900 @ 2.20GHz
stepping : 10
cpu MHz : 2194.540
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx lm constant_tsc up arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dtherm
bogomips : 4389.08
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

3. I have been experimenting with Python debug / analysis tools ( I am a complete beginner @ Python); by using the command line

 python -m trace --trace /usr/bin/openshot >python_trc.log 2>&1

I get a trace of every statement executed upto the point where I kill the process (for some reason, if you pass the name of the input file on the command line, Openshot does not start..).

Last 1,000 lines of a 600MByte log file are attached; it shows that the code is in a repetitive loop, dependent on things like whether pre-view is paused, and clip length, etc, etc..
      Maybe someone who is practiced in the art of reading Python code can review this, paying special attention to what happens if clip length has 'unexpected values', due to, for example, no clip being 'on the timeline'; or clip has been re-sized...

4. maybe this is really a Python bug...when I kill the process as started above, then switch back to the non-root console with Ctrl-Alt-F7, the logged in user session appears to be 'rebooted / re-started' (you see some process stop/start messages like when the PC boots/shuts down; then the log-in screen appears)....this does not happen in the the python -m trace option is not used..

5. NB: I have used the above method twice (first time was not redirecting the trace output to a log file); 1st time, I had to 'File > Import' the CIMG.AVI file, BUT 2nd time the AVI file was already 'visible' as a thumbnail... this does NOT happen when the python -m trace facility is NOT used ...

FWIW, IMHO, there is a race or hazard somewhere, which is why symptoms vary slightly on my machine, and so far do not appear on your machine.