Download it now!
Bug 105879 - Cutting text (Ctrl+X) lag 4-6 seconds ewery time
Summary: Cutting text (Ctrl+X) lag 4-6 seconds ewery time
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.3.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Cut-Copy
  Show dependency treegraph
 
Reported: 2017-02-09 12:54 UTC by nekonekolol111
Modified: 2018-07-03 14:20 UTC (History)
3 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 nekonekolol111 2017-02-09 12:54:10 UTC
Description:
Cutting text (Ctrl+X) makes lag 4-6 seconds ewery time in Calc app, in Writer app all looks fine. My last version is "LibreOffice_5.3.0_Win_x64.msi", first time I instilled file "LibreOffice_5.2.4_Win_x86.msi", there was lag also too.

Steps to Reproduce:
1.Write text in Calc app
2.Highlight text
3.Ctrl+X

Actual Results:  
Text don't want cut untill 4-6 seconds pass, all app don't respond

Expected Results:
Whant cutting text become without any lags, do it same speed like text pasting (Ctrl+V) in same app, or have same speed of instant cuting like in Writer app


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Comment 1 Xisco Faulí 2017-02-09 12:57:49 UTC Comment hidden (obsolete)
Comment 2 nekonekolol111 2017-02-09 13:10:24 UTC Comment hidden (obsolete)
Comment 3 Xisco Faulí 2017-02-09 13:12:14 UTC
the issue is still happening if you disable OpenGL?
Comment 4 nekonekolol111 2017-02-09 13:16:33 UTC
(In reply to Xisco Faulí from comment #3)
> the issue is still happening if you disable OpenGL?

Tools -> Options -> LibreOffice -> View

"Use OpenGL for all rendering" - I turn off/on, nothing changed.
Comment 5 Buovjaga 2017-02-12 15:30:39 UTC
What if you do: Help - Restart in safe mode and then Continue in safe mode without doing anything else?
Comment 6 nekonekolol111 2017-02-12 16:08:43 UTC
(In reply to Buovjaga from comment #5)
> What if you do: Help - Restart in safe mode and then Continue in safe mode
> without doing anything else?

Opened in safe mode, no difference at all :(
Comment 7 nekonekolol111 2017-03-02 11:40:38 UTC
Hello again! I accidentally find something strange. Уesterday calc program freezed, its didn't respond, but in Task Manager it looked fine. So I tired of waiting and stop tree of task of calc program. So I opened document again, restored it and magic happend-no lag when Ctr-X. So I opened/close files and there was no lag. When I rebooted, lag come back again, so I again stop tree of calc program, restore document, and all other files do Ctrl-X without lag. But I don't want every time close this program after reboot, maybe there is more an adequate solution of this problem?
Comment 8 Aron Budea 2017-03-05 04:46:37 UTC
I wonder if this is part of the big clipboard-conundrum like bug 62196.
Comment 9 Xisco Faulí 2017-11-15 10:00:03 UTC
Dear reporter,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Comment 10 QA Administrators 2018-05-30 16:40:15 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2018-07-03 14:20:05 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-20180703