Bug 142919 - Can't open Google Drive documents from nautilus on with Flatpak LibreOffice on Linux
Summary: Can't open Google Drive documents from nautilus on with Flatpak LibreOffice o...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-17 14:47 UTC by Finley Turner-Hall
Modified: 2023-03-22 03:24 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Finley Turner-Hall 2021-06-17 14:47:43 UTC
Description:
I'm using the Flatpak version of LibreOffice 7.1.4.2. With Google Drive added in Nautilus file manager on GNOME, you can't open or save any documents to Google Drive. It gives the error "basic input/output error". This feature works as expected in the non-flatpak version (7.1.4.2), so I guess that LibreOffice doesn't have permission to access Google Drive.

Steps to Reproduce:
1.File --> Save (NOT save-remote).
2.In the Nautilus file manager that pops up, select any location in the google drive section.
3.Press save.
4.The error message appears.

Actual Results:
The document doesn't save or open, and you get the error "basic input/output error".

Expected Results:
The File saves/opens as normal


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 7.1.4.2 / LibreOffice Community
Build ID: a529a4fab45b75fefc5b6226684193eb000654f6
CPU threads: 6; OS: Linux 5.12; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Flatpak
Calc: threaded
Comment 1 Roman Kuznetsov 2021-07-28 19:41:32 UTC
Please wait while 7.2.0.2 will be released and will try retest your problem in it. There were some patches around G-drive problem, possibly its can fix your problem too
Comment 2 Finley Turner-Hall 2021-08-21 16:22:23 UTC
(In reply to Roman Kuznetsov from comment #1)

Unfortunately the problem still persists in 7.2.0.4. It is reproducible using the same steps and gives the same error as it did in the original bug report.
Comment 3 QA Administrators 2021-08-22 03:47:49 UTC Comment hidden (obsolete)
Comment 4 Dieter 2022-08-22 06:31:48 UTC
Hello Finley, a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 QA Administrators 2023-02-19 03:20:11 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-03-22 03:24:10 UTC
Dear Finley Turner-Hall,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp