Bug 255059 – gnome-screensaver does not have xscreensaver screensavers available.

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description xiando 2009-01-15 16:25:18 UTC]

x11-misc/xscreensaver 5.07
gnome-extra/gnome-screensaver-2.24.1

1. gnome-screensaver can use the xscreensaver screensavers.
2. http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions story is that you need to run gnome-screensaver-$version/data/migrate-xscreensaver-config.sh and convert the files.
3. Manually enter the directory.
4. for f in /usr/share/xscreensaver/config/*;do ./migrate-xscreensaver-config.sh $f;done
5. mv *.desktop /usr/share/applications/screensavers/
6. gnome-screensaver-preferences now gives you access to the fancy xscreensaver technology.
7. Select and try chess screensaver. Works. Could be that there are those who don't(?).

It must be mentioned that gnome-extra/gnome-screensaver-2.24.1 ebuild story is:

                ewarn "You have xscreensaver installed, you probably want to disable it."
                ewarn "To prevent a duplicate screensaver entry in the menu, you need to"
                ewarn "build xscreensaver with -gnome in the USE flags."
                ewarn "echo \"x11-misc/xscreensaver -gnome\" >> /etc/portage/package.use"

ebuild story does not hold water as indicated by grep gnome /usr/portage/x11-misc/xscreensaver/* evidence showing only gdm and libglade "gnome" involvement.

I'm not enturely sure how to hack the ebuild to enter the data directory and to the 

for f in /usr/share/xscreensaver/config/*;do ./migrate-xscreensaver-config.sh $f;done
mv *.desktop /usr/share/applications/screensavers/

..which should probably only be done based on xscreensaver use flag for gnome-screensaver.

Reproducible: Always

Steps to Reproduce:
1. gnome-screensaver-preferences 
2. *4* screensavers. Very big choice.

Actual Results:  
get to choose between four boring screensavers

Expected Results:  
lots of fancy scrensavers

[Comment 1 Gilles Dartiguelongue (RETIRED) 2009-01-15 22:58:37 UTC]

*** This bug has been marked as a duplicate of bug 135067 ***