From: Daniel G. <dg...@su...> - 2006-06-22 19:11:30
|
On Thursday 22 June 2006 20:14, Achim Spangler wrote: > How did I get this: > 1) I started a fresh sync, where the standard reousrces for Kalendar and > =A0 =A0contact pointed to fresh generated files (i.e. empty). > =A0 --> calendar from mobile phone has been transfered fine > > 2) removed an obsolete calendar entry > > 3) restarted the sync > =A0--> several conflicts were detected - even if there was no real reason > =A0 =A0 =A0( nearly all calendar entries --> the history of my konsole is= no long > =A0 =A0 =A0 =A0enough; and I won't retry, as I had already a total perman= ent crash > =A0 =A0 =A0 =A0with my mobile during the last tries ) > =A0 =A0 =3D=3D> some of the control XML-tags like data source, ... were p= robably > =A0 =A0 =A0 =A0 causing the conflict ( so the user visible parts were ide= ntic, but > =A0 =A0 =A0 =A0 several other information was different in all reported c= alendar > =A0 =A0 =A0 =A0 conflicts ) > =A0 --> after all "conflicts" were resolved by taking the entry from phone > =A0 =A0 =A0 ( the entry, where the special XML-Tags indicated the phone a= s source (msynctool --sync YYYY --conflict X to let always member X win the conflic= t) > ), the changes were being commited > =A0 =A0 =A0 ---> during THIS flow, the mobile resetted itself Can you reproduce this with enabled OSYNC_TRACE? ( export OSYNC_TRACE=3D/tmp/osync_trace/; mkdir $OSYNC_TRACE; msynctool --s= ync=20 YYYY ) Does this crash only happen with this lotus generated calendar entries? Also interesting would be lotus generated vcalendar file (without sensitive= =20 information ;) ) best regards, Daniel |