After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 525756 - "Application" menu on keyboard invoke appears misplaced when using auto-hide gnome-panel
"Application" menu on keyboard invoke appears misplaced when using auto-hide ...
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: panel
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 576261 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-02 13:18 UTC by Sebastien Bacher
Modified: 2020-11-06 20:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Sebastien Bacher 2008-04-02 13:18:23 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/209666

"$ apt-cache policy gnome-panel

1:2.22.0-0ubuntu2

While invoking Menu from keyboard (default: <Alt>F1), Application list appears at the height of hidden panel size (/apps/panel/toplevels/top_panel_screen0/auto_hide_size), secondly panel un-hides and appears behind the menu. This happen regardless if panel hiding animations are on or off. I'm not sure whether this considers compiz or gnome-panel itself.

Menu should appear at the height of un-hidden panel, or panel should un-hide before menu is drawn."
Comment 1 Vincent Untz 2009-06-18 07:40:41 UTC 
*** Bug 576261 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2020-11-06 20:21:51 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

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