Thanks for trying with several terminals. I have utterly no clue what's happening here, and I can't reproduce it myself. Those look like maybe escape codes that are being spewed to the display but not interpreted, but why would that be?
The only thing I could think of is a background thread trying to write to the display before curses is initialized. But (a) only the foreground thread ever writes to the terminal (theoretically :-P ) and (b) no background thread is started before curses is ready anyway. A background thread directly calling a curses update routine could also theoretically cause trouble. However, all the code goes through an abstraction layer that puts a lock around curses updates, so that can't happen. Is there any possibility you could be running some other program that's putting your terminal into an odd state? Do you still get this problem if instead of just "aptitude" you run "reset ; aptitude"? Daniel
signature.asc
Description: Digital signature
