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:
starting Rhythmbox

Version-Release number of selected component:
rhythmbox-2.98-4.el7

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        rhythmbox
kernel:         3.6.0-0.29.el7.sgruszka1.x86_64.debug

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 ??
: #1 g_hash_table_remove_internal at /lib64/libglib-2.0.so.0
: #2 remove_child.isra.7 at /lib64/librhythmbox-core.so.6
: #3 remove_entry_from_album at /lib64/librhythmbox-core.so.6
: #4 remove_one_song at /lib64/librhythmbox-core.so.6
: #5 g_hash_table_foreach_remove_or_steal at /lib64/libglib-2.0.so.0
: #6 rhythmdb_tree_entry_delete_by_type at /lib64/librhythmbox-core.so.6
: #7 ffi_call_unix64 at /lib64/libffi.so.6
: #8 ffi_call at /lib64/libffi.so.6
: #9 g_callable_info_invoke at /lib64/libgirepository-1.0.so.1

Created attachment 650506 [details]
File: core_backtrace

Created attachment 650507 [details]
File: environ

Created attachment 650508 [details]
File: backtrace

Created attachment 650509 [details]
File: limits

Created attachment 650510 [details]
File: cgroup

Created attachment 650511 [details]
File: xsession_errors

Created attachment 650512 [details]
File: executable

Created attachment 650513 [details]
File: maps

Created attachment 650514 [details]
File: dso_list

Created attachment 650515 [details]
File: build_ids

Created attachment 650516 [details]
File: var_log_messages

Created attachment 650517 [details]
File: open_fds

Created attachment 650518 [details]
File: proc_pid_status

Please test with 2.99.1

Did you get a chance to test it? Otherwise I'll close this as being fixed in the newer version.

In rhythmbox-2.99.1-1.el7.x86_64 the situation is quite certainly much better. There are some crashes, but they are rare and generally I can use RB again. Thank you.