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 87405 - no way to configure panel without hide buttons
no way to configure panel without hide buttons
Status: RESOLVED DUPLICATE of bug 82642
Product: gnome-panel
Classification: Other
Component: panel
2.0.x
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-07-05 06:56 UTC by Trevor Spiteri
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Trevor Spiteri 2002-07-05 06:56:30 UTC 
When I create a panel (not an edge panel), add one item to it and disable
the hide buttons, I cannot configure the panel, because anywhere I
right-click on will give me the applet menu, not the panel menu. This means
that I cannot add to, create or delete the panel, or access its properties
or global preferences, without moving all its applets to another panel.
Comment 1 jensflorian 2002-07-05 19:45:44 UTC 
You could hit ALT-F1 to open the panel menu. In this menu you are able
to delete this panel but NOT changing the properties of the panel. A
excellent solution would to add "Properties Option" and change it to
something like ALT-F10 or so.

Anyway it seems that this is going to be removed too
(http://bugzilla.gnome.org/show_bug.cgi?id=87275) - this will leave
such a configured panel completely useless.
Comment 2 jensflorian 2002-07-05 20:03:05 UTC 
I see that the idea to add the "properties" option is taken into
account (http://bugzilla.gnome.org/show_bug.cgi?id=85619). 

There's another annoying error: Open the options menu with ALT-F1 then
try to add anything to the panel. It will add the apps to the upper
main panel and not to the panel where it belongs.
Comment 3 Heath Harrelson 2002-07-06 04:12:31 UTC 
The main part of this bug is a duplicate of bug 82642, and the
remainder is covered elsewhere, so I'm marking duplicate.

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