Description: Upgrade LO yesterday. Opened Calc and worked on a large spreadsheet with substantial LO Basic code that has been running for months. Without even noticing it, at some point I realised I the title bar had changed the extension from *.ods to "sheet.csv". However behaviour before I closed it was still that of a regular workbook, ie IDE was functional & loaded, my macros could be run, spreadsheet functions were operational, etc. Truly bizarre! There was no indication of whether it was triggered by something I was doing in BASIC or if that was coincidental. Wasn't doing anything outrageous. On closing, I was left with just the first sheet in the sheet.csv file, as would be expected. The previous save was still on disc and opened without apparent issue (so far!). There was no error message or indication, no crash - this just happened without even noticing it until it was too late. I had not seen this error with previous versions of Calc using this same workbook or any other. I had been saving the file a few times every hour. The recent LO upgrade was routine, done via Nala (apt). I run system update checks a few times a week, so the previous LO version was the latest in general release. Steps to Reproduce: Not deliberately reproducible.Issue following upgrade to 24.8.2.1 suspected. Actual Results: [workbook].ods changed filename to sheet.csv in background On save, csv file containing sheet #1 on disk. Previous save of [workbook].ods also found on disk and appears to be in good shape. Expected Results: No unprompted file conversion on the fly. Reproducible: Didn't try User Profile Reset: No Additional Info: Version: 24.8.2.1 (X86_64) / LibreOffice Community Build ID: 0f794b6e29741098670a3b95d60478a65d05ef13 CPU threads: 12; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-GB Flatpak Calc: threaded OS Details: OS details: RELEASE=22 CODENAME=wilma EDITION="Cinnamon" DESCRIPTION="Linux Mint 22 Wilma" DESKTOP=Gnome TOOLKIT=GTK
Please test in safe mode, Menu/Help/Restart in Safe Mode
Without reproducible steps it is difficult to analyse this. Have you run into this again?
Dear Carl, 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 Carl, 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