-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/05/2011 07:17 PM, [email protected] wrote:
> Hi,
> 
> On 11/18/2010 05:12 PM, Wolfgang Sourdeau wrote:
>>
>> Well... It could seem like a lame response, but all our free work is
>> provided without warranty. We cannot afford that (and nobody can)...
>>
>> I still think we do a pretty good job at fixing issues. Sometimes they
>> are just not easy to narrow down because of contextual problems. But
>> bugs that we fix rarely get reopened.
>>
> Totally agree with you - this is really great work - and it's free - you
> cannot knock that!
> 
> I too however have tried periodically to get thunderbird 3.1 + lightning
> (both the mozilla and inverse versions) to work since their respective
> releases.
> 
> But face the same issue every time I try (have posted here before).
> 
> When lightning tries to sync the calendar I get 100% CPU utilisation and
> basically a completely unusable thunderbird.
> 
> The only solution I have found is to roll back to thunderbird 3.0.x -
> being on linux you can imagine the hassle involved in keeping an old
> version when my packages keep updating.
> 
> Does anyone have a work around for this? I would really like to be
> running 3.1.

Have you tried to attach GDB to the process and get a backtrace?

One thing I'm missing for SOGo is a document explaining the different
ways we can extract debug and logging information out of the system. The
interaction between Thunderbird/Lightning and SOGo is complex and it
would be usefull to have some pointers on what logs to create, how to
run TB in some debug mode etc.

Does anyone have some pointers?

Regards,
T
> 
> Thanks
> 
> 
> 
> Vik
> 
> 
> 
> 
> 


- -- 
Tarjei Huse
Mobil: 920 63 413
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0lbnAACgkQYVRKCnSvzfJe/ACeORIQlgL0JL4R6Rbbk216E8ft
xy8AnR+HV0F5Ni4Qz3bWaTiEl5NPBENr
=FJT0
-----END PGP SIGNATURE-----
-- 
[email protected]
https://inverse.ca/sogo/lists

Reply via email to