Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-14 Thread Thijs Kinkhorst
On Thu, November 13, 2014 22:49, Thomas Liske wrote: tag 767370 upstream,fixed-upstream thanks Hi Thijs, needrestart did not find any kernel images which triggers this special bug. There was a divison by zero triggered by calculating the progressbar length. needrestart did not die since

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-14 Thread Patrick Matthäi
Am 14.11.2014 um 10:57 schrieb Thijs Kinkhorst: On Thu, November 13, 2014 22:49, Thomas Liske wrote: tag 767370 upstream,fixed-upstream thanks Hi Thijs, needrestart did not find any kernel images which triggers this special bug. There was a divison by zero triggered by calculating the

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-13 Thread Thomas Liske
tag 767370 upstream,fixed-upstream thanks Hi Thijs, needrestart did not find any kernel images which triggers this special bug. There was a divison by zero triggered by calculating the progressbar length. needrestart did not die since the linux specific stuff was running in an eval block.

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-12 Thread Thomas Liske
Re, On 11/11/2014 11:21 AM, Thijs Kinkhorst wrote: Interesting: it doesn't fail when running with -v. But doesn't use my standard dialog frontend either... the -v options forces needrestart to use NeedRestart::UI::stdio which does not use debconf. Could you please run needrestart (without

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-12 Thread Thijs Kinkhorst
On Wed, November 12, 2014 21:28, Thomas Liske wrote: Could you please run needrestart (without -v) again and run `pstree -a`? There should be debconf's frontend running as the parent process of needrestart: | | `-bash | | `-frontend -w

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-11 Thread Thijs Kinkhorst
On Mon, November 10, 2014 21:46, Thomas Liske wrote: What can I do to help debug this? Good question. I'm unable to reproduce it on any of my maschines nor do I have any idea why this happens. Maybe we require some debconf guru helping us to dig into it? Maybe.. I'm not a debconf guru

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-10 Thread Thijs Kinkhorst
On Sun, November 2, 2014 12:42, Thomas Liske wrote: Hi, On 10/30/2014 04:59 PM, Thijs Kinkhorst wrote: With current needrestart on jessie, after upgrading my packages I see debconf-command like output in my terminal (SET ...) but no debconf interface is presented. It waits for input after

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-10 Thread Thomas Liske
Hi Thijs, On 11/10/2014 04:43 PM, Thijs Kinkhorst wrote: It still exists, also when running directly. Using the dialog frontend, but can also reproduce when selecting the readline frontend. should be independent of the frontend... the debconf core is missing (/dev/stdout should never reach

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-11-02 Thread Thomas Liske
Hi, On 10/30/2014 04:59 PM, Thijs Kinkhorst wrote: With current needrestart on jessie, after upgrading my packages I see debconf-command like output in my terminal (SET ...) but no debconf interface is presented. It waits for input after each one, so I press enter after SET .., then afetr SUBST

Bug#767370: does not start debconf, displays debconf commands and waits for input

2014-10-30 Thread Thijs Kinkhorst
Package: needrestart Version: 1.2-2 Severity: normal Hi, With current needrestart on jessie, after upgrading my packages I see debconf-command like output in my terminal (SET ...) but no debconf interface is presented. It waits for input after each one, so I press enter after SET .., then afetr