Description: Once after we have dragged a header and pool flow chart into the libre office impress,and types a text in each coloum of the table, we r not able to get a proper alingment of text as the curser is not getting started in the same position. Steps to Reproduce: 1.Go to libre office impress and open the file 2.Select a flowchart with header and pool from gallery 3.Drag the flow chart into the libre office impress and type a text in each coloum 4.While typing the text, in each coloum the curser is starting from different position and the text alignment is not proper . Actual Results: In the first coloum of the flow chart the curser is starting from the left side corner ,whereas in the second and third coloum the curser is getting started from the centre of the coloum,hence there is no proper alignment of text. Expected Results: The curser should start at the same point in each coloum of the flow chart table and the text alignment should get proper. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.2 Calc: threaded
*** Bug 154529 has been marked as a duplicate of this bug. ***
I can reproduce this with the flow chart "swimlane-3-horizontal". Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1b463f697405e64a03378fb38a32172c4d3c25e6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Flow chart introduced in 7.0.
Andreas, I guess this is since the fixes for bug 99674. How does one amend these binary files? in /extras/source/gallery/gallery_system/ ? (SDG, SDV, THM)
Dear Anjali t a, 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