Created attachment 198362 [details] A working document that will eventually become a Policies and Procedures Manual This bug was filed from the crash reporting server and is br-b856ae74-e7e5-4e3f-8f42-c88299bd73a5. ========================================= This occurred while I had been editing a table of committees, responsibilities and roles. I had several topics out of sequence and inserted large number of new rows to accommodate copying and pasting topics from one section of the table to another. I had finished the reorganization of the table and had a number of blank rows in addition to the original entries at the end of the table. I split the table into two tables, one with all topics and the second with blank rows and the original entries that were out of sequence. I selected the second table and pressed the Delete key. LibreOffice Writer crashed, the file with one table was stored.
I opened the document file from the original crash, selected the table, repeated the split table action and saved the file with two tables. I then selected the second table, and selected the Delete key. LO Writer crashed. I opened the document file from the second crash, tried to delete the second table and LO Writer took no action. It ignored pressing the delete key.
In order to delete a table with Delete key, the table should be all selected, maybe even a line before or after. Other way, just the text inside will be selected and deleted. I could not reproduce this bug on Version: 25.2.0.1 (X86_64) / LibreOffice Community Build ID: ddb2a7ea3a8857aae619555f1a8743e430e146c9 CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
You can paste info from you LibreOffice: Help - About. Maybe is just a windows bug on a certain version.
You may also try to upgrade to 24.8.4 + try https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile
Not reproduced with attachment 198362 [details]. Do you still reproduce with 25.2.4? Version: 24.8.1.0.0+ (X86_64) / LibreOffice Community Build ID: 0b80db94d445434ab12002b9ba11c15f00accc19 CPU threads: 2; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear Dan Carr, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Dan Carr, 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-FollowUp