Bug 227762 - panel blocks clicking on objects when a window is fullscreened over it with desktop effects on.
Summary: panel blocks clicking on objects when a window is fullscreened over it with d...
Status: RESOLVED DUPLICATE of bug 217560
Alias: None
Product: plasma4
Classification: Unmaintained
Component: containment-panel (show other bugs)
Version: 4.9-git
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-20 01:23 UTC by Chris Rizzitello
Modified: 2013-06-09 08:36 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Rizzitello 2010-02-20 01:23:04 UTC
Version:           4.4.0 (using KDE 4.4.0)
Compiler:           packages from kubuntu
OS:                Linux
Installed from:    Ubuntu Packages

this bug requires:
      desktop effects enabled. (have not tested different plugin combos). 
      a panel set to auto-hide
      full-screen window.

if you have a full-screened window above an-auto hidden panel with desktop effects enabled you are unable to click anywhere in the area the panel is drawn, although the panel is not shown and you can't click on its widgets.

the easiest way to see the bug is to fullscreen a program either with is built in method (i.e. firefox f11) or by kwin's menu (advanced->fullscreen). either way it will result in the same thing...after full-screening try to right click on where your panel would be if it were being drawn. you will not get a menu... and be unable to click on the any items in that area also your pointer won't change to refelect the objects its over.the panel will just block any items there..

i have noticed that if the panel is not set on auto-hide this issue is not present.or if you suspend desktop effects.also the unclickable zone is bound to the default hight of the a panel but can affect any screen edge a panel is on.
Comment 1 Chris Rizzitello 2010-02-20 01:26:29 UTC
i have tested this on both my desktop and my netbook (where i first noticed it).
one is intel video the other ati. so i don't think that its a video issue.
Comment 2 Rob Walker 2010-09-08 10:06:45 UTC
I also see the same behaviour with ubuntu 10.04 (KDE 4.4.2) using vmware, virtualbox or krdc
Comment 3 Thomas Lübking 2012-03-17 13:36:11 UTC
Sorry for the delay.

It is not related to compositing, the panel proxy hangs around there.
Reassining to plasma.
Reason: the proxy may remain on top, but the size is probably not required (i've tried other autohiding implementations and they to not expose this behavior for being only 1-2px thick and/or being NET_WM_TYPE_DOCK, thus managed and stacked)

Ultimately there should probably be a NETWM type for these things.

xwininfo
----------------------------------
xwininfo: Please select the window about which you
          would like information by clicking the
          mouse in that window.

xwininfo: Window id: 0x12030c2 (has no name)

  Absolute upper-left X:  0
  Absolute upper-left Y:  0
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 1630
  Height: 30
  Depth: 0
  Visual: 0x21
  Visual Class: TrueColor
  Border width: 0
  Class: InputOnly
  Colormap: 0x0 (not installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: yes
  Corners:  +0+0  --30+0  --30-1170  +0-1170
  -geometry 1630x30+0+0
----------------------------------

xprop
----------------------------------
XdndAware(WINDOW): window id # 0x5
Comment 4 Myriam Schweingruber 2012-05-16 18:36:06 UTC
Thomas: which version did you test this with? The last report was about KDE 4.4.x which is really outdated.
Comment 5 Thomas Lübking 2012-05-16 18:50:05 UTC
4.8.1 or 4.8.2 for plasma-desktop/libplasma
git master, ie. to become 4.9 of kwin
Comment 6 Myriam Schweingruber 2012-06-03 18:56:22 UTC
Thank you for the fast feedback. JFYI; you should be able to set the version field anc change the status yourself.
Comment 7 Martin Flöser 2013-06-09 08:36:55 UTC

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