Version: 4.4.6 (Kiel) (using KDE 3.3.0, (3.1)) Compiler: gcc version 3.3.4 (Debian 1:3.3.4-12) OS: Linux (i686) release 2.6.5-1-k7 When the deamon is running it is not possible to start kpilot. The debug is the following: starting kpilotdaemon: kpilotDaemon main: Configuration version 443 KPilotDeviceLink: Pilot-link version 1108 getPilotSpeed: Speed set to PILOTRATE=9600 (0) setupPilotCodec: Creating codec iso 8859-1 setupPilotCodec: Got codec ISO 8859-1 for setting West-Europees ( iso 8859-1 ) reloadSettings: Got configuration net:any reloadSettings: Got conduit list internal_fileinstall,internal_kroupware,todo-conduit,vcal-conduit,knotes-conduit,abbrowser_conduit kpilotDaemon: WARNING: [virtual void PilotDaemon::requestSync(int)] : Bad mode set in config file. requestSync: Next sync is: HotSync reloadSettings: Resetting with device net:any close: Closing sockets -1 and -1 Bound devices: <none> close: Closing sockets -1 and -1 Bound devices: <none> setupWidget: Finished getting icons PilotDaemon: The daemon is ready with status PilotDaemon=Waiting for sync; NextSync=Onbekende synchronisatie-modus (KPilotDeviceLink=WaitingForDevice); (5) showTray: Tray icon displayed. Bound devices: <none> open: Typing to open net:any open: Got master 10 open: Binding to path net:any Bound devices: net:any acceptDevice: Found connection on device net:any acceptDevice: Current status KPilotDeviceLink=DeviceOpen and master 10 After that I start kpilot: setupPilotCodec: Creating codec iso 8859-1 setupPilotCodec: Got codec ISO 8859-1 for setting West-Europees ( iso 8859-1 ) setupWidget: Creating central widget. initComponents: Creating component pages. LogWidget: Using text size 87x18 addComponentPage: Adding component @136085560 called component_log addComponentPage: Using component action name HotSync for view_log addComponentPage: Adding component @136059192 called component_todo addComponentPage: Using component action name To-do Viewer for view_todo addComponentPage: Adding component @136401104 called component_address addComponentPage: Using component action name Adressen for view_address slotUpdateButtons: Selected items 0 addComponentPage: Adding component @136238800 called component_memo addComponentPage: Using component action name Memo for view_memo addComponentPage: Adding component @136393088 called component_files addComponentPage: Using component action name Bestandsinstallatie for view_files addComponentPage: Adding component @136033464 called component_generic addComponentPage: Using component action name Algemene database for view_generic setupWidget: Got XML from kpilotui.rc and /home/toma/.kde/share/apps/kpilot/kpilotui.rc allocationInfo: Allocated 0 Deleted 0 Here it 'hangs', nothing happens annymore. When I kill the deamon, kpilot continues: startDaemonIfNeeded: Daemon status is <none> startDaemonIfNeeded: Daemon not responding, trying to start it. startDaemonIfNeeded: Daemon status is PilotDaemon=Waiting for sync; NextSync=Onbekende synchronisatie-modus (KPilotDeviceLink=WaitingForDevice); kpilot: WARNING: KPilot error: PalmOS(tm)-apparaat net:any bestaat niet. Er wordt aangenomen dat het apparaat DevFS gebruikt. kpilot becomes visible... Hope this info helps. (this is HEAD, 10 minutes ago).
This came up on the mailing list recently and Adriaan commented with this: --------------------- You will also notice that the daemon's GUI (the tray icon) is unresponsive when using net:any and that DCOP communication with it fails. This is because it's waiting on a socket somewhere deep inside pilot-link, and I've never bothered tracking it down. I suspect that, failing pilot-link patches, the only fix is to move the pilot-communications part of the daemon to a thread, which will be pretty complicated. --------------------- It sounds like this problem will be fixed in pilot-link 0.12, so there's hope that soon this will be resolved, though not directly in kpilot.
Thanks for the update! Let me know if you need a beta tester for this part.
Hi Tom!! This should be fixed now. The not-yet-released version of kpilot from /branches/KDE/3.5/kdepim/kpilot should resolve this problem. Please test with that version (kpilot 4.9.1) and re-open this if you still have this problem. Thanks!! =:)