4. Troubleshooting

If you have problems running KisoCD they may have different reasons. Some of them can easily be found by looking at the versions of some programs, some settings....therefore I made a little script which also contains some other tips. Please download  and run it, read its instructions and send the infos back to me--it will help you and me finding the reasons with less work.

This script is just a first one, will hopefully be updated frequently to become more powerful.

If you have a problem please call KisoCD by typing kisocd.sh -3. This will dump debug-data in ~/.kde/share/apps/kisocd/, the files are called kisocdDebugXXX. Please send them to me when reporting a problem, it will speed up finding a solution to your problem a lot.

Known Problems

PLEASE REPORT PROBLEMS EVEN IF THEY ARE LISTED HERE!!!!!!!!!

• segfault while starting up: Seems to be a problem caused by the compiler linking KisoCD against two different versions of libstdc++. Check it out with ldd kisocd. This gives you information about which libs kisocd is linked against. Problem solved by deleting one of the libs and compiling it again. But I don't think this to be an easy way for everybody.... (reported by three users)
• The requirements stated in the help pages up to the current release tell you that Qt 1.42 is required--actually you need Qt 1.44...
• If KDEDIR and QTDIR are not set:
  First you have to locate those directories. On my SuSE-system the KDEDIR is /opt/kde. I think it should contain the directories bin, cgi-bin, include, lib, sbin, share. In those directories all the KDE-programs are kept, there are KDE's libraries, the directory with the help-files, your KDE-menu and so on. Should not be too hard to find.
  The QTDIR is /usr/lib/qt on my system. Should at least contain include and lib (the header-files and the libraries).
  When you've figured that out it's time to write it down in a shellscript so that your system always knows it when necessary. Therefore my startkde-script contains the following lines:

  #
  # set variables necessary for KDE
  #
  test -z "${QTDIR}"  && export QTDIR=/usr/lib/qt
  test -z "${KDEDIR}" && export KDEDIR=/opt/kde

  The script itself is in KDEDIR/bin. Unfortunately those lines may depend on which shell you use. Here it is bash. Don't know if and how it has to be changed for others....after having made those changes you start X11/KDE again and make sure the variables are correctly set with echo $KDEDIR and echo $QTDIR.
  After all that you should probably think about the reason why you have such a misconfigured system ;-)

• packages needed for compilation

  Often configure or the compilation fail because not all of the necessary programs are installed. Here are lists of packages that need to be installed (for SuSE 6.0/6.1 and SuSE 6.3 they are taken from SuSEs SPMs. You won't need all of them, I think, but most of them...). Hope they are correct...

  Well, before you are shocked by those lists, see the things that are missing most often:

  autoconf, automake, qtdevel, xdevel.

  SuSE 6.0/6.1

  aaa_base aaa_dir autoconf automake base bash binutils bison bzip compress cpio devs diff egcs ext2fs file fileutil find flex gawk gdbm gettext gpm gpp gppshare groff gzip kbase kbd klibs ksupp ldso less libc libgpp libjpeg libpng libtiff libz lx_suse (or kernel source) make mktemp modules ncurses net_tool netcfg nkita nkitb patch perl ps qtcompat qtdevel qtext qtlib rpm sh_utils shadow shlibs syslogd sysvinit texinfo textutil timezone unzip util xdevel xf86 xshared

  SuSE 6.3

  aaa_base aaa_dir autoconf automake base bash bindutil binutils bison bzip compress cpio cracklib devs diff egcs ext2fs file fileutil find flex gawk gdbm gettext gpm gpp gppshare groff gzip kbase kbd klibs ksupp ldso less libc libgpp libjpeg libpng libtiff libz lx_suse (or kernel source) make mktemp modules ncurses net_tool netcfg nkita nkitb nssv1 pam patch perl ps qtcompat qtdevel qtext qtlib rpm sh_utils shadow shlibs syslogd sysvinit texinfo textutil timezone unzip util xdevel xf86 xshared

• drive locked after CDRW-blank
  Using an old version of cdrecord it happens that after a CDRW-blank you can't eject the medium (reported with HP CD-Writer+ 8100). Use at least cdrecord-1.8-1 instead.
• where to put the imagefile/tmp-directory
  You can put the imagefile on a FAT-partition, but the directory for temporary data needs to reside on a partition which can handle symlinks.
• Note on Qt
  KisoCD currently needs Qt 1.44 or 1.45. If you have both Qt2.X and Qt1.44 on your system, you may need to compile like this:
  1) set QTDIR with 'export QTDIR=/usr/lib/qt-1.44'
  2) use './configure --with-qt-dir=/usr/lib/qt-1.44' instead of './configure'
  Of course you have do give the path which fits your system. The example suits RH6.1.
  Thanks to Jeroen!
• See the page about requirements for topics concerning different versions of cdrecord/mkisofs.