Description: Selecting “Sorting and Grouping” via the context menu or View menu always causes a (recoverable) crash in editing a report. Sorting and grouping are functional when the report is created via the wizard. Steps to Reproduce: 1. Create and save report. 2. Edit report. 3. Select View > Sorting and Grouping. 4. Crash. Actual Results: Crash Expected Results: Able to edit the grouping and sorting. Reproducible: Always User Profile Reset: Yes Additional Info: Attached is a simple database the exhibits the problem. The report is based on a query that pulls data from two tables based on a junction (third) table. I am running on a 2018 Intel based MacBook Pro.
Created attachment 184423 [details] Database that exhibits the problem.
First reported at ask.libreoffice.org, https://ask.libreoffice.org/t/base-crashes-when-selecting-sorting-and-grouping/85973. LO: 7.4.3.2 OS: macOS Big Sur 11.7.1 Results of running from the terminal: $ /Applications/LibreOffice.app/Contents/MacOS/soffice Jan 01, 2023 5:33:29 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibSerializer 1.1.6.10682 started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibBase 1.1.6.10682 started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibLoader 1.1.6.10682 started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibRepository 1.1.6.10682 started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibFonts 1.1.6.10682 started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibLayout null started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibFormula 1.1.7.10682 started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: LibXML 1.1.7.10682 started. Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.PackageManager loadModule WARNING: Exception while loading module: org.pentaho.reporting.libraries.base.boot.DefaultModuleInfo={ModuleClass=org.jfree.report.modules.gui.swing.common.SwingCommonModule} : java.lang.NullPointerException Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.PackageManager loadModule WARNING: Exception while loading module: org.pentaho.reporting.libraries.base.boot.DefaultModuleInfo={ModuleClass=org.jfree.report.modules.gui.swing.html.SwingHtmlModule} : java.lang.NullPointerException Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.PackageManager loadModule WARNING: Exception while loading module: org.pentaho.reporting.libraries.base.boot.DefaultModuleInfo={ModuleClass=org.jfree.report.modules.gui.swing.pdf.SwingPdfModule} : java.lang.NullPointerException Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.PackageManager loadModule WARNING: Exception while loading module: org.pentaho.reporting.libraries.base.boot.DefaultModuleInfo={ModuleClass=org.jfree.report.modules.gui.swing.preview.SwingPreviewModule} : java.lang.NullPointerException Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.PackageManager loadModule WARNING: Exception while loading module: org.pentaho.reporting.libraries.base.boot.DefaultModuleInfo={ModuleClass=org.jfree.report.modules.gui.swing.printing.SwingPrintingModule} : java.lang.NullPointerException Jan 01, 2023 5:33:30 AM org.pentaho.reporting.libraries.base.boot.AbstractBoot start INFO: Pentaho Reporting Flow-Engine null started. $
On pc Debian x86-64 with master sources updated today, I don't reproduce this (with gtk or gen renderings), perhaps macOS only bug? Would it be possible to have crash info? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#macOS:_How_to_get_debug_information)
Opened the report for editing. Switched to View → Sorting and Grouping Couldn't reproduce a bug here. The group exists already, but no field is chosen for the group. Might be this is the result of the crash? Tested with OpenSUSE 15.3 64bit rpm Linux. Should be tested with Mac.
(In reply to Julien Nabet from comment #3) > Would it be possible to have crash info? (see > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#macOS: > _How_to_get_debug_information) LO is detecting and reporting the crash, the macOS crash window does not appear. Instead I get a "LibreOffice 7.4 Document Recover" window with "Due to an error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically." and then the open files are listed. I click [OK] and LO closes and restarts.
(In reply to Robert Großkopf from comment #4) > Opened the report for editing. > Switched to View → Sorting and Grouping > Couldn't reproduce a bug here. > The group exists already, but no field is chosen for the group. Might be > this is the result of the crash? > > Tested with OpenSUSE 15.3 64bit rpm Linux. > Should be tested with Mac. It is possible I am doing something wrong, I have not been using LO for long. My intent was to change the grouping and/or sorting within the report. Is there a specific sequence (click on a region or field within the report) before opening the Grouping and Sorting panel?
(In reply to DougL from comment #6) > > It is possible I am doing something wrong, I have not been using LO for > long. It should never been wrong to click in a menu. You get a crash with you system, while others (with Linux) won't get the crash doing the same as you are doing. Might be it is specific Mac or Java …
No crash or hang for me with Version: 7.5.0.1 (AARCH64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 8; OS: Mac OS X 13.0.1; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded or: Version: 7.6.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 17a8cb1573c5b75e5b7a6c480e09c681edcc26c0 CPU threads: 8; OS: Mac OS X 13.0.1; UI render: Skia/Metal; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded @Doug: this was probably fixed with one of the various recent VCL scheduling fixes in master branch, future 7.5 release, and which has also been backported to 7.4.4. Please try with one of these versions and report back.
@Doug: please also provide the JDK version number and source (Oracle, OpenJDK, AdoptJDK, etc). FWIW, I'm using Eclipse Adoptium 18.0.1 (Temurin 18).
Dear DougL, 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 DougL, 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