Bug 89728
| Summary: | AbiWord 2.2.1 under FreeBSD 4.11 is stuck in a screen redraw loop when opening RTF files | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Steven Sidman <ssidman> |
| Component: | Individual Port(s) | Assignee: | freebsd-gnome (Nobody) <gnome> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->feedback Can you retry with AbiWord 2.4 (actual version in ports) ? > > Synopsis: AbiWord 2.2.1 under FreeBSD 4.11 is stuck in a screen redraw loop when opening RTF files > > > > State-Changed-From-To: open->feedback > > State-Changed-By: pav > > State-Changed-When: Tue Nov 29 18:55:36 GMT 2005 > > State-Changed-Why: > > Can you retry with AbiWord 2.4 (actual version in ports) ? > > I first went to abisource.com and got the tarball, using gmake to try to > build it. Things went along great until some kind of fatal error having > to do with being unhappy with some kind of global instruction decoder .h > file. (tptool?) > > Went to FreeBSD, found the 2.4 ports version, updated abiword in my > /usr/ports/editors/abiword. Things were fine until install, when > everything stops due to enchant. I have enchant 1.5, but the install > program apparently never sees it. The ports tree for enchant 1.2 is > apparently marked as broken. I found the enchant home page, and managed > to build it from source ok (using gmake), except that the install in the > abiword port still fails at enchant (claims the port is marked as > broken, even though I installed enchant 1.2 separately) even after doing > rehash, make clean, etc. Please don't mix installation from ports and from tarballs if you want any support from us. enchant port is not broken in any way. Are you updating your whole ports tree? What exact message are you getting? Where do you see enchant 1.5? http://www.abisource.com/projects/enchant/ -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> Geography is only physics slowed down, with a few trees stuck on it... -- Terry Pratchett Responsible Changed From-To: freebsd-ports-bugs->gnome Over to maintainer(s). State Changed From-To: feedback->closed Sorry, we don't deal with TMDA'ers. |
AbiWord goes into a screen redraw loop when opening RTF files, including RTF files that it has just generated. RTF files generated on the FreeBSD system are opened correctly using AbiWord on a Linux Fedora Core 2 system. RTF files generated by AbiWord on the Fedora Core 2 system still cause the infinite scree redraw behavior on the FreeBSD system. The RTF files are also correctly opened on the FreeBSD system by my trial copy of TextMaker, a commercial program by Softmaker Software GmbH. Since it is still a trial copy, I cannot yet write RTF using TextMaker, but TextMaker opens RTF files ok. The AbiWord generated RTF is also correctly parsed and read by the program rtfreader. When calling AbiWord from the command line, I sometimes find the following on exit in the terminal window: > abiword heisen.txt (AbiWord-2.2:98366): libgnomevfs-CRITICAL **: file gnome-vfs-utils.c: line 749 (gnome_vfs_get_uri_from_local_path): assertion `local_full_path[0] == '/'' failed There is some evidence that very simple documents are ok. I tried adding elements to the base document (bold, centering, page number, footnote) saving and reopening each time. All was ok. Trying to import the complete RTF document, with all elements (basically, more footnotes) causes the looping on open behavior. There is also a possibility that my pure text file from which I started may not have had 100% pure text. I am checking that out now. The point is, AbiWord 2.2 on Fedora Core 2 works ok. How-To-Repeat: Create a graphics-free RTF document of five pages or so, with footnotes, save it as RTF, and then see if the looping on display refresh behavior occurs when trying to re-open the document.