[apport] pitivi crashed with SIGSEGV in jpeg_idct_ifast()

Bug #114741 reported by pionse
2
Affects Status Importance Assigned to Milestone
libjpeg6b (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pitivi

.

ProblemType: Crash
Architecture: i386
Date: Mon May 14 09:02:42 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/pitivi
InterpreterPath: /usr/bin/python2.5
Package: pitivi 0.10.2-1
PackageArchitecture: all
ProcCmdline: python /usr/bin/pitivi
ProcCwd: /home/paolo
ProcEnviron:
 LANGUAGE=it_IT:it:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pitivi
StacktraceTop:
 jpeg_idct_ifast () from /usr/lib/libjpeg.so.62
 ?? () from /usr/lib/libjpeg.so.62
 ?? ()
 ?? ()
 ?? ()
Uname: Linux (none) 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
pionse (paolo-cossettini) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:?? () from /lib/ld-linux.so.2
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:?? () from /lib/ld-linux.so.2
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in libjpeg6b:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libjpeg6b (Ubuntu) because there has been no activity for 60 days.]

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.