Description: Hi, I'm using LibreOffice on a Debian based 64bit Linux workstation with GNOME interface (distro called as "Pardus 21.5") When i try to save my document as docx file to local/portable drive everything works well. But when i try to save it to google drive by choosing the folder via nautilius file explorer it saves it as a compressed archive file. It's impossible to open this file except using Libreoffice. But i don't experience this fault on my Windows 11 installed workstation with the same version of LibreOffice. I appreciate your help in advance. Actual Results: When i try to save my document as docx file to local/portable drive everything works well. But when i try to save it to google drive by choosing the folder via nautilius file explorer it saves it as a compressed archive file. It's impossible to open this file except using Libreoffice. Expected Results: In the given workstation above, LibreOffice Writer module should save my document to cloud storage as docx file format without corrupting the file, so that it can be readable by other word editor/viewer programs. Reproducible: Always User Profile Reset: No Additional Info: But i don't experience this fault on my Windows 11 installed workstation with the same version of LibreOffice. I appreciate your help in advance.
A DOCX file is just a zip file. What do you mean by "it is just a compressed archive file"? What happens if you copy that file from your google drive locally? Can you upload a broken docx to this bug report?
Whatever you use to access GDrive from your OS, so that it appears in the Nautilus, that thing likely changes the extension of the saved file from DOCX to ZIP. Or - you might not use the extension at all, in which case, possibly it's detected locally using an OS MIME detection mechanism, but on Google server, the detection works differently, only finding that it's a ZIP (which is correct), but not its flavor. What is shown in LibreOffice->File->Properties->General? Specifically, what is the name (the topmost line next to the icon) and location - both verbatim, for both file saved locally, and on the GDrive? That would allow to have some initial understanding, where to search next. Do both show '.docx' file extension?
Created attachment 188008 [details] Broken docx file When i copy it back to my local/portable drive it meliorates somehow. But when i try to access the cloud copy from my mobile or other device it still seen as a compressed archive file.
(In reply to Mike Kaganski from comment #2) > Whatever you use to access GDrive from your OS, so that it appears in the > Nautilus, that thing likely changes the extension of the saved file from > DOCX to ZIP. Or - you might not use the extension at all, in which case, > possibly it's detected locally using an OS MIME detection mechanism, but on > Google server, the detection works differently, only finding that it's a ZIP > (which is correct), but not its flavor. > > What is shown in LibreOffice->File->Properties->General? Specifically, what > is the name (the topmost line next to the icon) and location - both > verbatim, for both file saved locally, and on the GDrive? That would allow > to have some initial understanding, where to search next. Do both show > '.docx' file extension? I access my GDrive by using GNOME Online accounts, so that i can see my cloud drive as a portable drive in the Nautilius file explorer. I did your instruction above and the results are below Local Copy: MS Word Document Cloud Copy: File Extra Note: When i copy the cloud clone of the file to my local/portable drive it meliorates somehow and begin to seen as MS Word Document.
Created attachment 188009 [details] Local Drive Clone of the file
(In reply to libreuserx from comment #4) > (In reply to Mike Kaganski from comment #2) > > What is shown in LibreOffice->File->Properties->General? Specifically, what > > is the name (the topmost line next to the icon) and location - both > > verbatim, for both file saved locally, and on the GDrive? That would allow > > to have some initial understanding, where to search next. Do both show > > '.docx' file extension? > > > I did your instruction above and the results are below > Local Copy: MS Word Document > Cloud Copy: File No, you did not provide what I asked for. I wrote: "what is the name (the topmost line next to the icon) and location - both verbatim, for both file saved locally, and on the GDrive?" And you provided "Type", which I never asked; but you didn't provide exact strings from name and path...
(In reply to Mike Kaganski from comment #6) > (In reply to libreuserx from comment #4) > > (In reply to Mike Kaganski from comment #2) > > > What is shown in LibreOffice->File->Properties->General? Specifically, what > > > is the name (the topmost line next to the icon) and location - both > > > verbatim, for both file saved locally, and on the GDrive? That would allow > > > to have some initial understanding, where to search next. Do both show > > > '.docx' file extension? > > > > > > I did your instruction above and the results are below > > Local Copy: MS Word Document > > Cloud Copy: File > > No, you did not provide what I asked for. I wrote: "what is the name (the > topmost line next to the icon) and location - both verbatim, for both file > saved locally, and on the GDrive?" > > And you provided "Type", which I never asked; but you didn't provide exact > strings from name and path... I wish these below helps. For Local Clone: Name: TEST.docx Location: /home/atsyrd/Masaüstü For Cloud Clone: Name: 1Qae1hc_FpYeHcfBc9CSgFsm_hL3R3Ijj Location: google-drive://"my e-mail adress" The both files are same.
It looks like a "GnomeOnlineAccounts" issue. It strips the extension (and distorts filename) when saving. The process is transparent for LibreOffice, which simply uses normal IO for writing the file. Closing this as NOTOURBUG. Please file it to the respective bug tracker ( https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues ). It is possible that they will still nail it down to some issue in LibreOffice; but then, they will have much better diagnostic, because they would be able to debug the process inside their app. Then please reopen this, adding the relevant info. By the way, in case you open the issue there, mentioning that issue here right then would be nice, to allow interested users to find the continuation of the story. Thank you!