KDE doesn't list KSetiSaver in its screensaver
- KDE doesn't list KSetiSaver in its screensaver
- The sounds seem to "lag" behind the graphics
- libtool: link: cannot find the library
- Can I monitor more than one seti@home client?
- KSetiSaver doesn't stop the seti@home client when it is closed.
- Mandrake: KSetiSaver disappears from the screensaver configuration
- KSetiSaver says "Can't find <PATH>/state.sah, but the file IS there
This is a known problem. Since different distros put the Screensaver configurations
in different directories you often have to manually copy the KSetiSaver.desktop file
to the right location.
KSetiSaver.desktop locations on differnet systems:
This is based upon the experience of KsetiSaver user and may not be
correct or complete!
In general: If the KSeti screensaver doesn't appear in your KDE's
screensaver setup do the following:
- Mandrake 8.1: /usr/share/applnk-mdk/.hidden/ScreenSavers/
- Mdk 8.2 / KDE3: /opt/kde3/share/applnk-mdk/.hidden/ScreenSavers/
- RedHat 7.2: /usr/share/applnk/System/ScreenSavers/
- S.u.S.E: /opt/kde3/share/applnk/System/ScreenSavers
Search you hd for the directory containing the file
"KBanner.desktop". Copy the "ksetisaver.desktop" (this file is
included in the KSetiSaver sources) into the same directory.
The sounds seem to "lag" behind the graphics
This is because the KDE system is somewhat slow thinking of latencys.
Additionally KSetiSaver uses a quite primitive approach to play the sound
You should try to stop any CPU intensive programs that my run in the background
(but don't stop seti@home;-) )
If this doesn't work, turn the sound off. As a nice side effect you won't get
annoyed by the sounds ;-)
libtool: link: cannot find the library
Install your distribution's fam-devel package
Can I monitor more than one seti@home client?
Yes. But KSetiSaver can't handle this alone ;-). You have to install the great
http://ksetiwatch.sourceforge.net) tool. Add all your clients to KSetiwatch
and set KSetiSaver to use the KSetiwatch config file.
KSetiSaver doesn't stop the seti@home client when it is closed.
Make sure that you at least use KSetiSaver 0.3 or newer. This feature was broken in
older versions. If you use a recent version, make sure that you give KSetiSaver enough time.
It may take up to 1 minute to stop the seti@home client after the Screensaver is closed.
KSetiwatch also writes a logfile concerning it's activities in starting & killing the client.
You'll find it in $HOME/.setiwatchdog.log.
Mandrake: KSetiSaver disappears from the screensaver configuration
You forgot to copy the ksetisaver.menu file, or your release does not include this file
(the first release with a ksetisaver.menu file is 0.3.2).
Install a Mandrake RPM Version >= 0.3.2. If you use the .tgz source package do the following
after "make install":
Copy the "ksetisaver.menu" file in the ksetisaver directory to /usr/lib/menu/ksetisaver.
Note that "ksetisaver" is the new name of the file, not a directory.
cp ./ksetisaver/ksetisaver.menu /usr/lib/menu/ksetisaver
KSetiSaver says "Can't find <PATH>/state.sah, but the file IS there
You use a GCC3 based distribution and a KSetiSaver Version prior to 0.3.2. Solution: Update to
KsetiSaver 0.3.2 or higher
Back to KSetiSaver mainpage