FAQ
Prev
Next

Chapter 6. FAQ

KPilot Startup Problems

1. What do I put after --debug?
2. KPilot says Can't connect to pilot
1.

What do I put after --debug?

Nothing. Most versions of KPilot don't even have a --debug option, and will complain if you use it. For those versions that do have it, use a value between 1 and 4, which will control the amount of debugging printed (a little). Using a value of 1 will print a fairly complete call trace without the really-boring functions, while 4 will include every trivial function in all of KPilot.

2.

KPilot says Can't connect to pilot

This can have various causes. Check that:

  • The pilot device (usually /dev/pilot) exists and points to the serial port the PalmPilot is actually connected to.

    To link the PalmPilot device to the correct serial port, you can either fill in /dev/ttySn in the Pilot Device field in the setup dialog or (preferably) link /dev/pilot to /dev/ttySn with the following command (as root): ln -s /dev/ttySn /dev/pilot Here /dev/ttySn is the name of the serial port; replace n with the correct number (usually 0 or 1).

  • Check that you have permission to read and write to the serial port. The permissions for the serial port should be such that you can write to it. This is most easily done by running the following (as root): chmod 666 /dev/ttySn

  • Try starting the daemon by hand before starting KPilot.

  • (For Mandrakelinux™ 7 systems) Check the system security level: settings higher than 3 prevent some forms of inter-process communication which are necessary for KPilot to operate correctly.

    (Mandrakelinux™ security information courtesy of Jay Summett) To set your MSEC (Mandrake SECurity) settings to not block the KPilot socket (for connections to localhost) you can login as root and type /etc/security/msec/init.sh 3 Which will set your MSEC level to 3 (regular security). For more information about the various security levels, etc., see: the Mandrake reference guide.

Prev
Next
Home


Would you like to make a comment or contribute an update to this page?
Send feedback to the KDE Docs Team