Bug 450839 - ooimpress got crashed by pressing F5 or F9
Summary: ooimpress got crashed by pressing F5 or F9
Keywords:
Status: CLOSED DUPLICATE of bug 363301
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: openoffice.org
Version: 5.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Caolan McNamara
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-11 09:51 UTC by Xiaohong Wang
Modified: 2008-06-12 08:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-12 08:15:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Xiaohong Wang 2008-06-11 09:51:42 UTC
Description of problem:


Version-Release number of selected component (if applicable):
openoffice.org-*-2.3.0-6.5.1.el5_2

How reproducible:
always

Steps to Reproduce:
1. Open an existing Impress file and press F5 or F9
2.
3.
  
Actual results:
Got crashed

Expected results:


Additional info:
pls refer to
<http://nfs.nay.redhat.com/xwang/logs/crash-F5>
<http://nfs.nay.redhat.com/xwang/logs/crash-F9>

Comment 1 Caolan McNamara 2008-06-11 10:17:14 UTC
And does the prior release for RHEL-5.2 of 2.3.0-6.5 function correct under the
same circumstances. 

I'm having a difficulty in believing that this security release could possibly
have any effect in this area

Comment 2 Caolan McNamara 2008-06-11 10:19:04 UTC
Specifically can I get the output of "xdpyinfo" on the display you are using for
testing. Is it a vnc view ?

Comment 3 Caolan McNamara 2008-06-11 11:38:23 UTC
I strongly suspect that this is a duplicate of 363301 and is due to not handling
a missing RENDER extension.

If this is correct, then xdpyinfo | grep RENDER will say nothing on the display
on which the crash is seen.

Comment 4 Caolan McNamara 2008-06-12 08:15:43 UTC

*** This bug has been marked as a duplicate of 363301 ***


Note You need to log in before you can comment on or make changes to this bug.