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 567109 - Time delay before loading a new photo in a screensaver slideshow
Time delay before loading a new photo in a screensaver slideshow
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on: 354805
Blocks:
 
 
Reported: 2009-01-09 01:47 UTC by jakob Lempert
Modified: 2011-03-06 06:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description jakob Lempert 2009-01-09 01:47:04 UTC 
The ability to specify a delay before loading next photo in a screensaver slideshow in a .desktop file in order to keep each foto longer on the screen in a screensaver slideshow.  


Other information:
When creating a slideshow screensaver with a .desktop file using the program "slideshow" it could be very nice to have the option something like:

Exec=slideshow --delay=100 --location=/usr/share/pixmaps/backgrounds/whatever/

It could give a user the ability to use the slideshow in the screensaver as a "photoframe" with a user specific time delay before loading a new photo.
In my opinion the delay-range between 1sec to 3600sec would be great.
Comment 1 William Jon McCann 2011-03-06 06:45:54 UTC 
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.