Description of problem: Tried to play a song from a different album. Version-Release number of selected component: rhythmbox-2.99-1.fc19 Additional info: backtrace_rating: 4 cmdline: rhythmbox crash_function: g_base_info_get_name executable: /usr/bin/rhythmbox kernel: 3.9.0-0.rc6.git0.1.fc19.x86_64 runlevel: N 5 uid: 1000 ureports_counter: 2 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #3 g_base_info_get_name at girepository/gibaseinfo.c:370 #4 _pygi_closure_handle at pygi-closure.c:577 #5 ffi_closure_unix64_inner at ../src/x86/ffi64.c:667 #6 ffi_closure_unix64 at ../src/x86/unix64.S:229 #7 gst_pad_add_probe at gstpad.c:1246 #8 ffi_call_unix64 at ../src/x86/unix64.S:76 #9 ffi_call at ../src/x86/ffi64.c:522 #10 g_callable_info_invoke at girepository/gicallableinfo.c:680 #11 g_function_info_invoke at girepository/gifunctioninfo.c:274 #12 _invoke_callable at pygi-invoke.c:64
Created attachment 735387 [details] File: backtrace
Created attachment 735388 [details] File: cgroup
Created attachment 735389 [details] File: core_backtrace
Created attachment 735390 [details] File: dso_list
Created attachment 735391 [details] File: environ
Created attachment 735392 [details] File: limits
Created attachment 735393 [details] File: maps
Created attachment 735394 [details] File: open_fds
Created attachment 735395 [details] File: proc_pid_status
Created attachment 735396 [details] File: var_log_messages
Quicly switched to a different song in the same album. backtrace_rating: 4 cmdline: rhythmbox crash_function: g_base_info_get_name executable: /usr/bin/rhythmbox kernel: 3.9.0-0.rc7.git3.1.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 ureports_counter: 1 xsession_errors:
Rhythmbox is unusable with this bug. You can only play one song. Any attempts at playing another song cause rhythmbox to crash. Double-click on a new track, clicking the next track button, or stopping the current song and trying to play a different song. Is there any additional backtraces or information required to push this bug along? File an upstream bug?
*** Bug 956941 has been marked as a duplicate of this bug. ***
As noted in 956941, the Replay Gain plugin is the cause of the crash.
I've upgraded tp Fedora 19 and ever since then, whenever I change a radio station or song using the mouse (double-click next song or station) rhythmbox immediately crashes reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: rhythmbox crash_function: g_base_info_get_type executable: /usr/bin/rhythmbox kernel: 3.9.9-302.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 xsession_errors:
Switched between tracks reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: rhythmbox crash_function: g_base_info_get_name executable: /usr/bin/rhythmbox kernel: 3.9.9-302.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 xsession_errors:
I can confirm that the replay gain plugin causes these crashes
Yes, same here. I disabled the replay gain plugin and at least that particular problem with rhythmbox went away. But there are still numerous other problems, particularly with the gvfsd interfaces. Rhythmbox crashes regularly on my system, even after disabling all the plugins. It looks to me like it's primarily due to interface with gvfsd.
1. Start rhythmbox 2. Enable Replay Gain plugin 3. Play a couple of tracks Disabling replay gain plugin helps to work around the problem. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: rhythmbox crash_function: g_base_info_get_name executable: /usr/bin/rhythmbox kernel: 3.9.5-301.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
I hit the Next-Song Button on my external Keyboard. This is not configured to work with Rhythmbox. So I opened the Rhythmbox and delete the Sound from the Play Queue. The 1s Crossover started to the next sound and shortly after that Rhythmbox crashed. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: rhythmbox crash_function: g_base_info_get_name executable: /usr/bin/rhythmbox kernel: 3.10.9-200.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
I'm not seeing this anymore on F20 (rhythmbox-3.0-3.fc20.x86_64).
based on the description in this bug I think that one here is the proper upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=685303
bug was fixed by upstream with patch https://git.gnome.org/browse/rhythmbox/commit/?id=51b0878 on 2013-08-02 so it's included in Rhythmbox 3 (comment 21 supports that interpretation). I think the bug should be either closed with UPSTREAM or should get a backported patch (which might be hard to do even though this crash occurs pretty often: https://retrace.fedoraproject.org/faf/reports/191521/ )
sorry for spamming: I just wanted to mention that applying the upstream patch seems to work fine for Fedora 19's rhythmbox (rhythmbox-2.99.1-1.fc19.x86_64) so it would be nice if the patch could be included for F19. @Bastien/Kalev: If you like I can produce the necessary spec file changes though I won't be able to commit them because I'm not a provenpackager.
*** Bug 1008276 has been marked as a duplicate of this bug. ***
(In reply to Felix Schwarz from comment #23) > bug was fixed by upstream with patch > https://git.gnome.org/browse/rhythmbox/commit/?id=51b0878 on 2013-08-02 so > it's included in Rhythmbox 3 (comment 21 supports that interpretation). > > I think the bug should be either closed with UPSTREAM or should get a > backported patch (which might be hard to do even though this crash occurs > pretty often: > https://retrace.fedoraproject.org/faf/reports/191521/ ) I patched this but rhymbox still crash when I play next song. Maybe it's not relevant
If anyone has trouble with a crashing rhythmbox (if the ReplayGain plugin is enabled) you can try my patched RPM: http://koji.fedoraproject.org/koji/taskinfo?taskID=6182689 (click on the green "buildArch" link to see download links for the rpms). Then use yum to install, e.g. (for F19 x86_64): sudo yum install http://kojipkgs.fedoraproject.org//work/tasks/2690/6182690/rhythmbox-2.99.1-2.fc19.x86_64.rpm This build solves all my problems with regard to the ReplayGain plugin.
I can confirm that rhythmbox-2.99.1-2.fc19 fixes the issue. Any chance the patch and/or new rhythmbox release could be pushed to F19+?
Another user experienced a similar problem: I was listning to one song and selected a diffrent song. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: rhythmbox crash_function: g_base_info_get_type executable: /usr/bin/rhythmbox kernel: 3.14.19-100.fc19.x86_64 package: rhythmbox-2.99.1-1.fc19 reason: rhythmbox killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.