Abiword segfaults on copy

Bug #173695 reported by Don Marti
4
Affects Status Importance Assigned to Milestone
abiword (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Start abiword on a Microsoft Word .doc file.

In abiword: Control-A, Control-C to select all, then copy,

This is what I get in the shell:

$ file 33804_NetworkWorld_112807-linuxcast.doc
33804_NetworkWorld_112807-linuxcast.doc: Microsoft Office Document
$ abiword 33804_NetworkWorld_112807-linuxcast.doc

(abiword:19877): libgsf:msole-CRITICAL **: ole_get_block: assertion `block < ole->info->max_block' failed
Wrong Grammar|INT: Hi.|
 LowOff 0 HighOff 8
Wrong Grammar| Im Don (Mardy) and Im here with Brian Stevens, Vice President of Engineering and CTO at Red Hat.|
 LowOff 9 HighOff 108
Wrong Grammar| Welcome to the broadcast, Brian.|
 LowOff 109 HighOff 142
Aborted (core dumped)

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Can you provide us a .doc file which causes the crash ? Could also please run a backtrace with debugging symbols of this ? (see https://wiki.ubuntu.com/Backtrace ) Thank you !

Changed in abiword:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Sorry, I forgot something: what version of Ubuntu and of Abiword are you running ?

Revision history for this message
Don Marti (dmarti) wrote :

Here's the .doc file from this bug report.

I'm running Ubuntu 7.10, Gutsy Gibbon. Abiword is version 2.4.6.

Revision history for this message
Don Marti (dmarti) wrote :

And here's the backtrace.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you, I'll try to reproduce this and forward upstream.

Changed in abiword:
status: Incomplete → Triaged
Revision history for this message
Rylie Pavlik (abiryan) wrote :

Did this ever make it upstream? If/when it does please remember to link this bug.

Revision history for this message
Daniel Gimpelevich (daniel-gimpelevich) wrote :

"Ubuntu Tablet" seems to have been randomly/accidentally subscribed to this bug. Unsubscribing it.

Revision history for this message
penalvch (penalvch) wrote :

Don Marti, thank you for reporting this 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. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install abiword-dbg && sudo service apport start force_start=1

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

Now reproduce the crash, then 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'. If you run the command against the crash report and it does nothing, you may be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
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.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in abiword (Ubuntu):
status: Triaged → 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.