On Mon, 29 Mar 2010 08:43:07 +0200 Patrik Fimml <pat...@fimml.at> wrote:
> I have some things for you to try though that might help find the > cause: > > * Does it happen with other templates? Just tested these: 'Normal', 'Two-Columns', 'US-Letter', all go wrong the same way. > * What's your screen size? Do you have any unusual setup (Xinerama)? Not that I know of. Any diagnostic output you'd recommend? > * Does it also happen if instead of maximizing, you just manually > resize the window to fill the screen? > * If so, does it only occur when the window almost fills the screen, > or with smaller window sizes as well? After more tests, it seems the maximizing didn't matter -- if the window is left alone, it still hangs. Sort of... (read on) I find I can still type in 'abiword' -- when I switch to another window (e.g. 'sylpheed'), and back to 'abiword', the 'abiword' text is invisible, the (formerly white) text area is gray, but the cursor is still at the last place text was typed. Then I type something, and the the present line and the previous line appear, but any earlier part of the text area remains gray-on-gray. Today, on at least one occasion the text area froze and wouldn't display keystrokes. The pull down menus still work, but 'File>Quit' sometimes doesn't work. > * What happens if you don't kill abiword? Does it crash? Does it use > an increasing amount of memory? It continues to eat CPU cycles. How long would should I let it run? I'm not sure whether it's a memory hog, it never hung the system anyway. What memory usage metric would be useful? > Also, in case you are familiar with gdb, a backtrace from where it > gets stuck would be very nice. I'm not hep, would an 'strace' do? Is the 'gdb' backtrace difficult? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
