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. needrestart was not started in verbose mode so it does not report the error message (divsion by zero) of the eval call.

While dieing in the eval block the stdout/stdin fd's were left screwed up... resulting in the debconf commands on the tty.

In verbose mode the bug was not triggered since verbose mode disables the progressbar stuff.


Damn, fixed & sorry,
Thomas


On 11/13/2014 08:16 AM, Thijs Kinkhorst wrote:
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 /usr/share/debconf/frontend
/usr/sbin/needrestart
   |   |                   `-needrestart /usr/sbin/needrestart


   ├─sshd
   │   ├─sshd
   │   │   └─sshd
   │   │       └─bash
   │   │           └─sudo bash
   │   │               └─bash
   │   │                   └─pstree -a
   │   └─sshd
   │       └─sshd
   │           └─bash
   │               └─sudo bash
   │                   └─bash
   │                       └─frontend -w
/usr/share/debconf/frontend /usr/sbin/needrestart
   │                           └─needrestart
/usr/sbin/needrestart
   │                               └─(10-dpkg)

Your /dev/tty is a valid character device?

$ ls -lha /dev/tty
crw-rw-rw- 1 root tty 5, 0 Nov 12 21:19 /dev/tty

Yes:
crw-rw-rw- 1 root tty 5, 0 nov 13 08:12 /dev/tty


Cheers,
Thijs



--

    ::  WWW:                         http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:                   xmpp:[email protected]  :::
    ::  flickr:              http://www.flickr.com/photos/laugufe/  ::


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to