[regression] Inactive menus are not greyed out

[Timmmm]

Ubuntu 11.10
Unity 4.24.0-0ubuntu2b1

1. start deluge
2. see the 'Torrent' menu item

What happens:
the menu item is actually greyed out but in unity its shown as if its clickable, clicking it a few time makes it brighter and brighter

What should happen:
the menu item should be greyed out

=====Original Report=====
I just did a totally clean install of Ubuntu 11.10 and installed Qt Creator. Very weird bug, which I am certain is in unity rather than Qt Creator (since the menu has always worked properly without unity).

Basically, make Qt Creator full-screen, then hover on the title bar to make the menu appear. Click "Build". The menu doesn't open, but it does kind of get brighter, weirdly.

This only happens with the build menu. All other menus work properly, and you can click on other menus and then pan to the build menu as expected.

Note this is without any project loaded. I suspect the reason for this bug is because every item in the build menu is disabled. Perhaps unity is misguidedly trying to be "helpful" here?

[Omer Akram (om26er)]

What happens when a project is loaded? Does the 'build' menu work fine then? Could you start a gnome-shell session and there note if the menu is actually greyed out in that session when no project is loaded.

Menu getting brighter have happened in the past and bug 871327 is quite similar, its just for the dash button.

[Timmmm (tdhutt)]

Yes, when a project is loaded (so that some of the menu items are
enabled) it works. I tried to use the switch user thing to start a
gnome shell (I assume that's how you are supposed to do it), but...
well... if I want to spend an enjoyable afternoon filing bug reports I
know where to go!

I got to the greeter/login window bit. It all looks very good but the
power/volume buttons in the top right corner of the screen don't react
to clicks, and there appears to be no option to choose a login
environment (gnome/unity/kde etc).

So I tried to log back in as myself. Unfortunately, the screen went
blank and I was presented only with a *very* laggy cursor. I tried a
few CTRL-ALT-F?'s and managed to get back to my desktop but the window
manager had totally died, and there was no way to restart it. Even
CTRL-ALT-BACKSPACE seems to have been disabled. I eventually had to
resort to a hard reset!

Anyway, I doubt investigating that and filing bug reports would have
much effect, and I am rambling off topic. Basically I didn't manage to
run Qt Creator in a non-unity environment, but I seem to recall that
the build menu is indeed disabled if all submenus are disabled. I
can't recall what happens when you click it though.

... And I just found a screenshot that confirms it:
http://www.kitware.com/InfovisWiki/images/7/7f/Qt-creator-welcome.png
(There are other screenshots that don't show this so I guess they
changed it at some point.)

In which case, this bug should be "Disabled menus aren't displayed as such."

Cheers

On 6 December 2011 12:55, Omer Akram <email address hidden> wrote:
> What happens when a project is loaded? Does the 'build' menu work fine
> then? Could you start a gnome-shell session and there note if the menu
> is actually greyed out in that session when no project is loaded.
>
> Menu getting brighter have happened in the past and bug 871327 is quite
> similar, its just for the dash button.
>
> ** Also affects: unity (Ubuntu)
>   Importance: Undecided
>       Status: New
>
> ** Changed in: unity
>       Status: New => Incomplete
>
> ** Changed in: unity (Ubuntu)
>       Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/898259
>
> Title:
>  Hidden global menu breaks Qt Creator's "build" menu.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/898259/+subscriptions

[Omer Akram (om26er)]

a similar bug (i reported) was fixed in last cycle, could you confirm if thats what you are facing? bug 733740

[Timmmm (tdhutt)]

On 6 December 2011 16:09, Omer Akram <email address hidden> wrote:
> a similar bug (i reported) was fixed in last cycle, could you confirm if
> thats what you are facing? bug 733740

Yes that is an additional bug. There are two bugs:

1. The disabled menu gets brighter when clicked (fixed as bug 733740).
2. The disabled menu isn't drawn greyed out (this bug; not fixed).

[Omer Akram (om26er)]

its a regression so Medium.

[Bilal Akhtar (bilalakhtar)]

Reproducible on Quantal

[Bilal Akhtar (bilalakhtar)]

This test Python script demonstrates the issue,