Description of problem: OO.o Impress shows incorrect images for the slides of a presentation. It normally used to crash when trying to show the presentation (pressing F5), but with today's update 2.4.1-17.4.fc9 it doesn't crash anymore. But it shows wrong images. Version-Release number of selected component (if applicable): openoffice.org-2.4.1-17.4.fc9 How reproducible: Open the attached presentation file and press F5. Steps to Reproduce: 1. Open the presentation file attached 2. Press F5, then press an arrow key or click with the mouse to go to next screen. It will render a wrong image. 3. Actual results: The results are shown in the png attached image. Expected results: Additional info: My smolt: http://www.smolts.org/show?uuid=pub_66965710-8ee7-48ec-acdd-3cac71e6d60d I have desktop effects enabled.
Created attachment 310257 [details] the wrong rendered image when in F5
Created attachment 310258 [details] a presentation file to see the bug
I see it with compiz enabled (most times, but not always), and not with it disabled. I'd like to blame some compiz problem, but I'm unsure as to how to prove that one way or the other. caolanm->ajax: any tips on identifying the culprit here ?
Thanks for the tip Caolan. It works fine with compiz disabled. It seems to be a problem with compiz-gnome instead of openoffice. oo.o writer and calc do something strange too, not always (to test it, open a long document and press the down arrow key). I tested oo.o impress and it works. I'm testing oo.o writer, and it seems to work fine so far, with desktop effects disabled. There's another culprit and I think it's compiz-gnome. For my presentations I will use my F9 with compiz disabled until this bug is fixed. Thanks again. Domingo Becker (es)
The bug is fixed. I tested today after an update and it does not those strange things anymore. The fix came in an update between 2008-07-08 and 2008-07-28. I can't say which one because I wasn't testing since the last comment. Thanks a lot. Domingo Becker
Well, what'd you know, the same here. Must have gotten fixed in some other component after all :-)