Ubuntu

openshot crashed with SIGSEGV in mlt_properties_set()

Reported by Akshar Patel on 2012-01-26
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
OpenShot Video Editor
Undecided
Unassigned
openshot (Ubuntu)
Undecided
Unassigned

Bug Description

occurs when openshot is started

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: openshot 1.4.0-1
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic-pae 3.2.1
Uname: Linux 3.2.0-10-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Thu Jan 26 12:19:06 2012
ExecutablePath: /usr/bin/openshot
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120123)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/openshot
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb5cc6247: mov 0x4(%eax),%edi
 PC (0xb5cc6247) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: openshot
StacktraceTop:
 ?? () from /usr/lib/libmlt.so.4
 mlt_properties_set () from /usr/lib/libmlt.so.4
 Mlt::Properties::set(char const*, char const*) () from /usr/lib/libmlt++.so.3
 ?? () from /usr/lib/python2.7/dist-packages/_mlt.so
 ?? () from /usr/lib/python2.7/dist-packages/_mlt.so
Title: openshot crashed with SIGSEGV in mlt_properties_set()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Akshar Patel (akshar-patel-47) wrote :
visibility: private → public
Phil. V (philip.v) wrote :

Thanks for your bug report. Just commenting to say that I deleted the core dump attachment, as that might contain some private information.

tags: removed: need-i386-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openshot (Ubuntu):
status: New → Confirmed
Karl Hegbloom (karl.hegbloom) wrote :

Also happens on amd64.

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

Other bug subscribers