openshot crashed with signal 5 in _XError()

Bug #593116 reported by Bowmore
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openshot (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: openshot

Openshot crashes in Maverick when starting to play a video.

When openshot is run with XLIB_SKIP_ARGB_VISUALS=1 there is no crash.

Workaround in the terminal:
XLIB_SKIP_ARGB_VISUALS=1 openshot

Workaround editing the menu:
env XLIB_SKIP_ARGB_VISUALS=1 openshot

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: openshot 1.1.3-1
ProcVersionSignature: Ubuntu 2.6.35-2.3-generic-pae 2.6.35-rc2
Uname: Linux 2.6.35-2-generic-pae i686
Architecture: i386
Date: Fri Jun 11 01:12:58 2010
ExecutablePath: /usr/bin/openshot
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/openshot
ProcCwd: /home/rolf
ProcEnviron:
 LANGUAGE=sv_SE:sv:en_GB:en
 LANG=sv_SE.utf8
 SHELL=/bin/bash
Signal: 5
SourcePackage: openshot
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libSDL-1.2.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
Title: openshot crashed with signal 5 in _XError()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo

Revision history for this message
Bowmore (bowmore) wrote :
visibility: private → public
tags: added: gtk-csd rgba
Revision history for this message
vulfgar (vulfgar) wrote :

Same problem with 64bit version in Maverick

Revision history for this message
vulfgar (vulfgar) wrote :

Forgot to mention in the previous comment: The workaround works fine for me.

Revision history for this message
Omer Akram (om26er) wrote :

If any one want to fix this app the solution is to make the app use system colomap.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Changed in openshot (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (5.1 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1: installed version 1:4.5.0-5ubuntu1, latest version: 1:4.5.0-7ubuntu1
libqtgui4: installed version 4:4.7.0~beta1+git20100522-0ubuntu2, latest version: 4:4.7.0~beta1+git20100522-0ubuntu5
libqtcore4: installed version 4:4.7.0~beta1+git20100522-0ubuntu2, latest version: 4:4.7.0~beta1+git20100522-0ubuntu5
libtiff4: installed version 3.9.2-3, latest version: 3.9.4-1
libqt4-dbus: installed version 4:4.7.0~beta1+git20100522-0ubuntu2, latest version: 4:4.7.0~beta1+git20100522-0ubuntu5
libncursesw5: installed version 5.7+20090803-2ubuntu3, latest version: 5.7+20100313-2ubuntu1
coreutils: installed version 8.5-1ubuntu1, latest version: 8.5-1ubuntu3
libssl0.9.8: installed version 0.9.8k-7ubuntu8, latest version: 0.9.8o-1ubuntu1
libnewt0.52: installed version 0.52.10-8, latest version: 0.52.11-1
libmlt-data: installed version 0.5.4+git20100601-1, latest version: 0.5.6-1
libncurses5: installed version 5.7+20090803-2ubuntu3, latest version: 5.7+20100313-2ubuntu1
libgtk2.0-0: installed version 2.21.1-1ubuntu1, latest version: 2.21.2-0ubuntu5
libdc1394-22: installed version 2.1.2-2, latest version: 2.1.2-3
python-pygoocanvas: installed version 0.14.1-0ubuntu1, latest version: 0.14.1-1ubuntu1
python: installed version 2.6.5-0ubuntu1, latest version: 2.6.5-5ubuntu3
sensible-utils: installed version 0.0.1ubuntu3, latest version: 0.0.4ubuntu1
melt: installed version 0.5.4+git20100601-1, latest version: 0.5.6-1
libgoocanvas-common: installed version 0.15-0ubuntu2, latest version: 0.15-1
gcc-4.5-base: installed version 4.5.0-5ubuntu1, latest version: 4.5.0-7ubuntu1
libavformat52: installed version 4:0.6~svn20100505-1ubuntu2, latest version: 4:0.6-1ubuntu1
python2.6: installed version 2.6.5+20100529-0ubuntu1, latest version: 2.6.5+20100628-2ubuntu1
python-glade2: installed version 2.17.0-0ubuntu2, latest version: 2.17.0-2ubuntu1
libavutil50: installed version 4:0.6~svn20100505-1ubuntu2, latest version: 4:0.6-1ubuntu1
python-minimal: installed version 2.6.5-0ubuntu1, latest version: 2.6.5-5ubuntu3
python2.6-minimal: installed version 2.6.5+20100529-0ubuntu1, latest version: 2.6.5+20100628-2ubuntu1
python-gtk2: installed version 2.17.0-0ubuntu2, latest version: 2.17.0-2ubuntu1
libglib2.0-0: installed version 2.25.8-1ubuntu1, latest version: 2.25.10-1ubuntu1
whiptail: installed version 0.52.10-8, latest version: 0.52.11-1
libgomp1: installed version 4.5.0-5ubuntu1, latest version: 4.5.0-7ubuntu1
libraw1394-11: installed version 2.0.5-1ubuntu2, latest version: 2.0.5-2ubuntu1
libcups2: installed version 1.4.3-1ubuntu1, latest version: 1.4.4-1
libpango1.0-common: installed version 1.28.0-1ubuntu1, latest version: 1.28.1-1ubuntu2
python-xdg: installed version 0.19-1ubuntu1, latest version: 0.19-2ubuntu1
libc-bin: installed version 2.12-0ubuntu3, latest version: 2.12-0ubuntu4
libpng12-0: installed version 1.2.42-1ubuntu2, latest version: 1.2.44-1
libxdamage1: installed version 1:1.1.2-1,...

Read more...

tags: removed: need-i386-retrace
Revision history for this message
Bowmore (bowmore) wrote :

> Please upgrade your system to the latest package versions. If you still
> encounter the crash, please file a new report.
> Thank you for your understanding, and sorry for the inconvenience!

Ok, I'll give it another try when rgba is turned on again.

Strange though, that all three bugs
- banshee bug #585160
- xsane bug #585145
- openshot bug #593116
all have been marked invalid for the same reason!

> This might be caused by some outdated packages which were installed on your system
at the time of the report

Nope, the maverick system was up to date at that time.

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

Other bug subscribers

Remote bug watches

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