Summary: | gnome panel can be coverd by maximize window when using xcompmgr | ||
---|---|---|---|
Product: | xorg | Reporter: | Kanru Chen <kanru.96> |
Component: | App/xcompmgr | Assignee: | Xorg Project Team <xorg-team> |
Status: | CLOSED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | andre.bugs, burner, leio, s7wvntw02, sam |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Kanru Chen
2004-08-25 20:25:07 UTC
ps. test under Debian, nVidia GF4 MMX using nv or nvidia driver I can confirm this. I made a dump of the window manager hints for the panel
window before and after running xcompmgr. This is the diff:
2c2
< window state: Normal
---
> window state: Withdrawn
5,6d4
< _NET_WM_DESKTOP(CARDINAL) = 4294967295
< _NET_WM_STATE(ATOM) = _NET_WM_STATE_SKIP_PAGER, _NET_WM_STATE_SKIP_TASKBAR
(< lines were removed, > lines were new)
Highly annoying.
You should be able to get it fixed by killing metacity and running it again (the latter should be automatic). Works for me this way. That is, it appears that GNOME and/or metacity gets messed up regarding some ICCCM/EWMH hints, and gets fixed by a metacity reinitialization (relaunch). KDE's kicker/kwin seems to be free from this problem, so I wouldn't be sure if this is a xcompmgr or GNOME/metacity problem. See http://lists.freedesktop.org/archives/xorg/2005-October/010679.html for the full details about this problem and the proposed solution. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.