Bug 124887 - Libreoffice cannot open files from Google Drive file shared with Linux due to lockfiles
Summary: Libreoffice cannot open files from Google Drive file shared with Linux due to...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: Other other
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: File-Lock
  Show dependency treegraph
 
Reported: 2019-04-22 16:53 UTC by tywin77
Modified: 2021-09-09 03:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Latest error (31.43 KB, image/png)
2020-02-17 12:20 UTC, tywin77
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tywin77 2019-04-22 16:53:51 UTC
Description:
Chrome OS have a feature to share Google Drive files to the Linux sub system. However, when I tried opening an xlsx file, I get a general input/output error

Steps to Reproduce:
1. Open libreoffice and browse to the required folder on Google drive
2. Click open

Actual Results:
The software displays a general input/output error

Expected Results:
Software opens the required file


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 tywin77 2019-04-22 16:56:06 UTC
Bug on Chromium bug reporter: https://bugs.chromium.org/p/chromium/issues/detail?id=954980
Comment 2 tywin77 2019-04-23 14:30:12 UTC
File open also doesn't work when opening from the download folder. Only works on files in the Linux folder.
Comment 3 Xisco Faulí 2019-05-16 09:41:09 UTC
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone
else confirms it.
Comment 4 gary_liberson 2019-08-03 13:50:00 UTC
Getting same error on Chrome OS latest V75, shared linux folder, Linux install Libre Office.   Error General input/output error while accessing linux shared folder.   Regular opening of same file from copied folder (Chrome OS linux folder) works fine.   This may not be a Libre Office problem, cannot track down as of yet.

Very Respectfully,
Gary
Comment 5 tywin77 2019-08-03 13:52:53 UTC
There are a couple of technical discussions at https://bugs.chromium.org/p/chromium/issues/detail?id=922862
Comment 6 Xisco Faulí 2020-02-17 11:58:27 UTC
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 7 tywin77 2020-02-17 12:20:31 UTC
Created attachment 157941 [details]
Latest error
Comment 8 tywin77 2020-02-17 12:23:27 UTC
Libreoffice version Version: 6.4.0.3
Chrome: Google_Nami.10775.102.0
Comment 9 Xisco Faulí 2021-02-09 15:16:08 UTC
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 10 QA Administrators 2021-08-09 03:41:54 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2021-09-09 03:42:02 UTC
Dear tywin77,

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