Bug#663738: apt-listchanges doesn't wait for confirmation before installation proceeds
Hi,
I can confirm this (when using the curses UI, see below) and I have some
precisions as well a possible workaround.
First, this is the contents of the configuration file
(/etc/apt/listchanges.conf) on the "testing" box where the problem is
observable :
[apt]
frontend=pager
email_address=root
confirm=1
save_seen=/var/lib/apt/listchanges.db
which=both
The problem described in the original bug report is in my case further
aggravated by the fact that the mail report is not sent.
The box is updated daily. The last time the message was sent was on
February, 23rd. Here is the /var/log/aptitude excerpt for this day :
[CONSERVÉ] octave3.2
[INSTALLÉ] printer-driver-pxljr
[MIS A JOUR] alsa-oss 1.0.17-5 -> 1.0.25-1
[MIS A JOUR] alsa-tools 1.0.24.1-3 -> 1.0.25-1
[MIS A JOUR] alsa-tools-gui 1.0.24.1-3 -> 1.0.25-1
[MIS A JOUR] alsa-utils 1.0.24.2-5 -> 1.0.25-1
[MIS A JOUR] fonts-pecita 3.2-4 -> 3.3-1
[MIS A JOUR] foomatic-db 20111206-1 -> 20120212-1
[MIS A JOUR] foomatic-filters 4.0.9-1 -> 4.0.12-1
[MIS A JOUR] ghostscript 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] ghostscript-cups 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] ghostscript-x 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] libasound2 1.0.24.1-4 -> 1.0.25-2
[MIS A JOUR] libencode-locale-perl 1.02-2 -> 1.03-1
[MIS A JOUR] libev4 1:4.04-1 -> 1:4.11-1
[MIS A JOUR] libgs9 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] libgs9-common 9.04~dfsg-3 -> 9.05~dfsg-2
[MIS A JOUR] libqscintilla2-8 2.6-3 -> 2.6.1-1
[MIS A JOUR] libsqlite3-0 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] libsqlite3-dev 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] login 1:4.1.4.2+svn3283-3 -> 1:4.1.5-1
[MIS A JOUR] manpages-fr-extra 2018 -> 20120212
[MIS A JOUR] mime-support 3.51-1 -> 3.52-1
[MIS A JOUR] openprinting-ppds 20111206-1 -> 20120212-1
[MIS A JOUR] passwd 1:4.1.4.2+svn3283-3 -> 1:4.1.5-1
[MIS A JOUR] pyqt4-dev-tools 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-blockdiag 1.1.2-1 -> 1.1.2-2
[MIS A JOUR] python-qscintilla2 2.6-3 -> 2.6.1-1
[MIS A JOUR] python-qt4 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-dbus 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-dev 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-doc 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-gl 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-qt4-sql 4.9-2 -> 4.9.1-1
[MIS A JOUR] python-sip 4.13.1-3 -> 4.13.2-1
[MIS A JOUR] python-sip-dev 4.13.1-3 -> 4.13.2-1
[MIS A JOUR] sakura 2.4.2-3 -> 2.4.2-4
[MIS A JOUR] sqlite3 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] sqlite3-doc 3.7.9-2 -> 3.7.10-1
[MIS A JOUR] xserver-xorg-video-dummy 1:0.3.5-1 -> 1:0.3.5-2
The day after, the message was not sent. Here is what was upgraded on
February, 24th :
[INSTALLÉ, DÉPENDANCES] sphinx-common
[INSTALLÉ, DÉPENDANCES] sphinx-doc
[INSTALLÉ, DÉPENDANCES] xz-lzma
[CONSERVÉ] octave3.2
[MIS A JOUR] ca-certificates 20111211 -> 20120212
[MIS A JOUR] dbus 1.4.16-1 -> 1.4.18-1
[MIS A JOUR] dbus-x11 1.4.16-1 -> 1.4.18-1
[MIS A JOUR] libaacs0 0.3.0-3 -> 0.3.0-4
[MIS A JOUR] libass4 0.10.0-2 -> 0.10.0-3
[MIS A JOUR] libc-client2007e 8:2007e~dfsg-3.2 -> 8:2007e~dfsg-3.3
[MIS A JOUR] libdbus-1-3 1.4.16-1 -> 1.4.18-1
[MIS A JOUR] libdiscid0 0.2.2-2 -> 0.2.2-3
[MIS A JOUR] libevent-2.0-5 2.0.16-stable-1 -> 2.0.17-stable-1
[MIS A JOUR] libgudev-1.0-0 175-3 -> 175-3.1
[MIS A JOUR] libjs-sphinxdoc 1.0.8+dfsg-2 -> 1.1.2+dfsg-5
[MIS A JOUR] librhino-java 1.7R3-4 -> 1.7R3-5
[MIS A JOUR] libtamuanova-0.2 0.2-1 -> 0.2-2
[MIS A JOUR] libudev0 175-3 -> 175-3.1
[MIS A JOUR] libwrap0 7.6.q-22 -> 7.6.q-23
[MIS A JOUR] mercurial 2.0.2-1 -> 2.1-1
[MIS A JOUR] mercurial-common 2.0.2-1 -> 2.1-1
[MIS A JOUR] mlock 8:2007e~dfsg-3.2 -> 8:2007e~dfsg-3.3
[MIS A JOUR] pdf2djvu 0.7.11-1 -> 0.7.12-1
[MIS A JOUR] python-apt 0.8.0 -> 0.8.3+nmu1
[MIS A JOUR] python-apt-common 0.8.0 -> 0.8.3+nmu1
[MIS A JOUR] python-sphinx 1.0.8+dfsg-2 -> 1.1.2+dfsg-5
[MIS A JOUR] python-wimpiggy 0.0.7.31+dfsg-1 -> 0.0.7.36+dfsg-1
[MIS A JOUR] rhino 1.7R3-4 -> 1.7R3-5
[MIS A JOUR] tcpd 7.6.q-22 -> 7.6.q-23
[MIS A JOUR] udev 175-3 -> 175-3.1
[MIS A JOUR] xfce4-session 4.8.2-3 -> 4.8.3-1
[MIS A JOUR] xpra 0.0.7.31+dfsg-1 -> 0.0.7.36+dfsg-1
Please note the upgrade of python-apt 0.8.0 -> 0.8.3+nmu1 . Later, I tried
uninstalling xz-lzma but this did not change anything.
Yet, I find it strange that the problem only exhibited itself _during_ the
upgrade since when the error messages are printed the new packages are not
even unpacked (AFAIK). On the other hand, I don't see any package upgrade on
the day before that could have triggered the problem (not even on this day
activity log).
And now for the workaround : I found out that this problem only occur when
the curses UI of aptitude is launched by a normal user, gaining root
privileges when requesting a database update, packages upgrade, ...
If you first su to root before to run aptitude, then everything goes as
expected. This is why the problem does not show when using the CLI
("aptitude dist-upgrade") invocation.
Hope this helps.
phep
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
wi
Bug#663738: apt-listchanges doesn't wait for confirmation before installation proceeds
Package: apt-listchanges Version: 2.85.9 Severity: important When using aptitude, after displaying the list of changes correctly, the confirmation prompt immediately fails with the message: Confirmation failed, don't save seen state There's also a message afterwards to the effect that stdin cannot be re-opened by dpkg-preconfigure... here's a partial log of my last aptitude session: Reading changelogs... Done Confirmation failed, don't save seen state. dpkg-preconfigure: unable to re-open stdin: (Reading database ... 185633 files and directories currently installed.) Thanks! -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-listchanges depends on: ii apt0.8.15.10 ii debconf [debconf-2.0] 1.5.41 ii debianutils4.2.1 ii python 2.7.2-10 ii python-apt 0.8.3+nmu1 ii python-support 1.0.14 ii ucf3.0025+nmu2 Versions of packages apt-listchanges recommends: ii exim4 4.77-1 ii exim4-daemon-light [mail-transport-agent] 4.77-1+b1 Versions of packages apt-listchanges suggests: ii conkeror [www-browser] 1.0~~pre+git120102-1 ii google-chrome-stable [www-browser] 17.0.963.79-r125985 ii iceweasel [www-browser] 10.0.2-1 ii python-glade22.24.0-3 ii python-gtk2 2.24.0-3 ii rxvt-unicode-256color [x-terminal-emulator] 9.15-1 ii w3m [www-browser]0.5.3-5 ii xterm [x-terminal-emulator] 276-2 -- debconf information: * apt-listchanges/confirm: true * apt-listchanges/which: both * apt-listchanges/frontend: pager * apt-listchanges/email-address: * apt-listchanges/save-seen: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663738: apt-listchanges doesn't wait for confirmation before installation proceeds
Hi Robert, * Robert Luberda [04. Apr. 2016]: >> I can confirm this: I'm using apt-get and apt-listchanges on an >> up-to-date debian/testing system and since some time > > Since when exactly? I assume that your version of apt-listchanges is > 2.86 which has been available in testing since March 23rd. Does the > issue started to appear earlier or later than the above date? > > Is there any chance that you call apt-get with `-y' or `-q' > (`--assume-yes' or `--quiet') option? Thanks for the hint. I found the NEWS section and reconfigured apt-listchanges. Ciao; Gregor
Bug#663738: apt-listchanges doesn't wait for confirmation before installation proceeds
Dear Robert Luberda, debian maintainers, * Jose Antonio Ortega Ruiz [13. Mar. 2012]: > When using aptitude, after displaying the list of changes correctly, > the confirmation prompt immediately fails with the message: > > Confirmation failed, don't save seen state > > There's also a message afterwards to the effect that stdin cannot be > re-opened by dpkg-preconfigure... here's a partial log of my last > aptitude session: I can confirm this: I'm using apt-get and apt-listchanges on an up-to-date debian/testing system and since some time apt-listchanges does not wait for confirmation even after I dpkg-reconfigured it to do so. There is no indication whatsoever why it fails to wait for the confirmation, e.g.: [...] lxml (3.6.0-1) unstable; urgency=medium * New upstream version 3.6.0. -- Matthias Klose Tue, 29 Mar 2016 13:19:30 +0100 xserver-xorg-video-intel (2:2.99.917+git20160325-1) unstable; urgency=medium * New upstream snapshot. -- Timo Aaltonen Tue, 29 Mar 2016 10:29:35 +0300 apt-listchanges: Mailing root: apt-listchanges: changelogs for len (Reading database ... 194479 files and directories currently installed.) Preparing to unpack .../libapparmor1_2.10-4_amd64.deb ... [...] -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-listchanges depends on: ii apt1.2.9 ii debconf [debconf-2.0] 1.5.59 ii debianutils4.7 ii python-apt 1.1.0~beta2 pn python:any ii ucf3.0036 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii exim4-daemon-heavy [mail-transport-agent]4.87~RC6-3 ii firefox-esr [www-browser]45.0.1esr-1 ii lynx [www-browser] 2.8.9dev8-4 pn python-glade2 ii python-gtk2 2.24.0-4 ii rxvt-unicode-256color [x-terminal-emulator] 9.21-1+b1 ii w3m [www-browser]0.5.3-27 ii xterm [x-terminal-emulator] 324-1 -- debconf information: * apt-listchanges/save-seen: false * apt-listchanges/frontend: pager * apt-listchanges/email-address: root * apt-listchanges/confirm: true * apt-listchanges/which: both
Bug#663738: apt-listchanges doesn't wait for confirmation before installation proceeds
Gregor Zattler pisze: > > I can confirm this: I'm using apt-get and apt-listchanges on an > up-to-date debian/testing system and since some time Since when exactly? I assume that your version of apt-listchanges is 2.86 which has been available in testing since March 23rd. Does the issue started to appear earlier or later than the above date? Is there any chance that you call apt-get with `-y' or `-q' (`--assume-yes' or `--quiet') option? Regards, robert
