Control: tags -1 + pending
2016-04-27 11:35 Ralf Jung:
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.
I see. I was confused because I mixed this bug and another reported at
the same time with similar symptoms.
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.
curses will be restored to show this message now, but there will still
be some delay. I think that restoring curses to show messages rather
than staying blank will cause some extra repaints and "screen" updates.
On the bright side, the shutdown process will be a bit faster than
before due to other optimisations, though, but I don't know if it will
be noticeable. (In my system it takes less than 1 second, among other
reasons because the files are in cache due to continuous testing, so
it's difficult to notice).
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
