rhythmbox-metadata crashed with SIGSEGV in jpeg_idct_ifast()

Bug #555311 reported by Jérémi Couillard
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox-ubuntuone-music-store (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: rhythmbox-ubuntuone-music-store

Only opened rhythmbox and the error pop when it was browsing my 'watched' folder.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: rhythmbox-ubuntuone-music-store 0.0.5-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 4 15:37:56 2010
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
PackageArchitecture: all
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f392174fc82 <jpeg_idct_ifast+738>: mov %r12b,(%rdx)
 PC (0x7f392174fc82) ok
 source "%r12b" ok
 destination "(%rdx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox-ubuntuone-music-store
StacktraceTop:
 jpeg_idct_ifast () from /usr/lib/libjpeg.so.62
 ?? () from /usr/lib/libjpeg.so.62
 jpeg_read_raw_data () from /usr/lib/libjpeg.so.62
 ?? () from /usr/lib/gstreamer-0.10/libgstjpeg.so
 ?? () from /usr/lib/libgstreamer-0.10.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in jpeg_idct_ifast()
UserGroups: adm admin cdrom dialout gdm libvirtd lpadmin plugdev sambashare vboxusers

Revision history for this message
Jérémi Couillard (couillard45682) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #533627, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.