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:
Customer is trying to adapt to the changes in RHEL 7.8 and therefore is currently testing RHEL 7.8 Beta.
They noticed a new warning is logged in their environment:
Mar 05 14:31:45 hostname gnome-shell[6493]: STACK_OP_RAISE_ABOVE: sibling window 0x32001e9 not in stack
Version-Release number of selected component (if applicable): 3.28.3-24
How reproducible: Always with their (custom) application.
Steps to Reproduce:
1. Install RHEL 7.8 and run their (custom app)
I wasn't able to reproduce this with a vanilla RHEL 7.8 Beta and "some" applications.
Actual results:
Message - as seen in the description - is logged over and over again.
Expected results:
No message is logged.
Additional info:
I wasn't able to find this code in gnome-shell, but gnome-shell logged it therefore I'm assigning this to gnome-shell, but the code in question is probably in mutter (src/core/stack-tracker.c). Feel free to reassign to mutter, if that make sense.
Since this wasn't logged in RHEL 7.7, I'd say this is a regression; However, if this is hinting that the application is doing something wrong, please also let me know and point me in the right direction.
Customer case will be linked.
Comment 16Michael Boisvert
2020-06-25 12:49:50 UTC
I was able to reproduce the error using the c program Jonas provided, with mutter-3.28.3-27.el7 I can no longer trigger the warning.
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 (GNOME 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/RHBA-2020:3987
Description of problem: Customer is trying to adapt to the changes in RHEL 7.8 and therefore is currently testing RHEL 7.8 Beta. They noticed a new warning is logged in their environment: Mar 05 14:31:45 hostname gnome-shell[6493]: STACK_OP_RAISE_ABOVE: sibling window 0x32001e9 not in stack Version-Release number of selected component (if applicable): 3.28.3-24 How reproducible: Always with their (custom) application. Steps to Reproduce: 1. Install RHEL 7.8 and run their (custom app) I wasn't able to reproduce this with a vanilla RHEL 7.8 Beta and "some" applications. Actual results: Message - as seen in the description - is logged over and over again. Expected results: No message is logged. Additional info: I wasn't able to find this code in gnome-shell, but gnome-shell logged it therefore I'm assigning this to gnome-shell, but the code in question is probably in mutter (src/core/stack-tracker.c). Feel free to reassign to mutter, if that make sense. Since this wasn't logged in RHEL 7.7, I'd say this is a regression; However, if this is hinting that the application is doing something wrong, please also let me know and point me in the right direction. Customer case will be linked.