Hi, > In my case (using konsole) it just goes blank as part of restoring > curses, then shuts down and the previous lines of the screen are > visible, without painting any extra blank lines in between. > > aptitude doesn't print empty lines on purpose, so printing a message > like "Shutting down..." wouldn't help in this case -- if the extra blank > lines are printed (as far as aptitude can tell) for no apparent reason > and out of aptitude's control, then the "Shutting down..." message from > aptitude would disappear from the visible part of the terminal as well > when those blank lines are printed. > > So the key is to find out why the blanking of the screen happens.
Maybe there was a misunderstanding here, but there are no unexpected "blank lines". What happens is that the entire console goes black after pressing "q<ENTER>". Then, after some time (longer than I would expect), the prompt appears as expected. Additional empty lines appear only if I hit "<ENTER>" while the screen is black. The bug was reported because I was not patient enough to wait for this black screen to go away -- after 2 or 3 seconds, I concluded that something went wrong and did Ctrl-C. That's why I suggested to use curses to show some "Shutting down..." instead of going black. curses should be fast enough for that; after all, if I just hit "<ENTER>" (no "q"), then the aptitude main window immediately appears (and it tells me to wait a little while it does some work). The slow bit here is aptitude, not curses. Kind regards, Ralf _______________________________________________ Aptitude-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
