Created attachment 82500 [details] Last file used to reproduce (several times) the described bug Problem description: When trying to edit an ods file with a few formulas and several comments, when editing the comment, the computer freezes, getting in a suspend-like state (power light on, but no video/network/keyboard/disk activity) so, power button has to be pushed to power off the computer, and then again to power it on. Steps to reproduce: 1. Open ods file with a few formulas and several comments 2. Right click on a cell with comments and choose Show comment. 3. Double click the comment. The computer freezes. In some occasions, the computer freezed with only opening the file. Current behavior: Computer freezes. Expected behavior: Software should enable editing comments. My previous version was LibreOffice 3.5.4 before restoring to factory image computer. LibreOffice is running in Spanish language, installed on Windows XP Professional SP3 (Spanish) on a Lenovo PC (With Pentium D 3.0 Ghz Processor and 3 GB RAM). Computer was recently restored. Operating System: Windows XP Version: 4.0.4.2 release
I have no issue opening the file and I don't experience any crash following your instruction. tested on Win7 64bit using LibO 4.0.4.2 try downloading the portable version of LibO from here: http://www.winpenpack.com/main/download.php?view.1354 and test your file... do you still have problems? maybe there's something wrong with your user profile
(In reply to comment #1) > I have no issue opening the file and I don't experience any crash following > your instruction. tested on Win7 64bit using LibO 4.0.4.2 > > try downloading the portable version of LibO from here: > http://www.winpenpack.com/main/download.php?view.1354 > > and test your file... do you still have problems? > maybe there's something wrong with your user profile Thank you very much for your quick reply, and sorry for the delay. I downloaded the suggested portable version, and the same error happened. I will try with a different version (previous and beta) and post results.
any news?
(In reply to comment #3) > any news? Sorry for the late reply and information update. Certainly there is a problem with my computer. We haven't determined yet what it is causing it, but it is not LO fault. In fact, it is not, currently, the only app that triggers the described behaviour. Which status should I assign to this note as it was in fact not a LB bug ?
the correct status is RESOLVED NOTOURBUG. already changed by me.