Achim Schaefer wrote: > Hi, > > just one observation. > > With newer versions of ?? the problem seems to be fixed. > After upgrading my testing box the problem did not appear any more. > So I assume something migrated from unstable to testing, solving the > problem.
There have been no changes in debconf or whiptail or git, unless you somehow had a much older one than the current versions in testing when you filed the bug report. None of the changes in etckeeper relate to this bug as far as I can tell. So I don't know what could have changed. > Attached the typescript. (before upgrade) From the typescript, it looks like you: * ran apt-get install sudo at the command line * saw the dialog box about uncommitted changes, and pressed enter * only then saw the message about failure to open the terminal This suggests that either whiptail displays the dialog box and then displays the failure message, or that a second dialog run is the one that failed. The only way there can be a second dialog displayed is if the git commit of the changes failed for some reason. Then it would try to display an error dialog, which might be the one that's failing. Are you able to tell from the git log if it successfully committed during the installation you sent the typescript of? (That commit included adding apt/apt.conf.d/typescript, which you may want to remove. :-) If you were still able to reproduce it I'd ask you to export DEBCONF_DEBUG=. and send another typescript. -- see shy jo
signature.asc
Description: Digital signature
