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 329980 - metacity -- toggle_shade leaves wireframe outline when shaded
metacity -- toggle_shade leaves wireframe outline when shaded
Status: RESOLVED DUPLICATE of bug 156543
Product: metacity
Classification: Other
Component: general
2.12.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2006-02-05 09:32 UTC by ray
Modified: 2006-02-06 21:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description ray 2006-02-05 09:32:50 UTC
Please describe the problem:
metatcity is configured for "action_double_click_toolbar" to be toggle_shade and
nautils is stopped and has "background_set" to false such that xroot is a real
colour and not taken over by nautilus (such that "xsetroot -solid slateblue4"
actually changes the color)

when you double click a window, it will become shaded but the wireframe exists
drawn on the desktop/root window and only disappears if you drag another window
over the wireframe -- something is not getting refreshed correctlh

Steps to reproduce:
1. metatcity is configured for "action_double_click_toolbar" to be toggle_shade
2. nautils is configured for "background_set" to false
3. disable nautilus from running and quit metacity and restart
4. xsetroot -solid slateblue4
5. start an application (xterm etc)
6. double click toolbar to shade window

Actual results:
wireframe of window is still shown even when the window is supposed to be shaded

Expected results:
shaded, wireframe not visible

Does this happen every time?
yes

Other information:
Comment 1 Elijah Newren 2006-02-06 21:40:49 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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