Next Previous Table of Contents
Have you got the required libraries? Run Knapster from an xterm and see what the output is. If it is a library problem it will have a message about ld not finding a library. To fix it, get the library required. In some cases, the library problem may be because of a different version of a library used. This might be fixed by compiling the source on you machine. Give it a go.
Core dump? You've probably found a bug. Maybe about now would be a good time to email me with the symptoms, including machine type, whether a binary package or source package was used and what and when it happens.
Can't compile the source? The package uses autoconf to create the makefiles and will fail if it can't find the required libraries and include files. You must have them to compile the program. Another problem that happens every so often is that the configure step fails when testing for QT or for KDE even though you know they are installed. This is a real pain in the XXXX! You may be able to get it to work by specifying the paths to the libraries when invoking configure. If that doesn't work, you may have to make your own makefile. Maybe I'll include a basic one in later versions.
On a download, the download tab reports the file as queued and then initializing and then does nothing else. This happens usually when you are behind some kind of firewall. Try setting the connection port in preferences to port 0, and it may work correctly. There is no socks5 support implemented and so the socks option available in the original Windows client is as yet unavailable.
Next Previous Table of Contents