Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Whenever I switch to new track, or whenever I restart paused track, the crash happens.

Version-Release number of selected component:
rhythmbox-2.99.1-1.el7

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: g_base_info_get_type
executable:     /usr/bin/rhythmbox
kernel:         3.10.0-18.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_base_info_get_type at girepository/gibaseinfo.c:276
 #1 g_callable_info_load_return_type at girepository/gicallableinfo.c:197
 #2 _pygi_closure_set_out_arguments at pygi-closure.c:451
 #3 _pygi_closure_handle at pygi-closure.c:553
 #4 ffi_closure_unix64_inner at ../src/x86/ffi64.c:667
 #5 ffi_closure_unix64 at ../src/x86/unix64.S:229
 #6 gst_pad_add_probe at gstpad.c:1246
 #7 ffi_call_unix64 at ../src/x86/unix64.S:76
 #8 ffi_call at ../src/x86/ffi64.c:522
 #9 g_callable_info_invoke at girepository/gicallableinfo.c:680

Created attachment 806341 [details]
File: backtrace

Created attachment 806343 [details]
screencast of the reproduction

OK, so I was partially wrong. Restarting is not 100% way how to reproduce the bug. However, switching of the tracks is.

*** Bug 1034692 has been marked as a duplicate of this bug. ***

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.