Bug 19480 – KWord failed to open a Rich Text File (RTF) it had just written

• Product: Gentoo Linux
• Status: VERIFIED REMIND

[Description Lorenzo Bicci 2003-04-17 09:38:37 UTC]

Kword isn't able to display correctly or even open a Rich Text File it created. Sometimes 
it displays the file with some errors, sometimes it returns a format error and doesn't 
open it. Note that the same RTF file can be opened with MS Office. 

Reproducible: Always
Steps to Reproduce:
1. Open KWord from the K menu 
2. Select "Inizia con un documento vuoto" (sorry, but I use Italian version. In English it 
should be "Start with an empty document") and then click OK 
3. Write something, e.g. "ciao". 
4. Save as a Rich Text File, e.g. "ciao.rtf". 
5. Close KWord. 
6. Open the file by clicking on its icon. 
Actual Results:  
Sometimes KWord opened the file with some symbols that were not in the original, 
sometimes it says "Impossibile aprire file:/home/bicci/ciao.rtf 
Motivo: Errore di formato nel file alla riga 103, colonna 15" wich means: "It's impossible 
to open the file:/home/bicci/ciao.rtf - Reason: Format error in the file at row 103, 
column 15". The row and column values are not always the same. 
MS Office can open the same file and displays it correctly. 

Expected Results:  
KWord should open the file and display it correctly! 

KWord 1.2.1 on KDE 3.1.1a 
 
Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) 
================================================================= 
System uname: 2.4.19-gentoo-r10 i686 AMD Athlon(tm) XP 1800+ 
GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo// 
http://www.ibiblio.org/pub/Linux/distributions/gentoo" 
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config 
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config 
/usr/share/config" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
PORTDIR="/usr/portage" 
DISTDIR="/usr/portage/distfiles" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR_OVERLAY="" 
USE="x86 oss apm crypt gif gpm jpeg libg++ libwww mikmod mmx ncurses nls pdflib 
png quicktime truetype xml2 xmms xv zlib gdbm berkdb slang readline svga ggi tcltk 
guile sdl tcpd pam perl python esd imlib motif cdr X qt kde -gtk -gnome -alsa 3dnow avi 
cups arts acpi encode imap java mpeg oggvorbis opengl scanner spell ssl" 
COMPILER="gcc3" 
CHOST="i686-pc-linux-gnu" 
CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" 
CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" 
ACCEPT_KEYWORDS="x86 ~x86" 
MAKEOPTS="-j2" 
AUTOCLEAN="yes" 
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" 
FEATURES="sandbox ccache"

[Comment 1 Caleb Tennis (RETIRED) 2003-04-22 09:41:07 UTC]

I am unable to reproduce using virtually the same setup.  It works for me everytime. 
 
Perhaps the koffice people have seen this bug before?   

[Comment 2 Michele Balistreri (RETIRED) 2003-04-28 10:55:50 UTC]

i can reproduce this bug, but i can't find exactly where is the problem, with previous 
version of koffice i didn't have this issue at all... now i'll test with koffice 1.3b1 

[Comment 3 Michele Balistreri (RETIRED) 2003-05-04 05:53:32 UTC]

with koffice 1.3b1 this seem to work, the filter is completely rewritten, i'll see about a 
possible backport, koffice 1.3b1 is still to unstable to be used daily, can the user 
please test it too? 

[Comment 4 Lorenzo Bicci 2003-05-04 13:40:00 UTC]

I emerged Koffice 1.3b and now I've got KWord 1.2.90. Is it right? Anyway, it can open 
and display rtf files correctly, also the one that I created and tried to open with KWord 
1.2.1 to report the bug. 

[Comment 5 Caleb Tennis (RETIRED) 2003-05-05 09:20:18 UTC]

That's the correct version #.  KDE starts with 1.2.90 for beta versions so they can increment  
up to 1.2.99 through release candidates, then to jump to 1.3.  Sounds like this was a KDE  
bug that was fixed.  I'll set this to REMIND to note that this may or may not be backported as 
a fix to the 1.2 series. 

[Comment 6 Paul de Vrieze (RETIRED) 2003-06-28 01:36:56 UTC]

*** Bug 23622 has been marked as a duplicate of this bug. ***

[Comment 7 Carsten Lohrke (RETIRED) 2005-12-25 13:45:50 UTC]

Dead old bug left to close...