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 1845490 - Errors from gnome-shell locking screen
Summary: Errors from gnome-shell locking screen
Keywords:
Status: CLOSED DUPLICATE of bug 1751121
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-09 11:28 UTC by Oliver Falk
Modified: 2024-10-01 16:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-09 18:34:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Oliver Falk 2020-06-09 11:28:36 UTC 
Description of problem:
When locking the screen, errors are logged.

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


How reproducible: Always


Steps to Reproduce:
On a vanilla RHEL 7.8
1. Click lock in Gnome
2. Checking the messages you'll see something like the following logged:

    gnome-shell[<pid>]: JS WARNING: [resource:///org/gnome/shell/ui/popupMenu.js 717]: reference to undefined property "_delegate"

On some systems another message appears:

    gnome-shell[<pid>]: JS ERROR: TypeError: super._onDestroy is not a function
                                        _onDestroy@/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js:457:9
                                        destroy@resource:///org/gnome/shell/ui/panelMenu.js:192:9
                                        wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                        destroy@/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js:708:9
                                        disable@/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js:722:5
                                        disableExtension@resource:///org/gnome/shell/ui/extensionSystem.js:83:9
                                        disableAllExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:378:13
                                        disableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:377:9
                                        _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:395:9
                                        _emit@resource:///org/gnome/gjs/modules/signals.js:128:27
                                        _sync@resource:///org/gnome/shell/ui/sessionMode.js:204:9
                                        wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                        pushMode@resource:///org/gnome/shell/ui/sessionMode.js:166:9
                                        wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                        activate@resource:///org/gnome/shell/ui/screenShield.js:1281:17
                                        wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                        lock@resource:///org/gnome/shell/ui/screenShield.js:1330:9
                                        wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                        activateLockScreen@resource:///org/gnome/shell/misc/systemActions.js:403:9
                                        wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                        _createSubMenu/<@resource:///org/gnome/shell/ui/status/system.js:289:13
     gnome-shell[<pid>]: clutter_actor_get_parent: assertion 'CLUTTER_IS_ACTOR (self)' failed


Actual results: Errors in the log files, which is an unwanted behaviour for my customer.


Expected results: No errors are logged under normal circumstances, esp. for normal actions like locking the screen.


Additional info:
Attaching customer case.
Comment 2 Florian Müllner 2020-06-09 14:31:31 UTC 
(In reply to Oliver Falk from comment #0)
> 1. Click lock in Gnome
> 2. Checking the messages you'll see something like the following logged:
> 
>     gnome-shell[<pid>]: JS WARNING:
> [resource:///org/gnome/shell/ui/popupMenu.js 717]: reference to undefined
> property "_delegate"

It's unclear what triggers that warning, but it's easy to shut up if that's deemed important.


> On some systems another message appears:
> 
>     gnome-shell[<pid>]: JS ERROR: TypeError: super._onDestroy is not a
> function

Again, that's already handled in https://bugzilla.redhat.com/show_bug.cgi?id=1782102.
Comment 3 Florian Müllner 2020-06-09 18:34:22 UTC 
For the sake of simplicity, one "Various JS warnings" bug is enough; let's track the bits that haven't dedicated issues yet in #1751121.

*** This bug has been marked as a duplicate of bug 1751121 ***
Note You need to log in before you can comment on or make changes to this bug.