MX Linux Forum

old_guy wrote:Just tried Brasero - acted just the same. Image files and text files open - files trying to open in LibreOffice fail.

So we don't have an Xfburn problem, but a LibreOffice problem that fails on ver 5.4... it works on ver 5.0..., 5.1..., 5.3... those are all I have to test with.

Earl

That makes more sense.

Upgraded to the LibreOffice in Debian-Backport -NG -same.

The trouble says:
General Input/output error while accessing /media/...

BUT - if I copy the file from the CD to my HD, I can open the file - so it is an access problem from LO

The LO users mail list has had more than few complaints about 5.4. I have not seen any directly related to disk burning but know that 5.4 has differences from its
predecessors. I'll admit to using K3b even though it adds quite a bit of overhead, never had any problems with this KDE application and I do not have the time to
seek something better.

Thanks to all for your comments.

I can confirm that my problem does now seem to me more likely with LO 5.4, not Xfburn.
My other test with LO 5.2 and Brasero had no similar problems with LO files.
With LO 5.4 it seems _only_ my LO files have a problem with Xfburn; html, jpeg, txt not having a problem with Xfburn.

Similar LO i/o problems seen by Ubuntu with LO 4.2. One OP cured his complaint by re-installing LO.
See for example: https://askubuntu.com/questions/491292 ... h-libreoff

@old_guy from a likley_much_older_guy.

Thanks for helping me with a problem I'd luckily not seen before.
I've been using LO since it was a pup; since it was StarOffice sometime
in the distant past, before it forked from OpenOffice.
In Googling 'LibreOffice general input/output effor on reading saved file'
I find this problem has plagued, and continues to plague, LO folks throughout its
history.

Your solution for copying the file somewhere and opening it from there
works for me when nothing else has. I tried re-installing LO-calc and LO-write,
and diddling with the contents of ~/.config/libreoffice to no avail.
Simply copying whatever file wont work from the DVD it was saved to somewhere
writeable makes it readable, and potentially usable from there.

How this manages to get around the confused permissions situation, I have
no comprehension, but it works. I don't trust my hard drive, so I just used /tmp.
Many thanks for this magical work-around.

TJH

TJ Hoye
Thanks for the post. I just recently started playing around with MX. I have played around with linux for a few years just to be able to keep my mind working. I'm 71 and its been an interesting journey, with just the internet and not even knowing the right questions to ask, but when I come across a problem like this , I have a hard time letting go of it until there is some sort of resolution.
Earl

Glad to have met you, Earl.

I have a lot of time invested in two LO Spreadsheet programs that I've
developed over the years, one for taxes and one for finances. When I discovered
my backups weren't readable I was really anxious to get that squared away.

I'm a bit new to MX myself, but I really like it a lot. I'm particularly fond
of the elegance of its LiveUSB persistence & remastering infrastructure which
it shares with AntiX.

Hope to see you around.