Bug 98535 - FILESAVE DOCX not working to Google Drive
Summary: FILESAVE DOCX not working to Google Drive
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: CMIS
  Show dependency treegraph
Reported: 2016-03-09 02:15 UTC by roogeravila
Modified: 2016-11-08 12:48 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description roogeravila 2016-03-09 02:15:14 UTC
simplesmente perdi meu trabalho que pensei ter sido salvo no google drive, agora terei de refazê-lo.
Comment 1 Yousuf Philips (jay) (retired) 2016-03-09 22:54:38 UTC
Dear Roogeravilla,

I'm sorry to hear that you lost your work. Can you provide any additional information on how it happened, as i just tested it now and it worked for me.
Comment 2 Xisco Faulí 2016-10-10 11:24:19 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2016-11-08 12:48:22 UTC
Dear Bug Submitter,

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