| Summary: | Spreadsheet crashes Calc when changing sheets or try to enable sheet protection under Linux, works fine under Windows 10 | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | bjoern.alhaeuser |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bjoern.alhaeuser, serval2412, sokol |
| Priority: | medium | ||
| Version: | 7.2.4.1 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | The spreadsheet that keeps crashing | ||
|
Description
bjoern.alhaeuser
2022-01-07 10:48:31 UTC
Created attachment 177370 [details]
The spreadsheet that keeps crashing
Repro. Version: 7.2.2.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.2.2~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded On pc Debian x86-64 with master sources updated today + gtk3 rendering I don't reproduce this. But I could reproduce this with LO Debian package 7.2.4.1 I don't know if it could be already ok on prerelease 7.3.0 Julien, I don't know why you didn't close. Bjoern, please test with LO master from https://dev-builds.libreoffice.org/daily/master/current.html. Those who could reproduce, write if it was with macros disabled or enabled. Comment 2: reproduced when macros are enabled and when macros are disabled. LO 7.3.0.1 crashes with macros enabled and disabled. Will try with LO Master later... (In reply to Timur from comment #4) > Julien, I don't know why you didn't close. > Bjoern, please test with LO master from > https://dev-builds.libreoffice.org/daily/master/current.html. > Those who could reproduce, write if it was with macros disabled or enabled. I didn't the rules in this case (bug in 7.2.4, OK in master but no info in 7.3) and I must admit I didn't search about it. Spreadsheet works fine with LO 7.3.0.3. I changed status ti "resolved". Let's put this one to WFM since there's no specific patch to fix this. |