Version: 4.6.0 (blivit) (using KDE 3.5.2, Gentoo) Compiler: gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) OS: Linux (i686) release 2.6.16-gentoo if user set "net:any" in pilot-link sysbsytem wait network(ip) connection for start sync(in this case pilot-link bind on socket and wait for connection) But kpilot don't allow change optionsin this case and show 10% in Sync progress bar. This behavior don't allow to user change any options and oly manual change in kpilotrc can allow chaging
I can confirm that kpilot freezes with the port set to "net:any" (which is valid with the pilot-link utilities). To notice, it may take restarting kpilot. I have KPilot 4.6.0 with KDE 3.5.4 on Fedora Core 5.
Hi guys. 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!! =:)
Interesting line in log: 13:37:06 Pilot device net:any does not exist. Probably it is a USB device and will appear during a HotSync.
On Wednesday 16 May 2007 11:40, roman wrote: > 13:37:06 Pilot device net:any does not exist. Probably it is a USB device > and will appear during a HotSync. Not really; KPilot doesn't know about the device handling down lower in pilot-link, so it assumes everything is a /dev/ type entry and prints a harmless warning. net:any handling has been fixed in 3.5.7.
Iterface don't freeze now but I kpilotDaemon crash by SIGSEGV with tacktrace: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233058128 (LWP 16982)] [New Thread -1235420256 (LWP 18085)] 0xb7f0a410 in __kernel_vsyscall () #0 0xb7f0a410 in __kernel_vsyscall () #1 0xb6eaa316 in nanosleep () from /lib/libc.so.6 #2 0xb6eaa13b in sleep () from /lib/libc.so.6 #3 0xb6d2b3ef in KCrash::startDrKonqi () from /usr/kde/3.5/lib/libkdecore.so.4 #4 0xb6e5b90d in vfprintf () from /lib/libc.so.6 #5 0xb6e7c3f1 in vsnprintf () from /lib/libc.so.6 #6 0xb7d5312e in qWarning () from /usr/qt/3/lib/libqt-mt.so.3 #7 0xb705f87d in dlp_response_free (res=0xb6f39ff4) at dlp.c:690 #8 0xbfa685e8 in ?? () #9 0xb6f39ff4 in ?? () from /lib/libc.so.6 #10 0xb6f3b120 in ?? () from /lib/libc.so.6 #11 0x0815f6c0 in ?? () #12 0xbfa685f8 in ?? () #13 0xb6e842f4 in free () from /lib/libc.so.6 Backtrace stopped: previous frame inner to this frame (corrupt stack?) No calendar/tasks data on palm after the crash
May kpilotDaemon's crash be connected to using IMAP for calendar/todo?
KPilot absolutely has known crashes and problems when using non-local sources for calendar/todo/address data. Also, your backtrace doesn't help us trace down the problem since there's no code references to kpilot in there. To fix this, please rebuild kpilot with debug set to yes (./configure --enable-debug=yes). But, yes, to answer your question, kpilot cannot sync correctly with IMAP (or any non-local-file) sources due to problems in the underlying kdepim libraries.
On Wednesday 16 May 2007, roman wrote: > ------- May kpilotDaemon's crash be connected to using IMAP for > calendar/todo? Yes, that will crash most of the time.