Tracker bug for ReportBuilder most annoying bugs
I have added some reports for the report-builder.
Lines aren't shown - problem for users, who switch between LO and OOo/AOO.
Some bugs of grouping reports (pagecount, no possibility to repeat the footer ...)
Have added a report, which isn't confirmed. It seems to be impossible to edit or open a report in LO 184.108.40.206 rc. LO crashes immediately.
Don't know, if this is the right place to let you know this, but there is no reaction from any other user and the version is a release-candidate → impossible to use with the Report-Builder.
Second that! Can't open any reports in 220.127.116.11.
(In reply to comment #3)
> Second that! Can't open any reports in 18.104.22.168.
This bug is fixed in 4.0.5, and not present in 4.0.3.
Adding self to CC if not already on
After creating Database and a few forms, I try to go create reports, and LibreOffice Base Crashes. Every time. Doesn't matter which selection I make, design view or wizard.
Using Windows 7 on 64 bit machine.
@Eric, please don't make spurious changes in Hardware/OS or priorities. This meta tracker is correctly prioritized. Also the "patch" keyword is not appropriate.
If you have specifics of a use case/steps to reproduce that seem germane, review the linked issues and comment there. Or, open a new issue and link to this tracker.
With LibreOffice Portable 22.214.171.124 on WindowsXP (32):
Report Builder crashes when opening existing reports.
With LibreOffice 4.2.7 on Lubuntu 14.04.2 (32)(from Ubuntu SW Center):
Report Bulder fails to open existing reports (translated: document cannot be opened), creating a new report results in no action (not even an error message).
Reports open successful with 126.96.36.199 on WindowsXP and 188.8.131.52 on Lubuntu.
(In reply to Marc Schneider from comment #8)
please don't report another bug inside this meta-bugtracker. You could see there are a lot bugs named as "most annoying bugs".
Open a new bug - or write a mail directly to me (German user). So we could see if we could solve the problem.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
- Update the version field
- Reply via email (please reply directly on the bug tracker)
- Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
(In reply to tommy27 from comment #10)
> ** Please read this message in its entirety before responding **
This automatic message doesn't make sense here. Bug is a meta-bug for Report-Builder-bugs.