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:
We found some errors logged in syslog about gnome-shell. The reason why we report this issue is that the customer has to make sure there are no reoccurring errors/warnings in the log files.
Version-Release number of selected component (if applicable): 3.32.2-14.el8
How reproducible: Always. 3/3 test systems show this behaviour.
Steps to Reproduce:
1. Login to Gnome classic with a user
2. Click on the lock button
3. Messages are printed to syslog
Actual results:
Sep 21 16:44:00 testhost gnome-shell[178149]: Object .Gjs_DelegateFocusNavigator (0x5574cc373320), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 21 16:44:00 testhost org.gnome.Shell.desktop[178149]: == Stack trace for context 0x5574cbbaa320 ==
Sep 21 16:44:00 testhost org.gnome.Shell.desktop[178149]: #0 5574cbe7d990 i resource:///org/gnome/shell/ui/workspacesView.js:719 (7f671431dc10 @ 23)
Expected results: No messages upon normal operation.
Additional info:
* Customer case linked.
Comment 13Michael Boisvert
2021-01-26 17:58:25 UTC
I do not see any untoward messages in the logs on my 8.4 system running gnome-shell-3.32.2-27.el8. Oliver, perhaps you could provide the customer with the updated package to test on their systems?
Comment 17Michael Boisvert
2021-02-01 20:44:11 UTC
Going ahead with verification as the due date is today, please let me know if there are any issues Yaniv.
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 (Moderate: GNOME security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:1586
Description of problem: We found some errors logged in syslog about gnome-shell. The reason why we report this issue is that the customer has to make sure there are no reoccurring errors/warnings in the log files. Version-Release number of selected component (if applicable): 3.32.2-14.el8 How reproducible: Always. 3/3 test systems show this behaviour. Steps to Reproduce: 1. Login to Gnome classic with a user 2. Click on the lock button 3. Messages are printed to syslog Actual results: Sep 21 16:44:00 testhost gnome-shell[178149]: Object .Gjs_DelegateFocusNavigator (0x5574cc373320), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 21 16:44:00 testhost org.gnome.Shell.desktop[178149]: == Stack trace for context 0x5574cbbaa320 == Sep 21 16:44:00 testhost org.gnome.Shell.desktop[178149]: #0 5574cbe7d990 i resource:///org/gnome/shell/ui/workspacesView.js:719 (7f671431dc10 @ 23) Expected results: No messages upon normal operation. Additional info: * Customer case linked.