Apache OpenOffice (AOO) Bugzilla – Issue 60514
Impress causes freeze
Last modified: 2006-03-06 09:47:49 UTC
OpenOffice 2.0.0 Impress 14 January 2006 - 11:45 To learn OpenOffice Impress, I - created a 2-slide presentation, (1) title and (2) 3-line bulleted outline, 1 cm after paragraph spacing; - applied 8-spoke cartwheel transition to (2); - selected first line, clicked 'custom animation' and applied 'fly in', speed 'very fast' (default), preview on; (trying to test if OO2 supported Powerpoint-like 'text effects', which StarOffice 7 does not [apparently]); - first line diappeared then flew up from bottom, stopping just below line 2; - computer froze. On restart Recovery/CrashRep started, got the above info and 'allow Sun contact', and completed the recovery (though didn't seem to recover anything, but file had not been saved previously). on 'Send', got the following - 'Crashrep has caused an error in Kernel32,dll. Crashrep will now close'. (Windows Me). I'm the ICT Systems Manager in Liberties College (Dublin - Ireland), running StarOffice 7 on the network and intending to upgrade to SO8. I have to learn the applications in order to teach the TEACHERS (aka MS idolators), Part 2 (13:05) On trying the same thing again after restart, I could NOT replicate the error (sorry), but went ahead and extended it to a 5-slide sequence, and then fooled around with the effects. It was while running the slide-slow for the Nth time that the freeze happened again, and this is the (Notepad-ed) expanded report for CrashRep Denis J McCarthy Work: libsysmgr@eircom.net Home: djmc@indigo.ie (I accept it could be my computers fault, and will try it later om W2K machine) CrashRep crash 2 - 13:12
one for me
can you tell me the email adresse you entered in the crashreport?
Please tell me which graphic card do you use. It sounds like a known bug with ATI graphic cards.
Aha! Video card is Radeon 9200 (ATI), and I could not replicate the freeze etc. on either of two other computers. Also it (Impress freeze) doesn't happen with Open Office 2.0.1 so I'd say you've found the culprit.
Sorry, I forgot, thank you for taking the trouble to investigate.
Duplicate to issue 48454 *** This issue has been marked as a duplicate of 48454 ***
I close the issue as duplicate.