Replying tomyself: On Wed, Apr 11, 2012 at 10:27 PM, Peter Peltonen <[email protected]> wrote: > Hi, > > On Wed, Apr 11, 2012 at 5:35 PM, Luca Olivetti <[email protected]> wrote: >> Al 11/04/2012 15:55, En/na Peter Peltonen ha escrit: >> >> >>> *** stack smashing detected ***: /usr/sbin/sogod terminated >>> ======= Backtrace: ========= >>> /lib/i686/nosegneg/libc.so.6(__fortify_fail+0x4d)[0x62b62d] >>> /lib/i686/nosegneg/libc.so.6[0x62b5da] >>> /usr/lib/libNGCards.so.4.9[0x67b8824] >>> </snip> >> >> >> My old friend "stack smashing detected"! >> I've had this problem since 1.3.1, I put a nasty hack in my spec file to >> build NGCards with -fno-stack-protector:
I have now identified that the problem is with recurring events in Outlook. If I remove the user's first recurring events in the Outlook list view, remove the user with sogo-tool, syncing with Funambol works ok with the exception that no recurring events are showed in the SOGo web ui. If I export the ics with the problematic events and try to import it via SOGo web tool I get a stack smashing crash as well, but I manage to get some events imported ok (as opposed nonfunctional events resulting from the Funambol sync) although the upload window never closes. No recurring events imported this way either. The only way to get syncing or importing the events as ics file fully work is to remove all recurring events from Outlook first. I have now opened a bug report with example ics files: http://www.sogo.nu/bugs/view.php?id=1772 Regards, Peter -- [email protected] https://inverse.ca/sogo/lists
