abiword crash on document

Bug #1402017 reported by George Shuklin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
abiword (Ubuntu)
Undecided
Unassigned

Bug Description

Attached document crash abiword.

 Gdk-ERROR **: The program 'abiword' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 182 error_code 11 request_code 149 (unknown) minor_code 2)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: abiword 3.0.0-5ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic i686
ApportVersion: 2.14.7-0ubuntu10
Architecture: i386
CurrentDesktop: XFCE
Date: Fri Dec 12 20:38:07 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-07-19 (510 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
SourcePackage: abiword
UpgradeStatus: Upgraded to vivid on 2014-09-26 (77 days ago)

Revision history for this message
George Shuklin (george-shuklin) wrote :
description: updated
Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Not reproducible in Trusty with gnome-session-fallback, or Vivid with Unity (both amd64). Probably something specific to your combination of XFCE, hardware, and i386.

Revision history for this message
Lyn Perrine (walterorlin) wrote :

Not reproducible on zesty amd64 with LXDE

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

Other bug subscribers