abiword crashed with SIGSEGV in packspu_VBoxPackSetInjectID()

Bug #1391123 reported by David Pires on 2014-11-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
abiword (Ubuntu)

Bug Description

Peforming Xfce4 MIME Settings in Xubuntu Desktop for Vivid Daily (http://packages.qa.ubuntu.com/qatracker/milestones/327/builds/82959/testcases/1581/results) in Virtual Box 4.3.12.

When reproducing step 6, of the second section of the test (... check that application associations can be set and changed):
<dt>Double-click on any file with a .log extension</dt>
    <dd>The file opens with AbiWord</dd>

The expected outcome would be to Abiword open any log file choosen, instead it crashes.

~$ apt-cache policy abiword
  Installed: 3.0.0-5ubuntu1
  Candidate: 3.0.0-5ubuntu1
  Version table:
 *** 3.0.0-5ubuntu1 0
        500 http://pt.archive.ubuntu.com/ubuntu/ vivid/universe i386 Packages
        100 /var/lib/dpkg/status

~$ lsb_release -a && uname -r
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
Codename: vivid

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: abiword 3.0.0-5ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic i686
ApportVersion: 2.14.7-0ubuntu10
Architecture: i386
CurrentDesktop: XFCE
Date: Mon Nov 10 11:22:33 2014
InstallationDate: Installed on 2014-11-05 (4 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141104)
SourcePackage: abiword
UpgradeStatus: No upgrade log present (probably fresh install)

David Pires (slickymaster) wrote :
David Pires (slickymaster) wrote :

Uploading backtrace of the crash with the dump removed because it potentially could have sensible information.

description: updated
description: updated
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:

tags: added: package-qa-testing

David Pires, thank you for reporting this and helping make Ubuntu better. However, your crash report edited, and manually attached. 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 a window pops up asking you to report this, but then never opens a new report, you would 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:
sudo nano /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.

Please do not attach your crash report manually to this report, with or without editing it, and reopen it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:

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

David Pires, please do not mark this a bug against another package report, or vice versa.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers