Description: I recently got me a Microsoft Surface Pro 9 with Windows 11 Home (actually, I was not keen on Windows 11 but there was no choice). Tried today for the first time to do a bit of work with LibriOffice Calc (Version 24.2.0.3). While just entering input into a cell, Calc crashed silently. I would not complain too much about the crash. It is basically impossible to prevent it. Especially on Windows and probably evnen more likely on Windows 11. However, when I restarted Calc, it presented to me an empty sheet!!!! This is no go!!! I would not expect to have everthing back to the last character entered, ok, I can except that. However, nothing of it, is not acceptable and renders Calc basically useless!!!! Steps to Reproduce: 1. Have no idea how this could be repreduced! My main message is: DO NOT THROW AWAY USER INPUT! NEVER!!! Actual Results: Silent crash, i.e. the Calc window just closed with nothing that I could do, except watching it fail. Expected Results: I would have expected that could continue with my input. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded It is a Windows 10.0 build. Possibly you better start to test on Windows 11. I do not see that an explicit Windows 11 build would be available. I also noticed that Version 24.1 is available. I was not asked to update. If you want people to use the latest versions, make a check on updates default on start up. I did not switch something like this off. When I check on updates Calc tells me that I'm update. What is the idea about this. Are shy about new versions that you hide them from users?
If it crashes, it's expected you lose the data you were typing since there was no save. About this you can try https://wiki.documentfoundation.org/QA/FirstSteps but first are you able to reproduce at will ? About updating to 24.2.1, it seems a bug indeed. Anyway, 24.2.0.3 is first release of 24.2 branch so it could be interesting you upgrade to 24.2.1 to give a new try.
I would suggest trying with the "still" branch, LO 7.6.x ATM, instead of the "fresh" branch, LO 24.2.x ATM. Once LO 7.6 is installed instead of 24.2, I would suggest a profile reset and closing LO before starting to test. Alternatively, you could try installing a "portable" version of LO 7.6 in parallel; just beware not run more than one version simultaneously (i.e. always completely close LO before launching the other version). I would also suggest _not_ having LO automatically started with OS boot up (in the background – the optional setting is available during installation). I wonder whether the recently re-instated AutoRecovery might have something to do with the crash(es); I guess it would be one of the possible settings to put to a test too. Considering that we already have several reports about LO 24.2 crashing, I would suggest considering raising the severity/priority/importance of this and similar reports – we have several "hang" or "crash" or similar terms already with LO 24.2.
Thanks for your comments. As I already wrote, loss of user data is a no go. I felt attracted by the description of of version of 24.0.2 when I first installed it. I do consider myself as an eraly adopter. However, wasting time with data loss is nothing that I want to have. This is the first thing to take care of for a new version. Before that is safe, I would consider it beta and this should be made clear on the downlaod page. I switched back to 7.6.5. ...
I have no issues in Windows 11 (yes 11) with Version: 24.2.2.1 (X86_64) / LibreOffice Community Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded neither with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 01067e964a876e38e99a099f62fe514a211a5fca CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded About Windows version, please take a look in: https://en.wikipedia.org/wiki/Windows_11_version_history#:~:text=version%2023h2%20(2023%20update)%5Bedit%5D
There are enough "vague" reports about LO 24.2 either: * crashing or * hanging or * not responding or * with some strange behavior regarding AutoRecovery or * opening directly in Recovery mode without apparent reason. IMO, I would suggest for the QA Team to close this report as INVALID (unfortunately), not because I don't trust the reporter, but because there is no specific relevant information for anyone else to try to replicate it. Eventually, if at some point in the future there is some new concrete info to work with, the report could be reopened back.
(In reply to ady from comment #5) > ... > IMO, I would suggest for the QA Team to close this report as INVALID > (unfortunately), not because I don't trust the reporter, but because there > is no specific relevant information for anyone else to try to replicate it. > Anyway, user went back to LO 7.6.5. > Eventually, if at some point in the future there is some new concrete info > to work with, the report could be reopened back. Indeed and in this case, we need feedback following https://wiki.documentfoundation.org/QA/FirstSteps advice.