Bug 116097 - [Regression] Writer fails to correctly display progress bar of saving the document
Summary: [Regression] Writer fails to correctly display progress bar of saving the doc...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-28 22:00 UTC by Zetok
Modified: 2018-10-09 11:31 UTC (History)
1 user (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 Zetok 2018-02-28 22:00:53 UTC
Description:
When saving bigger documents, with previous versions of LO (all versions(?) before 6.x), one could see working progress bar that gets displayed on the bottom of LO when document is saved.

With LibreOffice 6, progress bar is not displayed until the very end of saving document. While saving is being done, LO is frozen, and it is impossible for user to discern whether LO is actually doing something, or just froze and needs to be killed.

At the end of the saving process, when progress bar finally is displayed, contrary to user expectation it is not fully filled, but remains empty. This does not fill the user with confidence that the document has been successfully saved.

Steps to Reproduce:
1. Open some large document in Writer (a few thousand pages should suffice)
2. Make some changes
3. Save the document

Actual Results:  
LibreOffice freezes, without indication of any progress with save operation.

Expected Results:
LibreOffice should display progress bar for saving operation, and the progress bar should be fully filled at the end of the save operation.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.0.1.1
Build ID: Gentoo official package
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); Calc: group


---

BTW, regarding UX – it's really nicer to have a working progress bar that shows that LO is doing its job, rather than just sitting without it and wondering for 15-20s whether it's still working, or if I need to kill the process and redo the changes. And yes, it does that that long to save some documents.


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 Xisco Faulí 2018-03-01 11:22:49 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 2 QA Administrators 2018-09-03 14:49:55 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2018-10-09 11:31:10 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

MassPing-NeedInfo-20181009