Bug 182338 - Need way to enable/disable individual screensavers
Summary: Need way to enable/disable individual screensavers
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: jmccann
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-21 21:58 UTC by G.Wolfe Woodbury
Modified: 2015-01-14 23:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-05 20:12:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 316462 0 None None None Never

Description G.Wolfe Woodbury 2006-02-21 21:58:36 UTC
Description of problem:
Are there plans to add individual controls to gnome-screensaver to select or
deselect individual screensaver modules when "random" is selected?
Sme are just too painful to watch on some machines.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ray Strode [halfline] 2007-03-28 17:11:24 UTC
Note you can already do this with gconf-editor by modifying
/apps/gnome-screensaver/themes

but there isn't a way in the UI to do what you want to do.

I guess before it could be added to the UI we would need to think about the best
way to present it the user.  I'm not sure the xscreensaver style checkbox by
every item is the right way to go.

Anyway, this is definitely upstream fodder.  Can you file there and post a link
to the bug here?

Comment 2 G.Wolfe Woodbury 2007-03-31 09:21:51 UTC
OK, will file RFE with upstream (Gnome bugzilla)

I'm personally happy to learn that gconf-editor will let me do what I want, and
I'll explore the gconf stuff a little deeper now that I have your pointer to the
appropriate place.

Comment 3 jmccann 2008-05-05 20:12:29 UTC
We'll track this via the upstream bug.


Note You need to log in before you can comment on or make changes to this bug.