abiword crashed with SIGABRT in FV_UnixSelectionHandles::FV_UnixSelectionHandles() saving as PDF file

Bug #1262375 reported by Keith Burnett on 2013-12-18
48
This bug affects 6 people
Affects Status Importance Assigned to Milestone
AbiWord
Fix Released
Critical
abiword (Ubuntu)
Medium
Unassigned

Bug Description

1) lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

2) apt-cache policy abiword
abiword:
  Installed: 3.0.0-4
  Candidate: 3.0.0-4
  Version table:
 *** 3.0.0-4 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.

4) What happened instead is it does. For a crash report with debugging symbols installed (and amd64 retrace) please see https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262635 .

Documented fix:
http://bugzilla.abisource.com/show_bug.cgi?id=13586#c2

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
 #0 0xb7742424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 5 (LWP 6441):
 #0 0xb7742424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Keith Burnett (keith-y) wrote :
information type: Private → Public
Keith Burnett (keith-y) wrote :
Keith Burnett (keith-y) wrote :

Similar to

https://bugs.launchpad.net/abiword/+bug/1054315

but perhaps not a duplicate of that as file type and actions different.

Stacktrace:
 #0 0xb7742424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x5
StacktraceSource: #0 0xb7742424 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 5 (LWP 6441):
 #0 0xb7742424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x6

Changed in abiword (Ubuntu):
status: New → Invalid

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libibus-1.0-5: package version 1.5.3-6ubuntu2.1 dbgsym version 1.5.3-6ubuntu2
outdated debug symbol package for libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18
outdated debug symbol package for ibus-gtk3: package version 1.5.3-6ubuntu2.1 dbgsym version 1.5.3-6ubuntu2
outdated debug symbol package for libp11-kit-gnome-keyring: package version 3.8.2-0ubuntu3.1 dbgsym version 3.8.2-0ubuntu3

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace

Keith Burnett, thank you for reporting this and helping make Ubuntu better. This wouldn't be considered Invalid due to https://help.ubuntu.com/community/ApportRetracingService#outdated_debug_symbol_package . Hence, could you please attach a file that when saved in the offending format, demonstrates this problem?

description: updated
Changed in abiword (Ubuntu):
importance: Undecided → Low
status: Invalid → Incomplete
summary: - abiword crashed with SIGABRT when saving a document as a PDF file
+ abiword crashed with SIGABRT saving as PDF file

Any file created in Abiword when Save As PDF is invoked causes Abiword to crash, so I've attached the simplest one that I was using to test Abiword when the crash report attached was produced.

Keith Burnett (keith-y) wrote :

Work around: PDFs can be produced using the File | Print dialog and selecting Print to File and ensuring that the PDF option is checked.

On my system, ODT export works fine without crashing. I shall test other file formats as time allows.

description: updated
summary: - abiword crashed with SIGABRT saving as PDF file
+ abiword crashed with SIGABRT in
+ FV_UnixSelectionHandles::FV_UnixSelectionHandles() saving as PDF file
description: updated

Keith Burnett, thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one. It would be nice if somebody having it could send the bug to the developers of the software by following the instructions verbatim at http://www.abisource.com/support/bugs/ . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about the status. Thanks in advance.

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

Changed in abiword (Ubuntu):
status: Incomplete → Triaged
Keith Burnett (keith-y) wrote :

Hello Christopher and all

http://bugzilla.abisource.com/show_bug.cgi?id=13586

Abisource bugzilla bug number 13586

I'd like this bug sorted before 14.04 simply because Xubuntu is such a nice small fast OS for older laptops, given the EOL of Windows XP. Users from Windows will expect Save As PDF, and a sudden crash will damage confidence.

I know that in the grand scheme of things there is an easy workround, and perhaps this is not a show stopper.

Changed in abiword (Ubuntu):
milestone: none → ubuntu-14.04-feature-freeze
Changed in abiword:
importance: Unknown → Critical
status: Unknown → Confirmed
description: updated
Changed in abiword:
status: Confirmed → Fix Released
Changed in abiword (Ubuntu):
importance: Low → Medium
tags: added: amd64 trusty
description: updated

The attachment "r33663_fix-crash-when-saving-to-pdf.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package abiword - 3.0.0-4ubuntu1

---------------
abiword (3.0.0-4ubuntu1) trusty; urgency=medium

  * New backported patches:
     + r33663_fix-crash-when-saving-as-pdf.patch (LP: #1262375)
     + r33871_fix-redraw-region-in-custom-widget.patch (LP: #1261203)
  * New patch to fix icon path in about dialog (LP: #1299582).
 -- Thaddaeus Tintenfisch <email address hidden> Sat, 12 Apr 2014 11:49:49 +0200

Changed in abiword (Ubuntu):
status: Triaged → Fix Released
Pasi Lallinaho (knome) on 2014-04-14
Changed in abiword (Ubuntu):
assignee: nobody → Thaddäus Tintenfisch (thad-fisch)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints

Remote bug watches

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