Bug#883977: *** stack smashing detected ***: evolution terminated

2017-12-12 Thread gregor herrmann
On Mon, 11 Dec 2017 23:12:46 +0100, Michael Biebl wrote: > > rebuilding evolution fixes the problem for me. > > Maybe re-assign to evolution? > Jeremy did sourceful uploads of evo and eds and other rdeps of libical > were binNMUed, so I guess this should be fixed after the next update. Thanks,

Bug#883977: *** stack smashing detected ***: evolution terminated

2017-12-11 Thread Michael Biebl
On Sat, 09 Dec 2017 18:01:35 -0500 Joachim Breitner wrote: > Hi, > > rebuilding evolution fixes the problem for me. > > Maybe re-assign to evolution? That's most likely a result of the uncoordinated libical3 transition / NMU of evolution-data-server. Jeremy did sourceful

Bug#883977: *** stack smashing detected ***: evolution terminated

2017-12-09 Thread gregor herrmann
On Sat, 09 Dec 2017 18:01:35 -0500, Joachim Breitner wrote: [qutoing changed] > On Sat, 09 Dec 2017 17:38:48 -0500 Joachim Breitner > wrote: > > I just upgraded evolution-data-server from 3.26.2.1-1 to 3.26.2.1-1.1, > > and now evolution will not start again: Even before a

Bug#883977: *** stack smashing detected ***: evolution terminated

2017-12-09 Thread Joachim Breitner
Hi, rebuilding evolution fixes the problem for me. Maybe re-assign to evolution? Joachim On Sat, 09 Dec 2017 17:38:48 -0500 Joachim Breitner wrote: > Package: evolution-data-server > Version: 3.26.2.1-1.1 > Severity: grave > > -BEGIN PGP SIGNED MESSAGE- > Hash:

Bug#883977: *** stack smashing detected ***: evolution terminated

2017-12-09 Thread Joachim Breitner
Package: evolution-data-server Version: 3.26.2.1-1.1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, marking this as grave under the assumption that I am not the only one affected, please downgrade if it is specific to my setup for some reason. I just upgraded