Comment 1 for bug 141366

OK, while investigating into this I found that there's in fact an (undocumented) configuration option "quiet" which can be used to make apt-listchanges do what I want if I put "quiet=2" in /etc/apt/listchanges.conf. But I'm not sure if this option was ever meant to be used that way, and it isn't reachable via the debconf dialog either.

What do you think, should this bug be reassigned to apt-listchanges as a documentation bug, or should synaptic be made to behave better? Maybe it'd be enough to simply remove the putenv("APT_LISTCHANGES_FRONTEND=gtk") from synaptic. The console window should open automatically after a timeout anyway, and apt-listchanges is not installed by default.