This bug was filed from the crash reporting server and is br-a81d1a07-8842-48f0-aa7f-ca0014de389b. ========================================= This has happened about 20 times over the period that I've had this release of LO. This is the first time that I've added a bug for it. I have no idea how to reproduce the error, it just 'happens' sometimes. But along with the other bugs, I'm not surprised. There's one bug that I submitted (105191) about LO leaving 'garbage' on the screen which consistes of a lot of pixels. I have to right click on the desktop and select refresh to rid myself of them. Maybe that's how I lose a pixel which causes this bug.
Could you give a try to 5.3.2?
*** This bug has been marked as a duplicate of bug 108299 ***
Reproduction in LO 5.3.6.1: 1) Open a table (doesn't matter whether it's saved as XLS or ODS) In my case, it's a game design doc listing all previous updates with all items that were added; not quite 5000 lines 2) Open Chrome, 62.0.3202.94 (Official Build) (64-bit), create a new Google Sheets table (the testcase I'm supposed to be working on) 3) Highlight a line in the table by clicking the line number 4) Press Ctrl and C 5) Switch to browser 6) in the Google Docs table, press Ctrl-V Result: Open Office crashes (estimated 80% reproduction rate)
(In reply to d.skreiner from comment #3) > Reproduction in LO 5.3.6.1: > > 1) Open a table (doesn't matter whether it's saved as XLS or ODS) > In my case, it's a game design doc listing all previous updates with all > items that were added; not quite 5000 lines > > 2) Open Chrome, 62.0.3202.94 (Official Build) (64-bit), create a new Google > Sheets table (the testcase I'm supposed to be working on) > > 3) Highlight a line in the table by clicking the line number > > 4) Press Ctrl and C > > 5) Switch to browser > > 6) in the Google Docs table, press Ctrl-V > > Result: Open Office crashes (estimated 80% reproduction rate) Does it happen with any line? I've just tried in LibreOffice 5.4.3.2. and I can't reproduce it. Could you please share the document?
OTOH, I think it would be better to create a new report in https://bugs.documentfoundation.org/enter_bug.cgi