Created attachment 843862 [details] backtrace Description of problem: With the ReplayGain plugin enabled, playing a second flac file often crashes rhythmbox. Version-Release number of selected component: rhythmbox-2.99.1-1.fc19.x86_64 How reproducible: It crashes most of the time, but it seems to be specific to the files played (some combinations crash more often than others). Steps to Reproduce: 1. Enable ReplayGain plugin 2. Play a flac file 3. Press the next track button, wait for the next track to play, or double click another track in the browser. Sometimes whole albums can be played without a crash occurring, but when attempting to play another album after this a crash has been seen. Actual results: Sometimes it doesn't crash, but crashes are often seen with multiple backtraces. I've attached a backtrace of one such crash. When this happened, GDB reported the following: Program received signal SIGSEGV, Segmentation fault. 0x0000003d1fc09017 in signature_offset (info=0x62d5f0) at girepository/gicallableinfo.c:80 80 return *(guint32 *)&rinfo->typelib->data[rinfo->offset + sigoff]; rinfo->typelib was a null pointer. These messages were printed to the console: Starting program: /usr/bin/rhythmbox Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3600.3-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace (rhythmbox:11064): GStreamer-WARNING **: gstpad.c:1311: pad `0xd9c910' has no probe with id `1' I've also seen a crash with a backtrace similar to the one reported in BGO 700401 [0]. Expected results: The next track plays without crashing. Additional info: Applying the path in commit 51b0878 [1] to /usr/lib64/rhythmbox/plugins/replaygain/player.py fixes the problem for me. [0] https://bugzilla.gnome.org/show_bug.cgi?id=700401 [1] https://git.gnome.org/browse/rhythmbox/commit/?id=51b0878349980b125c0c7bd24b177d86201479b2
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.