Previous Next Contents

3. Problems, Errors, and other Inconveniences

3.1 The configure script complains about my version of Qt. What can I do?

All recent versions of the KDE distribution require Qt v1.2. You must download and install this version for KDE to work.

3.2 I get ``no such file'' errors for .moc files when installing. What's the problem?

There isn't one. While computing initial make dependencies, .moc files that do not exist (because they haven't been built yet) generate several missing file errors. There is no cause for alarm.

3.3 What can I do about ``parse error at /'' errors when making?

Most KDE components are a mix of C and C++ code, and some developers tend to use the C++ comment syntax (ie. // everything on a line after two forward slashes in C++ is considered a comment) rather than the pure C syntax (ie. /* This is a correct C comment */). Some versions of gcc will balk at this (eg. 2.7.0), while others will not (eg. 2.7.2). If you do get this error, just edit the relevant file and change any comments from C++ form to C form. For example, if you get the error from a line of code like this:

        a_variable = square_a_circle(diameter, pi); // Is this possible? 
        

Just change it to look like this:

        a_variable = square_a_circle(diameter, pi); /* Is this possible? */
        

and then try compiling again.

3.4 Packages keep complaining that they can't find a given KDE library, but they're right there in KDEDIR/lib/. Can I fix this?

The problem is that your dynamic library loader (ld) has to be aware of the location of all the (.so) libraries on your system in order to make them available to programs that want to run. Since /usr/local/kde/lib/ is not a conventional library location (unlike, for example, /usr/lib/), ld probably has no idea that libraries can be found there. The easiest way to fix this is to edit your ld.so.conf file which should be located in /etc/. A ``normal'' ld.so.conf should look something like this:

        /usr/local/lib
        /usr/X11R6/lib
        /usr/i486-linuxaout/lib
        

Just edit this file in any text editor and add a line which points to your KDE lib directory. For most people this will be /usr/local/kde/lib and the resulting file should look something like:

        
        /usr/local/lib        
        /usr/X11R6/lib
        /usr/i486-linuxaout/lib        
        /usr/local/kde/lib
        

Now, every time you recompile a KDE library, issue the following command as root;

        ldconfig
        

3.5 Sometimes when making, I get ``Unexpected end of line seen''. Can this be corrected?

Rumour has it that this is caused by trying to compile KDE with a non-gnu make. The solution is to get make from the free software foundation ( http://www.fsf.org).

3.6 Everything installed fine, but I get ``ERROR: No path for templates specified in config files''. What's the solution?

This is a result of changes in where kde aplications should store their config files. The following should solve it:

        mv $HOME/.kde/config/.kfmrc $HOME/.kde/config/kfmrc
        

3.7 I get a ``cpio: unrecognized option: --quiet'' when I try and install the rpm package. What's wrong?

The rpm package (see http://www.rpm.org) requires cpio version 2.4.2 or greater. Most non-Redhat systems have an older version of cpio, so you must upgrade in order to be able to use rpm. You can get the most recent version from the download section of the Free Software Foundations ftp site (see http://www.fsf.org).

3.8 Why do I get ``resources.c:5: include' expects "FILENAME" or <FILENAME>'' when compiling kvt?

This is another example of the C/C++ comment syntax problem. Just edit the resources.c file and change the C++ comment on line 5 to a C style comment (ie. change ``// CC: for isspace'' to ``/* CC: for isspace */''.

3.9 What does ``rock.o(.text+0x8bf): undefined reference to `sin''' mean?

It means you're trying to compile a program that requires routines from the C math library without linking in that library. You can fix this by editing the relevant Makefile and adding ``-lm'' to the list of files to be linked (in the LDFLAGS declaration).

3.10 Whenever I choose Logout from kwm or kpanel, it doesn't work. What's wrong?

This can occur if you are running KDE with the startx command and using your .xinitrc file to launch the core KDE components. To fix this, make sure that kwn is the last application listed in your .xinitrc file, like this:

        #!/bin/sh
        exec kfm -d &
        exec kpanel &
        exec kdisplay -init &
        exec kwm
        

3.11 Program k* seems really powerful, but I can't figure out how to configure it. What should I do?

Remember, KDE developers are all volunteers, and are currently devoting most of their time to getting the software running properly. As such, documentation for some applications is a little scant. But the framework for a very powerful help system is already in place (ie. kdehelp), so this is a temporary problem. Most of the KDE team would be ecstatic if you could persevere with an application long enough to figure out how it works, write up an (html) guide to the program, and then submit it to the relevant author.

3.12 I have a problem with KDE that is not mentioned in this FAQ. Where can I turn?

If you're having problems, you are almost certainly not alone. Joining a mailing list (see More Information) will put you in contact with other KDE users (and developers). You should also consider sending e-mail directly to the author of the program that is giving you trouble, particularly if you can document the exact nature of the problem. In all communications with KDE developers, please try and remember that they are volunteers and that KDE is still in an ALPHA stage of development.

3.13 I had a problem, but then I managed to fix it. Who should I tell?

Write a very nice e-mail to the author of the program, explaining what the problem was, how to reproduce it, and your proposed fix. Be sure to include copious amounts of praise for the author's contribution to KDE.

Next, send a summary of the problem and fix to the maintainer of this FAQ ( thor@netcom.ca) so that in can be included in future versions of this document.

3.14 I posted some ideas/questions to a mailing list, and got dumped on. What should I do?

Remember, KDE is a free and open project. As such, there is nothing binding any of its participants together except for a shared goal of creating great software. Anyone is free to join the mailing lists, and there is no authority to arbitrate what is (and what isn't) appropriate behaviour. If you post something on the list that others find objectionable, then they are at liberty to shoot you down. And you, of course, are also free to rebut their responses.

If, however, you want to avoid getting dumped on, here are a few suggestions:

Enough said.


Previous Next Contents