-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Milos Wimmer schrieb:
> On Mon, 22 Nov 2010, Andreas Haumer wrote:
>
>>>> Nov 21 12:35:01 sogo-ealarms-notify [18844]:
>>>> [ERROR]<0x0x8278560[SOGoEMailAlarmsManager]> alarm number mismatch
>>>> for record: {c_alarm_number = 0; c_name =
>>>> "2DDA-4CE90300-1-73A11E00.ics"; c_path =
>>>> "/Users/xss/Calendar/personal"; c_recurrence_id = 0; c_uid =
>>>> "2DDA-4CE90300-1-73A11E00"; }
>>>
>> I already found bug #922 in the SOGo bugtracking system.
>>
>> The description of this bug mentions a value != 0 for field
>> c_recurrence_id to be the cause of the problem, but in my
>> case this field is always 0!
>>
>> Also bug #922 should be fixed in SOGo-1.3.4 but I see this
>> problem with SOGo-1.3.4 (I double-checked this: SOGo shows
>> version number 1.3.4 in the logs on startup)!
>
> I can confirm this problem.
> I found the same trouble on my system.
>
Good, I'm not alone... ;-)
Let me ask you some questions to see if there are any
similarities which might give us a hint for further bug
hunting:
* Did you compile the application from sources yourself or do
you use a binary package from the sogo website?
I did compile SOPE and SOGo myself from the official 1.3.4 sources.
* Do you use a 32 or a 64 bit system?
I'm using a 32 bit system
I don't currently know if anything else might be relevant.
- - andreas
- --
Andreas Haumer | mailto:[email protected]
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFM66H+xJmyeGcXPhERAnXiAJ9n8scoRnFJPt3okRMq0d2ekYbyVwCfWhj1
2w36cjtvDI2HE/8xJfxpkHk=
=LMBL
-----END PGP SIGNATURE-----
--
[email protected]
https://inverse.ca/sogo/lists
