GNOME Bugzilla – Bug 747650
Window close button for active window
Last modified: 2015-07-08 17:29:01 UTC
Created attachment 301319 [details] Screenshot of described issue With the recent upgrade to GNOME 3.16 the close button for any active window looks different than for any other window. It basically looks as if I was hovering over it with the mouse all of the time. This wasn't the case beforehand and looks inconsistent, especially when when dealing with multiple screens, since the title bar of the active window looks visibly different than the other one.
I think you have some issue with the theme on your system - this isn't happening in general.
this bug is fixed with the css changes here: https://bbs.archlinux.org/viewtopic.php?pid=1519016#p1519016 Owen, it affects at least all archlinux users, please take a look at the forum post above for more infos
I can confirm this bug on archlinux, although it's only happening in one of the two systems on which I'm running arch. What could be the difference between the two?
I see this strange "X"-button -- after next actions: logout (to GDM) and login-again (to GNOME) . OS -- archlinux
oh, very sorry (recently, my message is not quite true) .. there is NO direct-simple-relation with logout(to-GDM)-and-relogin(to-GNOME).
Can confirm this bug... But don't understand why mutter suddenly start to draw button as hovered...
https://bbs.archlinux.org/viewtopic.php?pid=1519016#p1519016 This tips doesn't fix the bug for me... Think it's inside source code... Can you point me which part of gnome shell source code is drawing buttons for ssd?
Same problem here on Arch Linux. When it happens, restarting the shell fixes it -- for a little while. Odd thing is that the cursor doesn't change to indicate the window is resizable on all the right side of the window when the bug is triggered. Only the left side seems to respond correctly.
Same problem here in Arch Linux. Restarting the shell helps, but it starts happening again after a point. Also resizing has the problems indicated in Comment 8.
Just to say that, at least at my Archlinux system, issue appears only with non-CSD windows (e.g. all GTK2 apps or e.g. gnome-terminal 3.16.x) and involved also minimized and maximized button (not only the close button)... With CSD windows issue is not present and titlebar button are drawned correctly also odd thing reported at https://bugzilla.gnome.org/show_bug.cgi?id=747650#c8 affected only non-CSD windows when main issue occurred Regards Andrea
Same mutter problem confirmed in two different computers (both with gnome 3.16): one with archlinux using default Adwaita theme, and other with Antergos using numix theme.
I also confirming it only happens on non-CSD windows. Just noticed something interesting: - Open a non-CSD window (a terminal) - Click on minimize button - Move the cursor away - Alt-tab to the minimized window - The minimized button will be hovered even though the cursor is away. Moving the cursor back to the window will correct it. Might be related.
Confirm this bug, archlinux using default Adwaita theme.
I am also facing this issue on Arch Linux since I updated to GNOME 3.16. Only non-CSD windows are affected. The workaround mentioned in https://bbs.archlinux.org/viewtopic.php?pid=1519016#p1519016 fixed it at the beginning, but now it is not working anymore. I think another update broke this fix as well.
Please don't keep adding "me too" comments - it is obvious that *some* users are affected by this, what we need instead is information about what differentiates affected systems from unaffected ones.
For a data point, when I ran under jhbuild on F21, this bug happened to me. When I upgraded to F22, it went away. I'm not exactly sure which component was out-of-date -- is there anything left in gnome-themes-standard which might need to be updated?
(In reply to Jasper St. Pierre from comment #16) > is there anything left in gnome-themes-standard which > might need to be updated? I don't think so. Could it be an input issue instead, where we get the actual hover state wrong rather than the drawing?
I don't think so. I do remember that the pressed state didn't take effect, either.
This is strange, but happens on: - Debian SID - Ubuntu - ArchLinux But not in Fedora!
Can someone see if https://git.gnome.org/browse/mutter/commit/?id=12771a555a9954ba9f002b7e422385cf2e904e86 fixes the problem? I have a hunch it's related.
Jasper, I applied the patch, and I've been unable to trigger the bug since. I've only tested for one hour. Great finding anyway :)
Any fix for a 3.16.3 release? Do we need to wait for GNOME 3.18?
It's on the 3.16 branch so whenever a 3.16.3 is released it will be included.
On Debian, with libmutter0f 3.16.2-2 (amd64), the patch below can be applied directly (hot fix). Opening libmutter.so in GHex, looking for "81C150010000", replacing the "50" by "C8" (the new sizeof value) and save it. Mutter will be instantly reloaded and the glitch is gone.