Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-07 Thread Nico Golde
Hi, * Craig Small csm...@debian.org [2011-03-07 10:49]: On Sun, Mar 06, 2011 at 09:38:09PM +0100, Stefano Zacchiroli wrote: I'm not sure if the problem is in newsbeuter (e.g. using the lib in some unappropriate way which worked up to now) or in libncursesw5 (e.g. unexpected/ undeclared

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-07 Thread Sven Joachim
On 2011-03-07 17:35 +0100, Nico Golde wrote: * Craig Small csm...@debian.org [2011-03-07 10:49]: On Sun, Mar 06, 2011 at 09:38:09PM +0100, Stefano Zacchiroli wrote: I'm not sure if the problem is in newsbeuter (e.g. using the lib in some unappropriate way which worked up to now) or in

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-07 Thread Nico Golde
Hi, * Sven Joachim svenj...@gmx.de [2011-03-07 17:53]: On 2011-03-07 17:35 +0100, Nico Golde wrote: * Craig Small csm...@debian.org [2011-03-07 10:49]: On Sun, Mar 06, 2011 at 09:38:09PM +0100, Stefano Zacchiroli wrote: I'm not sure if the problem is in newsbeuter (e.g. using the lib in

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-07 Thread Sven Joachim
On 2011-03-07 18:21 +0100, Nico Golde wrote: * Sven Joachim svenj...@gmx.de [2011-03-07 17:53]: It seems to be bug #617210 in ncurses. At least, changing the offending code in ncurses' newwin() function back to what is was before 5.8 fixes the newsbeuter segfault for me (stfl is calling

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-07 Thread dickey
Quoting Sven Joachim svenj...@gmx.de: On 2011-03-07 18:21 +0100, Nico Golde wrote: * Sven Joachim svenj...@gmx.de [2011-03-07 17:53]: It seems to be bug #617210 in ncurses. At least, changing the offending code in ncurses' newwin() function back to what is was before 5.8 fixes the

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-07 Thread Sven Joachim
On 2011-03-07 21:11 +0100, dic...@his.com wrote: Quoting Sven Joachim svenj...@gmx.de: Probably yes, if only because the faulty newwin() code is in a released version of ncurses, and other distributions might pick it up sooner or later. yes - that's not a good bug (far worse than the usual

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-06 Thread Stefano Zacchiroli
Package: newsbeuter Version: 2.4-1 Severity: serious After upgrading libncursesw5 from 5.7+20100313-5 to 5.8-1, newsbeuter started segfaulting at startup (no matter if invoked with -r or not). Reverting libncursesw5 to 5.7+20100313-5, currently in testing, fixes the problem. I'm not sure if the

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-06 Thread Nico Golde
Hi, * Stefano Zacchiroli z...@debian.org [2011-03-06 21:46]: After upgrading libncursesw5 from 5.7+20100313-5 to 5.8-1, newsbeuter started segfaulting at startup (no matter if invoked with -r or not). Reverting libncursesw5 to 5.7+20100313-5, currently in testing, fixes the problem. I'm not

Bug#616711: segfault at start with libncursesw5 5.8-1

2011-03-06 Thread Craig Small
On Sun, Mar 06, 2011 at 09:38:09PM +0100, Stefano Zacchiroli wrote: I'm not sure if the problem is in newsbeuter (e.g. using the lib in some unappropriate way which worked up to now) or in libncursesw5 (e.g. unexpected/ undeclared ABI change). I'm Cc:-ing the libncursesw5 maintainer with this