Created attachment 78367 [details] The "buggy" report When building a report under LO 4.0.2 and Report Builder, fields are wrongly fomatted. Everything works correctly as specified under 3.6.6.2. The errors involve using the wrong fonts, as well as some fields being positioned wrongly. This can be seen from the report enclosed and an addtional bug report, eeing as apparently only ONE attachment can be added. I generate these reports from a MySQL database accessed through Base. As long as this is not corrected, I cannot use 4.0. By the way, 4.0.3.RC1 shows the same buggy behaviour.
You can attach more than one document, marking this as a duplicate of other bug
*** Bug 63839 has been marked as a duplicate of this bug. ***
Changed my mind, marked the other one as a duplicate of this one, please attach a very simple test database, explain what we need to do to see the problem and I will bibisect to see where the problem began. Also, changing version to 4.0.0.3 release (oldest version that you seem to experience the problem) as you've stated you cannot upgrade to Version 4 at all due to the problem. Attach document, explain steps and then mark as UNCONFIRMED and I will investigate
Created attachment 78967 [details] repAnwesenheitFaulty.pdf Hello, Please find enclosed some material for further investigation of the above bug reported by me: - repAnwesenheitFaulty.pdf -- the report generated in LO 4.0.3 (don't worry about the "|N". It is a result of loading the testdata into the test-DB) - repAnwesenheitCorrect.pdf -- the report as produced correctly under LO 3.6.6 - testMaterial: statements used to create the test-environment - rainermusikTest.sql -- file created by mysqldump for defining/loading db, table and view - rmnativeTest.odb -- odb-file for test-database In case of problems (eg. passwords or similar!) I am of course available for a discussion (phone: +43 664 14 47 642). I hope to hear from you soon... Regards H. Stoellinger On Wed, 01 May 2013 05:57:04 +0200, <bugzilla-daemon@freedesktop.org> wrote: > https://bugs.freedesktop.org/show_bug.cgi?id=63838 > > Joel Madero <jmadero.dev@gmail.com> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDINFO > Version|4.0.2.2 release |4.0.0.3 release > Ever confirmed|0 |1 > --- Comment #3 from Joel Madero <jmadero.dev@gmail.com> --- > Changed my mind, marked the other one as a duplicate of this one, please attach > a very simple test database, explain what we need to do to see the problem and > I will bibisect to see where the problem began. > > Also, changing version to 4.0.0.3 release (oldest version that you seem to > experience the problem) as you've stated you cannot upgrade to Version 4 at all > due to the problem. > > Attach document, explain steps and then mark as UNCONFIRMED and I will > investigate >
Created attachment 78968 [details] repAnwesenheitCorrect.pdf
Created attachment 78969 [details] rainermusikTest.sql
Created attachment 78970 [details] rmnativeTest.odb
Created attachment 78971 [details] testMaterial
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO