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.
Bug 1962756 - [abrt] [faf] gnome-control-center: raise(): /usr/bin/gnome-control-center killed by 6
Summary: [abrt] [faf] gnome-control-center: raise(): /usr/bin/gnome-control-center kil...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-control-center
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Bastien Nocera
QA Contact: Michal Odehnal
URL: http://faf.lab.eng.brq.redhat.com/faf...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-20 15:11 UTC by Michal Odehnal
Modified: 2021-10-06 10:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-06 10:33:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
coredumpctl gdb log (59.03 KB, text/plain)
2021-05-20 15:11 UTC, Michal Odehnal
no flags Details

Description Michal Odehnal 2021-05-20 15:11:03 UTC
Created attachment 1785239 [details]
coredumpctl gdb log

This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/bdf9203d36cd800efbe7d9ddf10fbb761943a65d/

Comment 1 Michal Odehnal 2021-05-20 15:18:56 UTC
This is the affected version gnome-control-center-40.0-11.el9.x86_64 as i noticed the FAF does not have the usual data.

Comment 2 Tomas Popela 2021-05-21 09:11:19 UTC
Looking at the backtrace that is in FAF:

power_profiles_properties_changed_cb

Bastien might know.

Comment 3 Bastien Nocera 2021-05-21 09:25:36 UTC
Looks like:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/974

It's likely that this is a side effect of power-profiles-daemon not running in the background, which it should be by default.

Comment 4 Tomas Popela 2021-09-14 08:32:39 UTC
@modehnal do you know if this is still happening? @bnocera do you know if the change mentioned in comment 3 is part of RHEL 9?

Comment 5 Michal Odehnal 2021-09-14 08:47:51 UTC
I have not seen it lately I believe, probably can be closed as current version?

Comment 6 Bastien Nocera 2021-09-15 08:31:56 UTC
(In reply to Tomas Popela from comment #4)
> @bnocera do you know if the change mentioned in comment 3 is part
> of RHEL 9?

It is. It's also a side effect of:
https://bugzilla.redhat.com/show_bug.cgi?id=2000134

Comment 7 Bastien Nocera 2021-10-06 10:33:04 UTC
This was fixed in a newer version of gnome-control-center, closing.


Note You need to log in before you can comment on or make changes to this bug.