After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 166721 - Segfault when playing ogg vorbis file in Totem or Rhythmbox.
Segfault when playing ogg vorbis file in Totem or Rhythmbox.
Status: RESOLVED DUPLICATE of bug 166201
Product: gtk-engines
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: gtk-engines maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-08 22:14 UTC by Ismael Juma
Modified: 2005-02-09 12:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ismael Juma 2005-02-08 22:14:41 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 
  • #0 ??
  • #1 smooth_draw_flat_box
    from /usr/lib/gtk-2.0/2.4.0/engines/libsmooth.so
  • #2 IA__gtk_paint_flat_box
    at gtkstyle.c line 6116
  • #3 gtk_tree_view_expose
    at gtktreeview.c line 3659
  • #4 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #5 g_type_class_meta_marshal
    at gclosure.c line 514
  • #6 IA__g_closure_invoke
    at gclosure.c line 437
  • #7 signal_emit_unlocked_R
    at gsignal.c line 2523
  • #8 IA__g_signal_emit_valist
    at gsignal.c line 2254
  • #9 IA__g_signal_emit
    at gsignal.c line 2288
  • #10 gtk_widget_event_internal
    at gtkwidget.c line 3626
  • #11 IA__gtk_main_do_event
    at gtkmain.c line 1342
  • #12 gdk_window_process_updates_internal
    at gdkwindow.c line 2182
  • #13 IA__gdk_window_process_all_updates
    at gdkwindow.c line 2235
  • #14 gtk_container_idle_sizer
    at gtkcontainer.c line 1117
  • #15 g_idle_dispatch
    at gmain.c line 3821
  • #16 IA__g_main_context_dispatch
    at gmain.c line 1947
  • #17 g_main_context_iterate
    at gmain.c line 2578
  • #18 IA__g_main_loop_run
    at gmain.c line 2782
  • #19 IA__gtk_dialog_run
    at gtkdialog.c line 1032
  • #20 on_open1_activate
  • #21 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #22 IA__g_closure_invoke
    at gclosure.c line 437
  • #23 signal_emit_unlocked_R
    at gsignal.c line 2485
  • #24 IA__g_signal_emit_valist
    at gsignal.c line 2244
  • #25 IA__g_signal_emit
    at gsignal.c line 2288
  • #26 IA__gtk_widget_activate
    at gtkwidget.c line 3657
  • #27 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 943
  • #28 gtk_menu_shell_button_release
    at gtkmenushell.c line 556
  • #29 gtk_menu_button_release
  • #30 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #31 g_type_class_meta_marshal
    at gclosure.c line 514
  • #32 IA__g_closure_invoke
    at gclosure.c line 437
  • #33 signal_emit_unlocked_R
    at gsignal.c line 2523
  • #34 IA__g_signal_emit_valist
    at gsignal.c line 2254
  • #35 IA__g_signal_emit
    at gsignal.c line 2288
  • #36 gtk_widget_event_internal
    at gtkwidget.c line 3626
  • #37 IA__gtk_propagate_event
    at gtkmain.c line 2145
  • #38 IA__gtk_main_do_event
    at gtkmain.c line 1383
  • #39 gdk_event_dispatch
    at gdkevents-x11.c line 2220
  • #40 IA__g_main_context_dispatch
    at gmain.c line 1947
  • #41 g_main_context_iterate
    at gmain.c line 2578
  • #42 IA__g_main_loop_run
    at gmain.c line 2782
  • #43 IA__gtk_main
    at gtkmain.c line 963
  • #44 main

Comment 1 Ronald Bultje 2005-02-09 09:43:04 UTC
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.
Comment 2 Andrew Johnson 2005-02-09 12:43:02 UTC

*** This bug has been marked as a duplicate of 166201 ***