v2.9.2 crashes constantly during use

Bug #1056181 reported by StefanHuszics
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
abiword (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have constant crashes with UNSTABLE* abiword 2.9.2 when working with documents created STABLE* abiword 2.8.6.
On top of this I have lots of errors with misaligned pictures, text not showing at all, etc.

Who made the bright decision to replace the STABLE 2.8.6 for the UNSTABLE 2.9.2 that the developers them selves don't even recomend for a production environment?

If I wanted a system where basic functionallity software was unstable I would NOT be using Ubuntu in the first place. Someone please make put back the working 2.8.6 version of abiword in Ubuntu so my PRODUCTION SYSTEM again is usable.

----------
Cut and paste today from the abiword website

    Our latest stable release is version 2.8.6. It's available for a number of languages and operating systems.

    Our latest development release is version 2.9.2. Development releases are aimed at developers, or people willing to test unstable software. They should not be used in a production environment
----------

Revision history for this message
penalvch (penalvch) wrote :

StefanHuszics, 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. One may execute at a terminal:
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'.

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 Link:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette

Changed in abiword (Ubuntu):
status: New → Invalid
Revision history for this message
StefanHuszics (stefan-huszics) wrote :

Thanks for the detailed help but I have already fixed the problem on my end by

sudo add-apt-repository ppa:mrpouit/ppa

which gets me the STABLE 2.8.6 version of abiword on my Ubuntu 12.04 PRODUCTION SYSTEM. Not a single crash or weird behaviours since then.

Meanwhile, crash reports with 2.9.2 have already been sent in by the semiautomatic crashreport service in Ubuntu 12.04.

Also, I've read on another bugreport about abiword 2.9.2 that a lot of fixes have already been implemented in 2.9.3, among others crasher bugs. So both your and my time are probably best spent by concentrating on ASAP replacing 2.9.2 with either STABLE 2.8.6 or at the very least the much improved UNSTABLE 2.9.3

Revision history for this message
StefanHuszics (stefan-huszics) wrote :

Sorry, I mean the improved QQ 2.9.2 version, when I wrote 2.9.3

http://ubuntuforums.org/showpost.php?p=12209958&postcount=18

Revision history for this message
StefanHuszics (stefan-huszics) wrote :

Given that my previous link clearly show A LOT of crasher bugfixes have gone into the QQ version I feel that marking this report invalid is very inapropriate. Thus I'm instead making this a duplicate of Bug #1019621
"Precise abiword version needs to be reverted to stable release prior to 12.04.1"

In short PP 2.9.2 version is a PROVEN broken piece of dodo and it NEEDS to be adressed, not just swept under the carpet.

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.