Control: tags -1 + unreproducible moreinfo
On Sun, 12 Oct 2025 12:44:38 +0200 only4com wrote: [...] > Hi! Hello only4com! > > this is the second time I notice this behavior. > May be it is worth reporting... Thanks for your bug report. I have just tested the whole scenario on a sid virtual machine. I cannot reproduce the issue you are experiencing. I need some more information, in the hope I can help you to debug this weird behavior that you see (and I don't...). > > When I try to upgrade a package with bugs I get a warning (as expected) and I > abort the upgrade: > > > # apt update > Hit:1 https://security.debian.org/debian-security forky-security InRelease > Get:2 ... > [...] > > # apt full-upgrade > Upgrading: [...] > Summary: > Upgrading: 30, Installing: 1, Removing: 0, Not Upgrading: 0 > > Continue? [Y/n] Y > Get:1 https://deb.debian.org/debian forky/main > [...] > > retrieving bug reports... Done > Parsing Found/Fixed information... Done > critical bugs of chromium (141.0.7390.54-1 → 141.0.7390.65-1) <Outstanding> > b1 - #1117815 - Whole Trixie system freezes, requires hard reset. > Summary: > chromium(1 bug) > Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n > ********************************************************************** > ****** Exiting with an error in order to stop the installation. ****** > ********************************************************************** > Error: Sub-process /usr/bin/apt-listbugs apt returned an error code (10) > Error: Failure running script /usr/bin/apt-listbugs apt As an aside, if you answer 'n' to the "Are you sure you want to install/upgrade the above packages? [Y/n/?/...]", you stop the whole upgrade, just because one package is troublesome. Doing so can sometimes prevent the system from being upgraded for weeks, or months, while waiting for one single fixed package. This can be inconvenient (and a bad idea from a security point of view). A better choice can be to use the 'p' and/or the 'd' (see the online help that you can print with the '?' answer) to pin the troublesome package. Then you can stop the upgrade (by answering [Enter]) and restart it (with 'apt upgrade', which will skip the pinned package and possibly other related packages that must be upgraded together, but will upgrade all the rest of the packages). > > > ### after this I'm doing again: > > # apt update > [...] > # apt full-upgrade > Upgrading: [...] > Summary: [...] > Continue? [Y/n] > > > ### No warning any more! (second time and subsequent tries to full-upgrade) As I said, I am unable to reproduce this behavior. I see the warning on the second time, and on the third time, the fourth time, and so forth... > > ### But I can see the still existing bugs with > > # apt-listbugs list chromium > Retrieving bug reports... Done > Parsing Found/Fixed information... Done > critical bugs of chromium (→ ) <Outstanding> > b1 - #1117815 - Whole Trixie system freezes, requires hard reset. > Summary: > chromium(1 bug) > > > > Thank you very much! OK, I have some questions for you: * did the upgrade of the 'chromium' package actually happen? + when? (looking at '/var/log/apt/history.log' could help in figuring it out) - during the first full-upgrade attempt? - or during the second full-upgrade attempt? - or was there another attempt in between, where you answered 'y' (or just [Enter]) to the "Are you sure..." question? * what is the output of the following commands on your system? $ apt policy chromium $ cat /etc/apt/listbugs/ignore_bugs $ cat /var/lib/apt-listbugs/ignore_bugs $ cat /etc/apt/preferences.d/apt-listbugs Please let me know, thanks for caring about apt-listbugs! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgp1sAoiW7iex.pgp
Description: PGP signature
