[Libreoffice-bugs] [Bug 154280] Inserted png images do not print color
https://bugs.documentfoundation.org/show_bug.cgi?id=154280 --- Comment #2 from Robert Großkopf --- Is this a special effect of png images? What happens with colored characters? So might be printer is set to "grayscale" → 'on'. Please show all properties and all options of the printer dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91289] Base Report Chart does not show the X-Axis Value on Output generation, if X-Axis is formatted as Date
https://bugs.documentfoundation.org/show_bug.cgi?id=91289 --- Comment #10 from Robert Großkopf --- Bug still exist in LO 7.5.1.2 under OpenSUSE 15.3 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95405] Sidebar deck for find/search and replace
https://bugs.documentfoundation.org/show_bug.cgi?id=95405 Buovjaga changed: What|Removed |Added CC||moazalaa4...@gmail.com --- Comment #31 from Buovjaga --- (In reply to MoazAlaa from comment #30) > Hi, I want to work on this bug as my GSoC project but i'm lacking some > knowledge about how to implement the idea like how to make a dialog into a > sidebar deck/panel. could you please provide some guidance ? > thanks. Please contact the mentors listed on the ideas page. Before you contact them, however, do your research and in your email explain what you have learned and where you are stuck. Your current question is not in good style. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152260] Template Name Has Dark Text on Dark
https://bugs.documentfoundation.org/show_bug.cgi?id=152260 --- Comment #4 from Rizal Muttaqin --- (In reply to Buovjaga from comment #3) > I know were testing on Linux instead of macOS, but Rizal: do you still see > this? The mac machine is not mine, I can not test without asking again. @Roman, may be you can test in your mac. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64679] [META] Printer settings related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=64679 --- Comment #38 from devops --- https://devopsacademy.co/ https://devopsacademy.co/devops-training/ https://devopsacademy.co/terraform-training-in-bangalore/ https://devopsacademy.co/aws-training-in-bangalore/ https://devopsacademy.co/top-5-devops-tools-in-2021/ https://devopsacademy.co/welcome-to-uni-education/ https://devopsacademy.co/about-us/ https://devopsacademy.co/blog/ https://devopsacademy.co/contact-us/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149097] [DOCX] Importing Word file with rotated equations cause them to be misplaced in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=149097 Aron Budea changed: What|Removed |Added Version|6.4.0.3 release |Inherited From OOo Keywords|bibisectRequest, regression |bibisected, bisected CC||aron.bu...@gmail.com --- Comment #3 from Aron Budea --- This was never really okay, because the formula was horizontal and not rotated even when it was shown (or even worse in older versions). Nevertheless, it disappeared with the following commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=8fdbda18b593e7014e44a0fd590bbf98d83258b7 author Miklos Vajna 2019-02-15 14:06:15 +0100 committer Miklos Vajna 2019-02-15 15:05:07 +0100 sw btlr writing mode: implement DOCX filter -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153996] Protect Sheet Structure Enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=153996 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153994] Sidebar character deck/tab shows Western font with no excuse
https://bugs.documentfoundation.org/show_bug.cgi?id=153994 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153992] Sidebar character deck/tab doesn't indicate the current language/language group
https://bugs.documentfoundation.org/show_bug.cgi?id=153992 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153991] Sidebar panel character deck/tab doesn't allow switching language groups
https://bugs.documentfoundation.org/show_bug.cgi?id=153991 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153990] Can't change object direction from sidebar if not in text-editing mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153990 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153987] Can't set per-language quotation marks in Tools | AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=153987 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153988] Autocorrect dialog should offer starting-ending quote pairs more conveniently
https://bugs.documentfoundation.org/show_bug.cgi?id=153988 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153967] Writer import filter misinterprets/ignores direction of RTL lines
https://bugs.documentfoundation.org/show_bug.cgi?id=153967 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153967] Writer import filter misinterprets/ignores direction of RTL lines
https://bugs.documentfoundation.org/show_bug.cgi?id=153967 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152619] Basic, Writer: Trying to inspect a just created not yet inserted instance of textfield.DateTime in the IDE causes a crash.
https://bugs.documentfoundation.org/show_bug.cgi?id=152619 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150503] Libre Calc Paste Special
https://bugs.documentfoundation.org/show_bug.cgi?id=150503 --- Comment #3 from QA Administrators --- Dear MartinP, 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-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152619] Basic, Writer: Trying to inspect a just created not yet inserted instance of textfield.DateTime in the IDE causes a crash.
https://bugs.documentfoundation.org/show_bug.cgi?id=152619 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150503] Libre Calc Paste Special
https://bugs.documentfoundation.org/show_bug.cgi?id=150503 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151066] Reload breaks Calc save icon properly showing document changed and not saved red circle
https://bugs.documentfoundation.org/show_bug.cgi?id=151066 --- Comment #3 from QA Administrators --- Dear jebsolutions, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137040] Writing in Persian and English Simultaneously in one line make libreoffice writer too slow
https://bugs.documentfoundation.org/show_bug.cgi?id=137040 --- Comment #11 from QA Administrators --- Dear omid, 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-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133274] Signing a document with x.509 soft certificate not possible when DATEV Middleware is installed (Germany)
https://bugs.documentfoundation.org/show_bug.cgi?id=133274 --- Comment #9 from QA Administrators --- Dear Stephan, 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-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96707] EDITING: Data - Form does not respect Data - Validity
https://bugs.documentfoundation.org/show_bug.cgi?id=96707 --- Comment #8 from QA Administrators --- Dear burnuser2, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138644] large spreadsheet severe performance bug while creating pivot table - changing data field function is very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=138644 --- Comment #16 from QA Administrators --- Dear Joseph Ervin, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95847] Error with log scale starting at 0: says it "can't use a negative number"
https://bugs.documentfoundation.org/show_bug.cgi?id=95847 --- Comment #4 from QA Administrators --- Dear Carl Ponder, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94365] Charts inserted with a data table dont have white chart area fill
https://bugs.documentfoundation.org/show_bug.cgi?id=94365 --- Comment #4 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91289] Base Report Chart does not show the X-Axis Value on Output generation, if X-Axis is formatted as Date
https://bugs.documentfoundation.org/show_bug.cgi?id=91289 --- Comment #9 from QA Administrators --- 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61238] Drawing edges aliased in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=61238 --- Comment #10 from QA Administrators --- Dear Petr Mladek, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85430] FILEOPEN DOC OLE objects scaled down with messed up aspect ratio
https://bugs.documentfoundation.org/show_bug.cgi?id=85430 --- Comment #11 from QA Administrators --- Dear Buovjaga, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61720] FILEOPEN PPT Magnify animation is incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=61720 --- Comment #12 from QA Administrators --- Dear ign_christian, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60166] FILEOPEN: BOM not ignored when using text file as database
https://bugs.documentfoundation.org/show_bug.cgi?id=60166 --- Comment #24 from QA Administrators --- Dear pasqual milvaques, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59346] FILESAVE: FILEOPEN: Certain conditional formatting is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=59346 --- Comment #16 from QA Administrators --- Dear mike.hall, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58180] FILEOPEN DOC Table cell contents truncated
https://bugs.documentfoundation.org/show_bug.cgi?id=58180 --- Comment #21 from QA Administrators --- Dear Yifan Jiang, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135562] Worksheet OLE object in Writer displayed and printed off-center (top and left borders look thinner)
https://bugs.documentfoundation.org/show_bug.cgi?id=135562 --- Comment #4 from QA Administrators --- Dear zh_CN User Community Liaison, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58079] FILEOPEN: Table shrinked in Word 2003 XML document
https://bugs.documentfoundation.org/show_bug.cgi?id=58079 --- Comment #11 from QA Administrators --- Dear Rusbearing, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134305] [EDITING] Grouped image refuses Original Size command
https://bugs.documentfoundation.org/show_bug.cgi?id=134305 --- Comment #4 from QA Administrators --- Dear zzz, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127392] "Autofit text" reacts wrongly for custom shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=127392 --- Comment #8 from QA Administrators --- Dear nd101, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116454] Foreground OLE object on top of a table cannot be moved with Alt+ keyboard shortcuts after table cell has been resized with the same shortcuts
https://bugs.documentfoundation.org/show_bug.cgi?id=116454 --- Comment #9 from QA Administrators --- Dear Severo Raz, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117255] EDITING: Star Obj Descr (XML) Resize preview is sometimes inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=117255 --- Comment #7 from QA Administrators --- Dear Lorenzo Chiola, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113765] PRINT Partial objects are printed on other pages
https://bugs.documentfoundation.org/show_bug.cgi?id=113765 --- Comment #8 from QA Administrators --- Dear Ole Tange, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112649] EDITING Canceling Add rows in Chart does not cancel the action
https://bugs.documentfoundation.org/show_bug.cgi?id=112649 --- Comment #5 from QA Administrators --- Dear Emil Tanev, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114906] Import of Drawings to Writer fails- Drawings completely screwed up (ok to Calc or Impress)
https://bugs.documentfoundation.org/show_bug.cgi?id=114906 --- Comment #13 from QA Administrators --- Dear Hermann Rochholz, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112007] FILEOPEN XLSX: Lighting of deep 3D column chart is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=112007 --- Comment #6 from QA Administrators --- Dear Regina Henschel, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111825] Import from xlsx has wrong scaling of deep 3D column chart
https://bugs.documentfoundation.org/show_bug.cgi?id=111825 --- Comment #8 from QA Administrators --- Dear Regina Henschel, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111820] Axes are not rendered in 3D chart
https://bugs.documentfoundation.org/show_bug.cgi?id=111820 --- Comment #7 from QA Administrators --- Dear Regina Henschel, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104417] FILEOPEN DOCX: Writer drawing is missing blue lines (WPS) - OK if resaved in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=104417 --- Comment #6 from QA Administrators --- Dear Telesto, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100064] Cannot remove error bars along Y axis when errors are defined on a cells range
https://bugs.documentfoundation.org/show_bug.cgi?id=100064 --- Comment #5 from QA Administrators --- Dear richard_g, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152406] macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document
https://bugs.documentfoundation.org/show_bug.cgi?id=152406 --- Comment #38 from Patrick Luby --- (In reply to Patrick Luby from comment #37) > Here's a diff that you can use to reproduce the bug by spinning the scroll > wheel while pressing the Shift key. Open an empty spreadsheet, > Shift-scrollwheel 5 to 10 times, then release the Shift key and scrollwheel: One more data point: with my patch in comment #37, if I swipe horizontally I can get to the column furthest to the right and immediately vertically swipe without any problem. This makes me think that the idle timer is waiting for the maximum column number to be added to the visible columns and the idle timer is just getting overwhelmed by the number of visible columns to add. Since swiping makes significantly larger jumps than a scroll wheel triggers the bug but making the jump ridiculously high does not, I think that there is some jump range that creates significantly more new visible columns to add and so it just takes forever for the idle timer to plough through adding all those columns. Whereas when you can jump to the end of the columns with a handful of swipes, maybe the idle timer only needs to handle a few hundred visible rows in total? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152406] macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document
https://bugs.documentfoundation.org/show_bug.cgi?id=152406 --- Comment #37 from Patrick Luby --- (In reply to Patrick Luby from comment #36) > Also, if I multiple the X and Y by 10K, I > can reproduce the bug using Shift-scrollwheel instead of swiping. In other > words, it seems you have to jump way out right (maybe past 8K columns?) very > rapidly to trigger this bug. Here's a diff that you can use to reproduce the bug by spinning the scroll wheel while pressing the Shift key. Open an empty spreadsheet, Shift-scrollwheel 5 to 10 times, then release the Shift key and scrollwheel: diff --git a/vcl/osx/salframeview.mm b/vcl/osx/salframeview.mm index ae9528306cfa..c22812b6c894 100644 --- a/vcl/osx/salframeview.mm +++ b/vcl/osx/salframeview.mm @@ -1048,6 +1048,10 @@ -(void)scrollWheel: (NSEvent*)pEvent pEvent = pNextEvent; } +dX *= 10; +dY *= 10; + + NSPoint aPt = [NSEvent mouseLocation]; mpFrame->CocoaToVCL( aPt ); Note: I found two other cases where you can escape from this bug so here is the complete list: - Horizontal scrollwheel - Click anywhere in vertical scrollbar - Click in native menubar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152406] macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document
https://bugs.documentfoundation.org/show_bug.cgi?id=152406 --- Comment #36 from Patrick Luby --- (In reply to Caolán McNamara from comment #35) > For gtk back in the day I recall we struggled with "smooth scrolling" events > with https://bugzilla.redhat.com/show_bug.cgi?id=1367846#c18 and ended up > overwhelmed by scroll events. I wonder if trying the same pattern as the > gtk3 "AsyncScroll" in vcl/unx/gtk3/gtkframe.cxx would be useful. Launch an > Idle on the first scroll event, accumulate the scrolls events and merge > together and and dispatch as one scroll notification when the Idle gets > fired. Thanks for the hint! In my testing, macOS isn't getting flooded as the code in vcl/osx/salframeview.mm is pulling all the pending mouse wheel events in the native queue, coalescing them, and then dispatching the combined change. What is interesting is that the bug becomes easier to reproduce on my MacBook Pro Silicon if I ignore any mouse wheel events that have zero X and Y change (i.e. dispatch less events). But I think I am getting closer. I can now reproduce this bug if I swipe rapidly and repeatedly from right to left for at least 10 seconds. Then I swipe rapidly, the vertical scrollbar and visible rows stop changing, and the horizontal scrollbar's thumb gets shorter and shifts to the right (i.e. more visible columns are added). Also, if I multiple the X and Y by 10K, I can reproduce the bug using Shift-scrollwheel instead of swiping. In other words, it seems you have to jump way out right (maybe past 8K columns?) very rapidly to trigger this bug. Theory: Calc is repeatedly running an idle timer that expands the number of visible columns in the sheet (i.e. a horizontal scroll wheel handler). What is interesting is that after this idle timer adds all columns, all vertical scroll wheel events dispatched in vcl are ignored. Other mouse events and key events are handled normally (even dragged the scrollbar thumb) so my last theory that a long-running job was blocking the main thread was wrong. So I think Calc's idle timer that adds visible columns blocks handling of vertical scroll wheel events until an unknown condition is set. So far, another horizontal scroll wheel event is the only known case that will set this unknown condition. Even adding the maximum 16K columns does not seem to set this condition. @Telesto: thank you for the samples. One sample is repainting the scrollbar in a timer and that helped me come up with my current theory. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94731] Look of square/quadratic gradient changed
https://bugs.documentfoundation.org/show_bug.cgi?id=94731 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=98 ||595 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98595] FILEOPEN: OOXML - Rectangular fill not imported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=98595 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=94 ||731 CC||rb.hensc...@t-online.de -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72567] FILEOPEN: Impress does not import text gradient from .PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=72567 --- Comment #20 from Regina Henschel --- Gradients for characters are not implemented at all and not supported by strict ODF. So that is not a bug but would be an enhancement request. I consider it as bug, that the character color is not Yellow. Solid character color is possible and should be near to the gradient colors. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36766] [META] Impress Gradient and Transparency issues
https://bugs.documentfoundation.org/show_bug.cgi?id=36766 Regina Henschel changed: What|Removed |Added Depends on||34551 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=34551 [Bug 34551] Gradient: Option to "Rotate fill effect with shape" not available -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34551] Gradient: Option to "Rotate fill effect with shape" not available
https://bugs.documentfoundation.org/show_bug.cgi?id=34551 Regina Henschel changed: What|Removed |Added Blocks||36766 CC||rb.hensc...@t-online.de Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=36766 [Bug 36766] [META] Impress Gradient and Transparency issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154271] Ctrl End inconsistently jumps to the last half screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154271 --- Comment #2 from maison --- And if your document has columns that extend over the limit of the screen, Ctrl+End will jump in such a way that will only fill a top left *quarter* of your screen! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154280] Inserted png images do not print color
https://bugs.documentfoundation.org/show_bug.cgi?id=154280 --- Comment #1 from Dean Hunter --- Created attachment 186086 --> https://bugs.documentfoundation.org/attachment.cgi?id=186086&action=edit Screen clip of printer setup -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154280] New: Inserted png images do not print color
https://bugs.documentfoundation.org/show_bug.cgi?id=154280 Bug ID: 154280 Summary: Inserted png images do not print color Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: deanhun...@comcast.net Description: A new document with an inserted PNG image displays on the screen correctly and print preview displays the image correctly. But printing the document results in an image on the page that is gray instead of color or very pale color. Steps to Reproduce: 1. Create a new document 2. Insert a PNG image with color 3. Print the document Actual Results: The printed page shows grays or very faint color. Expected Results: The image should have printed as displayed on the screen. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.6.2 Build ID: 40(Build:2) CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded on Fedora 37 The printer setup is attached. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118017] [META] macOS Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=118017 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152220 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152220 [Bug 152220] Previously displayed Preference tab is shown in background (in macos dark mode) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152220] Previously displayed Preference tab is shown in background (in macos dark mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=152220 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Blocks||118017 Component|LibreOffice |UI --- Comment #7 from Stéphane Guillou (stragu) --- confirmed via duplicate Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=118017 [Bug 118017] [META] macOS Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95405] Sidebar deck for find/search and replace
https://bugs.documentfoundation.org/show_bug.cgi?id=95405 --- Comment #30 from MoazAlaa --- Hi, I want to work on this bug as my GSoC project but i'm lacking some knowledge about how to implement the idea like how to make a dialog into a sidebar deck/panel. could you please provide some guidance ? thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152220] Previously displayed Preference tab is shown in background (in macos dark mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=152220 Stéphane Guillou (stragu) changed: What|Removed |Added CC||usanenko_va...@ukr.net --- Comment #6 from Stéphane Guillou (stragu) --- *** Bug 153645 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153645] Graphical artifacts when editing chart
https://bugs.documentfoundation.org/show_bug.cgi?id=153645 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #8 from Stéphane Guillou (stragu) --- Sounds like the same issue as 152220, as Eisa pointed out. Which allows us to set that one to "New". Vadym, would be great if you could confirm there that it only happens in macOS dark mode (or not). Thank you both! *** This bug has been marked as a duplicate of bug 152220 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152579] Build LibreOffice for macOS on Apple Silicon with pointer authentication codes (PACs): arm64e, rather than without PAC (arm64)
https://bugs.documentfoundation.org/show_bug.cgi?id=152579 eisa01 changed: What|Removed |Added Blocks||144200 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144200 [Bug 144200] LibreOffice 7.2 for ARM on Apple Silicon claims its an iOS application -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144200] LibreOffice 7.2 for ARM on Apple Silicon claims its an iOS application
https://bugs.documentfoundation.org/show_bug.cgi?id=144200 eisa01 changed: What|Removed |Added Severity|minor |trivial Depends on||152579 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152579 [Bug 152579] Build LibreOffice for macOS on Apple Silicon with pointer authentication codes (PACs): arm64e, rather than without PAC (arm64) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115321] Vertical Japanese text lines with emphasis mark above in odt exported to PDF is shown a quarter font height lower than the normal lines, and no emphasis mark is shown
https://bugs.documentfoundation.org/show_bug.cgi?id=115321 --- Comment #10 from himajin100...@gmail.com --- Created attachment 186085 --> https://bugs.documentfoundation.org/attachment.cgi?id=186085&action=edit results in dd3c7051 Now, 1. the base text is correctly placed. 2. emphasis mark is visible. 3. the emphasis mark positions are 1-char height lower than expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154254] Adding precision is lost when calculation is done by steps
https://bugs.documentfoundation.org/show_bug.cgi?id=154254 --- Comment #3 from Mike Kaganski --- No. It would mean that a change somewhere in the chain would result in complete recalculation, including cells before the changed cell. This is not an option. If one needs increased precision, one needs to use respective formula. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153538] Writer freezes and crashes without any error message
https://bugs.documentfoundation.org/show_bug.cgi?id=153538 Julien Nabet changed: What|Removed |Added Resolution|FIXED |--- Whiteboard|target:7.6.0 target:7.5.2 | Status|RESOLVED|REOPENED Assignee|serval2...@yahoo.fr |libreoffice-b...@lists.free ||desktop.org CC|serval2...@yahoo.fr | --- Comment #18 from Julien Nabet --- Ok let’s reopen this one. However i got no idea then so uncc myself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134716] Incorrect rendering of this .svg file (accentuated characters)
https://bugs.documentfoundation.org/show_bug.cgi?id=134716 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||3888 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134716] Incorrect rendering of this .svg file (accentuated characters)
https://bugs.documentfoundation.org/show_bug.cgi?id=134716 --- Comment #13 from Aron Budea --- Created attachment 186084 --> https://bugs.documentfoundation.org/attachment.cgi?id=186084&action=edit Screenshot in LO 7.6 This is what it looks like in LO 7.6 (7a7eb4aa21ca0c83db825fe8d5a5278611b391d8) / Ubuntu, at 100% and 110% zoom. Note how now at 100% there isn't enough spacing in EXCENTRICITÉ and OBLIQUITÉ between the 'T' and 'É', while at 110% there's extra spacing (the spacing was there before the change in 7.4/7.5, too, even more of it). The change happened with the following fix to bug 103888 in 7.4/7.5, bibisected to the 7.4 backport using repo bibisect-linux-64-7.4: https://cgit.freedesktop.org/libreoffice/core/commit/?id=a42f5faac7c6d4590e632cf40e3ba9eb618e6f56 author Xisco Fauli 2022-09-21 17:25:17 +0200 committer Xisco Fauli 2022-09-21 21:04:40 +0200 tdf#103888: Do not add a gap at the end of each text portion -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134716] Incorrect rendering of this .svg file (accentuated characters)
https://bugs.documentfoundation.org/show_bug.cgi?id=134716 --- Comment #12 from Frederic Parrenin --- Actually, I can still repro in 7.4.5, but it depends on the zoom level. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152406] macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document
https://bugs.documentfoundation.org/show_bug.cgi?id=152406 --- Comment #35 from Caolán McNamara --- For gtk back in the day I recall we struggled with "smooth scrolling" events with https://bugzilla.redhat.com/show_bug.cgi?id=1367846#c18 and ended up overwhelmed by scroll events. I wonder if trying the same pattern as the gtk3 "AsyncScroll" in vcl/unx/gtk3/gtkframe.cxx would be useful. Launch an Idle on the first scroll event, accumulate the scrolls events and merge together and and dispatch as one scroll notification when the Idle gets fired. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154254] Adding precision is lost when calculation is done by steps
https://bugs.documentfoundation.org/show_bug.cgi?id=154254 --- Comment #2 from Albert Astals Cid --- I sorry but this is a somewhat weak answer. Yes, floating point arithmetic is "broken", but as you said, Libreoffice knows how to do it correctly when doing the calculation in one step, so well, do the calculation in one step ;) The intermediate results are formulas, there's nothing preventing Calc from evaluating the final formula completely instead of using the already pre-calculated intermediate results. (Speaking from the "I know nothing about this code" point of view obviously, when i say "there's nothing" i mean "in theory it should be possible", no idea how hard it'd be or not in practice) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153969] No text imported from PDF document with RTL text
https://bugs.documentfoundation.org/show_bug.cgi?id=153969 --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- No repro in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL threaded gtk only? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153969] No text imported from PDF document with RTL text
https://bugs.documentfoundation.org/show_bug.cgi?id=153969 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153967] Writer import filter misinterprets/ignores direction of RTL lines
https://bugs.documentfoundation.org/show_bug.cgi?id=153967 Eyal Rozenberg changed: What|Removed |Added Version|unspecified |7.5.0.3 release --- Comment #7 from Eyal Rozenberg --- Oh, I should mention that you need to try it in LO 7.5 or earlier, as in 7.6 this whole business is masked by the more severe bug 153969, due to which _no_ text is imported into Writer. I'm guessing that when that one is resolved, we'll see this one in 7.6 as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153967] Writer import filter misinterprets/ignores direction of RTL lines
https://bugs.documentfoundation.org/show_bug.cgi?id=153967 --- Comment #6 from Eyal Rozenberg --- Created attachment 186083 --> https://bugs.documentfoundation.org/attachment.cgi?id=186083&action=edit Screenshot of attachment 186082 in Writer and in a native viewer Screenshot of the export PDF in Writer and in a native viewer. Notes: * The wrong choice of font is an unrelated issue (bug 143095). * The second line says מילהואזרווח without a space, then a space, then underscores. This is intentional, i.e. I've concatenated a few words together since I only want one space. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152877] Dates are getting formatted as dollar amounts and can't change
https://bugs.documentfoundation.org/show_bug.cgi?id=152877 keith hayden changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152877] Dates are getting formatted as dollar amounts and can't change
https://bugs.documentfoundation.org/show_bug.cgi?id=152877 --- Comment #4 from keith hayden --- correction on previous comment where I said "Unfortunately, After I upgraded to 7.5" I meant to say "7.4.3". I have not tried any version since that. I had to stop using Calc and move to Google sheets because this bug made Calc totally unusable for what I needed it for. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153967] Writer import filter misinterprets/ignores direction of RTL lines
https://bugs.documentfoundation.org/show_bug.cgi?id=153967 --- Comment #5 from Eyal Rozenberg --- Created attachment 186082 --> https://bugs.documentfoundation.org/attachment.cgi?id=186082&action=edit Writer-exported PDF The PDF is ok - the underscores follow the text, to its left. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153967] Writer import filter misinterprets/ignores direction of RTL lines
https://bugs.documentfoundation.org/show_bug.cgi?id=153967 --- Comment #4 from Eyal Rozenberg --- (In reply to Dieter from comment #3) > So I can't see the problem here. Could you please clearify it? Perhaps you didn't specifically have the PDF open in Writer, seeing how you asked about this in bug 152679? Anyway, will soon attach the PDF and a screenshot. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152877] Dates are getting formatted as dollar amounts and can't change
https://bugs.documentfoundation.org/show_bug.cgi?id=152877 --- Comment #3 from keith hayden --- (In reply to eisa01 from comment #2) > So this would likely not be macOS specific > > It is also not a bug that spreadsheets store Dates as numbers, that's > standard behavior > > For the ods from 6.x series in 7.4.3, does that corruption still happen with > the new 7.5? > > If so, can you upload a sample document that shows fine in 6.x, but not in > 7.5? So not the document you may have saved in 7.5 I am aware and agree that storing the date as a number isn't unusual, but the displaying it as one is. Unfortunately, After I upgraded to 7.5, none of my ods files are correct, even when downgrading back to 6.x. So I no longer have a "document that shows fine in 6.x, but not in 7.5". Also, I didn't need to save the doc in 7.x for this to occur, simply had to open it in 7.x and it happened. After downgrading back to 6.x, it was happening there too. I even tried completely uninstalling and reinstalling, nothing worked anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154276] Missing Menue Entry in calc Libreoffice version 7.4.6.2
https://bugs.documentfoundation.org/show_bug.cgi?id=154276 --- Comment #2 from Dietmar Heiser --- Tried the newest 7.5. Still missing. Weired -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146163] A file created using Direct PDF export, doesn't show up in the Finder
https://bugs.documentfoundation.org/show_bug.cgi?id=146163 eisa01 changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #9 from eisa01 --- Reportedly fixed in 7.5 by comment #7 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154276] Missing Menue Entry in calc Libreoffice version 7.4.6.2
https://bugs.documentfoundation.org/show_bug.cgi?id=154276 --- Comment #1 from eisa01 --- Is is there on 7.5 for me, can you try that? Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152679] RTL text boxes misplaced when fallback font is used in importing a PDF into Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152679 --- Comment #4 from Eyal Rozenberg --- (In reply to Dieter from comment #3) > (In reply to Eyal Rozenberg from comment #2) > > No, Dieter. Use the Writer-targeting import filter. > > I don't know this filter. How can I use it? Well, if bug 141732 were solved, you would just need to open the PDF in Writer. Unfortunately, what you need to do is, in the file open dialog box, scroll down the list of file types / import filters, until you get to "Portable Document Format (Writer)"; then select the PDF and open. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154117] Line break removed when applying a hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=154117 Eyal Rozenberg changed: What|Removed |Added Version|7.6.0.0 alpha0+ Master |4.1.0.4 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136801] BASIC: CInt("+2") returns 0
https://bugs.documentfoundation.org/show_bug.cgi?id=136801 Bug 136801 depends on bug 123158, which changed state. Bug 123158 Summary: isNumeric returns false if number is passed as String https://bugs.documentfoundation.org/show_bug.cgi?id=123158 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127592] [META] LibreOffice Basic incl."Option Compatible" modules
https://bugs.documentfoundation.org/show_bug.cgi?id=127592 Bug 127592 depends on bug 123158, which changed state. Bug 123158 Summary: isNumeric returns false if number is passed as String https://bugs.documentfoundation.org/show_bug.cgi?id=123158 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123158] isNumeric returns false if number is passed as String
https://bugs.documentfoundation.org/show_bug.cgi?id=123158 eisa01 changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #15 from eisa01 --- Seems to work now? Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123158] isNumeric returns false if number is passed as String
https://bugs.documentfoundation.org/show_bug.cgi?id=123158 --- Comment #14 from eisa01 --- Created attachment 186081 --> https://bugs.documentfoundation.org/attachment.cgi?id=186081&action=edit Testcase in LO 7.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154279] New: Writer freezes on right mouse click on a highlighted word
https://bugs.documentfoundation.org/show_bug.cgi?id=154279 Bug ID: 154279 Summary: Writer freezes on right mouse click on a highlighted word Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: f.kr...@freenet.de When you quickly right-click the context menu after double-clicking a word, Writer sometimes freezes. This is especially common when performing this operation multiple times in quick repetition. Freezing can last from half a second to minutes. Sometimes so long that LibreOffice has to be canceled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147906] Use hypot function for Pythagorean addition
https://bugs.documentfoundation.org/show_bug.cgi?id=147906 --- Comment #20 from Commit Notification --- adityasingh22 committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1f22d01b7ae96a7efa91c9285f3d2f8c37f05237 tdf#147906: Use python's math.hypot() for Pythagorean addition It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151618] Colorbar gradient from an imported SVG is wrongly displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=151618 --- Comment #11 from ed...@gmx.fr --- You are right that this has nothing to do with gradients. Another figure, that should hold a rasterized image (a bitmap) inside a frame, is weirdly displayed in impress (7.4.3.2), but fine in firefox or pdf. I'm not sure I understand your questions, but yes the bitmap should be positioned relative to the frame and move/scale with it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154132] INDEX DIALOG: Add help for user-defined dialog as related topic
https://bugs.documentfoundation.org/show_bug.cgi?id=154132 Dieter changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #2 from Dieter --- VERIFIED! Seth, thank you for fixing it! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123527] Insert / special Character not correctly rebuilding font chart to match selected font and search string
https://bugs.documentfoundation.org/show_bug.cgi?id=123527 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de --- Comment #5 from Dieter --- Still present in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136230] SPECIAL CHARACTER DIALOG: Results of search field are not displayed after font changing
https://bugs.documentfoundation.org/show_bug.cgi?id=136230 Dieter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #7 from Dieter --- (In reply to Andreas Heinisch from comment #6) > Maybe someone else can confirm that the bug is gone too? Yes, I can Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109232] [META] Special character dialog and toolbar group button bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109232 Bug 109232 depends on bug 136230, which changed state. Bug 136230 Summary: SPECIAL CHARACTER DIALOG: Results of search field are not displayed after font changing https://bugs.documentfoundation.org/show_bug.cgi?id=136230 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108741] [META] Shapes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108741 Bug 108741 depends on bug 140500, which changed state. Bug 140500 Summary: TABLE: Arrow changes position in a cell across two pages https://bugs.documentfoundation.org/show_bug.cgi?id=140500 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Bug 103100 depends on bug 140500, which changed state. Bug 140500 Summary: TABLE: Arrow changes position in a cell across two pages https://bugs.documentfoundation.org/show_bug.cgi?id=140500 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
