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.

Version-Release number of selected component:
control-center-3.8.6-14.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: adapter_changed
executable:     /usr/bin/gnome-control-center
kernel:         3.10.0-114.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 adapter_changed at bluetooth-client.c:663
 #1 adapter_g_signal at bluetooth-client.c:729
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:522
 #4 g_cclosure_marshal_generic at gclosure.c:1454
 #9 on_signal_received at gdbusproxy.c:927
 #10 emit_signal_instance_in_idle_cb at gdbusconnection.c:3715
 #14 g_main_context_iteration at gmain.c:3766
 #15 g_application_run at gapplication.c:1623

Created attachment 879076 [details]
File: backtrace

Created attachment 879077 [details]
File: cgroup

Created attachment 879078 [details]
File: core_backtrace

Created attachment 879079 [details]
File: dso_list

Created attachment 879080 [details]
File: environ

Created attachment 879081 [details]
File: exploitable

Created attachment 879082 [details]
File: limits

Created attachment 879083 [details]
File: maps

Created attachment 879084 [details]
File: open_fds

Created attachment 879085 [details]
File: proc_pid_status

Created attachment 879086 [details]
File: var_log_messages

Created attachment 879087 [details]
File: sosreport.tar.xz

I was testing bug 1054212.

It's reproducible randomly I did following steps: https://bugzilla.redhat.com/show_bug.cgi?id=1054212#c15 and navigated between Bluetooth and Network components. I got core dump on Control Center close.

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.

This should be fixed in the rebased GNOME version in 7.2.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2157.html