Directory Opus filemanager (v.12, latest as of today) with file preview panel enabled. If you clic on a LO spreadsheet file in Directory Opus the preview panel shows the preview, but the LibreOffice process stops working and crashes.
when you use windows explorer did you get the same crash?
No, preview enabled in Windows Explorer doesn't causes the problem
Mike, NOTOURBUG?
Definitely OURBUG (just needs confirming). We must not expose APIs that allow to crash us.
But the description misses everything needed for reproduction (even trying to install it doesn't hep me): 1. "v.12, latest as of today" - is it 12.21 x64? 2. The program allows to be installed in two kinds (Pro edition vs Light edition) - which one? 3. "with file preview panel enabled" - how one enables that stuff? The program is rich in settings, and I don't want to spent lots of lime trying to find something in a program I don't use and need, other than to reproduce the problem.
And which Windows is that?
OK, I try to give more details Windows is
OK, I try to give more details I'm on Windows 10 Home build 1909 (18363.1016) Directory Opus is the Pro version 12.21 x64 build 7478 22/0682020 AFAIK you can install the Pro edition in trial mode for 30 days To enable the preview mode you can use the F7 key or the toolbar: the button is normally displayed by default and it's the last one on the righ, just before the search field.
Repro with Version: 7.0.1.1 (x64) Build ID: <buildversion> CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Curiously this happens even with LibreOffice started from a parallel installation. Unfortunately, I cannot repro with master, even replacing C:\Program Files\LibreOffice with contents of my master instdir. Don't know if that's because it's fixed in master, or because it's a debug build. Setting NEW for now.
Dear cianoz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug