Created attachment 167314 [details] screenshot of error message STR ( 0) Optionally download soon-to-be-attached embedded_fb_missing_table.odb and skip to step (8). ( 1) Create a new embedded Firebird database. ( 2) Create a table. ( 3) Create a report based on the table. ( 4) Save as embedded_fb_missing_table.odb. ( 5) Close and reopen embedded_fb_missing_table.odb. ( 6) Delete the table. ( 7) Save and close the .odb. ( 8) Open embedded_fb_missing_table.odb. ( 9) In pane Database, click <Reports>. (10) In lower pane Reports, click <Table1>. Expected : a polite error message Observed : as per attached screenshot, a dialog box with two java backtraces before the dialog runs off the bottom of my screen This observations is from a local build of commit 38b1497d (2020-11-04), built and running on debian-buster. Aside: this report arises from poking into bug 138201.
Created attachment 167315 [details] broken database
@Off-topic Expected some kind of "IDIOT" warning message based on they title. As variant to 'b0rked' :-). But they dialog info doesn't seem useful/helpful, I admit that [based on screenshot; didn't test]
Tested this one. The first paragraph of the message is the same you get in LO 7.0.3.1 - says there doesn't exist a table named "Table1". This part is also translated in the language you choose. And this is the same I get with LO 7.1.0.0Alpha1+ from 2020-11-06 and 2020-11-13 So I couldn't confirm the behavior on OpenSUSE 15.1 64bit rpm Linux
Created attachment 170663 [details] message I was able to reproduce this with libreoffice-base-7.1.0.3-3.el9.x86_64 1. Create new empty database 2. Add just 4 simple VARCHAR fields, no data 3. Save and run report wizard 4. In Report Wizzard add all fields, click Finish The similiar ugly message. The same reproducer works without errors in libreoffice-base:6.4.7.2-5
Bug still present in LO 7.4.2.3 with the "broken database.odb" reproducer. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-PT (pt_PT); UI: en-US Calc: threaded I suggest renaming this bug to: "Opening a Report referencing a deleted Table results in a verbose error message (callstack trace) that is not user-friendly".
Created attachment 183448 [details] Shows different error messages for failing report since LO 6.4.7.2 Tested with OpenSUSE 15.3. Have installed different version of LO here. Up to LO 6.4.7.2 the error-message is, as it should be. LO 7.0.0.3 give an uncomplete message, which is been shown later in LO 7.0 as it appears for many messages in databases: Something with ./home/buildslave… Since LO 7.2.0.3 there has been added all the stuff about the report builder.
Must be a regression. So I set the keyword, but I can't set the right version for this bug. Bug appears here first in LO 7.2.0.3, but is also detected by others here with earlier versions. Hope everybody did test it with LO directly from LibreOffice, not with a special build of a Linux-version.
Created attachment 183480 [details] tail of bibisect output in repo linux-64-7.2 Working on debian-buster in bibisect repository linux-64-7.2, and taking the display of java callstacks as "bad", I see state commit s-h date ----- -------- -------- ------------------- good be461b0d ff673ce8 2021-05-03 10:02:18 bad 9f0f3be6 ed33d1d4 2021-05-03 10:33:33 leading to commit ed33d1d4928dc9886eaace62d3c62ea4305efdac Author: Noel Grandin <noel.grandin@collabora.co.uk> AuthorDate: Mon May 3 09:59:08 2021 +0200 Commit: Noel Grandin <noel.grandin@collabora.co.uk> CommitDate: Mon May 3 12:33:33 2021 +0200 clean up some Java warnings Change-Id: Id54e8fd6803c3a6c0d924338d1781679ed0b1bfd Reviewed-on: https://gerrit.libreoffice.org/c/core/+/115025 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk> I am removing keyword bibisect request and adding bibisected and bisected.
(In reply to mkrajnak from comment #4) I do not see the problem in the Report Wizzard in bibisect repository linux-64-7.5 s-h cfc8a8f5.