[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: [kdepim-users] 3 KPilot problems
From:       Peter Palensky <palensky () gmx ! net>
Date:       2004-04-02 13:35:07
Message-ID: 200404021535.07628.palensky () gmx ! net
[Download RAW message or body]

Am Thursday 01 April 2004 00:57 schrieb Adriaan de Groot:
> On Thursday 01 April 2004 00:03, you wrote:

> > the first two problems, however, still remain. i therefore compiled with
> > CFLAGS="-DDEBUG -DDEBUG_CERR" ./configure && make && make install
> > but the 2 hour calendar-sync only told
>
> Hm. Why is the knotes conduit in there twice? And it should have printed
> _something_ more than that. Make sure you run the daemon from a konsole
> before starting anything else. Ideally, configure kpilot, quit it and the
> daemon, and run just the daemon in konsole.

doing this, i get the following stderr log:

-- cut --

kpilotDaemon:  log file name /home/palensky/.kde3.2/share/apps/kpilot/lastsync.log
kpilotDaemon: WARNING: : Modified note unknown to Pilot
Data too large
kpilotconduit: $Id: vcal-conduitbase.cc,v 1.60 2004/03/25 09:27:24 adridg Exp $
kpilotconduit: -------- paper
kpilotconduit: -------- IB
kpilotconduit: -------- MAS
   .... 3112 lines like that with various calendar entries....
kpilotconduit: -------- EVA meeting
kpilotconduit: -------- Martin: VHDL
kpilotconduit: -------- AOD
kpilotconduit: $Id: abbrowser-conduit.cc,v 1.92 2004/03/25 09:44:58 adridg Exp $
kpilotconduit: Loading standard addressbook
kpilotconduit: $Id: vcal-conduitbase.cc,v 1.60 2004/03/25 09:27:24 adridg Exp $

-- end cut --

the sync still does not work as it should (and as it did in previous versions):
 - addressbook is only partly synced (but is fast)
 - calendar takes more than 2 hours to sync (but synces fine)

greetings,
peter.
_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users
[prev in list] [next in list] [prev in thread] [next in thread]