Activity log for bug #844454

Date Who What changed Old value New value Message
2011-09-08 02:42:31 John Clemens bug added bug
2011-09-08 02:43:53 John Clemens description Bug #635268 is back in Onieric Beta 1, intel 4500, unity 3d. To reproduce, just open xterm and start typing.... what you type will be garbles, but the output will be fine. Similar corruption to before, with a white box covering the first part of any letter typed, and scrolling leaving a few pixels of the fonts on the left side of the terminal window. I can't figure out how to reopen that bug for onieric, since its closed for maverick. Also, since this has now come back at least twice, and xterm has uncovered other previously unknown bugs (like nouveau w/ 3d support crashing Xorg with fixed width fonts) can we get the ubuntu QA team to add 'xterm' to a test case somewhere? xterm is a basic application, and problems like this with it often indicate real issues that other applications will eventually hit. Just run it, make sure you can type into the window, and that all the fonts look right on both the input and output text, and that it's white text on a black background. Its a simple 30 second test, and will catch issues like this. Bug #635258 is back in Onieric Beta 1, intel 4500, unity 3d. To reproduce, just open xterm and start typing.... what you type will be garbles, but the output will be fine. Similar corruption to before, with a white box covering the first part of any letter typed, and scrolling leaving a few pixels of the fonts on the left side of the terminal window. I can't figure out how to reopen that bug for onieric, since its closed for maverick. Also, since this has now come back at least twice, and xterm has uncovered other previously unknown bugs (like nouveau w/ 3d support crashing Xorg with fixed width fonts) can we get the ubuntu QA team to add 'xterm' to a test case somewhere? xterm is a basic application, and problems like this with it often indicate real issues that other applications will eventually hit. Just run it, make sure you can type into the window, and that all the fonts look right on both the input and output text, and that it's white text on a black background. Its a simple 30 second test, and will catch issues like this.
2011-09-08 18:40:50 John Clemens marked as duplicate 841103