Samba problem with AVM 'Fritz!' Box OS ver 7.20 up | was: Calc: fail 'text import' on load of file, no meaningful data ... possibly TDF1.3 format failing

[newbie-02]

hi @all,

[edit] IMHO solved, see below, changed subject to point to source of problem,
this is a LO problem only in sight of special settings needed for access, and broken files [/edit]

sorry, i’m not familiar with the new forum, couldn’t find meaningful ‘category’ and ‘item’ … any mod may move and retag this post,

my actual problem: a file which worked for some time became somehow corrupted and now shows ‘text import’ when i try to open it. see:

the file on disk (network, samba share) is about 1,5 times bigger than before and opens with no program and no setting i tried so far.

as i worked somehow chaotic with that file, accessing by different Calc versions from different devices, even with gnumeric, i can’t say for sure when it happened.

but my ‘feeling’ is that it started when i switched the file save format to tdf1.3(extended?) in LO Calc dev. 7.3.0.0, and i remember a similar fail some time ago which as well could be related to using that version and format.

i have a working backup and the file is not mission critical, but if there is an issue with that version or format or storing on samba shares - which i hope to learn from comments or other posts - i’d like to warn other users and file it as a bug …

reg. b.

[erAck]

Fwiw, the file format is ODF, not TDF, OpenDocument Format.

[erAck]

I doubt that’s related to ODF 1.3 in any way, about everyone using newer LibreOffice versions stores in ODF 1.3 extended if not explicitly changed. Also whether to store in ODF 1.2 or 1.3 (extended or not) is only about which features are stored to the XML streams in the package, not about the container format (which is zip in all cases) that seems to be broken in your case.

More likely your Samba share acted weird at some point in time, or if you had the file open in different clients at the same time they may have written to it concurrently and destroyed it.

As ODF document package files are zip files you might try to use a zip file repair tool.

[newbie-02]

:-), nice to hear from you, and you are rigth,
i meant ‘ODF’ not TDF, sorry,
the broken files are not accessible with archive manager or zippers (as other *.ods are),
but
i didn’t have concurrent access, no complaints about ‘locked by another person’, and i have clear savings from ctrl-S, from that i see a little risk that it’s ODF 1.3 or LibO 7.3 when using that format,
will do some targetted experimenting once i find time … and in general i propose better to have two independent backups than one …
reg. b.

[newbie-02]

have a clearer view why i suspect it’s LO related … something more or less meaningful is! written to the file, see screenshot, thus Calc had access to it … or is ‘mimetypeapplication/vnd.oasis.opendocume’ from another program?

[erAck]

The first file in an ODF zip container is called mimetype and its content is not compressed and designates the, well, mimetype of the file, so for example for Calc .ods it’s application/vnd.oasis.opendocument.spreadsheet which already appears to be garbled in your file.

[newbie-02]

An absolutely huge ball of unpleasant stuff which no one likes on their plate for dinner!!!
solved:

1. AVM updates the OS of its Fritz!boxes (standard DSL etc. routers widespread in Germany) regularly and without being asked, (my Samba share is on a FB 7490).
2. in ver. 7.21 (and possibly already 7.20) the support for Samba is changed, and that was placed on my box in mid-July.
3. changes: Samba 1.0 would have to be enabled specifically - I didn’t find a button for it on mine,
   3a. It is no longer Samba but ‘YNQ’ or something similar,
   3b. under Windows it still runs halfway, I mean I didn’t change anything in the protocol,
   3c. on Linux it worked only after I changed the mount command from vers=1.0 to vers=2.0, pure trial and error, I didn’t know that the box was changed,
   3d. under Linux some programs can access, so save and read again,
   3e. but gnumeric e.g. cannot update the file date,
   3f. and LibreOffice stores a long string ‘NULL’ characters at the beginning of each file, and can’t load it again afterwards,
4. solution with good analysis from @wbauer and workaround with ‘cache=none’ and !!! Tip for saving messed up files from @Linuximatrix at
   [Fritzbox 6490 update auf 7.20 danach NAS Problem](Linux Mint Site / forum )
   4a. to delete the unwanted characters i used ‘midnight commander’ - F4,
5. there are also tipps to change special expert configurations in LO, not yet tested,
6. ufffffff,
7. if someone has a guided missile, a bitter mail, or anything in between to spare … please send it to the AVM headquarter in Berlin with the comment ‘cheekiness’.