Red Hat Bugzilla – Bug 408461
openoffice.org impress crash while creating new presentation
Last modified: 2007-12-03 07:03:59 EST
Description of problem: OpenOffice.org impress when I'm trying to create a new presentation. Version-Release number of selected component (if applicable): openoffice.org-impress-2.0.4-5.4.17.3 How reproducible: always Steps to Reproduce: 1. Run OOo impress 2. At presnetation wizard, click next 3. Select "Dark blue with orange" :) next 4. "Wipe right" as effect, when selecting this effect OO crashes Actual results: OOo crashes. Expected results: Customer is happy to make his nice presentation. Additional info: Will attach logs in a second.
Created attachment 275521 [details] backtrace info
Could you tell me what the output of xdpyinfo | grep RENDER is ? If there is no output at all, i.e. no XRender extension then this is likely to be #363301
Hello Caolan, [mmahut@mmahut ~]$ xdpyinfo | grep RENDER RENDER [mmahut@mmahut ~]$
Not quite the same then as that other issue, though it is clearly something to do with the cairo canvas. I'd like to know what X driver is in use, seems missing from the report. What is the output of grep drivers /var/log/Xorg.0.log caolanm->jnavrati: Can you see this problem on your RHEL-5 setup ?, maybe the bit depth of 16 is important to reproduce this. It would be interesting if someone who can reproduce this could try the proposed 2.3.0 RHEL-5.2 rpms at /mnt/redhat/brewroot/packages/openoffice.org/2.3.0/6.2.el5 to see if that will make any difference
It's occurring on my vmware virtual desktop. [mmahut@mmahut ~]$ grep drivers /var/log/Xorg.0.log (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so [mmahut@mmahut ~]$ I'm downloading these rpms, I will let you know soon.
Nah, hold it. Comment #5 is what I expected to see instead of Comment #3. If, from the perspective of OOo being run inside vmware there is no RENDER extension then this is bug 363301. A workaround is to launch might be to e.g. launch oowriter and toggle off "tools->options->view->use hardware acceleration" and then try to repeat the original steps. *** This bug has been marked as a duplicate of 363301 ***