GNOME Bugzilla – Bug 346185
rhythmbox crashes when playing an m4a file on an x86_64 machine
Last modified: 2006-06-30 07:19:46 UTC
Steps to reproduce: 1. Open rhythmbox. 2. Play an m4a file in the library. Stack trace: Program received signal SIGSEGV, Segmentation fault.
+ Trace 69113
Thread 1094986048 (LWP 8881)
Thread 16 (Thread 1136945472 (LWP 8886))
Thread 11 (Thread 1094986048 (LWP 8881))
Thread 6 (Thread 1094986048 (LWP 8860))
Thread 5 (Thread 1094986048 (LWP 8859))
Thread 4 (Thread 1094986048 (LWP 8853))
Other information: This problem seems to be specific to the x86_64 version of rhythmbox; I can play m4a files on my i386 machine without any problems. I am using version 2.0-8 of faad2 (that I obtained from the dries repository) and version 0.10.3-1 of gstreamer-plugins-bad (which I obtained from the freshrpms repository).
Try playing one of the files that causes rhythmbox to crash with gst-launch-0.10 ("gst-launch-0.10 playbin uri=file:///path/to/file.m4a"). What versions of gstreamer core and gst-plugins-base are you using?
$ rpm -q gstreamer gstreamer-plugins-base gstreamer-0.10.8-0.gst.1.5 gstreamer-plugins-base-0.10.8-0.gst.1.5 When I tried to play one of the files gst-launch-0.10, I got the following messages: $ gst-launch-0.10 playbin uri=file:///home/ebair/share/rhythmbox/They\ Might\ Be\ Giants/Apollo\ 18/01\ Dig\ My\ Grave.m4a Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Segmentation fault I can produce a gdb trace for the above command if that would be halpful.
I don't expect the stack trace for gst-launch would be noticeably different to the one from rhythmbox. Since this is clearly a gstreamer problem, I'm reassigning to gst-plugins-bad.
Looks like it's the same problem as bug #344901. FWIW, there are limits on how you can mix repositories (especially using faad2 from other repositories might lead to borkage), but I'm not sure exactly which repositores are ok to mix and not. What we really need in this case is a stack trace with full debugging symbols or someone who can confirm/check whether the problem still exists with gst-plugins-bad from CVS. *** This bug has been marked as a duplicate of 344901 ***