Bug 550640 - Unable to click outermost edge
Summary: Unable to click outermost edge
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 597013 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-26 15:45 UTC by Hernán Schmidt
Modified: 2018-04-11 09:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 597013 (view as bug list)
Environment:
Last Closed: 2010-12-04 01:12:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hernán Schmidt 2009-12-26 15:45:54 UTC
Description of problem:
With compiz enabled, I cannot click on the outermost edge of my screen.

How reproducible:
Every time.

Steps to Reproduce:
1. Enable compiz
2. Move cursor to the top edge of the screen, above the "Applications" menu.
3. Click.
  
Actual results:
Nothing happens.

Expected results:
This should open the "Applications" gnome-panel menu, which is what happens with compiz disabled.


Additional info:
- This bug applies to ALL edges, not just the top one.
- The edges don't work, BUT the corners do, ie. if I move the cursor to the top-left corner and click, this opens the Applications menu; likewise the bottom-right corner opens the Trash.

Comment 1 warcry.spam 2010-02-07 14:01:06 UTC
This happens to me too.

Comment 2 cobra the joker 2010-03-05 16:49:25 UTC
same here also .

Comment 3 cobra the joker 2010-03-07 18:03:25 UTC
It was fixed when i enabled the Desktop Cube .
wasnt fixed when i enabled the desktopWall.

Comment 4 James 2010-03-07 20:34:34 UTC
I find enabling the "Rotate Cube" plugin makes the outermost pixels unclickable.

Comment 5 Matěj Cepl 2010-05-28 08:49:05 UTC
Per bug 597013 reproducible also on F13.

Comment 6 Matěj Cepl 2010-05-28 08:49:18 UTC
*** Bug 597013 has been marked as a duplicate of this bug. ***

Comment 7 Bug Zapper 2010-11-04 02:31:09 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 James 2010-11-04 08:11:45 UTC
Still present in F14, please update Release field.

Comment 9 James 2010-11-04 08:13:03 UTC
Still present in F14, please update Release field.

Comment 10 Bug Zapper 2010-12-04 01:12:38 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.