Openshot will not start - segfault

Bug #580130 reported by psych1610
100
This bug affects 21 people
Affects Status Importance Assigned to Milestone
OpenShot Video Editor
Won't Fix
Undecided
OpenShot Developers

Bug Description

Using Ubuntu Lucid 10.04 64 bit, 2.6.32-22 and Openshot 1.1.3 (latest in the PPA)

I've installed openshot from the PPA and from http://launchpad.net/openshot/1.1/1.1.3/+download/openshot_1.1.3-1_all.deb (from openshots page here on launchpad). I have not tried the build wizard which seems to be up to 1.0.6 only.

Starting Openshot from the terminal this is all I see:
--------------------------------
   OpenShot (version 1.1.3)
--------------------------------
Process no longer exists: 3343. Creating new pid lock file.
A new frmMain has been created
Segmentation fault

before being returned to a prompt. It is possible this started occurring with an update from VLC. Openshot used to start before with the same version from PPA.

In openshot.debug file it says something about not finding python-mlt (though python-mlt2 is there) but python-mlt is not found in lucids repo's that I can see. I've attached openshot.debug

Revision history for this message
psych1610 (psych1610) wrote :
Revision history for this message
Olivier Girard (eolinwen) wrote :

Here it is all the dependencies necessary for Openshot and you can see that python-mlt2 is for this version (and not python-mlt) : http://openshotusers.com/forum/viewtopic.php?f=12&t=372
A question but what is your version of vlc (the one who is in lucid or another) ?
Thanks

Revision history for this message
psych1610 (psych1610) wrote :

Hi, I'm using VLC 1.06 Goldeneye.

Regarding the dependencies, I have all of them except for the following:

You said "MLT (libmlt, libmlt-data et libmlt++3)" were needed. I have libmlt++3, libmlt-data, and libmlt2. libmlt is nowhere to be found.

I was also missing the freior-plugins, sox, and x264

Besides these I also installed some of their -dev packages just for the heck of it.

Openshot Still gives me the same error as before.

Removing VLC does not solve this problem.

Revision history for this message
psych1610 (psych1610) wrote :

Found another person with this bug here: https://bugs.launchpad.net/openshot/+bug/579067

Can they be merged?

Revision history for this message
Olivier Girard (eolinwen) wrote :

Certainly, same if the pid (3323/3343) is lightly different. That's done i have duplicated it with this one .

Revision history for this message
Olivier Girard (eolinwen) wrote :

Error for me in synaptic about libmlt i have run too the script for this version and i post below. It is a functional version installed by synaptic .
Strange about vlc i have the same version (is it the official ? not a ppa ? )

Revision history for this message
Olivier Girard (eolinwen) wrote :
Revision history for this message
psych1610 (psych1610) wrote :

This is an odd one. I've went through and compared the two debug logs almost line by line and (assuming my French) they're almost identical.

I'll toy around with it some more tomorrow and see if I can't come up with something. A very similar install has a working Openshot in Virtual Box currently with nearly identical sources.list files for PPA's, etc. I'll see if I can't compare those two.

Rheise, would you mind saying what your install looks like or maybe running the debug script:

https://answers.launchpad.net/openshot/+faq/1032

Wonder if it's just us seeing this?

Also, cenwen, the pid does change every time Openshot is started from a command line. For example, tried it just now and mine is 25118.

Revision history for this message
vagrale (vagrale) wrote :

I have the same problem with OpenShot 1.1.3 and Ubuntu 10.04LTS

The output of terminal:
:~$ openshot
--------------------------------
   OpenShot (version 1.1.3)
--------------------------------
Process no longer exists: 6713. Creating new pid lock file.
A new frmMain has been created
Segmentation fault

Revision history for this message
Balázs Kisterenyei (moltenice80) wrote :

Also merged in #573792 which is another duplicate of this bug. Please also consider assigning the bug to Openshot Developers, and changing status to Confirmed.

Revision history for this message
psych1610 (psych1610) wrote :

Moltenice, I've done what you suggested. Wasn't aware I could.

Changed in openshot:
status: New → Confirmed
assignee: nobody → OpenShot Developers (openshot.developers)
Revision history for this message
a (rtyjfgsef45yrf-deactivatedaccount) wrote :

I'm experiencing the same problem and it began yesterday while I was using Openshot. I was working on a video when Openshot either crashed (it has crashed before so that wasn't too odd) or it was acting funny and I closed it myself (I can't remember which one happened as I had been using Openshot all day) and when I immediately reloaded I started received this error.

I have tried all the suggestions on the various bug reports and I have tried a ppa install, deb install and wizard install and all result in the same error (however, the wizard install resulted in a error message that did not include the line "A new frmMain has been created" while the others did). I'm running Ubuntu 10.04.

The only thing I can think of that changed during the time that I was using Openshot fine and it started seg faulting is that I did a package update, I don't know if this is helpful but here is the list of changes from Synaptic history (Gimp shows up because I had just added a ppa to get version 2.7):

Removed the following packages:
python-docky

Upgraded the following packages:
docky (2.1.0~bzr1384-0ubuntu1~10.04~dockycore1) to 2.1.0~bzr1397-0ubuntu1~10.04~dockycore1
gimp (2.6.8-2ubuntu1.1) to 2.7.3-2010022601~ll
gimp-data (2.6.8-2ubuntu1.1) to 2.7.3-2010022601~ll
libbabl-0.0-0 (0.0.22-1build1) to 0.1.3-2010032301~ll
libcairo2 (1.8.10-2ubuntu1) to 1.9.6-6~mrw4
libcairo2-dev (1.8.10-2ubuntu1) to 1.9.6-6~mrw4
libgegl-0.0-0 (0.0.22-0ubuntu4) to 0.1.2.3-2010042002~ll
libgimp2.0 (2.6.8-2ubuntu1.1) to 2.7.3-2010022601~ll
libgimp2.0-dev (2.6.8-2ubuntu1.1) to 2.7.3-2010022601~ll

Installed the following packages:
libopenraw1 (0.0.8-1)
libxcb-shm0-dev (1.5-2)

Revision history for this message
mangwills (mangwills) wrote :

I am only able to run Openshot by using Synaptic, and using Package->Force version on to set libcairo version to 1.8.10-2.

Revision history for this message
Olivier Girard (eolinwen) wrote :

@Mangwills, you confirm what i was thinking about the libcairo2 (and his version dev) that the fact to pass at the version 1.8.10-2ubuntu1 at the 1.9.6-6 provoke a problem in the creation of the interface. This bug seems to be for the libcairo and i have none solution for resolve that. The only advice that i have is to keep the official version.
Thanks. Try to remove it for testing if it is really the cause.

Revision history for this message
Balázs Kisterenyei (moltenice80) wrote :

@mangvills & @cenwen

  I can also confirm, that forcing libcairo2 version to 1.8.10-2ubuntu1 fixes the issue and I can start OpenShot without problems. Forcing the system to use an outdated library, should not be the permanent solution though.
It needs to be determined, whether we should file a bug against the 1.9.6-6 version of the libcairo2 library, or is it just a packaging issue of the libcairo2 package provided by the repository.

Revision history for this message
psych1610 (psych1610) wrote :

Is there any way to prevent forcing libcairo2 to 1.1.10-2 from removing a bunch of other things from my system?

They're mostly -dev files that I've probably used in the past to get other things working and I'm not sure I want to take the risk of breaking other things just to get openshot (potentially) working.

Revision history for this message
vagrale (vagrale) wrote :

i found a solution:
Open synaptic - find libcairo2 and chose it - press Ctrl+E - then choose ver 1.8.10
press coercion version and after choose Apply.
After that is ok!
look image http://img638.imageshack.us/img638/6213/screenshotex.png

After all just lock package libcairo2 version 1.8.10

Revision history for this message
Balázs Kisterenyei (moltenice80) wrote : Re: [Bug 580130] Re: Openshot will not start - segfault

The problem, with your solution is, that it is not so much a solution,
as rather a workaround. It is working for a couple of people (including
me) for now, but the real solution, would be a patch that deals with the
problem once and for all, but that is up to the developers.

Revision history for this message
vagrale (vagrale) wrote :

Yes, I agree, not a permanent solution, is a temporary solution until corrected,
just my English is not very well, and I didn' t write exactly what I mean!
Just in this way, no need to remove all the packages, which pulls the libcairo2,
when trying to remove it!

Revision history for this message
Diego Estévez (dgmvecuador) wrote :

I see that you use the ppa:matthaeus123/mrw-insane-build PPA, so that's the problem, that code is alpha/beta, he say that... maybe you should not use them. Could anyone explain me why you use that package and not the official one?? and this bug must be reported to https://launchpad.net/~matthaeus123....

Revision history for this message
Balázs Kisterenyei (moltenice80) wrote :

The reason is GIMP. This PPA contains the most recent build of it, but
unfortunately also the latest build of cairo, with which OpenShot is not
compatible yet. Or at least there is some other kind of conflict between
the two. I still think the problem is on OpenShot's side, but feel free
to prove me otherwise, because this is just my logic, no programming
skills here.

Revision history for this message
Diego Estévez (dgmvecuador) wrote :

@Moltenice80, I don't think so, it's not usual that bugs in a Python cause a "Segmentation fault", the PPA contains the GIMP you said, but it doesn't have a version of the package "python-cairo", that could be a problem because the Python bindings has another version and depends on libcairo.

Revision history for this message
rami (lehtinen-rami) wrote :

openshot
--------------------------------
   OpenShot (version 1.1.3)
--------------------------------
Process no longer exists: 3626. Creating new pid lock file.
A new frmMain has been created
Segmentation fault

-i also have installed libcairo2 1.9.6-6~mrw4, for same reasons as 'Moltenice80'

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

I had this exact problem until I downgraded libcairo2 from 1.9.6-6~mrw4 to 1.8.10-2ubuntu1.

Revision history for this message
Andy Finch (fincha) wrote :

I'm marking this as Won't Fix, as it's not a bug in Openshot. The PPA you are using to install the updated libcairo does not provide the matching version of the Python bindings

Changed in openshot:
status: Confirmed → Won't Fix
Revision history for this message
xcape77 (xcape77) wrote :

I had this exact problem until I downgraded libcairo2 from 1.9.6-6~mrw4 to 1.8.10-2ubuntu1.

Revision history for this message
Guifarro (jesusguifarro) wrote :

xcape77, yes it work for me too!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.