Accessing File menu after starting OpenOffice locks up machine for approx 10 mins
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openoffice.org (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: openoffice.org
Hi, I suspect this is not going to be a useful report, but I'll do what I can, and if you need any more details let me know.
When I start OpenOffice, I usually go to the File menu (to e.g. open a document, or print one if I opened a document from the command line with 'oowriter foo'). When I do that, often (but not always, I think) my entire machine locks up. I used to think it had crashed and just rebooted, but lately I have noticed that if I wait for what seems like 5-10 minutes everything comes back OK. I don't think it is swapping as there is not continual hard drive activity during this time. Usually the mouse pointer will follow mouse movements, but the keyboard LEDs are unresponsive and I am unable to perform any operations using the mouse (e.g. switching to a terminal to see what processes might be eating CPU).
I am using what I believe to be a bog-standard version of Feisty Fawn. I am using the proprietary fglrx X server, since I am unable to get anything else to work with my Radeon X1300 card, this may or may not be relevant.
I don't know what else I can say, I couldn't see any similar bug reports so thought I would raise this as an issue even though I doubt there's enough information here to be helpful. I should say this has been happening for a long time, but up until recently when I noticed the machine had not locked up permanently, I just put it down to the X server crashing and decided it wasn't worth reporting since it's proprietary software. Any suggestions on how I could investigate this further would be gratefully received. Thanks.
| beauharg (denharg) wrote | #1 |
| df.daly (df-daly) wrote | #2 |
| Chris Cheney (ccheney) wrote | #3 |
| Changed in openoffice.org: | |
| status: | New → Fix Released |
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.