Bug 512491 - screensaver "job" is restarted every 10 minutes
Summary: screensaver "job" is restarted every 10 minutes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: jmccann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-17 23:36 UTC by Christian Krause
Modified: 2015-01-14 23:23 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-09-02 18:51:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 485626 0 low CLOSED f-spot screensaver repeats itself 2021-02-22 00:41:40 UTC

Internal Links: 485626

Description Christian Krause 2009-07-17 23:36:52 UTC
Description of problem:

During investigating BZ #485626 I've found a strange behaviour of the gnome-screensaver: Every 10 minutes the screensaver process which actually draws the screensaver is restarted.
This is controlled by the gconf entry: /apps/gnome-screensaver/cycle_delay, which is by default 10 (minutes).

Version-Release number of selected component (if applicable):
gnome-screensaver-2.26.1-2.fc11.i586

How reproducible:
100%

Steps to Reproduce:
1. start gnome-screensaver manually with --no-daemon and --debug
2. activate screensaver, wait 10 minutes (or configure the cycle_delay to a shorter value ;-) )
  
Actual results:
[gs_manager_cycle] gs-manager.c:640 (00:41:32):  cycling jobs
[gs_job_stop] gs-job.c:483 (00:41:32):   stopping job
[gs_job_died] gs-job.c:128 (00:41:32):   Waiting on process 5729
[gs_job_died] gs-job.c:142 (00:41:32):   Job died
[gs_job_set_command] gs-job.c:193 (00:41:32):    Setting command for job:
'f-spot-screensaver'


Expected results:
If there is only one possible screensaver configured, gnome-screensaver should let it running instead of restarting it every cycle_delay minutes.

Comment 1 jmccann 2009-09-02 18:51:56 UTC
This is as designed.  One reason for it is so that a rogue screensaver engine can't take down a running system with leaks etc.  If you want to change the default value for this time - you may.


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