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 499148 - "Change menu" not hidden when /apps/panel/global/locked_down is true
"Change menu" not hidden when /apps/panel/global/locked_down is true
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: menu
unspecified
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-23 11:08 UTC by Martin Jürgens
Modified: 2011-05-06 11:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20

Attachments
the change seems to do the trick (1.05 KB, patch)
2009-06-17 11:50 UTC, Sebastien Bacher 		none Details | Review
the change seems to do the trick (1.05 KB, patch)
2009-06-17 11:50 UTC, Sebastien Bacher 		none Details | Review

Description Martin Jürgens 2007-11-23 11:08:20 UTC 
Please describe the problem:
When setting /apps/panel/global/locked_down to true, the Panel should be locked.

This is mostly true. But when right-clicking on the main menu of GNOME, there is still an option "Change menu". 

Steps to reproduce:
1. Set /apps/panel/global/locked_down to true
2. Right click on the GNOME-main-menu (traditional one, with Applications, Places, System)


Actual results:
"Change menu" still appears

Expected results:
"Change menu" should not appear, as the Panel is locked down.

Does this happen every time?
Yes

Other information:
Comment 1 Martin Jürgens 2008-09-01 19:51:28 UTC 
Well, what's the point in locking the desktop down when you can't lock down it completly.. I have respect to the work that has flown into GNOME but why are bugs like this just lying around? It really bugs me as an end user..
Comment 2 Sebastien Bacher 2009-06-17 11:50:47 UTC 
Created attachment 136824 [details] [review]
the change seems to do the trick
Comment 3 Sebastien Bacher 2009-06-17 11:50:50 UTC 
Created attachment 136825 [details] [review]
the change seems to do the trick
Comment 4 Vincent Untz 2009-08-12 02:03:57 UTC 
Sébastien: thinking about it... If we want to do it correctly, I would think we probably want to tell gnome-menus to not load user data for menus (ie, not load menus files nor desktop files from ~/.config/... and ~/.local/...). What do you think?

(it should be easy to add a lockdown mode to gnome-menus)
Comment 5 Jeremy Bicha 2011-05-06 11:33:26 UTC 
This appears to be fixed in gnome-panel 3.
Comment 6 Vincent Untz 2011-05-06 11:40:40 UTC 
Indeed. And thinking about my comment #4, I think it would need another lockdown setting, so let's close this.