Description: A cell holds a formula adding up cells in externally linked documents. This cell is protected and the sheet is protecting it. When I double click the cell to view the formula (which is too long to view any other way because it includes the addresses for each linked cell), a warning window pops up telling me I cannot edit a protected cell on a protected sheet. When I click "OK," Calc crashes. It does this consistently. Steps to Reproduce: 1.Enter a formula into any cell (e g. "=A2+A3") 2. Protect Cell 3. Protect Sheet 4. Double click on cell to edit 5. Calc crashes shortly after. Actual Results: Calc Crashes Expected Results: Calc should not crash. It should show the contents of the cell without allowing changes or it should bring up a dialogue window saying it cannot be edited. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
http://crashreport.libreoffice.org/stats/crash_details/adc9b4d0-8b25-43b4-96a2-61c5c5b204a9
crashreport.libreoffice.org/stats/crash_details/f88f23e1-dfae-48fc-bde9-466a776c11a4
Could you give a try with LO 5.4.4? Indeed, it might already been fixed since crashreport shows a part impacted by the fix for https://bugs.documentfoundation.org/show_bug.cgi?id=113179
crashreport.libreoffice.org/stats/crash_details/71198b87-9875-4174-a259-36bccfa92397
http://crashreport.libreoffice.org/stats/crash_details/71198b87-9875-4174-a259-36bccfa92397 shows 5.4.3.2 (at the very beginning of the report)
(In reply to Julien Nabet from comment #3) > Could you give a try with LO 5.4.4? > Indeed, it might already been fixed since crashreport shows a part impacted > by the fix for https://bugs.documentfoundation.org/show_bug.cgi?id=113179 Thank you for your help, Julien. I wish I could test out the update, but I'm using this on a work computer as our main spreadsheet program, and I'm in the middle of all the end of year bookkeeping work, so I cannot risk upgrading to an early adopter version. If there's a more stable version I can downgrade to, I'd consider that approach. I'm primarily an administrator, not in IT, so I cannot do extensive testing or stay on top of developer's notes. Nevertheless, I wanted to make the community aware of a major issue I was running across. It's happened to me very consistently over the past few weeks. I'm not trying to waste anyone's time with bad bug reports or anything, so if there's a better way for me to address this kind of problem in the future, I'll comply with it.
It's fixed in 5.4.4.2! *** This bug has been marked as a duplicate of bug 113850 ***
(In reply to john from comment #6) > ... > I wish I could test out the update, but I'm using this on a work computer as > our main spreadsheet program, and I'm in the middle of all the end of year > bookkeeping work, so I cannot risk upgrading to an early adopter version. To avoid any risk, make a backup of your file (if it's not already done). Have in mind that since it you'd stay on the same branch if you upgrade from 5.4.3 to 5.4.4, it's quite safe since it concerns fixes. Of course, there's always a risk of regression. > > I'm not trying to waste anyone's time with bad bug reports or anything, so > if there's a better way for me to address this kind of problem in the > future, I'll comply with it. Indeed, it'd better to declare bugs with last stable LO version.