Yep Brian, I reviewed after posting the message, it seems like the
kdenlive bug. melt in command line works like a charm. ;D

On 4/11/15, Brian Matherly <c...@brianmatherly.com> wrote:
> I don't see any evidence in your output that suggests MLT is crashing. The
> "[mpegts...]" messages are from ffmpeg and are beneign. The rest of the
> messages are from KDNELIVE.
>
> ~Brian
>
>       From: Zenny <garbytr...@gmail.com>
>  To: mlt-devel@lists.sourceforge.net
>  Sent: Saturday, April 11, 2015 7:19 AM
>  Subject: [Mlt-devel] kdenlive crashes so does mlt
>
> Hi,
>
> I am trying to run kdenlive inside a multiseat computer (two kvms
> meaning separate set of kb+video+mouse connected to the same computer
> Ref. https://wiki.ubuntu.com/MultiseatTeam/Instructions) .
>
> It runs fine in seat0, but not in seat-1 and outputs error as follows:
>
> USER@MACHINE:~$ kdenlive --nocrashhandler
> [mpegts @ 0x377ee00] max_analyze_duration 5000000 reached at 5000000
> microseconds
> [mpegts @ 0x31d7e00] max_analyze_duration 5000000 reached at 5000000
> microseconds
> [mpegts @ 0x321a180] max_analyze_duration 5000000 reached at 5000000
> microseconds
> kdenlive(14893) Render::checkMaxThreads: // TRACTOR PROBLEM
> Segmentation fault (core dumped)
>
> USER@MACHINE:~$ kdenlive
> [mpegts @ 0x318f840] max_analyze_duration 5000000 reached at 5000000
> microseconds
> [mpegts @ 0x31d1bc0] max_analyze_duration 5000000 reached at 5000000
> microseconds
> [mpegts @ 0x29aa280] max_analyze_duration 5000000 reached at 5000000
> microseconds
> kdenlive(15072) Render::checkMaxThreads: // TRACTOR PROBLEM
> [mpegts @ 0x7f5818006140] max_analyze_duration 5000000 reached at
> 5000000 microseconds
> [mpegts @ 0x7f58180040c0] max_analyze_duration 5000000 reached at
> 5000000 microseconds
> [mpegts @ 0x7f581800e600] max_analyze_duration 5000000 reached at
> 5000000 microseconds
> KCrash: Application 'kdenlive' crashing...
> kdenlive: Fatal IO error: client killed
> KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
> sock_file=/home/USER/.kde/socket-MACHINE/kdeinit4__1
> Unable to start Dr. Konqi
> Not forwarding the crash to Apport.
>
> USER@MACHINE:~$ KDE_DEBUG=False kdenlive --nocrashhandler
> [mpegts @ 0x3eadec0] max_analyze_duration 5000000 reached at 5000000
> microseconds
> [mpegts @ 0x38ce700] max_analyze_duration 5000000 reached at 5000000
> microseconds
> [mpegts @ 0x38fe600] max_analyze_duration 5000000 reached at 5000000
> microseconds
> kdenlive(15232) Render::checkMaxThreads: // TRACTOR PROBLEM
> [mpegts @ 0x7f29f40077a0] max_analyze_duration 5000000 reached at
> 5000000 microseconds
> [mpegts @ 0x7f29f4005b80] max_analyze_duration 5000000 reached at
> 5000000 microseconds
> [mpegts @ 0x7f29f400f120] max_analyze_duration 5000000 reached at
> 5000000 microseconds
> Segmentation fault (core dumped)
>
> Any pointer appreciated! Thanks!
>
> Wbr,
> /z
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Mlt-devel mailing list
> Mlt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mlt-devel
>
>
>

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel

Reply via email to