After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 660026 - Smooth window edges doesn't work for all parent windows
Smooth window edges doesn't work for all parent windows
Status: RESOLVED DUPLICATE of bug 659302
Product: mutter
Classification: Core
Component: general
3.1.x
Other Linux
: High critical
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-24 18:18 UTC by Alex Hultman
Modified: 2011-09-24 21:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The upper window has jagged edges (134.56 KB, image/png)
2011-09-24 18:18 UTC, Alex Hultman 		Details

Description Alex Hultman 2011-09-24 18:18:06 UTC 
Created attachment 197409 [details]
The upper window has jagged edges

When a window gets underneath that Mac OS X drop-down child window, the smooth edges turn into white jagged edges.

Start the terminal, type su and enter password. Now close the window, making a warning window slide out of the terminal causing this glitch.

Gallium3D Mesa for AMD/ATI 7.11-4
Comment 1 Jasper St. Pierre (not reading bugmail) 2011-09-24 18:59:04 UTC 
What version of gnome-shell are you using?
Comment 2 Alex Hultman 2011-09-24 21:26:44 UTC 
3.1.91. Haven't gotten the rc yet. Also, I'm trying to report less duplicates / nonsense, just so you know :)
Comment 3 Jasper St. Pierre (not reading bugmail) 2011-09-24 21:35:16 UTC 
(In reply to comment #2)
> 3.1.91. Haven't gotten the rc yet. Also, I'm trying to report less duplicates /
> nonsense, just so you know :)

I'd rather have fifteen duplicates and nonsense than miss a bug. Please file as many bugs as you can.

--

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

Fixed in 3.1.92

*** This bug has been marked as a duplicate of bug 659302 ***