Created attachment 115603 [details] bugreportbase x-axis not visable Hi my first bug report ever Version: 4.4.3.2 Build-ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16 OS Ubuntu 14.04 but im with it since OOO and now got to 14.04 ubuntu First all is good in 3.2 on ubuntu 10.04 i did the hole report new so i assume its not the old file 1 Generated a chart in a report footer with SQL command the preview showes all correct as expected 2 when hiting the output REPORT Run Button the report generates but with no X-axis value at all X axis label or tilel is well below shown so it seams to me that the X-axis field is simply not there in generation of the real report
Could not confirm the x-axis is missing. But there are many other problems with charts and date or time... See https://bugs.documentfoundation.org/show_bug.cgi?id=84882 and all the bugs at "See also".
@maxcnc: please provide a test odb file, and detailed explanation of what you are doing to reproduce the behaviour : "generated a chart in a report footer with SQL command" is not sufficient for us to be able to reproduce. Setting to NEEDINFO pending requested information. Please set back to UNCONFIRMED once you have done so.
hi first thanks to get feedback so what is going on i got a csv file from a Farmstation with the Data i import to Calc with setting dates YMD in imortfield correct so it showes localised 15.05.2015 correct as dates it also converts to whatever i want in calc Dateformates CORRECT Behavier Then mark all the data rows (200) and paste into an NEW Table in BASE with setting all the formats as needed by Declaration Correct Behave now i can work back and forth to all Forms Reports ok Fault is Report builder API maybee does not give the correct Format to the Writer output as Report is generated via Internel Reportbuilder (maybe in EN Mode throu a fail dataexport into chart implement in writer There are siimply no data exported THE Report preview of the chart shoes correct info in Preview as expected the output i will produce a test file with some data
Created attachment 115729 [details] 91289 bug atachment this is the testfile open the report in edit mode you shoudt see the correct DATE values in the charts produce the real output and you see there are gone
I could confirm the behavior for x-axis as date-formatted value. Will attach a new file. Have a look at the second report. I changed the date into char with the following query: SELECT RIGHT('0'||DAY("Datum"),2)||'.'||RIGHT('0'||MONTH("Datum"),2)||'.'||YEAR("Datum") AS "Dat", COUNT( "AUNr" ) AS "Fahrten", COUNT(DISTINCT "FeldNr" ) AS "Felder" FROM "biogas" WHERE "ID" > 4 GROUP BY "Dat" The characters were shown right in the x-axis.
Created attachment 115732 [details] x-axis formatted as text will be shown ... Have tested it with other versions. The bug doesn't appear with LO 3.6.7.2. The first versions of LO 4.0 doesn't open the report ("Failed to parse the report"). I could test this up to 4.0.3.3. Next version I have installed is LO 4.0.5.2. This version is the first here which could open the report but shows the buggy behavior. Date isn't shown in x-axis, if it is formatted as date.
** 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.1.5 or 5.2.1 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear maxcnc, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear maxcnc, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exist in LO 7.5.1.2 under OpenSUSE 15.3 64bit rpm Linux.
Same here using Version: 7.3.6.2 / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded