Hello,
I am running on linux (debian). I encounter a recent issue which is the following (libreoffice 7.6.3.2), running on flatpak. If the file is in a folder with path containing , libreoffice will indicate “The operation on … was started with an invalid parameter)”. It worked up to now and for years with my usual settings (even if french i use english interface). Thanks for your help
libreoffice7.6 /tmp/tester\'s\ directory/test.ods works for me.
I don’t use containers:
Version: 7.6.3.2 (X86_64) / LibreOffice Community
Build ID: 29d686fea9f6705b262d369fede658f824154cc0
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: x11
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded
? Your path has an accent ’ (as your questions title reads) or a comma , ?
I just tested installing the .deb from LibreOffice website. Same version.
It works. It is the flatpak version which fails. Not strictly related to LibreOffice then.
I go on testing to see if i find something on flatpak settings.
Cannot reproduce the issue neither with one of
"´`'„“”«»"
in path or filename!
with me:
debian bookworm
Version: 7.6.3.2 (AARCH64) / LibreOffice Community
Build ID: 29d686fea9f6705b262d369fede658f824154cc0
CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: en-US
Flatpak
Calc: threaded
Yes. it has been working for me, on flatpak for months. There is something now which is broken. I need to find out what to tune in flapak to recover it i think.
Version: 7.6.3.2 (X86_64) / LibreOffice Community
Build ID: 29d686fea9f6705b262d369fede658f824154cc0
CPU threads: 20; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: en-GB (fr_FR.UTF-8); UI: en-US
Flatpak
Calc: threaded
my issue is coming with folder name like /home/…/Téléchargements/.
So it was about accented letters.
indeed. accented letters.
seems to have been related to a bug, happening i don’t know when, since reinstalling it solves the issue simply.
I simply desinstall libreoffice (flapak) and re install it. Solved the issue.
just to mention i got the same issue on a second computer. Same conditions, same solution.