Registered Member
|
That's correct...it's within the parseScriptsFiles function.. #14 0x00007faa68b609af in QTreeWidget::setCurrentItem (this=0x21ca7b0, item=0x25f1340, column=0) at itemviews/qtreewidget.cpp:2815 #15 0x00000000006ea0a5 in RenderWidget::parseScriptFiles (this=this@entry=0x21243b0) at /build/buildd/kdenlive-0.9.6/src/renderwidget.cpp:1949 Here's the code: QTreeWidgetItem *script = m_view.scripts_list->topLevelItem(0); if (script) { m_view.scripts_list->setCurrentItem(script); <--- BONK !!! script->setSelected(true); } The parseScriptsFiles function goes through your 'scripts' subdirectory within the project directory looking for anything with a .sh extension. It then loads those scrips in the scripts_list object on the screen. First suspect is a fubar'd script file. So...search your directory tree for a 'scripts' subdir w/ '.sh' files in it. This subdir should be in the directory that your project file is in. Rename 'scripts' to something appropriate like 'nfgScripts' and try to reproduce the error. If the error goes away then zip up the contents of your 'nfgScripts' subdir and post that to the bug report. |
Registered Member
|
Did you try to rename your ~/.kde4/share/config/kdenliverc file and restart kdenlive?
|
Registered Member
|
Renaming the scripts in ~/kdenlive/scripts so they are not .sh files fixes the crash.
I'm uploading to the bug one .sh file that causes it to crash. The presence of this one file is enough. |
Registered Member
|
Can confirm, deleting scripts folder allowed me to workaround the crash:
|
Registered Member
|
Hi.. I am just joining the Forum..
I am using KDEnliive for about 2 years.. and there is no problem at all, suddenly it's crashed everytime I press Render button. I've Tried the ways from this forum, like : re-installing from PPA and downgrading the melt After searching so many web, I am reading bug-trace from https://bugs.kdenlive.org/view.php?id=3452.. it's says just try to delete files in ~/kdenlive/scripts/ and GREAT !!! the render button working again.. I hope my reply can help someone who have same rendering crashes problem. |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot]