Hi Fabio, - #2396 is already fixed in openchange master and Zentyal 3.5 packages. - #2708 is indexed into Zentyal crashreport system. Fixing the consequence is not very complicated but finding the root cause and addressing it shall be trickier here. I'll try to give a look into it before openchange 2.2 release next week but I can't commit into this.
FYI, I am not monitoring sogo bug tracker. In the meanwhile, if you can reproduce the crash with Zentyal 3.5 or superior, send the crashreport and submit a bug in tracker.zentyal.org, the probability is gets fixed in a very reasonable time frame is much higher. For case #2708, it is not needed as we already have a trace we can inspect with gdb. I presume all forthcoming SOGo versions are going to merge Zentyal pull requests which addresses bugs in SOGo/OpenChange and are going to be based on newer OpenChange version. Therefore I would say that spend a little time on setting up an environment we can debug easily is a win-win strategy for everybody. Cheers, Julien. On 08/08/14 09:30, Fabio Onorini wrote: > There are news about samba panic internal error bug: #2708 or #2396 ? > > Someone can correctly use outlook like sogo site video screencast? > > > > -- > > Fabio Onorini -- Julien Kerihuel [email protected] OpenChange Project Founder Twitter: http://twitter.com/jkerihuel GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: OpenPGP digital signature
