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
** Changed in: mutter (Ubuntu
Same bug in Ubuntu 19.10.
Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x350
not in stack
Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x350
not in stack
Dec 25 9:50:28 PM gnome-shell: STACK_OP_RAISE_ABOVE: sibling window 0x350
not in
@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.
--
You received this bug notificati
@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 v
@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.
--
You received this bug notification because you ar
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
** No longer affects: systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE_ABOVE: window not in stack
To manage notifications about this bug go to:
https://bugs.launc
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STAC
still see this (log flooded with mutter warnings "window xx..xx not in
stack") on Ubuntu Gnome 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE_ABOVE: window not in
** Bug watch added: Red Hat Bugzilla #1280194
https://bugzilla.redhat.com/show_bug.cgi?id=1280194
** Also affects: mutter (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1280194
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a m
** Tags removed: vivid wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE_ABOVE: window not in stack
To manage notifications about this bug go to:
https://bugs.launchp
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE_ABOVE: window not in stack
To manage notifications about this bug go to:
https://bugs.launchpad.net
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE
I see this (log flooded with mutter warnings "window xx..xx not in
stack") on Ubuntu Gnome 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE_ABOVE: window not in sta
** Changed in: ubuntu-gnome
Milestone: vivid => xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE_ABOVE: window not in stack
To manage notifications about this
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 0x341
(Atom)
Oct 19 20:55:04 hostname gnome-session[2580]: Window manager warning: Buggy
client sent a _NET_A
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425349
Title:
STACK_OP_RAISE_ABOVE: window not in stack
To manage notifications about this bug go to:
https://bugs.launchpad.net/m
** Description changed:
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 0x1d5011a not in
- stack]
+ gnome-session[1551]: message repeated 26 times: [ (gnome-shell:163
not only met on ubuntu/debian
https://bugzilla.redhat.com/show_bug.cgi?id=1159470
** Bug watch added: Red Hat Bugzilla #1159470
https://bugzilla.redhat.com/show_bug.cgi?id=1159470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Description changed:
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 0x1d5011a not in
stack]
+ gnome-session[1594]: Window manager warning: Buggy client sent
20 matches
Mail list logo
