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 400239 - Rhythmbox don't respect GNOME lockdown features
Rhythmbox don't respect GNOME lockdown features
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: general
HEAD
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-24 15:17 UTC by Luca Ferretti
Modified: 2018-05-24 12:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luca Ferretti 2007-01-24 15:17:42 UTC
A good GNOME-compliant application should respect basic lockdown features provided by GNOME Desktop.

You can find them under gconf:///desktop/gnome/lockdown directory.

By now, the only lockdown key related to Rhythmbox features is "disable_file_to_disk".

When this key is true, Rhythmbox should not save anything on disk; this will include:
  * no "Save Playlist" feature
  * no rip CD feature
  * no podcasts download (maybe no podcast plugin at all?)
  * no music shop download (maybe no music shop at all if you can't stream?)
  * no album art and lyrics retrival (not sure about it)
  * other ?

Of course you'll have a "gelded" player if this key is true, but note that it will be used only on special environment.

For example you could need to use Rhythmbox as a simple jukebox (play only available music files or radio stations). This also means that Rhythmbox should provide its own lockdown keys, for example a key to set enabled music sources (for example enable only Magnatune to create a music buying kiosk), or a key to prevent the addition of new radio stations or podcast's feeds. But this is stuff for another bug report.
Comment 1 Karsten Schmiedecke 2007-02-15 08:17:14 UTC
Recent Discussion on the Mailing list suggested lockdown features for Rhythmbox. 

Alex Lancaster wrote:
I don't think offering 3 modes in the user interface is a good idea.  Not only
is this very confusing from a UI perspective (how is the user going to know the difference between them) but I don't think entering something like an internet kiosk (total lockdown) mode is something that the typical user will do.  However, I think is still worth adding a finer grained lockdown in gconf only (and with pessulus etc) so that the system designer/admin can set up a kiosk.

The suggestions for lockdown keys so far are:
Don't allow user plugins   -   lockdown/no_user_plugins
Disable the source list    -   lockdown/disable_source_list
Disable playlists          -   lockdown/disable_playlists
Hide Menu                  -   lockdown/hide_menu
Disable Volume Change      -   lockdown/fix_volume
Disable Browser            -   lockdown/disable_browser
Disable CD Burning         -   lockdown/disable_cdburner
Hide Sources List is, iirc already in gconf somewhere...
Comment 2 Alex Lancaster 2007-02-15 09:30:44 UTC
(In reply to comment #1)
> Recent Discussion on the Mailing list suggested lockdown features for
> Rhythmbox. 

See thread here:

http://mail.gnome.org/archives/rhythmbox-devel/2007-February/thread.html#00054

> Alex Lancaster wrote:

Actually it was William Jon McCann who wrote the following:

> I don't think offering 3 modes in the user interface is a good idea.  Not only
> is this very confusing from a UI perspective (how is the user going to know the
> difference between them) but I don't think entering something like an internet
> kiosk (total lockdown) mode is something that the typical user will do. 
> However, I think is still worth adding a finer grained lockdown in gconf only
> (and with pessulus etc) so that the system designer/admin can set up a kiosk.
> 
> The suggestions for lockdown keys so far are:
> Don't allow user plugins   -   lockdown/no_user_plugins
> Disable the source list    -   lockdown/disable_source_list
> Disable playlists          -   lockdown/disable_playlists
> Hide Menu                  -   lockdown/hide_menu
> Disable Volume Change      -   lockdown/fix_volume
> Disable Browser            -   lockdown/disable_browser
> Disable CD Burning         -   lockdown/disable_cdburner
> Hide Sources List is, iirc already in gconf somewhere...

Other possible gconf keys (some of these could be made part of the defaults or otherwise combined):

Disable playlists creation          - lockdown/disable_playlist_creation
Disable playlists modification      - lockdown/disable_playlist_modification
Disable podcasts   "         "      - lockdown/disable_podcast_modification
Disable iradio     "         "      - lockdown/disable_iradio_modification
Disable CD ripping                  - lockdown/disable_cd_ripping

Currently in Party Mode, items can't be removed from playlists, but tracks can added to playlists or reordered.  This should be prevented by default.  Only the Queue should be reorderable or added to.

It would also be possible to write a Python plugin that would allow these to be configured via the GUI (using the plugin "Configure" feature) without having to resort to the gconf-editor.
Comment 3 James "Doc" Livingston 2007-02-15 11:59:09 UTC
"Disable the source list" is already done as /apps/rhythmbox/ui/sourcelist_hidden.

Radio and CD burning are implemented as plugins, so they can be disabled with /apps/rhythmbox/plugins/iradio/active et al. You can disable per-user plugins with  /apps/rhythmbox/plugins/no_user_plugins.


These other ideas sound good, and we should probably document them somewhere.
Comment 4 GNOME Infrastructure Team 2018-05-24 12:17:15 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/308.