Hi, guys. I apologise if I've posted this in the wrong place.

I'm running the latest version of kdenlive from the kdenlive.org repo on Ubuntu 13.04 and I've noticed that whenever I try to use key-spill mop-up Kdelive force quits. I've only had this problem since upgrading my Ubuntu installation.

Has anyone experienced this/knows how I might go about fixing it? I've removed all the config files and reinstalled, reinstalled to a previous version but no success. Please help.

Kindest Regards
Chris Were

Anybody? Still having the problem. Am I the only one experiencing it?

When "Kdenlive" is "force quit" are you offered any option to get "Developer Information" or anything along those lines?
If so, try posting that information here as it may be helpful to determining the fault you are experiencing.

Unfortunately I don't get any info whatsoever. It's just force quits and when I re-open Kdenlive it acts as if nothing's wrong.

Which platform / operating system is this occurring under?

I'm running Ubuntu 13.04 with Kdenlive live version 0.9.6

Okay, it seems that Ubuntu overrides the KDE crash handler - which is why you don't see "Developer Information" unfortunately.
Can you try manually running Kdenlive under gdb (see https://wiki.debian.org/HowToGetABacktrace) and trying to generate a backtrace using that method?

christopherwere,

Running Linux Mint 15 here and had the exact same issues as you. For "Giggles" I decided to install the full KDE environment on and low and behold the Key Spill Mop-Up works! There must be a required piece of code missing. If you have the room I would suggest trying this in Ubuntu as well if you need to get this feature working.

Hope this helps!

Unfortunately installing kde-full hasn't helped.

Here's the debug report
http://paste.ubuntu.com/6054477/

Any help would be greatly appreciated. Also not to be rude but would anyone here know of any paid software I could use until the open-source on Linux get's less buggy?

Kindest Regards
Chris

Could you please try generating a full backtrace when gdb reports that Kdenlive has segfaulted?

How would I go about doing that?

That is explained over here in step 3: http://kdenlive.org/node/872

I'm sorry I don't have the time for all of this. Thanks for trying to help though. Maybe Kdenlive will catch up with all it's bug fixes soon.