can still launch the menu editor in locked down mode

Bug #4712 reported by shaggy
6
Affects Status Importance Assigned to Milestone
GNOME Panel
Fix Released
Medium
gnome-panel (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

For building a restricted desktop system you can lock the gnome-panel with this fancy gconf key: /apps/panel/global/locked_down true/false

In the gnome-panel, in the gnome-menu's kontext menu is the "Edit Menu" button, it should dissapear when /apps/panel/global/locked_down is set, but it doesnt.

Users are able to add menu-entrys again, which the administrator decided to remove. e.g. the terminal.

Related branches

Revision history for this message
shaggy (slimshaggy) wrote :

workaround is:
sudo chown root:root /home/fakeuser/.config/menus
sudo chown root:root /home/fakeuser/.config/menus/*

Changed in gnome-panel:
assignee: nobody → gnome
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. This is a known upstream issue: http://bugs.gnome.org/show_bug.cgi?id=300832 - the "workaround" is nothing we could force on our users.

Changed in gnome-panel:
assignee: gnome → desktop-bugs
status: Unconfirmed → Confirmed
Changed in gnome-panel:
importance: Medium → Low
Revision history for this message
shaggy (slimshaggy) wrote :

The bug still exists in gutsy.

With a closer look at gnome's bug #300832 i can say that one is not related with this one.

Try on your own: Open a terminal. Then lock down the desktop with this command:
gconftool -t bool -s /apps/panel/global/locked_down "true"

Open the context menu of the applications-menü top-left on your gnome desktop, see that you are able to launch the menu editor.
This should never be possible in a locked down environment.

From my point of view this bug's importance is not "Low", since i can not create locked down "kiosk" systems.

shaggy (slimshaggy)
description: updated
Revision history for this message
shaggy (slimshaggy) wrote :
Changed in gnome-panel:
status: Confirmed → Triaged
Revision history for this message
shaggy (slimshaggy) wrote :

The bug still exists in hardy.

Revision history for this message
Peter Matulis (petermatulis) wrote :

The bug still exists in jaunty.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

I've changed the upstream bug to be http://bugzilla.gnome.org/show_bug.cgi?id=499148 which reflects better the issue the users are having with this.

Changed in gnome-panel:
status: New → Unknown
Changed in gnome-panel:
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-panel - 1:2.26.3-0ubuntu1

---------------
gnome-panel (1:2.26.3-0ubuntu1) karmic; urgency=low

  * New upstream version
  * debian/control.in:
    - typo fix
  * debian/patches/18_lockdown_lock_editor.patch:
    - change to have lockdown locking the menu editor (lp: #4712, #385596)
  * debian/patches/31_fix_crash_second_screen.patch:
    - the change is in the new version

 -- Sebastien Bacher <email address hidden> Fri, 10 Jul 2009 14:24:56 +0200

Changed in gnome-panel (Ubuntu):
status: Triaged → Fix Released
Changed in gnome-panel:
importance: Unknown → Medium
Changed in gnome-panel:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.