4.1
When I start Ksetiwatch it doesn't show me anything.
Ksetiwatch cannot actively search for SETI@home locations on your
computer. Instead, you have to let Ksetiwatch know where you have stored
your SETI@home client. See here
for details.
4.2
When trying to start a client via Ksetiwatch the status first
shows "Running", but switches back to "Stop" after some time. What
happened?
This indicates that Ksetiwatch wasn't able to start the SETI@home
client. Most probably you don't have the permission execute the client.
4.3
Sometimes Ksetiwatch tells me that the client is still running, although
the work unit has been completed, and no client task can be found in the
process table. How is this possible?
This seems to be a bug on the client's side. Obviously the SETI@home
client sometimes fails to write the `result.sah' file after it has
finished a work unit. Just restart Ksetiwatch and the SETI@home client,
and everything should be ok again.
4.4
Ksetiwatch crashes when I try to start the program, or when I click
on the little Ksetiwatch icon in the taskbar.
This is most probably due to a buggy portable network graphics (png)
system library installed on your system. Please upgrade your png library
to the most recent version.
4.5
Why are all icons missing (display shows "?"), and why can't I open the
skymap?
You obviously installed a binary rpm package that wasn't built for your
distribution. Please ask the vendor of your distribution if he can provide
binary packages of Ksetiwatch. Alternatively, check out
rpmfind.net to see whether somebody
else has already built a binary package matching your system.
4.6
I'm using RedHat 7.x with the gcc 2.96 compiler, and my self-compiled version
of Ksetiwatch crashes right after startup. What happens here?
The binary code produced by gcc 2.96 is incompatible to the latest official
releases of the GNU compiler (2.95.2 or 2.95.3). As a work-around,
recompile Ksetiwatch with --enable debug (./configure --enable-debug). In
addition, visit the RedHat website and grab the latest revision of gcc 2.96,
which hopefully fixes the abovementioned incompatibilities.