STACK_OP_RAISE_ABOVE: window not in stack

[dino99]

Since a while logs are fullfilled by such error:

gnome-session[1551]: message repeated 26 times: [ (gnome-shell:1636): mutter-WARNING **: STACK_OP_RAISE_ABOVE: window 0x1d50100001a not in stack]
(from:
http://code.metager.de/source/xref/gnome/Desktop/mutter/src/core/stack-tracker.c#86 )

gnome-session[1594]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000086

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mutter 3.14.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-6.6-generic 3.19.0
Uname: Linux 3.19.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Wed Feb 25 02:49:58 2015
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

[Tim Lunn (darkxst)]

dino99, can you file this in debian bug tracker as well, and link bug here.

[dino99 (9d9)]

hi Tim,

that issue is already known from Debian, and also point to the missing commit. I says 'missing' because prior 3.14.? version this was not seen into the logs (syslog/journalctl).

Possibly that "Drop git patches included in new release" have dropped a bit too much ?

mutter (3.14.3-0ubuntu1) vivid; urgency=medium

  * New upstream release
  * Drop git patches included in new release

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776018

[Alberto Salvia Novella (es20490446e)]

@ Tim

You have set this bug status to triaged without assigning a priority.

[Alberto Salvia Novella (es20490446e)]

@ Tim

Please, set the milestone back for the Ubuntu GNOME project. I am sorry I removed it by mistake, and I cannot bring it back.

[Tim Lunn (darkxst)]

That linked patch is already included in mutter that is in vivid.

[dino99 (9d9)]

Looks like the graphic stack does not like systemd rules:

oem@u32:~$ systemctl status mutter
● mutter.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

oem@u32:~$ systemctl status clutter
● clutter.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

oem@u32:~$ systemctl status mesa
● mesa.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

[dino99 (9d9)]

oem@u32:~$ systemctl restart mesa
Failed to restart mesa.service: Unit mesa.service failed to load: No such file or directory.

oem@u32:~$ systemctl restart clutter
Failed to restart clutter.service: Unit clutter.service failed to load: No such file or directory.

oem@u32:~$ systemctl restart mutter
Failed to restart mutter.service: Unit mutter.service failed to load: No such file or directory.

[dino99 (9d9)]

Well, using nautilus 'search' utility to find those xxx.service files, none are found.

[dino99 (9d9)]

not only met on ubuntu/debian https://bugzilla.redhat.com/show_bug.cgi?id=1159470

[Bruce Pieterse (octoquad)]

I get this message when lauching atom:

Oct 19 20:55:04 hostname gnome-session[2580]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400001 (Atom)
Oct 19 20:55:04 hostname gnome-session[2580]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400001 (Atom)

Service files are also missing as mentioned by dino99 on wily.

[Klaus Bielke (k-bielke)]

I see this (log flooded with mutter warnings "window xx..xx not in stack") on Ubuntu Gnome 16.04.

[dino99 (9d9)]

That error is gone now i'm using the gnome3-staging ppa with a gnome-shell session on xenial 64 bits.

mutter 3.20.1 used

[paz (mozit)]

still see this (log flooded with mutter warnings "window xx..xx not in stack") on Ubuntu Gnome 16.04.

[paz (mozit)]

any chance to have a fix for the annoying spamming or maybe someone have an idea for a workaround to stop it in Ubuntu Gnome Xenial.

[dino99 (9d9)]

Upstream has fixed that problem long time ago.
https://mail.gnome.org/archives/commits-list/2014-September/msg04244.html

As Xenial now only receive 'security' updates, but use mutter 3.18.x which should include the fix, if your system still log that error, then its time to clean the system and/or reconfigure mutter & associated packages. At last recent ubuntu versions are not spammed with this problem.

[paz (mozit)]

@dino99, I don't really know how to go about your reply. I'm using Xenial LTS and according to your answer I'm using mutter version that fixed the problem.
How do I clean/reconfigure my system. Any explanation would be very much appreciated.

[dino99 (9d9)]

@mozit

i suppose you already know these commands:
- sudo apt-get clean
- sudo apt-get autoclean
- sudo apt-get autoremove
- sudo dpkg --configure -a

To clean a bit more, gtkorphan & bleachbit can also be used.

And for the record, questions are usually asked via ubuntuforums/askubuntu; learning via the many ubuntu's wiki/howto you can find around the buntu galaxy.

[paz (mozit)]

@dino99, Thanks for the reply but as I know Ubuntu 16.04 LTS is not reaching eof just yet(April 2021). and I thought we are talking about a specific bug here that not resolved for me.
Doing the obvious cleaning/reconfiguring did not yield any healing as well.

[Clinton H (49studebaker)]

Same bug in Ubuntu 19.10.

Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x3000050 not in stack
Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x3000050 not in stack
Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x3000050 not in stack
Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x3000050 not in stack
Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x3000050 not in stack
Dec 25 9:48:29 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x300002b not in stack
Dec 25 9:48:29 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x300002b not in stack
Dec 25 9:48:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x300002b not in stack
Dec 25 9:48:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x300002b not in stack

[Daniel van Vugt (vanvugt)]

Given upstream declared this fixed in 2014 and the messages are *slightly* different, we should declare this bug fixed and open a new bug for the messages in comment #20.

Clinton, please open a new bug from your affected machine by running:

  ubuntu-bug gnome-shell