Bug 2156615

Summary: gnome-control-center segfaults
Product: Red Hat Enterprise Linux 9 Reporter: JL <registered>
Component: gnome-control-centerAssignee: Nobody <nobody>
gnome-control-center sub component: Bluetooth panel QA Contact: Desktop QE <desktop-qa-list>
Status: CLOSED MIGRATED Docs Contact:
Severity: unspecified    
Priority: unspecified CC: cgarnach, neil
Version: 9.1Keywords: MigratedToJIRA
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-18 11:09:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description JL 2022-12-27 23:21:38 UTC 
Description of problem:

Gnome-control-center segfaults

Version-Release number of selected component (if applicable):

Name         : gnome-control-center
Version      : 40.0
Release      : 27.el9
Architecture : x86_64
Size         : 20 M
Source       : gnome-control-center-40.0-27.el9.src.rpm
Repository   : @System
From repo    : appstream
Summary      : Utilities to configure the GNOME desktop
URL          : http://www.gnome.org
License      : GPLv2+ and CC-BY-SA
Description  : This package contains configuration utilities for the GNOME desktop, which
             : allow to configure accessibility options, desktop fonts, keyboard and mouse
             : properties, sound setup, desktop theme and background, user interface
             : properties, screen resolution, and other settings.


How reproducible:

unknown at this time

Steps to Reproduce:
1. unknown at this time
2.
3.

Actual results:


Expected results:


Additional info:

/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5101]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
/var/log/messages-20221221-Dec 20 17:04:39 machine journal[5234]: [string "policy-bluetooth.lua"]:121: bad argument #1 to 'find' (string expected, got nil)#012stack traceback:#012#011[C]: in function 'string.find'#012#011[string "policy-bluetooth.lua"]:121: in upvalue 'isBluez5AudioSink'#012#011[string "policy-bluetooth.lua"]:389: in function <[string "policy-bluetooth.lua"]:387>
/var/log/messages-20221221-Dec 20 17:04:43 machine gdm[3879]: GLib: Source ID 171 was not found when attempting to remove it
/var/log/messages-20221221:Dec 20 17:04:43 machine kernel: gnome-control-c[29650]: segfault at fb80 ip 000055a46f240572 sp 00007fff442616f0 error 4 in gnome-control-center[55a46f1f2000+15a000]
/var/log/messages-20221221-Dec 20 17:04:43 machine kernel: Code: ff ff 0f 84 30 fe ff ff e9 0b ff ff ff e8 f6 c5 fb ff 66 0f 1f 44 00 00 41 54 55 53 48 89 fb 48 83 ec 10 48 8b bf 20 01 00 00 <48> 8b 07 ff 90 98 00 00 00 85 c0 0f 84 fd 01 00 00 48 8b bb f8 00
/var/log/messages-20221221-Dec 20 17:04:43 machine systemd[1]: Started Process Core Dump (PID 48795/UID 0).
/var/log/messages-20221221-Dec 20 17:04:43 machine systemd-coredump[48797]: Resource limits disable core dumping for process 29650 (gnome-control-c).
/var/log/messages-20221221-Dec 20 17:04:43 machine systemd-coredump[48797]: Process 29650 (gnome-control-c) of user 1003 dumped core.
/var/log/messages-20221221-Dec 20 17:04:43 machine systemd[1]: systemd-coredump: Deactivated successfully.
/var/log/messages-20221221-Dec 20 17:04:43 machine systemd[4957]: app-glib-gnome\x2dpower\x2dpanel-29650.scope: Consumed 45.368s CPU time.
/var/log/messages-20221221-Dec 20 17:04:43 machine gnome-shell[48833]: The XKEYBOARD keymap compiler (xkbcomp) reports:
/var/log/messages-20221221-Dec 20 17:04:43 machine gnome-shell[48833]: > Warning:          Unsupported maximum keycode 708, clipping.
/var/log/messages-20221221-Dec 20 17:04:43 machine gnome-shell[48833]: >                   X11 cannot support keycodes above 255.
Comment 1 Neil Hanlon 2023-01-03 19:50:38 UTC 
seems the same source as #2156613 i.e., from wireplumber.


did some digging and found 

https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/193
Comment 2 Bastien Nocera 2023-01-11 09:42:41 UTC 
Please use abrt or coredumpctl to capture a backtrace of the crash. If in doubt how to do this, please contact your support representative.
Comment 3 JL 2023-07-31 14:45:50 UTC 
I stopped using RHEL derived distro
Comment 4 RHEL Program Management 2023-09-18 11:07:20 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-18 11:09:37 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.