rhythmbox-metadata crashed with SIGSEGV in jpeg_idct_ifast()

Bug #210745 reported by Mathieu Marquer
6
Affects Status Importance Assigned to Milestone
libjpeg6b (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

I was just filling the library for the first time. Rythmbox didn't crash apparently, but I had this crash message appearing.

ProblemType: Crash
Architecture: i386
Date: Wed Apr 2 12:16:40 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.5-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 jpeg_idct_ifast () from /usr/lib/libjpeg.so.62
 ?? () from /usr/lib/libjpeg.so.62
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox-metadata crashed with SIGSEGV in jpeg_idct_ifast()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
Mathieu Marquer (slasher-fun) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:decompress_onepass (cinfo=0x82664b4, output_buf=0xb6a7cf44) at ./jdcoefct.c:197
jpeg_read_raw_data (cinfo=0x82664b4, data=0xb6a7cf44, max_lines=16) at ./jdapistd.c:210
gst_jpeg_dec_chain (pad=0xb48ea300, buf=0x8514a50) at gstjpegdec.c:707
gst_pad_chain_unchecked (pad=0xb48ea300, buffer=0x8514a50) at gstpad.c:3523
gst_pad_push (pad=0x85a3120, buffer=0x8514a50) at gstpad.c:3691

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in rhythmbox:
importance: Undecided → Medium
Revision history for this message
Mathieu Marquer (slasher-fun) wrote :

Confirming since there is a duplicate bug.

Changed in libjpeg6b:
status: New → Confirmed
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.