Created attachment 178595 [details] report breaks When opening the “content type” as “SQL order” we enter the SQL and exit and return to the report to edit it, the program breaks.
Created attachment 178596 [details] base de datos
Have tested this: Opened the report "R2xPersonal" for editing. View → Report Navigator In the main part of the report go to properties → data and have a look. It is already set as Content type → SQL Command. So nothing to do. Opened the query GUI to see the command, closed the GUI. Executed the report. Could detect no problem here with LO 7.3.1.2 on OpenSUSE 15.3 64bit rpm Linux. Special Windows bug?
Buenos días En primer lugar gracias por su interés Si usted entre en el informe y seguidamente pasa al sql y se mete en la consulta del sql, luego va ha mover los campos del informe para editarlos y el programa se rompe Un saludo --------------------------------------------------------------------- Good Morning First of all thank you for your interest If you enter the report and then go to sql and enter the sql query, then you will move the report fields to edit them and the program breaks ---------------------------------------------------------------------
(In reply to jorojmaqui from comment #3) > > If you enter the report and then go to sql and enter the sql query, then > you will move the report fields to edit them and the program breaks > > --------------------------------------------------------------------- Couldn't reproduce a break here. Could be it is a special bug of Windows version of LO.
Windows 10 home (64 bits) and Ubuntu Libreoffice 7313 (64 bits)version spain
When I click on the Data tab of the Properties sidebar, I get an instant hang on macOS with Arm build 7312 and the provided ODB file. Backtrace seems to indicate some kind of mutex problem linked to Java threading. Unfortunately, I don't know whether this is just an Arm build problem specific to macOS, or whether it corresponds to OP's report.
Can reproduce the hang requiring force kill when I click on the Data tab also with Version: 7.2.6.2 / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded 1) Load the ODB file provided by the OP into LibreOffice. 2) Click on the Reports icon. 3) Select the first report in the list, right-mouse button click and choose Edit 4) Open the Form Navigator 5) Right-mouse button click on "Informe", then choose Properties from the context menu. 6) In the Properties sidebar, click on "Data" >>> hang requiring forced kill. Enclosing backtrace.
Created attachment 179157 [details] Apple provided backtrace on hang and forced kill via Finder
Created attachment 179184 [details] LLdb bactrace on crash This is the bt when attempting to open the report on a daily master dev build from 29/03/2022. Seems that there is quite a lot wrong with the XML.
(In reply to Alex Thurgood from comment #7) > Can reproduce the hang requiring force kill when I click on the Data tab > also with > > Version: 7.2.6.2 / LibreOffice Community > Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 > CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR > Calc: threaded > > > 1) Load the ODB file provided by the OP into LibreOffice. > 2) Click on the Reports icon. > 3) Select the first report in the list, right-mouse button click and choose > Edit > 4) Open the Form Navigator This would be View - Report Navigator > 5) Right-mouse button click on "Informe", then choose Properties from the > context menu. > 6) In the Properties sidebar, click on "Data" >>> hang requiring forced kill. > > Enclosing backtrace. I don't reproduce this on Linux or Windows. Also tried to go by what jorojmaqui described. jorojmaqui, Alex: do you still reproduce this? If yes, a bibisect would be nice to have. I'm not seeing a mention of how this worked in an older version. Alex added the regression keyword. jorojmaqui: if you want to try bibisecting: https://wiki.documentfoundation.org/QA/Bibisect/Windows Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 229123ccc6f90ebf66b3e659bebbd53f8a9bdd3a CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0ee9501c0b7dc1a291715fff9c1934b1c08cb654 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1ee5ae0eec2d1c673af6b8f18a2c36b4d1e7fb70 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 18 April 2023
No repro any more with: Version: 7.6.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 96aad0d0497c8486f8affc8fed79e63a060c9a59 CPU threads: 8; OS: Mac OS X 13.3; UI render: Skia/Metal; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded
No repro either in Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Mac OS X 13.3; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded I would say this is RESOLVED WFM
Thanks :)
(In reply to Buovjaga from comment #13) > Thanks :) Thanks for prodding me ;-)