Comment 1 for bug 135300

I can confirm that this has happened to me a number of times, and in fact just happened again about 30 minutes ago. It has occurred with Dapper, Edgy and Feisty on 3 different machines the last year. One was 64-bit, the other two were 32-bit. One machine has Intel i810 graphics, one has a Radeon X500, one has some manner of Nvidia chipset.

The machine does hang. The mouse moves slowly. X does not respond to events, nor do any of the keyboard lights respond. Sometimes it never comes back. One time I let it sit there for 45 minutes and it did come back.

It happens when I start up oowriter and then immediately when the window appears I click on 'File'. 'File' is highlighted, but the menu never appears. On one occasion I was able to SSH into the machine and see that X and OOo were using all the CPU. OOo required a kill -9. There is nothing in any log file I can find.

The question I have is: What is OOo doing, internally, at the time it starts and when 'File' is selected? It's a deadlock of some sort.