This bug was filed from the crash reporting server and is br-c98af06b-d81a-4a7e-a31a-8d1ab9426003. ========================================= During a Calc EDITING session on a Table, an attempt to Delete Rows (Ctrl-Minus) crashes Calc, repeatable with a single row selected, with multiple rows selected, with Autofilter On and Off, with a single cell selected, with a single row selected by clicking on the row number label. The file came originally from Excel 365, but was converted to .ods format. The Table is a new table created in that workbook. The same problem occurs when deleting rows in a Table originally created in the Excel 365 application.
Please test with a clean profile, Menu/Help/Restart in Safe Mode
I restarted LO Calc in Safe Mode and loaded the .ods workbook. After selecting rows in the Table I was successful in Deleting Rows with Ctrl-Minus. In this case, the file originated from Excel but the sheet containing the Table had its rows of data contents pasted from the Clipboard while running Calc. I restarted Calc in normal mode, opened the same file, repeated the same Ctrl-Minus delete row action, and Calc crashed as before. Apparently, something is loading in Normal mode that causes the problem. I am a noob Calc user, just beginning to migrate from years of Excel experience. If you can suggest other things I can do to research this problem please advise. Thank You, ...Patrick
You should rename profile to create a new one (unless you customized it, but then you should work step by step to discover a problem). https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile Since you already wrote that safe mode is OK, that makes it NotABug. If you reproduce with new profile, please attach ODS (you may clean personals but make sure it crashes), write exact steps (what to delete) and set Unconfirmed.
On Windows 10 I renamed %APPDATA%\Roaming\LibreOffice to another name. After restarting LO Calc and loading my test file it worked correctly. It also fixed an annoying display issue I had experienced where the selected cell rectangle overlapped the row boundary above and below whenever the row heights were non-default in size. So something in the user profile was causing several problems. Since I did almost no customizations or changes to the profile before the problem occurred this is surprising. And I disagree with your statement that this is not a bug. Whenever a program repeatedly crashes there is a bug somewhere. Perhaps the issue lies in the user profile configuration data, but the program still crashes and from a user point of view is not robust. Maybe some kind of error checking on the user profile data, or a profile cleaner, or something, is needed to prevent this kind of experience. I was almost ready to walk away from LO due to these problems I experienced, and even today I don't believe it was anything "weird" that I may have done to create the issue on my part.