Bug 109288 - ReportBuilder - seems identical to 107215
Summary: ReportBuilder - seems identical to 107215
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.2.3.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-23 15:12 UTC by idem
Modified: 2018-04-04 13:26 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description idem 2017-07-23 15:12:56 UTC
REPORTBUILDER

After upgrade to LibreOffice 5.2.3.3 can I not more print old Report (from LibO 3.x) : LibO print the reports without Reportheader and without Groupheader: only the data are (correctly) printed. Trying new report to build with new Builder: only the data are printed.
Fedora25
Postgres 9.5.7
Database driver JDBC
LibreOffice 5.2.3.3
Comment 1 Julien Nabet 2017-07-23 15:32:38 UTC
5.2 branch is EOL.
Could you give a try to last stable LO version 5.3.4?
Comment 2 Alex Thurgood 2017-07-24 08:16:29 UTC
@Idem : please provide a sample report that is no longer working with which we can test against current release builds.

Also please test with a recent release build and report back here as suggested by Julien.

Setting to NEEDINFO pending requested information.
Comment 3 idem 2017-08-06 16:13:59 UTC
With LibreOffice 5.1.6.2.8 on Fedora 24 
can I reports print from datas (Postgresql 9.5.7 - through JDBC); 
datas, Reportheader & -footer, Pageheader & -footer are correct.

Bug: data OK - report- & pageheader are not more printed (screen & paper).

LibreOffice 5.2.7.2.6 on Fedora 25 is bugged.
LibreOffice 5.3.4.2.6 on Fedora 26 is bugged.

I cannot attach a report (prod data).
Comment 4 Xisco Faulí 2017-08-06 22:01:52 UTC
Please attach a sanitize document as explain here: See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Comment 5 Alex Thurgood 2017-08-07 08:15:05 UTC
(In reply to idem from comment #3)


> LibreOffice 5.2.7.2.6 on Fedora 25 is bugged.
> LibreOffice 5.3.4.2.6 on Fedora 26 is bugged.
> 
> I cannot attach a report (prod data).

Perhaps the problem is specific to Fedora if you are using Fedora-provided releases of LibreOffice ?

We need a sample ODB file containing the report definition that you built with LibO 3.x, but based on an embedded hsqldb instead of postgres/jdbc - without that, there is no way to test/confirm.
Comment 6 Alex Thurgood 2017-08-07 08:16:33 UTC
@idem : Also please check that what you describe isn't the same as bug 60953
Comment 7 Alex Thurgood 2017-08-07 08:22:52 UTC
@idem : you also don't say whether you are using just the distro-provided LO packages, or whether you have tested against the latest TDF-release of LibreOffice ?
Comment 8 QA Administrators 2018-03-02 10:01:18 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2018-04-04 13:26:42 UTC
Dear Bug Submitter,

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-20180404