#193694 stdin not released after debconf db_stop

Package:
debconf
Source:
debconf
Submitter:
Miernik
Date:
2025-08-17 17:47:04 UTC
Severity:
normal
Tags:
#193694#5
Date:
2003-05-18 03:04:48 UTC
From:
To:
Setting up proftpd (1.2.8-6) ...
Installing new version of config file /etc/init.d/proftpd ...
NO MATCH: No such file or directory
Configuration file `/etc/proftpd.conf'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
    3 or T  : show a thre way difference between current, older,
              and new versions of the file
      M     : Do a 3 way merge between current, older,
              and new versions of the file [Very Experimental]
      Z     : start a new shell to examine the situation
 The default action is to keep your current version.
***  proftpd.conf  (Y/I/N/O/D/Z) [default=N] ?3
t

m
T

M



D


d




dpkg: error processing proftpd (--configure):
 subprocess post-installation script killed by signal (Interrupt)
Setting up mozilla-browser-snapshot (0.0.20030507.12.trunk-1) ...


Pressing 3, T or M or any other letter at this prompt doesn't do
anything, while it should. Finally I pressed Ctrl+C to go through.

Besides that:

3 or T  : show a thre way difference between current, older,

should be:

3 or T  : show a three way difference between current, older,

And ***  proftpd.conf  (Y/I/N/O/D/Z) [default=N] ?
should list the 3 T and M letters as options.

#193694#10
Date:
2003-05-19 02:18:27 UTC
From:
To:
This is debconf breakage.  stdin is not connected to the tty, so interaction
is impossible.  What I did in apt-listchanges to work around this was to
redirect ucf's stdin from /dev/tty.  This sucks.

#193694#21
Date:
2003-05-20 16:10:07 UTC
From:
To:
Manoj Srivastava wrote:

Well db_stop is not meant to drop the tty, it just tells the debconf
engine to stop listening for commands. There is unlikely to be a better
workaround until debconf's whole communications system is redone.

#193694#26
Date:
2003-05-20 16:28:57 UTC
From:
To:
(note: I didn't reassign this bug, nor claim that db_stop was supposed to do
anything other than what it does)

However, at this point, is there still an open fd which is connected to
stdin inherited from dpkg which could be put back at fd 0?

#193694#31
Date:
2003-05-20 22:25:11 UTC
From:
To:
Matt Zimmerman wrote:

Nope. I suppose there could be, but it'd require modifiying debconf.