Opened 15 years ago

Closed 15 years ago

Last modified 13 years ago

#2637 closed task (wontfix)

abiword-2.6.8

Reported by: ken@… Owned by: ken@…
Priority: normal Milestone:
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

A bit more involved to build than it used to be, and split up into four parts -

depends on wv : somebody suggested it can be built without if you pass a switch to configure, but I could find no evidence to support that in recent 2.6.

build and intall abiword itself, keep the source. build and install the plugins, pointing configure to the source

 --with-abiword=../abiword-2.6.4

source can be removed build and install the extras build and install the docs

In theory, the extras are separate because they might not change. This doesn't seem to match what actually happens.

Still lagging the rest of gnome by a considerable margin (needs libgnomeprintui and thus libgnomeprint libgnomecanvas which most of gnome no longer use), and still fails to use fontconfig to find a glyph when it isn't in the chosen font. However, it's still a useable lightweight wordprocessor.

Change History (12)

comment:1 by ken@…, 15 years ago

Owner: changed from blfs-book@… to ken@…
Status: newassigned

comment:2 by ken@…, 15 years ago

Summary: abiword-2.6.4abiword-2.6.5

2.6.5 has been out since November, apparently lots of bug fixes since 2.6.4.

comment:3 by willimm, 15 years ago

Hey. I noticed an new release of Abiword, 2.6.6. It is avable here:

http://www.abisource.com/downloads/abiword/2.6.6/source/

Through the website still says 2.6.5.

comment:4 by ken@…, 15 years ago

Summary: abiword-2.6.5abiword-2.6.6

Thanks for the advice on the new version, I would have missed it.

I'm starting to have doubts on this - as with previous versions, it doesn't use fontconfig to find glyphs, so if a selected font doesn't contain the glyph you want, you're SOL (and occasionally it misrenders uncommon characters such as the hungarian o and u with double-acute accents) - as with konqueror in kde3, this can be worked around by choosing a suitable font. But I've just realised that the options in the main window are never translated, they always appear in english. At the moment, I don't know if that is a regression - google shows there was a separate locales package for 2.4.1 in at least one distro, but it probably was a one-off.

I got into that because I was looking at the additional docs package - en-US, fr-FR, pl-PL : what a mess! The english version is a slight superset of the docs in the base packages, the french and polish are translations of this. Except that the en-US link for problems points to the french page, for french the corresponding page cannot be found, and at least one other page has similar breakage. For the polish pages, text appears to be in UTF-8 (i.e. it renders), but at least one heading is in something odd, I guess iso8859-2 ('?' instead of c-acute). Will need to look more deeply before raising bug reports, then see if 2.4 still builds and is any better. More seriously, the extra docs are only in html - abiword's own 'help' doesn't find them, and yelp cannot find any office docs.

If we do go with 2.6, I'm proposing to include the plugins on the main page (they need a configured abiword source tree to be configured, and look for ../{,../,../../}abiword without specifying the version, so have to be told where to look. They allow it to read/write some other formats, including kwd and some OOo formats.

For 'extras' (more templates, pixmaps) and the docs, I'm inclined to point to the files (they don't have separate locations), with a brief note of who might want them. They're both CMMI, I'm starting to think they're unnecessary.

comment:5 by ken@…, 15 years ago

What I didn't initially spot was that the main help is mostly at abisource.com - the additional docs are sometimes slightly more detailed, but nothing significant (although, of course, they are present even without an internet connection, provided you tell your browser where to look, so they are more useful to some people).

Anyway, as far as I can see there are no regressions compared to 2.4.

For localisation, it uses $LANG - epiphany was picking up my $LC_ALL and I hadn't noticed $LANG was also set (to en_GB.UTF-8) which was why abiword gave me everything in english <sigh>.

For the help, the minor misrendering of the polish pages is common to the online and the local versions, and in any case it's also true for 2.4.

Looks good to go, when I've looked a bit deeper into the online broken links and misrendering.

comment:6 by ken@…, 15 years ago

I can fix most of the misrendering in the Polish docs, filed http://bugzilla.abisource.com/show_bug.cgi?id=11965 with an attachment, but I'm not proposing to put it in lfs-patches because I can't work out where the two remaining misrenderings are generated from (nor can I provide translations for the missing pages in French and Polish ;)

Getting a bit nearer to committing abiword itself, and the plugins.

comment:7 by ken@…, 15 years ago

I thought my problem with this was deciding how to set it out in the book, and for that I was going to just do abiword itself plus the plugins (extras are mostly unnecessary, local docs are NOT found by default ('help' opens a browser with www.abisource.com), and both of them are just CMMI unlike the plugins.

Seems I have a bigger problem - on the current (LFS-6.4) build on this machine, abiword-2.6.{5,6} crash when I try to open an existing file, or (on a new empty document) as soon as I've typed in a word (with a trailign space, presumably when the spellchecker activates). In an xterm I get this backtrace, but as far as I can see ALL the versions of every linked lib have not changed from my last build on another machine (where 2.6.5 works ok). Colour me confused.

*** glibc detected *** abiword: free(): invalid next size (fast): 0x09ea8428 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7051f1a]
/lib/libc.so.6(cfree+0x9c)[0xb705386c]
/usr/lib/libenchant.so.1[0xb730de71]
/usr/lib/libenchant.so.1(br_thread_local_store+0x48)[0xb730e278]
/usr/lib/libenchant.so.1(enchant_get_prefix_dir+0x28)[0xb730e6f8]
/usr/lib/libenchant.so.1(enchant_broker_init+0x245)[0xb73105e5]
abiword(_ZN14EnchantCheckerC1Ev+0x34)[0x846c458]
abiword(_ZN12SpellManager17requestDictionaryEPKc+0x9b)[0x84698b3]
abiword(_ZN14fl_BlockLayout16_getSpellCheckerEj+0xef)[0x834ce9d]
abiword(_ZN14fl_BlockLayout15_spellCheckWordEPKjjj+0x18)[0x834cf1a]
abiword(_ZN14fl_BlockLayout12_doCheckWordEP14fl_PartOfBlockPKjibb+0x40)[0x834cf9c]
abiword(_ZN14fl_BlockLayout15_checkMultiWordEiib+0xd6)[0x834d2e2]
abiword(_ZN14fl_BlockLayout18_recalcPendingWordEji+0x368)[0x834d86c]
abiword(_ZN12fl_Squiggles12textInsertedEii+0x1c8)[0x8373550]
abiword(_ZN14fl_BlockLayout22doclistener_insertSpanEPK20PX_ChangeRecord_Span+0x49e)[0x8347e7c]
abiword(_ZN16fl_SectionLayout25bl_doclistener_insertSpanEP18fl_ContainerLayoutPK20PX_ChangeRecord_Span+0x7c)[0x836d4d0]
abiword(_ZN14fl_DocListener6changeEPKvPK15PX_ChangeRecord+0x210)[0x835b790]
abiword(_ZNK11PD_Document15notifyListenersEPK13pf_Frag_StruxPK15PX_ChangeRecord+0x143)[0x843149b]
abiword(_ZN13pt_PieceTable15_realInsertSpanEjPKjjPPKcS4_P8fd_Fieldb+0x790)[0x845990a]
abiword(_ZN13pt_PieceTable10insertSpanEjPKjjP8fd_Fieldb+0x416)[0x8459da0]
abiword(_ZN11PD_Document10insertSpanEjPKjjP11PP_AttrProp+0x480)[0x8436360]
abiword(_ZN7FV_View11_charInsertEPKjjb+0x8da)[0x84183b0]
abiword(_ZN7FV_View13cmdCharInsertEPKjjb+0x3b3)[0x83dfe37]
abiword(_ZN14ap_EditMethods10insertDataEP7AV_ViewP21EV_EditMethodCallData+0x4d)[0x819548d]
abiword(_ZNK13EV_EditMethod2FnEP7AV_ViewP21EV_EditMethodCallData+0x25)[0x831ea21]
abiword(_ZN11EV_Keyboard20invokeKeyboardMethodEP7AV_ViewP13EV_EditMethodPKjj+0x82)[0x8320700]
abiword(_ZN15ev_UnixKeyboard13charDataEventEP7AV_ViewjPKcj+0x13a)[0x8324e62]
abiword(_ZN17XAP_UnixFrameImpl9_imCommitEP13_GtkIMContextPKc+0xc7)[0x82e2691]
abiword(_ZN17XAP_UnixFrameImpl12_imCommit_cbEP13_GtkIMContextPKcPv+0x25)[0x82e26b9]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__STRING+0x8c)[0xb778708c]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b3)[0xb777a173]
/usr/lib/libgobject-2.0.so.0[0xb778e52d]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7e4)[0xb778fa54]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_by_name+0x17d)[0xb778fd5d]
/usr/lib/libgtk-x11-2.0.so.0[0xb7ca6d5e]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__STRING+0x8c)[0xb778708c]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b3)[0xb777a173]
/usr/lib/libgobject-2.0.so.0[0xb778e52d]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7e4)[0xb778fa54]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_by_name+0x17d)[0xb778fd5d]
/usr/lib/libgtk-x11-2.0.so.0[0xb7ca44dd]
/usr/lib/libgtk-x11-2.0.so.0[0xb7ca52a7]
/usr/lib/libgtk-x11-2.0.so.0(gtk_im_context_filter_keypress+0x90)[0xb7ca3980]
/usr/lib/libgtk-x11-2.0.so.0(gtk_im_context_filter_keypress+0x90)[0xb7ca3980]
abiword(_ZN17XAP_UnixFrameImpl3_fe15key_press_eventEP10_GtkWidgetP12_GdkEventKey+0x49)[0x82e350d]
/usr/lib/libgtk-x11-2.0.so.0[0xb7cc0b26]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b3)[0xb777a173]
/usr/lib/libgobject-2.0.so.0[0xb778e52d]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x65b)[0xb778f8cb]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x26)[0xb778feb6]
/usr/lib/libgtk-x11-2.0.so.0[0xb7dd61ee]
/usr/lib/libgtk-x11-2.0.so.0(gtk_propagate_event+0x1b1)[0xb7cb96c1]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x2e7)[0xb7cba9b7]
/usr/lib/libgdk-x11-2.0.so.0[0xb7a23aca]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f1)[0xb76f1d31]
/usr/lib/libglib-2.0.so.0[0xb76f53c3]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1d2)[0xb76f58e2]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb9)[0xb7cbae99]
abiword(_ZN10AP_UnixApp4mainEPKciPS1_+0x38c)[0x8175576]
abiword(main+0x2a)[0x817187e]
/lib/libc.so.6(__libc_start_main+0xe5)[0xb6ffe5b5]
abiword[0x81717c1]
======= Memory map: ========ken@ac30 ~ $

comment:8 by ken@…, 15 years ago

Seems to be libxml2-2.7.3 that provokes this. After building 2.7.2 and then manually fixing up the symlinks for libxml2.so{,.2} it works again. Further investigation to follow.

comment:9 by ken@…, 15 years ago

Finally got to running gdb on it - the trace when it crashes on opening a file is also in libenchant. Turns out enchant-1.3.0, which I had been using, is old. Installing enchant-1.4.2 fixes the problem (the only other user was gedit - running spell check there works with 1.4.2).

I didn't have to recompile abiword and gedit to get a working system, but I suppose I need to do that now to make sure they still compile :-(

comment:10 by ken@…, 15 years ago

Summary: abiword-2.6.6abiword-2.6.8

Version increase to 2.6.8, but this ticket is blocked by the problems with printing (including save as PDF or PS) when it links to libgnome / libgnomecups : http://bugzilla.abisource.com/show_bug.cgi?id=11974 - for me this only started happening when I upgraded to libxml2-2.7.3.

comment:11 by ken@…, 15 years ago

Resolution: wontfix
Status: assignedclosed

Update on status: fedora and debian both seem to have open bugs on this. Upstream is concentrating on what will be 2.8. For the record, BOTH libxml2.so and libxml2.so.2 need to point to the 2.7.2 versions - with those symlinks it works ok.

The general assumption is that something in libgnomeprint is the cause of this.

In the absence of a "CAN'T FIX" option, closing as WONTFIX because it's hard to justify rolling back libxml2.

comment:12 by (none), 13 years ago

Milestone: 6.4

Milestone 6.4 deleted

Note: See TracTickets for help on using tickets.