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 333222 - Add ability to lock menu editing
Add ability to lock menu editing
Status: RESOLVED WONTFIX
Product: pessulus
Classification: Deprecated
Component: general
0.8
Other All
: Normal enhancement
: ---
Assigned To: Pessulus Maintainer(s)
Pessulus Maintainer(s)
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-03-03 08:04 UTC by Corey Burger
Modified: 2013-01-15 22:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Corey Burger 2006-03-03 08:04:28 UTC 
There is currently no way to stop the user from editing the menus. This is a
must have in a public computing environment.
Comment 1 Vincent Untz 2006-03-18 07:48:33 UTC 
The only right way to do it (and that I can think of) is to put a file somewhere to tell gnome-menus to ignore the local modifications made by the user. Else, the user will always be able to modify it by editing a file in a text editor, or downloading a file, or...
Comment 2 Mark McLoughlin 2006-04-02 18:07:37 UTC 
You could maybe:

  1) add a GMENU_TREE_FLAGS_IGNORE_USER

     Basically, this would stop the g_get_user_config/data_dir() APIs from
     being used in gnome-menus if it was set

  2) have /desktop/gnome/lockdown/disable_menu_edits

  3) Make apps which use the libgnome-menu API check the GConf key and
     use pass the flag to gmenu_tree_lookup() if it's set

  4) Disable access to the menu editor if it's set
Comment 3 Christian Kirbach 2013-01-15 22:43:21 UTC 
We are sorry, but pessulus will no longer be maintained due to lack of manpower. I am closing all remaining open bug reports. Pessulus is already closed down for new report submissions.

Apologies for the noise and any inconvenience caused by it.