When deleting a row in a spreadsheet, this error occurs and once closed, the whole spreadsheet application closes. Error Text: multi_type_vector::position#1321: block position not found! (logical pos=18446744073709551557, block size=30, logical size=1048576)
Hey. Thanks for the report. That said we need to be able to reproduce it before someone attempts to fix it. I can say that on my 64-bit Ubuntu Xenial with Libreoffice 5.1.4.2 or 5.2.0.4 when I open a new spreadsheet and delete any row (tried first and 5th) everything works as expected. What is special about your case so it doesn't?
Is this related? https://bugs.documentfoundation.org/show_bug.cgi?id=43535
nao715: on which env are you? on which version are you? If not last stable one (5.1.5), please give it a try. Indeed, a similar bug has been fixed in 5.1.5
I just updated last night to the newest version of xubuntu (10.4 i think, sorry just a plain user) and this spreadsheet file was the last thing I was working on yesterday before the upgrade. All seemed normal so far, except this fatal error when deleting rows within the table I was working on yesterday. But when I tried to delete rows outside of the table I was working on, it was fine. You think there may have been something wrong when the file was converted from the old version to the new version? Thanks!
Upon boot up... xubuntu 4.4.0-31-generic This is what it says at About LibreOffice: Version: 5.1.4.2 Build ID: 1:5.1.4-0ubuntu1 CPU Threads: 2; OS Version: Linux 4.4; UI Render: default; Locale: en-PH (en_PH.UTF-8) hope it helps.
(In reply to nao715 from comment #5) > Upon boot up... xubuntu 4.4.0-31-generic > > This is what it says at About LibreOffice: > > Version: 5.1.4.2 > Build ID: 1:5.1.4-0ubuntu1 > CPU Threads: 2; OS Version: Linux 4.4; UI Render: default; > Locale: en-PH (en_PH.UTF-8) > > hope it helps. You should wait for 5.1.5 (perhaps soon on LO ppa) or test 5.2.0 (present on LO ppa). I put in cc tdf#100764
This looks much like bug 100764 that was fixed, please check the upcoming 5.1.5 *** This bug has been marked as a duplicate of bug 100764 ***