[Synckolab] Exception while syncing calendar items

Patrick Cornelißen cornelis at pcornelissen.de
Tue Jul 6 00:55:34 PDT 2010


Hi!

I'm using Thunderbird 3.0.4 with synckolab 1.5.0 and lightning 1.0b1
on my 64 Bit Ubuntu 10.04.
When I sync the calendar folder (kolab 2) then I'm getting this exception:

Fehler: uncaught exception: [Exception... "Cannot modify properties of
a WrappedNative"  nsresult: "0x80570034
(NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN)"  location: "JS frame ::
chrome://synckolab/content/calendarTools.js :: anonymous :: line 813"
data: no]

And the sync pauses (forever) showing "reading" and "unknown" in the
sync window.

I have attached the eml of the entry and anonymized it. I hope the
anonymization didn't fix the file... ;-)

Is that problem known? I'm having a similar problem with some
contacts, but I had no time to investigate that further.

Thanks and keep up the good work!

-- 
Mit freundlichen Grüßen,  // Bye,
  Patrick Cornelißen
  http://www.openprojectguide.org
  http://www.pcornelissen.de http://code.google.com/p/gloudy/
-------------- next part --------------
From: XXXXXXX <XXX at XXXnt.de>
Reply-To: XXXXXXX <XXX at XXXnt.de>
Organization: xxxxxx GmbH
X-KMail-Fcc: .1691286191.directory/.INBOX.directory/Sent
Subject: libkcal-942576500.240
Date: Fri, 28 May 2010 18:17:19 +0200
User-Agent: KMail/1.9.10 (enterprise35 20100409.1112955)
MIME-Version: 1.0
X-Kolab-SchedulingID: 040000008200E00074C5B7101A82E00800000000A0567DB2FBCFCA0100000000000000001000000047C1A0571C9FFD4C822BAA74B1CFB6D6
X-Kolab-Type: application/x-vnd.kolab.event
Content-Type: Multipart/Mixed;
  boundary="Boundary-00=_Py+/LxLF7LTIHXW"
Status: RO
X-Status: O
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
X-KMail-MDN-Sent:  
X-UID: 0

--Boundary-00=_Py+/LxLF7LTIHXW
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: 

Dies ist ein Kolab Groupware-Objekt.
Um dieses Objekt anzeigen zu k=F6nnen, brauchen Sie ein E-Mail Programm, da=
s das Kolab Groupware-Format versteht.
Eine Liste solcher E-Mail-Programme finden Sie hier:
http://www.kolab.org/kolab2-clients.html

=2D----------------------------------------------------

This is a Kolab Groupware object.
To view this object you will need an email client that can understand the K=
olab Groupware format.
=46or a list of such email clients please visit
http://www.kolab.org/kolab2-clients.html
--Boundary-00=_Py+/LxLF7LTIHXW
Content-Type: application/x-vnd.kolab.event;
  name="kolab.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
  filename="kolab.xml"

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<event version=3D"1.0" >
 <product-id>KOrganizer 3.5.9 (enterprise35 20100409.1112955), Kolab resour=
ce</product-id>
 <uid>040000008200E00074C5B7101A82E00800000000A0567DB2FBCFCA010000000000000=
0001000000047C1A0571C9FFD4C822BAA74B1CFB6D6</uid>
 <body>Das Projektleitermeeting l=C3=A4uft auch in Q2 2010 weiter, um

a) Fortschritt zu dokumentieren
b) Probleme zu diskutieren
c) Konflikte zu l=C3=B6sen

Bitte die Statustberichte bis 11.00 Uhr an xxxxxx schicken, danke!

</body>
 <creation-date>2010-03-30T09:25:28Z</creation-date>
 <last-modification-date>2010-05-28T16:15:02Z</last-modification-date>
 <sensitivity>public</sensitivity>
 <pilot-sync-status>0</pilot-sync-status>
 <start-date>2010-04-01T11:30:00Z</start-date>
 <summary>Projektleitermeeting</summary>
 <location>xxxxxxxx</location>
 <organizer>
  <display-name>xxxxx</display-name>
  <smtp-address>xxx at xxx.de</smtp-address>
 </organizer>
 <recurrence cycle=3D"weekly" >
  <interval>1</interval>
  <day>thursday</day>
  <range type=3D"date" >2010-07-29</range>
  <exclusion>2010-04-29</exclusion>
 </recurrence>
 <attendee>
  <display-name>'xxxxx'</display-name>
  <smtp-address>xxxx at xxx.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>xxxxx at xxx.de</display-name>
  <smtp-address>xxxxx at xxx.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>'xxxxxxx at xxx.de'</display-name>
  <smtp-address>xxxxxxx at xxx.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>'xxxxxxxx'</display-name>
  <smtp-address>xxxxxxxx at xxx.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>'xxxxxxxxxxx at xxx.de'</display-name>
  <smtp-address>xxxxxxxxxxxx at xxx.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>xxxxxxxxxxx</display-name>
  <smtp-address>xxxxxxxxxxxxxxxx at xxx.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>fdsadsafdsa</display-name>
  <smtp-address>fdsa at fadsfasf.com</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>'fdsafdasfads at trgfdsgsdfdsigns.de'</display-name>
  <smtp-address>fdsasadfdsaf at rewrdsafadsns.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>'43reafdsaf4ad'</display-name>
  <smtp-address>asdfadsfads at adsfasdfsf.de</smtp-address>
  <status>accepted</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>43rrewafasdf4ds</display-name>
  <smtp-address>fadsfsasd at fasdf-afdsasdfs.com</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>'rfdsafaalf.ffffffff at fdsafsdf.de'</display-name>
  <smtp-address>ffffffff.dddddd at corpfdsafsdforatequality.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>fdsaf, fsadf, ddfasf, Bodsafsnn</display-name>
  <smtp-address>K.dsaf at fsdafsa.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <attendee>
  <display-name>W.fdsaf at dpfasdfacom.de</display-name>
  <smtp-address>W.Ecfsadfakert at fasdasdf.de</smtp-address>
  <status>none</status>
  <request-response>true</request-response>
  <invitation-sent>false</invitation-sent>
  <role>required</role>
 </attendee>
 <alarm>15</alarm>
 <advanced-alarms>
  <alarm type=3D"display" >
   <enabled>1</enabled>
   <start-offset>-15</start-offset>
  </alarm>
 </advanced-alarms>
 <x-kde-internaluid>libkcal-942576500.240</x-kde-internaluid>
 <revision>0</revision>
 <x-custom key=3D"X-KDE-LIBKCAL-ID" value=3D"libkcal-942576500.240" />
 <x-custom key=3D"X-MICROSOFT-CDO-ALLDAYEVENT" value=3D"FALSE" />
 <x-custom key=3D"X-MICROSOFT-CDO-APPT-SEQUENCE" value=3D"0" />
 <x-custom key=3D"X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE" value=3D"201003=
30T092527Z" />
 <x-custom key=3D"X-MICROSOFT-CDO-BUSYSTATUS" value=3D"BUSY" />
 <x-custom key=3D"X-MICROSOFT-CDO-IMPORTANCE" value=3D"1" />
 <x-custom key=3D"X-MICROSOFT-CDO-INSTTYPE" value=3D"1" />
 <x-custom key=3D"X-MICROSOFT-CDO-INTENDEDSTATUS" value=3D"BUSY" />
 <x-custom key=3D"X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE" value=3D"20100330T=
092527Z" />
 <x-custom key=3D"X-MICROSOFT-CDO-OWNERAPPTID" value=3D"-708954150" />
 <show-time-as>busy</show-time-as>
 <end-date>2010-04-01T13:30:00Z</end-date>
</event>

--Boundary-00=_Py+/LxLF7LTIHXW--


More information about the Synckolab mailing list