Gnome main menu can't be activated when clicking at the top of the screen

Bug #174999 reported by Oded Arbel on 2007-12-08
6
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Undecided
Unassigned

Bug Description

This problem appears only when "desktop effects" is enabled - with out it the menu access is OK:

The problem is that for good usability you want the main menu to be very accessible. In Ubuntu's GNOME this requirement is met by positioning the menu on the top left corner of the screen making the target size to hit it infinite in size (see Fits Law). The problem is that with "desktop effects" enabled if the cursor is thrown to the top left corner then it can't activate the menu - although it looks like it should, clicking the first 2 top most pixels of the screen does not trigger the menu (or any other launcher for that matter - it might not actually hit the panel).

The result is very poor usability - a-la MS-Windows 95 through 2000 where the start button was a few pixels off from the bottom left corner - making it difficult to hit as you have to either carefully approach the menu in order to click it or throw the mouse to the top of the screen and then bring it back just a bit.

Sebastien Bacher (seb128) wrote :

That looks like a compiz configuration issue, that's not an issue using the standard installation

John Arthur Fensome (fensj) wrote :

NOT just a compiz problem, I have tried it with effects OFF and ON.

Sorry should have mentioned using Ubuntu 7.10 and a small 2 pixel square seems to appear instead.

Trying to run the Main Menu tool(s) even after re-installing them (via synaptic) does not fix things

HELP!
URGENT!

How do we do anything if we cannot access our apps?

JAF

@John It sounds as if you might have a different issue. You might want to open a separate bug report it this continues to occur.

I'm marking this confirmed as the bugs that are duplicates show this as still occurring on Hardy.

Changed in compiz:
status: New → Confirmed
Glenn (glenn-v) wrote :

Sounds like this is caused by bug #103306.

Jeffrey Baker (jwbaker) wrote :

I doubt that, since 103306 predates Gutsy, and Gutsy doesn't have this defect.

Travis Watkins (amaranth) wrote :

It's a regression, this is a dupe of bug 103306.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers