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 126427 - Launcher Properties dialog incorrectly tries to always stay on top
Launcher Properties dialog incorrectly tries to always stay on top
Status: RESOLVED DUPLICATE of bug 96140
Product: metacity
Classification: Other
Component: general
unspecified
Other Linux
: High normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
AP2
: 126220 127312 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-11-07 11:05 UTC by Malcolm Tredinnick
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
probable fix. (1.65 KB, patch)
2003-11-27 07:04 UTC, Arvind S N 		none Details | Review

Description Malcolm Tredinnick 2003-11-07 11:05:39 UTC 
When adding a launcher to the panel via Panel menu->Add to
panel->Launcher.., I clicked on the Icon button. This opened up a dialog
box containing the icon possibilities.

Unfortunately, due to whataver window hints are involved, the new dialog
box opened up underneath the "Launcher Properties" dialog box and cannot be
raised above it. In fact, the Launcher Properties dialog tries to stay on
top of everything, including other windows (only noticed this while trying
to run xprop on the window -- couldn't raise the terminal window).
Comment 1 Arvind S N 2003-11-27 07:04:26 UTC 
Created attachment 21855 [details] [review]
probable fix.
Comment 2 Arvind S N 2003-11-27 07:12:55 UTC 
havoc,rob : This bug is in metacity. The window->layer for the
transients of the panel have to be set correctly. Does this fix
make sense ?
Comment 3 Arvind S N 2003-11-27 09:01:02 UTC 
*** Bug 126220 has been marked as a duplicate of this bug. ***
Comment 4 padraig.obriain 2003-11-27 17:35:13 UTC 
*** Bug 127312 has been marked as a duplicate of this bug. ***
Comment 5 Rob Adams 2003-11-27 17:38:22 UTC 
what version of metacity did you see this in?  This works fine for me
using either HEAD or 2.6.2.
Comment 6 padraig.obriain 2003-11-28 08:40:44 UTC 
I see this problem using metacity from HEAD.
Comment 7 Havoc Pennington 2003-12-07 20:43:31 UTC 
The fix is more complicated than that, see bug #96140

Note that get_standalone_layer() is called that because it gets the
layer of the window absent interactions with transients or application
group.


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