This works fine on a local RH9 box with the abiword-provided packages, or over X from that selfsame box. But when I run on 9.0.93+all rawhide updates, I get this, after splash screen and partial display of the UI: [louie@localhost louie]$ AbiWord-2.0 *** attempt to put segment in horiz list twice *** attempt to put segment in horiz list twice 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 2546 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.) GDB is not showing me the love tonight, though, maybe tomorrow. Thought I'd file in the meantime and see if maybe it's not just me.
Hrmm, works fine for me here on my laptop and also works for me on my desktop at work. The X error is potentially telling -- what resolution/bit depth are you running and which X driver? Will try to poke on a fresh install, too
Works fine on a fresh install with i865 video running at 1024x768/24bpp as well. Which X server are you using?
Problem on ATI Radeon (generic) for me. Works fine on ATI Rage 128 Pro Ultra. These are two different machines, of course. Go figure...
Version should be changed to Beta 3, as that's the latest version where it still happens.
Can you get a backtrace of the segfault?
Sorry, it just says "No stack." My guess is that it is due to the nature of the error - Abiword shuts down because of the errors elsewhere. Anything else I can try?
*** Bug 109302 has been marked as a duplicate of this bug. ***
ugh, as I stated in the dup bug posted above, this problem is easily fixed by starting abiword with a geometry setting: $ abiword --geometry 800x600 Once you do that, it will be fixed.
This bug also exists in the AbiWord bugzilla database at http://bugzilla.abisource.com/show_bug.cgi?id=5623 I added tkmame's suggestion to that bug. Oh, and thanks tkmame! It worked like a charm for me!
Should be all ok in abiword now, certainly can't reproduce it with FC2/FC3.
*** This bug has been marked as a duplicate of 140321 ***