Abiword Dumps with Gdk Error

[Elvis]

I am running kubuntu 14.04 lts

Linux 3.13.0-49-generic #81-Ubuntu SMP Tue Mar 24 19:29:48 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

With the following installed:

wayno@bart:~$ dpkg -l | grep abiword
ii abiword 3.0.0-4ubuntu1.1 amd64 efficient, featureful word processor with collaboration
ii abiword-common 3.0.0-4ubuntu1.1 all efficient, featureful word processor with collaboration -- common files
ii abiword-plugin-grammar 3.0.0-4ubuntu1.1 amd64 grammar checking plugin for AbiWord
ii abiword-plugin-mathview 3.0.0-4ubuntu1.1 amd64 equation editor plugin for AbiWord
ii libabiword-3.0:amd64 3.0.0-4ubuntu1.1 amd64 efficient, featureful word processor with collaboration -- shared library

When I run it, it produces this output:

(abiword:19559): Gdk-ERROR **: The program 'abiword' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 149 error_code 1 request_code 155 (GLX) minor_code 19)
  (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)

Problem is reproducible. All other programmes work perfectly.

Wayno

[penalvch (penalvch)]

Elvis, thank you for reporting this and helping make Ubuntu better. However, your crash report is 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 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 feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs