GNOME Bugzilla – Bug 166721
Segfault when playing ogg vorbis file in Totem or Rhythmbox.
Last modified: 2005-02-09 12:43:02 UTC
Distribution/Version: Fedora Core 3 I will show a way to reproduce the problem from 2 different applications that use GStreamer to show that the problem does not lie in the applications themselves: Make sure Gtk 2.6.2 is installed. Using Rhythmbox 0.8.8: 1. Open Rhythmbox 2. Double-click on an ogg vorbis song. Using Totem 0.99.22: 1. Open Totem. 2. Select Movie/Open. 3. Select an ogg vorbis file. 4. Select Movie/Open again. This is reproduceable every single time. As this behaviour only started showing itself recently, I tried to revert back some packages to see which one was causing the problem. I narrowed it down to gtk 2.6.2. Everything works fine when using gtk 2.4.14 (with glib 2.4.8 _and_ with glib 2.6.2). It seems therefore that there is an interaction problem between gstreamer and gtk2 2.6.2. I'm using gstreamer 0.8.9, gstreamer-plugins 0.8.7 and Fedora Core 3. GStreamer was installed by using the packages from the gstreamer website. It is a possibility that the bug is actually in gtk 2.6.2, but I do not have enough knowledge to know whether that is the case. A backtrace from a segfault that took place when using totem as outlined above follows. I only had the debugging symbols for gtk and glib installed as the debuginfo RPMS for gstreamer were not available from the website. However, let me know if you want me to recompile gstreamer with the debugging symbols. Thanks. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1215203104 (LWP 19327)] 0x00000000 in ?? () (gdb) bt
+ Trace 55473
Right, the fact that this happens specifically with GStreamer applications is noticed. However, the backtrace occurs in gtk-engines code, and is triggered by a strict gtk action. Also, I don't see any GStreamer symbols in the backtrace. For now, I'll move this bug to gtk-engines. Maintainers there: if this bug is completely stupid, or if valgrind shows otherwise, feel free to move it back to GStreamer. I'll happily solve bugs if I have a good indication that it's a GStreamer bug.
*** This bug has been marked as a duplicate of 166201 ***