The number after --debug indicates what kind of messages you want to see; 1023 indicates all messages. The exact numbers you can use are as follows:
Table 3-1. Debug Values
Value | Meaning |
---|---|
1 | List the name of *every* function called. Very tedious. |
2 | Major GUI operations (e.g. Creating windows). |
4 | Minor GUI operations (e.g. Adding visual elements). |
8 | All GUI operations (e.g. Filling list boxes -- this is very tedious). |
16 | Major database operations. |
32 | Minor database operations. |
64 | All database operations. |
128 | Major sync actions. |
256 | Minor sync actions. |
512 | All sync actions. |
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 Mandrake 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.
(Mandrake 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.