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 300832 - Add to Panel dialog don't respect lockdown
Add to Panel dialog don't respect lockdown
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: general
git master
Other Linux
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-16 07:11 UTC by Luca Ferretti
Modified: 2020-11-06 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luca Ferretti 2005-04-16 07:11:58 UTC
To reproduce 
1. Open the Add to Panel dialog and scroll the list to show the Lock Screen item.
2. Change value to the /apps/panel/global/disable_lock_screen GConf key from
TRUE to FALSE.
3. The Lock Screen item is still in list
4. Close and reopen the Add to Panel dialog
5. The Lock Screen is disappeared, as it should be.

Aspected results
The Add to Dialog should be automatically updated when it's open.

Notes.
Same behavior for Exit Session, and maybe other "lockable" stuff. A deeper check
is needed. Maybe the Add to Dialog panel don't provide any lockdown feature:
previouly there was the Add to Panel menu, and you can't edit a GConf key while
browsing a manu :-)
Comment 1 Luca Ferretti 2005-04-16 07:17:00 UTC
Same issue opening the Add to Panel dialog, then setting to TRUE the 
/apps/panel/global/locked_down GConf key: you can finish to add an object to panel.

What should be the behavior? The dialog shoul disappear, it should became
insensible (only Cancel button as available target) or the object list should
became empty?
Comment 2 Daniel Holbach 2005-12-12 12:04:22 UTC
The bug is in Malone too:
https://launchpad.net/distros/ubuntu/+source/gnome-panel/+bug/4712
Comment 3 Sven J. 2008-01-20 17:17:50 UTC
The bug in Daniel's "Comment #2" relates to the applications context menu, which allows to launch a menu editor even in locked down environments.

I think this doesnt relate to this bug, right?
Comment 4 dtsiamasiotis 2010-04-17 17:09:43 UTC
Bug status should change to NEEDINFO and try to reproduce with a more recent version.
Comment 5 André Klapper 2020-11-06 20:23: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.