[Libreoffice-bugs] [Bug 156887] Exporting csv or xlsx to dbf
https://bugs.documentfoundation.org/show_bug.cgi?id=156887 --- Comment #1 from Dick Hildreth --- Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 32; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156887] Exporting csv or xlsx to dbf
https://bugs.documentfoundation.org/show_bug.cgi?id=156887 Dick Hildreth changed: What|Removed |Added Version|unspecified |7.3.7.2 release OS|All |Linux (All) Hardware|All |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156887] New: Exporting csv or xlsx to dbf
https://bugs.documentfoundation.org/show_bug.cgi?id=156887 Bug ID: 156887 Summary: Exporting csv or xlsx to dbf Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dickhildr...@gmail.com The problem occurs when an alphanumeric column contains zeroes. The problem is NOT consistent and I have been unable to identify a consistent pattern. An alphanumeric (text or '@' pattern) value containing one or more zeroes will drop one of the zeroes. If there are multiple zeroes in the value, it is neither consistently the first nor the last. In a spreadsheet containing just fewer than 54,000 rows, each containing a unique 8-character value (the value in question), there were about 170 values that were not output properly: as stated, the incorrect values were missing a zero character. There were also several (quantity undetermined) that appeared to be completely similar in format but were output properly. The data set contains PII, so sharing example data must be handled carefully and properly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137589] Repeat: Merge Cells (Shift-Ctrl-Y) doesn't do same as Merge
https://bugs.documentfoundation.org/show_bug.cgi?id=137589 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #3 from Aaron --- This bug is still present in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156671] Icon needed for "?" help button in the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=156671 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 156697] Text Box vs. Formatted Field in a DATABASE FORM layout are not consistent for their > Control Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=156697 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 156705] macOS keybindings for Home/End malfunctioning
https://bugs.documentfoundation.org/show_bug.cgi?id=156705 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 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 --- Comment #14 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156691] [FR] export to markup tables
https://bugs.documentfoundation.org/show_bug.cgi?id=156691 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 153189] Libre froze while using Find and Replace, to the point that it's only Task Manager to the rescue.
https://bugs.documentfoundation.org/show_bug.cgi?id=153189 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 152638] Rotating an image and not able to position correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=152638 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153189] Libre froze while using Find and Replace, to the point that it's only Task Manager to the rescue.
https://bugs.documentfoundation.org/show_bug.cgi?id=153189 --- Comment #4 from QA Administrators --- Dear Steve-oh, 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 152638] Rotating an image and not able to position correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=152638 --- Comment #7 from QA Administrators --- Dear Alan, 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 149730] Wrong text about "external data" when opening a label document
https://bugs.documentfoundation.org/show_bug.cgi?id=149730 --- Comment #17 from QA Administrators --- Dear makisushi622, 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 149903] LibreOffice Base crash if i open tables, forms in a design mode
https://bugs.documentfoundation.org/show_bug.cgi?id=149903 --- Comment #6 from QA Administrators --- Dear Polly_juice, 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 153448] Footer and header missing on first page
https://bugs.documentfoundation.org/show_bug.cgi?id=153448 --- Comment #2 from QA Administrators --- Dear Grobe, 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 149696] Unexpected HTTP Head request triggered by queryContent (HTTP GET requests to REST API)
https://bugs.documentfoundation.org/show_bug.cgi?id=149696 --- Comment #4 from QA Administrators --- Dear yanncailleux, 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 151533] The effect "change font size", acts as Exit fly-out left effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151533 --- Comment #3 from QA Administrators --- Dear Telesto, 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 151586] Libreoffice crash, throw 'free(): double free detected in tcache 2'
https://bugs.documentfoundation.org/show_bug.cgi?id=151586 --- Comment #3 from QA Administrators --- Dear Guanping, 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 149145] Text prediction causes cells to be non-drawn for a period of time
https://bugs.documentfoundation.org/show_bug.cgi?id=149145 --- Comment #4 from QA Administrators --- Dear studog, 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 151523] Margins shift left in Print, Preview, or Print to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151523 --- Comment #2 from QA Administrators --- Dear Mary Lee, 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 141506] EDITING: Calc crashes with Fatal Error when altering formula
https://bugs.documentfoundation.org/show_bug.cgi?id=141506 --- Comment #12 from QA Administrators --- Dear cl, 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 96635] FILEOPEN PDF: Wrong masking, box shown over triangle in arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=96635 --- Comment #15 from QA Administrators --- Dear ZioTibia81, 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 74801] TABLE: Wrong table formatting while posting an html table
https://bugs.documentfoundation.org/show_bug.cgi?id=74801 --- Comment #17 from QA Administrators --- Dear Zeki Bildirici, 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 76232] Table: Merging Two Cells Leads to an Additional Line Break
https://bugs.documentfoundation.org/show_bug.cgi?id=76232 --- Comment #9 from QA Administrators --- Dear A (Andy), 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 72032] FORMATTING: Vertically merged cells in TABLE are distorted
https://bugs.documentfoundation.org/show_bug.cgi?id=72032 --- Comment #10 from QA Administrators --- Dear Mike Kaganski, 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 69593] FILEOPEN: PPTX import with shapes causes text to disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=69593 --- Comment #25 from QA Administrators --- Dear Keith Curtis, 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 70678] Fatal error when adding a chart for cells with formulas (Summary in Comment 24)
https://bugs.documentfoundation.org/show_bug.cgi?id=70678 --- Comment #33 from QA Administrators --- Dear Дмитрий, 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 44729] PDF import from Inkscape PDF export with opacity shows black background for each opaque object
https://bugs.documentfoundation.org/show_bug.cgi?id=44729 --- Comment #20 from QA Administrators --- Dear mathog, 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 41638] FILESAVE: Black character shadows will be shown grey by MS PPT Viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=41638 --- Comment #12 from QA Administrators --- Dear Rainer Bielefeld 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 43806] Line style of imported PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=43806 --- Comment #38 from QA Administrators --- Dear mathog, 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 123210] Calc: Insert Rows Below if above hidden row should make visible/not hidden row
https://bugs.documentfoundation.org/show_bug.cgi?id=123210 --- Comment #4 from QA Administrators --- Dear Timur, 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 116654] GTK3: hourglass icon is missing in slideshow (bottom left corner)
https://bugs.documentfoundation.org/show_bug.cgi?id=116654 --- Comment #12 from QA Administrators --- Dear Xisco Faulí, 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 114914] FILEOPEN: gif image has blank background (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=114914 --- Comment #8 from QA Administrators --- Dear Xisco Faulí, 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 113936] Importing a PDF is slower compared to 5.4
https://bugs.documentfoundation.org/show_bug.cgi?id=113936 --- Comment #10 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 51510] FILESAVE: Exporting documents with embedded SVG to doc or docx converts the image to low-resolution pixel graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=51510 --- Comment #32 from Dev --- (In reply to Regina Henschel from comment #31) > For export to docx I would expect, that the SVG image is exported as SVG, > because modern MS Office are able to render SVG. Or wmf file at least? We have no idea for now how to implement it but we're willing to give it a try if anyone would like to give us some hints or advice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76134] FORMATTING: Column widths are not interpreted properly from Microsoft Word 2003 XML format
https://bugs.documentfoundation.org/show_bug.cgi?id=76134 Kohei Yoshida changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |8227| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118227] XML 2003 Excel import export filter issues
https://bugs.documentfoundation.org/show_bug.cgi?id=118227 Kohei Yoshida changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=76 | |134 | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118227] XML 2003 Excel import export filter issues
https://bugs.documentfoundation.org/show_bug.cgi?id=118227 Kohei Yoshida changed: What|Removed |Added See Also||https://gitlab.com/orcus/or ||cus/-/issues/185 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156886] Calc fails to format date as requested
https://bugs.documentfoundation.org/show_bug.cgi?id=156886 --- Comment #1 from Bogaboga Man --- Created attachment 189121 --> https://bugs.documentfoundation.org/attachment.cgi?id=189121=edit Test Spreadsheet file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156886] New: Calc fails to format date as requested
https://bugs.documentfoundation.org/show_bug.cgi?id=156886 Bug ID: 156886 Summary: Calc fails to format date as requested Product: LibreOffice Version: 7.6.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bogaboga...@gmail.com Description: Calc adding an "'" to the date on date format change, fails to format date, which when removed, formatting happens as initially expected. Steps to Reproduce: 1. Have a date in LibreOffice Calc appear as 1/3/2023. 2. Right click the cell 3. Click Format Cells 4. Choose Date and select the type of format (I chose the format D. MMM. ) 5. Click OK. Actual Results: LibreOffice Calc adds a "'" to the beginning of the date cell value (not visible at first), and does nothing requested. When this "'" is removed, date is formatted as initially expected. Expected Results: It should have changed the "1/3/2023" date format to "03 January 2023" Reproducible: Always User Profile Reset: Yes Additional Info: Same applies to multiple date selections and custom date formats -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102493] FILESAVE: save to HTML, list elements formatted incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=102493 Kira Tubo changed: What|Removed |Added CC||kira.t...@gmail.com --- Comment #9 from Kira Tubo --- Created attachment 189120 --> https://bugs.documentfoundation.org/attachment.cgi?id=189120=edit list item html format The contents of the list item are available with Writer, but the format of the is incorrect. Either the beginning or the ending of the tag is missing. Reproduction steps: 1. Download attachment 127592 [details] from the web browser 2. Open HTML download in Writer 3. Note that contents of the list is available 4. View > HTML Source 5. Observe tags Note: Viewing as HTML Source does not seem to be available in the daily build, so this was tested in the latest stable build: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 --- Comment #2 from Adrian Thewlis --- Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156868] Find function should highligh all instances of found keyword
https://bugs.documentfoundation.org/show_bug.cgi?id=156868 --- Comment #6 from Juergen --- (In reply to m.a.riosv from comment #5) > Maybe because it is a button to execute, not a choice. That is what I meant. If "Find All" is a button it should be displayed like the other to buttons. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156885] New: Metadata in Calc's comment system
https://bugs.documentfoundation.org/show_bug.cgi?id=156885 Bug ID: 156885 Summary: Metadata in Calc's comment system Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jayb...@yahoo.co.nz Add an option to show, and not show, metadata in Calc's comment system. NOTES: https://ask.libreoffice.org/t/comments-in-calc-added-dates-after-updating-from-7-5-to-7-6/94934/3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154271] Adjust view port on auto scroll to maximize the visible area
https://bugs.documentfoundation.org/show_bug.cgi?id=154271 --- Comment #7 from maison --- Any hope for a beautiful day? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156858] LibreCalc wrong subtraction of numbers 0, 0000000000001
https://bugs.documentfoundation.org/show_bug.cgi?id=156858 ASi changed: What|Removed |Added CC||a...@tlen.pl --- Comment #6 from ASi --- Created attachment 189119 --> https://bugs.documentfoundation.org/attachment.cgi?id=189119=edit Visualisation in 7.5.5.2 same in 7.5.5.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 --- Comment #17 from Julien Nabet --- (In reply to Lionel Elie Mamane from comment #16) > (In reply to Lionel Elie Mamane from comment #14) > > > So we need to "understand" whether that is really > > an integer or the integer storage for a NUMERIC or DECIMAL, but I don't > > immediately see how one determines that. > > Hmm... Try something like that: > >... Ok I'll try this (rather tomorrow since it's getting a bit late for me) > Additionally this code is fundamentally wrong, at least placed where it is. > > 200 if (str.getLength() > pVar->sqllen) > 201 str = str.copy(0, pVar->sqllen); > > It is not linked to "believing we need an integer value", it is just a > coincidence; an SQL_LONG takes four bytes AND IN THIS PARTICULAR EXAMPLE, > four CHARACTERS OF THE STRING takes the integer value plus the dot, BUT > THAT'S JUST A COINCIDENCE. This code should be only in the codepath of the > cases SQL_VARYING, SQL_TEXT, SQL_BLOB, and NOT in the cases > SQL_INT/LONG/FLOAT/etc. > ... I had noticed this too and had begun to change this. However, I had removed it in my first attempt to reduce noise. In the same way, OString str = OUStringToOString(sInput , RTL_TEXTENCODING_UTF8 ); is only useful for SQL_VARYING and SQL_TEXT parts. and finally just a nitpick, I thought about adding brackets for SQL_TEXT and SQL_BLOB (just wonder why only these don't have them). Thank you for all the feedback! :-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #1 from Regina Henschel --- I cannot reproduce the problem with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded @Adrian: Please go to Help > About, copy the version information (click on the button) and paste it here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156880] LibreOffice spellcheck/dictionary issues in 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156880 --- Comment #4 from John Schuetz --- Hi Mike, Yes, it is. It's been installed for quite some time. This was all fine in 7.5.5. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530
--- Comment #16 from Lionel Elie Mamane ---
(In reply to Lionel Elie Mamane from comment #14)
> So we need to "understand" whether that is really
> an integer or the integer storage for a NUMERIC or DECIMAL, but I don't
> immediately see how one determines that.
Hmm... Try something like that:
case SQL_LONG:
{
short sqlscale = pVar->sqlscale;
// move the decimal in the string by -sqlscale
// and AFTER THAT take the integer part of it
// e.g. if the string is "123.456789" and sqlscale is -1
// then int32Value should be "1234"
// if the string is "123.456789" and sqlscale is -2
// then int32Value should be maybe "12345"
// or maybe "12346" because we need to use rounding, not truncation?
// yes, I think do rounding, not truncation
setInt(nParameterIndex, int32Value);
break;
}
and do the same for the other cases: SQL_SHORT, SQL_INT64, etc.
Additionally this code is fundamentally wrong, at least placed where it is.
200 if (str.getLength() > pVar->sqllen)
201 str = str.copy(0, pVar->sqllen);
It is not linked to "believing we need an integer value", it is just a
coincidence; an SQL_LONG takes four bytes AND IN THIS PARTICULAR EXAMPLE, four
CHARACTERS OF THE STRING takes the integer value plus the dot, BUT THAT'S JUST
A COINCIDENCE. This code should be only in the codepath of the cases
SQL_VARYING, SQL_TEXT, SQL_BLOB, and NOT in the cases SQL_INT/LONG/FLOAT/etc.
It would be nice to have a unittest for all that. It would be pretty simple,
just have a firebird database with columns of different types (VARCHAR,
NUMERIC, DECIMAL, INTEGER, FLOAT, ...) and try to set values of these columns
by setString(), then read the value from the database and check it is the
correct one depending on the string.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 --- Comment #15 from Julien Nabet --- (In reply to Lionel Elie Mamane from comment #14) > (In reply to Lionel Elie Mamane from comment #13) > >... > Ah, but we are in the Firebird-specific code. I was responding when I saw this second message, it's indeed the pb. > > I'm biting... Reading the "InterBase 6" API GUIDE pages 91 to 93, it seems > indeed that in Firefox, in the C-level API, NUMERIC and DECIMAL give an > "sqltype" of an integer... So we need to "understand" whether that is really > an integer or the integer storage for a NUMERIC or DECIMAL, but I don't > immediately see how one determines that. In the doc page I quoted (https://firebirdsql.org/file/documentation/chunk/en/refdocs/fblangref30/fblangref30-datatypes-fixedtypes.html), take a look at: "Table 3.3.1 Method of Physical Storage for Real Numbers". It's an array so can't copy this directly in the bugtracker without losing the whole formatting. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 --- Comment #14 from Lionel Elie Mamane --- (In reply to Lionel Elie Mamane from comment #13) > Well, OK, but that is an internal Firebird implementation decision and > detail. No code outside of connectivity/source/drivers/firebird should need > to know that or be aware of that. Ah, but we are in the Firebird-specific code. I'm biting... Reading the "InterBase 6" API GUIDE pages 91 to 93, it seems indeed that in Firefox, in the C-level API, NUMERIC and DECIMAL give an "sqltype" of an integer... So we need to "understand" whether that is really an integer or the integer storage for a NUMERIC or DECIMAL, but I don't immediately see how one determines that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530
--- Comment #13 from Lionel Elie Mamane ---
(In reply to Julien Nabet from comment #11)
> "sInput" is "123.45"
> "str" is well converted to "123.45"
> "dtype" is SQL_LONG (it'll be important next)
Well, the code seems to (mistakenly?) believe the value should be set into a
(long) integer field.
> str.getLength() is equal to 6 => OK
> but
> pVar->sqllen = 4 so the str is truncated to "123."
Well, it smells like this comes from the (wrong?) value of dtype.
> not right but whatever, since "dtype" is SQL_LONG, we go there:
> 242 case SQL_LONG:
> 243 {
> 244 sal_Int32 int32Value = sInput.toInt32();
> 245 setInt(nParameterIndex, int32Value);
> 246 break;
> so we don't use str but "sInput", sInput which contains "123.45" is
> converted to Int32 so 123.
Well, yes, since according to dtype, we need an integer, so we get an integer
out of the data.
> In //, I read some info about DECIMAL and NUMERIC here:
> https://firebirdsql.org/file/documentation/chunk/en/refdocs/fblangref30/
> fblangref30-datatypes-fixedtypes.html
>
> a lot of info here but the point to have in mind is this one:
> "The form of declaration for fixed-point data, for instance, NUMERIC(p, s),
> is common to both types. It is important to realise that the s argument in
> this template is scale, rather than "a count of digits after the decimal
> point". Understanding the mechanism for storing and retrieving fixed-point
> data should help to visualise why: for storage, the number is multiplied by
> 10s (10 to the power of s), converting it to an integer; when read, the
> integer is converted back."
> If I don't misunderstand, it means that in Firebird a DECIMAL or NUMERIC
> with display value "123.45" stores physically "12345" plus some info to
> indicate it must be divided by 100.
Well, OK, but that is an internal Firebird implementation decision and detail.
No code outside of connectivity/source/drivers/firebird should need to know
that or be aware of that.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99609] Expert Configuration dialog does not correctly expose column names or row attributes (Windows, NVDA)
https://bugs.documentfoundation.org/show_bug.cgi?id=99609 --- Comment #18 from Commit Notification --- Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/bf15445b7102a4e2bea2f96891093bc4bf07c4c6 tdf#99609 tdf#156473 a11y: Check whether row header exists It will be available in 24.2.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 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530
--- Comment #12 from Julien Nabet ---
I gave a try with this patch:
diff --git a/connectivity/source/drivers/firebird/PreparedStatement.cxx
b/connectivity/source/drivers/firebird/PreparedStatement.cxx
index 35847d021ea0..529ab8a39cde 100644
--- a/connectivity/source/drivers/firebird/PreparedStatement.cxx
+++ b/connectivity/source/drivers/firebird/PreparedStatement.cxx
@@ -227,7 +227,7 @@ void SAL_CALL OPreparedStatement::setString(sal_Int32
nParameterIndex,
break;
case SQL_SHORT:
{
-sal_Int32 int32Value = sInput.toInt32();
+sal_Int32 int32Value = sInput.replaceAll(".", "").toInt32();
if ( (int32Value < std::numeric_limits::min()) ||
(int32Value > std::numeric_limits::max()) )
{
@@ -241,13 +241,13 @@ void SAL_CALL OPreparedStatement::setString(sal_Int32
nParameterIndex,
}
case SQL_LONG:
{
-sal_Int32 int32Value = sInput.toInt32();
+sal_Int32 int32Value = sInput.replaceAll(".", "").toInt32();
setInt(nParameterIndex, int32Value);
break;
}
case SQL_INT64:
{
-sal_Int64 int64Value = sInput.toInt64();
+sal_Int64 int64Value = sInput.replaceAll(".", "").toInt64();
setLong(nParameterIndex, int64Value);
break;
}
Remarks:
1)
the "replaceAll" is required for both SQL_LONG and SQL_INT64, so concerning
SQL_SHORT it was more to be the same way
2)
It was OK with French UI so I supposed it's not useful to test if decimal
separator was ".", "," or whatever. Indeed it seemed to me only the internal
representation of the value (which I expect always use ".") must be used.
Result:
non decimal part is ok but not the decimal part, we lose some precision
Conclusion:
not the right thing to do :-(
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156714] .uno:IndexMarktoIndex does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=156714
sdc.bla...@youmail.dk changed:
What|Removed |Added
Summary|.uno:IndexMarktoIndex does |.uno:IndexMarktoIndex does
|not work (and is|not work
|functionally unclear) |
--- Comment #7 from sdc.bla...@youmail.dk ---
The functionality of this .uno seems clear enough. As the name indicates (and
the comments in the source code underpin), the cursor should be moved from the
index mark to its index.
https://opengrok.libreoffice.org/xref/core/sw/source/uibase/shells/textidx.cxx?r=0908c7c1#168
case FN_IDX_MARK_TO_IDX: /* from the index mark to the index */
{
GetShell().GotoTOXMarkBase();
break;
}
https://opengrok.libreoffice.org/xref/core/sw/source/core/crsr/crstrvl.cxx?r=d86a6d2b=GotoTOXMarkBase#360
void SwCursorShell::GotoTOXMarkBase() /// jump to index of TOXMark
The GotoTOXMarkBase function was present in the initial check-in from 2000,
with a use case to provide an easy way to navigate from index entries to its
index (without having to use Navigator).
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156864] Active tab/button is unreadable on Mac with Increase Contrast enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156864 smurf 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 156864] Active tab/button is unreadable on Mac with Increase Contrast enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156864 --- Comment #2 from smurf --- (In reply to m.a.riosv from comment #1) > Have you tested, playing with accessibility options in LibreOffice > Menu/Edit/Preferences/LibreOffice/Accessibility. They have no effect on this issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156681] The underline line in Writer doesn't match the length of the sentence, even in simple cases
https://bugs.documentfoundation.org/show_bug.cgi?id=156681 Stéphane Guillou (stragu) changed: What|Removed |Added URL||https://ask.libreoffice.org ||/t/problema-con-la-sottolin ||eatura-del-testo-errore-di- ||visualizzazione/94045/18 --- Comment #22 from Stéphane Guillou (stragu) --- (In reply to خالد حسني from comment #11) > This commit depends on a few other commits and it wouldn’t be easy to port > it to release branches Ah, I misunderstood that. So yes, delaying until 24.2 then. Thanks for reverting, Xisco, and thanks for all the fixes, Khaled! And thanks Victor, Leroy and Aron for the QA :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530
Julien Nabet changed:
What|Removed |Added
CC||lio...@mamane.lu
--- Comment #11 from Julien Nabet ---
Trying to debugging a bit:
when copying the table, we go in:
dbaccess/source/ui/uno/copytablewizard.cxx
1178 case DataType::CHAR:
1179 case DataType::VARCHAR:
1180 case DataType::LONGVARCHAR:
1181 case DataType::DECIMAL:
1182 case DataType::NUMERIC:
1183 aTransfer.transferComplexValue( nSourceColumn,
nDestColumn, ::getString, ::setString );
(see
https://opengrok.libreoffice.org/xref/core/dbaccess/source/ui/uno/copytablewizard.cxx?r=9d2355b6#1183)
then LO goes in OPreparedStatement::setString
See
https://opengrok.libreoffice.org/xref/core/connectivity/source/drivers/firebird/PreparedStatement.cxx?r=9227fbab#181
and pbs happen:
181 void SAL_CALL OPreparedStatement::setString(sal_Int32 nParameterIndex,
182 const OUString& sInput)
...
194 OString str = OUStringToOString(sInput , RTL_TEXTENCODING_UTF8 );
...
198 int dtype = (pVar->sqltype & ~1); // drop flag bit for now
...
200 if (str.getLength() > pVar->sqllen)
201 str = str.copy(0, pVar->sqllen);
"sInput" is "123.45"
"str" is well converted to "123.45"
"dtype" is SQL_LONG (it'll be important next)
str.getLength() is equal to 6 => OK
but
pVar->sqllen = 4 so the str is truncated to "123."
not right but whatever, since "dtype" is SQL_LONG, we go there:
242 case SQL_LONG:
243 {
244 sal_Int32 int32Value = sInput.toInt32();
245 setInt(nParameterIndex, int32Value);
246 break;
so we don't use str but "sInput", sInput which contains "123.45" is converted
to Int32 so 123.
Trying to understand how to fix this, I noticed:
https://opengrok.libreoffice.org/xref/core/offapi/com/sun/star/sdbc/XParameters.idl?r=5687eba4#343
...
334 @param scale
335 for
336 com::sun::star::sdbc::DataType::DECIMAL
337 or
338 com::sun::star::sdbc::DataType::NUMERIC
339 types, this is the number of digits after the decimal point.
For all other types, this value will be ignored.
340 @throws SQLException
341 if a database access error occurs.
342 */
343 void setObjectWithInfo([in]long parameterIndex,
344 [in]any x, [in]long targetSqlType, [in]long
scale)
345 raises (SQLException);
so "setObjectWithInfo" should be used instead of "setString" in
copytablewizard.cxx part.
but there's no "getObjectWithInfo" in XRow.idl, just "getObject" in
https://opengrok.libreoffice.org/xref/core/offapi/com/sun/star/sdbc/XRow.idl?r=5687eba4#244
Is it sufficient, don't know but I gave a try and then the pb how to adapt the
method "transferValue" or "transferComplexValue", 2 template methods
from
https://opengrok.libreoffice.org/xref/core/dbaccess/source/ui/uno/copytablewizard.cxx?r=9d2355b6#952
In //, I read some info about DECIMAL and NUMERIC here:
https://firebirdsql.org/file/documentation/chunk/en/refdocs/fblangref30/fblangref30-datatypes-fixedtypes.html
a lot of info here but the point to have in mind is this one:
"The form of declaration for fixed-point data, for instance, NUMERIC(p, s), is
common to both types. It is important to realise that the s argument in this
template is scale, rather than "a count of digits after the decimal point".
Understanding the mechanism for storing and retrieving fixed-point data should
help to visualise why: for storage, the number is multiplied by 10s (10 to the
power of s), converting it to an integer; when read, the integer is converted
back."
If I don't misunderstand, it means that in Firebird a DECIMAL or NUMERIC with
display value "123.45" stores physically "12345" plus some info to indicate it
must be divided by 100.
Lionel: perhaps you may have some hints to how to fix this? (for devs in
general because I expect it won't be easy enough for me :-))
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 --- Comment #13 from Eyal Rozenberg --- (In reply to Miklos Vajna from comment #11) So, in the document I attached, suppose, our user persona Eve wants to also have the third row repeat across pages (i.e. to have rows 1-3 repeat, not just 1-2). Well, she starts by selecting the row. First, she checks the the context menu: Nothing relevant there. Second, she checks out the table menu, because maybe she remembers having used "Header rows repeat across pages". Well, that menu item is checked. On the one hand, that might make sense to her, because some repeated header rows are enabled; but on the other hand, the row she's selected is not part of those, and she cannot use the only UI widget for this functionality, to apply this feature to the current row. What is Even I do? She is somewhat exasperated What she can do at that point is either uncheck the "Header rows repeat", select the top 3 rows, and re-check it - which works, but is a hassle and not intuitive enough; or she might find the corresponding setting in the Table Properties dialog - but that would be mostly a stroke of luck (and frankly I personally didn't notice that for years). Hence the request to allow doing this via the context menu. ... and the same request for removing the last row(s) from the set of repeating header rows, via the context menu. > The unclear part for me is what to do when you would have 3 repeating > headlines, you're in the second and you would toggle. That would not be possible, since the semantics are not obvious enough. I'd have this menu item grayed out when I'm on the second of three header rows. (Maybe even change the label to indicate why that is; or not.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 --- Comment #12 from Eyal Rozenberg --- Created attachment 189118 --> https://bugs.documentfoundation.org/attachment.cgi?id=189118=edit Bug for illustrating the ask This document has a table breaking across the 1st and 2nd pages. It's also had the first two lines of the table selected and "Table | Header rows repeat across pages" enabled for them. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156884] Selection box lags navigation with keyboard arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=156884 --- Comment #3 from Alex --- Created attachment 189117 --> https://bugs.documentfoundation.org/attachment.cgi?id=189117=edit Odd results from graphics test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156884] Selection box lags navigation with keyboard arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=156884 --- Comment #2 from Alex --- I was not able to reproduce in safe mode. However restoring my user profile to defaults did not resolve the issue outside of safe mode. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156884] Selection box lags navigation with keyboard arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=156884 --- Comment #1 from Alex --- Created attachment 189116 --> https://bugs.documentfoundation.org/attachment.cgi?id=189116=edit Example doc where issue was observed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156884] New: Selection box lags navigation with keyboard arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=156884 Bug ID: 156884 Summary: Selection box lags navigation with keyboard arrows Product: LibreOffice Version: 7.6.0.3 release Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xfac...@gmail.com Description: Sometimes when I navigate cells using keyboard arrows the apparent cell selection will lag behind where the cell cursor actually went, sometimes updating after a moment or a few seconds, or sometimes never. Behavior seems to depend on spreadsheet contents. Steps to Reproduce: 1. Open or create a spreadsheet with some various types and sizes of data. 2. Navigate with the keyboard arrow keys. 3. Observe cell selection vs cell cursor position. Actual Results: Selection lags behind cursor. Expected Results: Selection and cursor are the same. Reproducible: Sometimes User Profile Reset: No Additional Info: Version: 7.6.0.3 (AARCH64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 8; OS: Mac OS X 13.5.1; UI render: Skia/Metal; 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 156883] New: The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 Bug ID: 156883 Summary: The background color of text with trailing spaces is no longer drawn correctly. Product: LibreOffice Version: 7.5.5.2 release Hardware: IA64 (Itanium) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: adr...@joshuatech.com Description: If a piece of text with a colored background has trailing spaces, the trailing spaces are not drawn with the background color. This is a new bug as until very recently text rendered correctly. Steps to Reproduce: 1.In Writer type " Testing x" (without the quotes). 2.Select the test and hilite in some color. 3.Move the cursor to just before the "x" and insert a new-line. Actual Results: The space after "Testing " is no longer displayed hilited. Expected Results: The space after "Testing " should be shown as hilited. Until the most recent versions of Writer this worked correctly. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156707] FORMCONTROLS: Textboxes will be created with flat Border - 3D won't be shown after reopening Document
https://bugs.documentfoundation.org/show_bug.cgi?id=156707 raal changed: What|Removed |Added CC||caolan.mcnamara@collabora.c ||om, r...@post.cz Regression By||Caolán McNamara Keywords|bibisectRequest |bibisected, bisected --- Comment #5 from raal --- This seems to have begun at the below commit in bibisect repository/OS . Adding Cc: to Caolán McNamara ; Could you possibly take a look at this one? Thanks 29a39b72408b7090b1c3d439dc83b54416224599 is the first bad commit commit 29a39b72408b7090b1c3d439dc83b54416224599 Author: Jenkins Build User Date: Tue Oct 4 21:42:03 2022 +0200 source sha:ca46afebb7dc0ec4375e995fa90edccbed6c2530 140947: default to 'flat' instead of '3D Look' for form controls | https://gerrit.libreoffice.org/c/core/+/140947 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156880] LibreOffice spellcheck/dictionary issues in 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156880 --- Comment #3 from Mike Kaganski --- Is English dictionary installed? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112489] Writer: In track changes, redline in left margin prints too thin to see.
https://bugs.documentfoundation.org/show_bug.cgi?id=112489 --- Comment #16 from Justin L --- (In reply to awyvern1983 from comment #0) > The track changes redline in the margins is perfectly visible on my screen, > but when printed or converted to pdf, it outputs very thinly, I tried exporting to PDF (Ubuntu 20.04), and it looked as clear as in LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 Julien Nabet changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #10 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. I tried locally by reverting https://git.libreoffice.org/core/+/b9a0dc13a02e71dc680ad6b3d1d9f55ae27e3217%5E%21/, it still fails. I also added a trace to know if LO goes there at this moment, it's not the case. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156858] LibreCalc wrong subtraction of numbers 0, 0000000000001
https://bugs.documentfoundation.org/show_bug.cgi?id=156858 --- Comment #5 from ady --- (In reply to m.a.riosv from comment #4) > In Number-General format, it shows 23,4 > changing to a format like 00,0 indeed it shows 23,40001. FWIW, testing with LO Dev 24.2 built 2023-08-22, there is no need to change the cell format. Using the default standard cell format with default column width, it shows 23.4 (or 23,4). By double-clicking the column right-side border in order to auto-expand the column's width, it shows 23.40001 (or 23,40001). Anyway, I am just reporting the behavior I see, just in case. I still tend to think this is about floating-point math, but, as I said in a prior comment, I am guessing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156880] LibreOffice spellcheck/dictionary issues in 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156880 --- Comment #2 from John Schuetz --- Created attachment 189115 --> https://bugs.documentfoundation.org/attachment.cgi?id=189115=edit Screenshot of error -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93795] "Restart Numbering" is not shown as change when recording changes
https://bugs.documentfoundation.org/show_bug.cgi?id=93795 Justin L changed: What|Removed |Added Hardware|Other |All CC||jl...@mail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Julien Nabet changed: What|Removed |Added Depends on||156854 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156854 [Bug 156854] Menu icons are broken on macOS with Skia -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156854] Menu icons are broken on macOS with Skia
https://bugs.documentfoundation.org/show_bug.cgi?id=156854 Julien Nabet changed: What|Removed |Added Blocks||129062 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Julien Nabet changed: What|Removed |Added Depends on||156866 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156866 [Bug 156866] Logo in help about not properly rendered with Skia Raster/Metal (macOS) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Julien Nabet changed: What|Removed |Added Depends on||156881 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156881 [Bug 156881] Background padding is green on 7.6.0.3 when skia enabled -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156881] Background padding is green on 7.6.0.3 when skia enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156881 Julien Nabet changed: What|Removed |Added Blocks||129062 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Bug 83946 depends on bug 63237, which changed state. Bug 63237 Summary: Record all changes in highlighted/selected text range https://bugs.documentfoundation.org/show_bug.cgi?id=63237 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63237] Record all changes in highlighted/selected text range
https://bugs.documentfoundation.org/show_bug.cgi?id=63237 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Justin L --- Fixed in LO 4.2.5 with commit d46e7dabd3090697c46e24a350cc75f35c28a8f7 Author: Luboš Luňák on Tue Apr 29 11:11:53 2014 +0200 do not have a separate action for accepting changes in a selection -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156880] LibreOffice spellcheck/dictionary issues in 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156880 --- Comment #1 from Mike Kaganski --- Created attachment 189114 --> https://bugs.documentfoundation.org/attachment.cgi?id=189114=edit Error Underlined Works here using Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156851] LibreOffice Calc & Writer UI-Bugs / Incosistency
https://bugs.documentfoundation.org/show_bug.cgi?id=156851 d changed: What|Removed |Added Component|BASIC |Calc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128312] Calculation involing some decimals return incorrect floats with 12 d.p.
https://bugs.documentfoundation.org/show_bug.cgi?id=128312 m.a.riosv changed: What|Removed |Added CC||d...@olsza.cloudns.ph --- Comment #15 from m.a.riosv --- *** Bug 156858 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 156858] LibreCalc wrong subtraction of numbers 0, 0000000000001
https://bugs.documentfoundation.org/show_bug.cgi?id=156858 m.a.riosv changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from m.a.riosv --- In Number-General format, it shows 23,4 changing to a format like 00,0 indeed it shows 23,40001. But I think the one it out of the precision. https://wiki.documentfoundation.org/Faq/Calc/Accuracy https://ask.libreoffice.org/t/accuracy-in-libreoffice-calc/83750/2 https://ask.libreoffice.org/t/calc-rounding-general-precision-problem/64358/2 Seems we can consider this one like a duplicate of 128312, please if you are not agree reopen it. *** This bug has been marked as a duplicate of bug 128312 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87351] [META] Conditional formatting bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87351 Bug 87351 depends on bug 100894, which changed state. Bug 100894 Summary: FILEOPEN FILESAVE IMPORT Conditional formatting: xls file with a lot of Conditional formatting freeze Calc when opening Styles sidebar https://bugs.documentfoundation.org/show_bug.cgi?id=100894 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100894] FILEOPEN FILESAVE IMPORT Conditional formatting: xls file with a lot of Conditional formatting freeze Calc when opening Styles sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=100894 Noel Grandin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100894] FILEOPEN FILESAVE IMPORT Conditional formatting: xls file with a lot of Conditional formatting freeze Calc when opening Styles sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=100894 --- Comment #22 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6fd755fb36472938757b2581cbe99f5e5fe1ae40 tdf#100894 lots of Conditional formatting freeze calc Styles sidebar It will be available in 24.2.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 100894] FILEOPEN FILESAVE IMPORT Conditional formatting: xls file with a lot of Conditional formatting freeze Calc when opening Styles sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=100894 Commit Notification changed: What|Removed |Added Whiteboard|interoperability|interoperability |target:6.2.0|target:6.2.0 target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156882] New: Alo ker
https://bugs.documentfoundation.org/show_bug.cgi?id=156882 Bug ID: 156882 Summary: Alo ker Product: cppunit Version: 1.12 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bungaadelweiss...@gmail.com CC: markus.mohrh...@googlemail.com Created attachment 189113 --> https://bugs.documentfoundation.org/attachment.cgi?id=189113=edit Hahah -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156881] Background padding is green on 7.6.0.3 when skia enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156881 Hurri39 changed: What|Removed |Added Attachment #189112|Writere with Skia disabled |Writer with Skia disabled description|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156881] Background padding is green on 7.6.0.3 when skia enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156881 --- Comment #1 from Hurri39 --- Created attachment 189112 --> https://bugs.documentfoundation.org/attachment.cgi?id=189112=edit Writere with Skia disabled -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156881] New: Background padding is green on 7.6.0.3 when skia enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156881 Bug ID: 156881 Summary: Background padding is green on 7.6.0.3 when skia enabled Product: LibreOffice Version: 7.6.0.3 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jm.gigan...@free.fr Created attachment 189111 --> https://bugs.documentfoundation.org/attachment.cgi?id=189111=edit Writer with Skia enabled Since upgrading to 7.6.0.3 I have a green background instead of a transparent background for interface elements. With Skia disabled, there's no issue. Attached 2 screenshots, one with Skia enabled, one with Skia disabled. Software / Hardware MacOS 10.15.7 (19H2026) MacBook Pro (16", 2019) 2,6 GHz Intel Core i7 16 Go ram AMD Radeon Pro 5300M 4 Go Intel UHD Graphics 630 1536 Mo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156857] FILEOPEN PPTX: text boxes (with more text) expand vertically to fit text (when they don't in PowerPoint)
https://bugs.documentfoundation.org/show_bug.cgi?id=156857 --- Comment #5 from Gerald Pfeifer --- Created attachment 189110 --> https://bugs.documentfoundation.org/attachment.cgi?id=189110=edit Visual comparison PowerPoint (left) vs Impress (right) (In reply to Gabor Kelemen (allotropia) from comment #3) > But for me only the "Global Events" is two lines, the Web/Organic > fits in one line (even back to bibisect-6.0). The font is also > called "Poppins Light" which is something I don't have locally Indeed, now that I tried again the "Global Events" box looks like the one to focus on. (In reply to Hossein from comment #4) > Is it possible that it is a font issue? For example lack of specific > font on Linux? I originally wondered about that, too, but seeing how in PowerPoint "Events" is not shown, whereas Impress shows "Events" in a second line and increases the height of the box accordingly makes me think it's not merely a font issue? Let me share a screenshot comparing PowerPoint (online) vs Impress. The former shows "Global", drops "Events", and leave the box' height. The latter shows "Global Event" spread over two lines and grows the box. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114039] [META] Fields dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114039 Bug 114039 depends on bug 139344, which changed state. Bug 139344 Summary: Edit Fields dialogs looses format of next field when selected via "Next-Field" button https://bugs.documentfoundation.org/show_bug.cgi?id=139344 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139344] Edit Fields dialogs looses format of next field when selected via "Next-Field" button
https://bugs.documentfoundation.org/show_bug.cgi?id=139344 BogdanB changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156868] Find function should highligh all instances of found keyword
https://bugs.documentfoundation.org/show_bug.cgi?id=156868 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #5 from m.a.riosv --- Maybe because it is a button to execute, not a choice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156880] New: LibreOffice spellcheck/dictionary issues in 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156880 Bug ID: 156880 Summary: LibreOffice spellcheck/dictionary issues in 7.6 Product: LibreOffice Version: 7.6.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: psudrum...@gmail.com Description: It seems that something got messed up with regards to dictionaries in 7.6. Spell check isn't working in Writer. It's easy to test, just type a garbage string, and if spelling check is enabled, it is not flagged as an error. Steps to Reproduce: 1. type a known wrongly spelled word 2. press F7 Actual Results: incorrect word is not flagged Expected Results: incorrect word should be flagged Reproducible: Always User Profile Reset: No Additional Info: I use the English-US language -- You are receiving this mail because: You are the assignee for the bug.
