Hide Forgot
Description of problem: Rhythmbox causes a segfault (by dereferencing a null pointer) in rb_player_gst_find_element_with_property when attempting to play a track while the GUI is loaded over an ssh connection. Version-Release number of selected component (if applicable): rhythmbox-2.90.1-17.git20110927.fc16.x86_64 How reproducible: Always. I have attempted this between a few different computers running F16. Steps to Reproduce: 1. on computer_A, ssh -X computer_B 2. Start rhythmbox from the terminal as: rhythmbox --gst-disable-segtrap --gst-disable-registry-fork 3. When rhythmbox window opens on computer_A, select an audio track and click play. Actual results: Rhythmbox dies with a Segmentation Fault message. The backtrace is as follows: (gdb) bt #0 0x00007ffff7b6e6e1 in rb_player_gst_find_element_with_property ( element=0x0, property=0x7ffff7b8e54e "volume") at rb-player-gst-helper.c:123 #1 0x00007ffff7b77970 in track_change_done (mp=0x637260, error=<optimized out>) at rb-player-gst.c:361 #2 track_change_done (mp=0x637260, error=<optimized out>) at rb-player-gst.c:329 #3 0x00007ffff7b780a1 in bus_cb (bus=0x17a1c00, message=0x1835100, mp=0x637260) at rb-player-gst.c:529 #4 0x00007ffff1bcd0a4 in gst_bus_source_dispatch (source=0x18ad6d0, callback=0x7ffff7b77b90 <bus_cb>, user_data=0x637260) at gstbus.c:761 #5 0x00007ffff0244a7d in g_main_dispatch (context=0x806320) at gmain.c:2425 #6 g_main_context_dispatch (context=0x806320) at gmain.c:2995 #7 0x00007ffff0245278 in g_main_context_iterate (context=0x806320, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073 #8 0x00007ffff02457c5 in g_main_loop_run (loop=0x8f4980) at gmain.c:3281 #9 0x00007ffff426f6ad in gtk_main () at gtkmain.c:1362 #10 0x0000000000402b16 in main (argc=1, argv=0x7fffffffe4b8) at main.c:324 (gdb) list 118 rb_player_gst_find_element_with_property (GstElement *element, const char *property) 119 { 120 GstIterator *iter; 121 GstElement *result; 122 123 if (GST_IS_BIN (element) == FALSE) { 124 if (g_object_class_find_property (G_OBJECT_GET_CLASS (element), 125 property) != NULL) { 126 return g_object_ref (element); 127 } (gdb) print element $1 = (GstElement *) 0x0 Expected results: Any of the following would be acceptable: 1) (ideal) the song plays on Computer_A 2) (expected) the song plays on Computer_B 3) (acceptable) An error message is produced saying that rhythmbox can't run over SSH, or can't load a gstreamer sink. Additional info: I assume this has something to do with connecting to DBus on computer_A. I realize this isn't a super common activity, but it should definitely not result in a segfault.
Created attachment 665825 [details] Backtrace I'm seeing what appears to be the same thing. This is fully local run on F 17 with the following packages: rhythmbox-2.97-1.fc17.x86_64 grilo-0.1.18-3.fc17.x86_64 The reproducer as is follows: 1. launch rhythmbox 2. (have some songs in your "browse" pane. You don't need to select any though) 3. press "play" In my case the reproducer is really just "launch rhythmbox" and "press play". I do have something in my music database though, and perhaps that makes a difference. I did try to work with grilo-plugins and use UPnP, but uninstalling that package and disabling "grilo media browser" in plugin menu, I still see the failure.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.