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: > > However this will only mask the symptoms, not the root cause of the problem > (which I couldn't debug and it seems that nobody else was experiencing it).
Thanks for your reply. Are there some known dangers disabling the stack-protector? Is it the sope49-cards package I need to modify? Any other solutions? All I basically would want to do is to start from scratch with one user: to completely remove all information from Funambol and SOGo about the account (as syncing works fine with new SOGo users). I am using postgresql backend for both SOGo and Funambol, any pointers what data from which tables should I use to start all over again with this user? Regards, Peter -- [email protected] https://inverse.ca/sogo/lists
