Bug 476298 - [a11y] OOo Calc crashed while opening a file
Summary: [a11y] OOo Calc crashed while opening a file
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-12 21:51 UTC by Dave Ludlow
Modified: 2008-12-15 12:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-15 12:33:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
The crashed handler asked me to attach this (12.25 KB, text/plain)
2008-12-12 21:51 UTC, Dave Ludlow 		no flags Details
mapped stack (9.48 KB, text/plain)
2008-12-15 12:24 UTC, Caolan McNamara 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
OpenOffice.org 94045 0 None None None Never

Description Dave Ludlow 2008-12-12 21:51:26 UTC 
Created attachment 326784 [details]
The crashed handler asked me to attach this

Description of problem:
OOo Calc crashed while opening a file

Version-Release number of selected component (if applicable):
OOO300m9 (Build:9358) aka 3.0.0-9.10.fc10


How reproducible:
Just this once (sorry!)

Steps to Reproduce:
1. Open OOO Calc then open a file from File | Recent
  
Actual results:
OOo Crashed

Expected results:
The file opens

Additional info:
The file opened just fine on the second attempt.  See the attached dump log.
Comment 1 Caolan McNamara 2008-12-14 15:22:59 UTC 
An accessibility crash anyway
Comment 2 Caolan McNamara 2008-12-15 12:24:19 UTC 
Created attachment 326936 [details]
mapped stack
Comment 3 Caolan McNamara 2008-12-15 12:33:19 UTC 
If you don't need accessibility support then I suggest disabling it for your entire Desktop under system->preferences->personal->assistive technologies which should make everything slightly faster FWIW
Note You need to log in before you can comment on or make changes to this bug.