By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2257

Summary:	KWord/KSpread can't open valid .odt/.ods files
Product:	TDE	Reporter:	Kristopher <gamrat.kristopher>
Component:	non-core programs	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, gamrat.kristopher, michele.calgaro, slavek.banko
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:	2562
Bug Blocks:	1185, 2540

Description Kristopher 2014-12-13 09:30:33 CST

I cannot open any .odt file in KWord. This includes .odt files from LibreOffice and .odt files created in KWord itself. When I try to open a .odt file, I get the following error message:

================================
Error - KWord
================================
Could not open <file>

Reason: Not a valid KOffice
file: <file>
================================

LibreOffice opens all .odt files I give it without complaint, regardless of whether they were created in KOffice, LibreOffice, Openop

This may be related to bug 846 , however that report has been marked as RESOLVED FIXED for over a year and pertains to one specific file, while this issue applies to every .odt file I've tried it with.

Despite this issue, KWord seems fully capable of properly saving .odt files as every document I've saved in KWord has opened and displayed correctly in LibreOffice.

Comment 1 Kristopher 2014-12-13 09:53:18 CST

I get the same error message for every KWord Template except for "Blank", "Memorandum", and "Two Columns".

Comment 2 Kristopher 2015-01-05 11:13:40 CST

This bug can be extended to KSpread as it cannot open valid OpenDocument Spreadsheet documents created in LibreOffice.

KPresenter does *not* seem to have any issues as far as I can tell.

Comment 3 Slávek Banko 2015-12-21 11:11:23 CST

Please can you test whether with the R14.0.3~preliminary is this problem also solved?

Comment 4 Kristopher 2015-12-22 19:30:03 CST

(In reply to Slávek Banko from comment #3)
> Please can you test whether with the R14.0.3~preliminary is this problem
> also solved?

Only if there are packages available for Debian Jessie.

Comment 5 Slávek Banko 2015-12-22 19:33:16 CST

(In reply to Kristopher from comment #4)
> (In reply to Slávek Banko from comment #3)
> > Please can you test whether with the R14.0.3~preliminary is this problem
> > also solved?
> 
> Only if there are packages available for Debian Jessie.

Debian Jessie as well as many others are available.
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds

Comment 6 Kristopher 2015-12-22 20:44:30 CST

(In reply to Slávek Banko from comment #5)
> (In reply to Kristopher from comment #4)
> > (In reply to Slávek Banko from comment #3)
> > > Please can you test whether with the R14.0.3~preliminary is this problem
> > > also solved?
> > 
> > Only if there are packages available for Debian Jessie.
> 
> Debian Jessie as well as many others are available.
> https://wiki.trinitydesktop.org/Preliminary_Stable_Builds

This seems fixed under R14.0.3-pre2.

Comment 7 Slávek Banko 2015-12-22 23:22:14 CST

(In reply to Kristopher from comment #6)
> (In reply to Slávek Banko from comment #5)
> > (In reply to Kristopher from comment #4)
> > > (In reply to Slávek Banko from comment #3)
> > > > Please can you test whether with the R14.0.3~preliminary is this problem
> > > > also solved?
> > > 
> > > Only if there are packages available for Debian Jessie.
> > 
> > Debian Jessie as well as many others are available.
> > https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
> 
> This seems fixed under R14.0.3-pre2.

Thank you for testing and confirmation.