OpenOffice.org Writer crash with Orca screen reader

Bug #669354 reported by Paolo Rotolo
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openoffice.org (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

OpenOffice.org Writer crash with Orca Screen Reader active. (Ubuntu 10.10)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: openoffice.org-common 1:3.2.1-7ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Nov 1 09:29:20 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
SourcePackage: openoffice.org

The terminal wrote:

:~$ error: line 3: bad flagvector
error: line 7: bad flagvector
error: line 10: bad flagvector
error: line 12: bad flagvector
error: line 14: bad flagvector
error: line 16: bad flagvector
error: line 21: bad flagvector
error: line 26: bad flagvector

** (soffice:3218): WARNING **: Exception in get_text_at_offset()

Revision history for this message
Paolo Rotolo (paolorotolo) wrote :
summary: - OpenOffice.org Writer crash with Orca screen reader.
+ OpenOffice.org Writer crash with Orca screen reader
description: updated
Revision history for this message
Attila Hammer (hammera) wrote :

I see similar problem with Ubuntu Lucid, so this bug is not only Maverick specific.
If I known right, in Lucid have packaged Openoffice.org 1:3.2.0-7ubuntu4 version.
In Ubuntu Accessibility List Milton sent following letter:
"Dear List,

On my machine I use Orca 2.91.2 pre and Maverick.
I notice that OpenOffice crashes when I for example create a new wirter
document and want to quit OpenOffice.
This stops Orca speaking, a sighted person told me a dialog is on the
screen that OpenOffice crashed. Pressing enter for OK default Orca is
talking resuming.
When I open a document from my Document folder OpenOffice has no
problems when I quit the document."

Attila

tags: added: a11y ooo-writer
Revision history for this message
Attila Hammer (hammera) wrote :

Charlie, if not matter I change this bug status with confirmed status, and wayt Milton comments, because I not found a sure reproducation method yet with help reproducing this issue. But unfortunately this bug is valid Under Lucid and Maverick packaged Openoffice.org Writer.

Attila

Changed in openoffice.org (Ubuntu):
status: New → Confirmed
Revision history for this message
jose vilmar estacio de souza (vilmar-informal) wrote :

In addition, I found that sometimes when I am editing a file, OO seems to crash and orca stays mute.
After killing OO manually, orca back to talking.

tags: added: lucid maverick
Revision history for this message
Milton (milton-tomaatnet) wrote :

I confirm the crash also simmerlarly for Calc. Without Orca running everything is fine. Starting a new document and after quit OO either with ctrl+w or through File > Close, Orca stops speaking and pressing enter on the dialog window on the screen Orca resume speaking. I have to start OO over again to continue with other documents.

description: updated
tags: added: orca
tags: removed: orca
Revision history for this message
penalvch (penalvch) wrote :

Paolo Rotolo, thank you for reporting this bug and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in openoffice.org (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.