From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040804 Galeon/1.3.17

Description of problem:
(This is basically bug 105624 but people claim not to be able to
reproduce it any more)

A user who had migrated from abiword on FC1 was unable to start
abiword under FC3. Closer inspection revealed some kerazee geometry
settings in  ~/.AbiSuite/AbiWord.Profile

Version-Release number of selected component (if applicable):
abiword-2.0.12-4.fc3

How reproducible:
Always

Steps to Reproduce:
1. Copy duff AbiWord.Profile to ~/.AbiSuite/AbiWord.Profile .
2. Start abiword.

Actual Results:
abiword quits immediately. If launched from a terminal the following
is printed:
he 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 2514 error_code 11 request_code 53 minor_code 0)
  (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 --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.)

User feels inadequate and blames themselves even though it wasn't
their fault.

Expected Results:
Abiword to work around/detect silly settings and select a sensible
window size and start.

User to moderately happy as everything works as normal. No blame
assignment is done by anyone.

Additional info:

The attached AbiWord.Profile is the smallest version I could make
which still reproduced the error. Deleting the errant lines or moving
the file resolved the problem and allowed abiword to start.

This is probably still bug 105624 /
http://bugzilla.abisource.com/show_bug.cgi?id=5623