[Libreoffice-bugs] [Bug 144405] cli_cppuhelper policy installed in GAC for wrong architecture
https://bugs.documentfoundation.org/show_bug.cgi?id=144405 Buovjaga changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||1200 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101200] Two objects are not deleted after the uninstallation
https://bugs.documentfoundation.org/show_bug.cgi?id=101200 Buovjaga changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4405 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33749] Inconsistencies in Help pages on Cell Merging and Splitting (unmerging) in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=33749 --- Comment #27 from Ross Johnson --- Proposal (relative to the current development version of LO): 1) Replace the entire "Format > Merge Cells" submenu with the single "Format > Merge and Center Cells" button with all the same behaviour it has on the Formatting Bar. 2) Replace the "Split Cells" button from the context menu of a selected merged cell with the "Merge and Center Cells" button showing the current merge status, as it does elsewhere. Rationale: The current behaviour of the "Merge and Center Cells" button on the Formatting Bar is consistent with all other formatting buttons, eg, "Align Left" is still "Align Left" (but shown activated) when the text is currently already left aligned, and toggling it off reverts the alignment to a default alignment. It behaves correctly and intuitively IMO. The "Merge Cells" button in the "Format > Merge Cells" submenu should be removed as it appears to do the same as "Merge and Center Cells", that is, when it works correctly. It isn't helpful though as it has at least two problems: 1) it is greyed out if a merged cell is selected, unlike "Merge and Centre Cells"; 2) it becomes selectable when a range of cells is selected that includes a merged cell, but won't perform the merge. Removing both "Merge Cells" and "Split Cells" buttons from the Format > Merge Cells submenu leaves one entry, the "Merge and Center Cells" button, which should then be promoted to the top level menu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68459] EDITING: frames are jumping and impossible to position correctly with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=68459 --- Comment #24 from mango wodzak --- Not yet fixed the bug is still firmly present. Version:7.2.1.2 (x64) Build: 87b77fad49947c1441b67c559 Environment:CPU Threads 12; OS; Windows 10.0 Build 19403 User Interface: UI render: Skia/Raster; VCL; win Locale: en-AU (en-AU); UI en-GB Misc: Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144579] New: Font color and character highlight buttons do not allow change color in palette
https://bugs.documentfoundation.org/show_bug.cgi?id=144579 Bug ID: 144579 Summary: Font color and character highlight buttons do not allow change color in palette Product: LibreOffice Version: 7.2.1.1 rc Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jose.ve...@urjc.es Description: If you click in the arrow of the font color button (in the toolbar or in the side bar) you cant select any color in the palette that appears. Steps to Reproduce: 1. Click in the arrow of the font color button 2. In the pallete that appears try to select any color Actual Results: The color is not selected Expected Results: The color is selected Reproducible: Always User Profile Reset: No Additional Info: Tested in KDe (kubuntu 21.04 and Neon 20.4) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140834] Crash in Draw 7.1.0.3(64) when export graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=140834 Timur changed: What|Removed |Added CC||xiscofa...@libreoffice.org --- Comment #12 from Timur --- Xisco, please explain how QA script works, it's wrong sending. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131323] Libreoffice pdf conversion fails in FIPS mode
https://bugs.documentfoundation.org/show_bug.cgi?id=131323 --- Comment #11 from Timur --- LO is volunteer driven. So bug can be resolved in a week or not resolved in a decade. You can fix it yourself, find or pay someone to get it fixed, or just wait until some dev does it, if ever. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89863] Calc: Long captions in chart are out of background - option should choose just the beginning or break text
https://bugs.documentfoundation.org/show_bug.cgi?id=89863 Timur changed: What|Removed |Added CC||xiscofa...@libreoffice.org --- Comment #11 from Timur --- Xisco, please see what's wrong with QA script, it came here more times. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140901] EDITING Crash when deleting rows that are referenced by a chart
https://bugs.documentfoundation.org/show_bug.cgi?id=140901 Timur changed: What|Removed |Added Keywords||filter:xls --- Comment #7 from Timur --- Thanks for explanation. General note: bug started as XLS but should also be checked in MSO, by opening XLS if correct and saving afaim as XLS aand XLSX, to see how that one opens in LO. Usually "Xls/x saved in Lo" are not proper samples because source ODS is needed. But they are of they open well in MSO and can be resaved there. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144578] The outline numbering is showing all levels even though the "Show sublevels" is set as "1"
https://bugs.documentfoundation.org/show_bug.cgi?id=144578 Kevin Suo changed: What|Removed |Added CC||jl...@mail.com --- Comment #2 from Kevin Suo --- Adding Justin Luth to cc, I think you may also be interested in this one since you have committed various "chapter number" related fixes recently. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124176] Use pragma once instead of include guards
https://bugs.documentfoundation.org/show_bug.cgi?id=124176 --- Comment #227 from Commit Notification --- Chris Sherlock committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/83070c694c742ef1e86e017a5e684e72b23bf3c9 tdf#124176 - Use pragma once instead of include guards It will be available in 7.3.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 131323] Libreoffice pdf conversion fails in FIPS mode
https://bugs.documentfoundation.org/show_bug.cgi?id=131323 --- Comment #10 from Shawn Bonham --- I am running into the same exact issue. RHEL 8.4 running FIPS mode. Surprised there has been no movement on this for over a year. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141886] Data saving error in latest updates 7.1.2 & 7.1.1
https://bugs.documentfoundation.org/show_bug.cgi?id=141886 --- Comment #3 from gjr...@xtra.co.nz --- Still able to reproduce in 7.1.6 after updating -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144282] Crash when changing protection options on document
https://bugs.documentfoundation.org/show_bug.cgi?id=144282 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 144272] EDITING Changing paragraph style is not recorded as tracked change
https://bugs.documentfoundation.org/show_bug.cgi?id=144272 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 144271] leaks of SwTextBoxHelper
https://bugs.documentfoundation.org/show_bug.cgi?id=144271 QA Administrators changed: What|Removed |Added Whiteboard|target:7.3.0|target:7.3.0 ||QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144270] Tracked table changes are split up to cell level instead of row/table level
https://bugs.documentfoundation.org/show_bug.cgi?id=144270 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 144200] LibreOffice 7.2 for ARM on Apple Silicon claims its an iOS application
https://bugs.documentfoundation.org/show_bug.cgi?id=144200 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 140492] 5 bugs related to tables
https://bugs.documentfoundation.org/show_bug.cgi?id=140492 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 140492] 5 bugs related to tables
https://bugs.documentfoundation.org/show_bug.cgi?id=140492 --- Comment #4 from QA Administrators --- Dear Don Meinsen, 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 140487] Crash in: WinFontInstance::ImplGetGlyphBoundRect(unsigned short, tools::Rectangle &, bool)
https://bugs.documentfoundation.org/show_bug.cgi?id=140487 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 140487] Crash in: WinFontInstance::ImplGetGlyphBoundRect(unsigned short, tools::Rectangle &, bool)
https://bugs.documentfoundation.org/show_bug.cgi?id=140487 --- Comment #3 from QA Administrators --- Dear Deborah Smith, 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 140364] xml bug
https://bugs.documentfoundation.org/show_bug.cgi?id=140364 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 140364] xml bug
https://bugs.documentfoundation.org/show_bug.cgi?id=140364 --- Comment #3 from QA Administrators --- Dear Ovidiu, 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 140834] Crash in Draw 7.1.0.3(64) when export graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=140834 --- Comment #11 from QA Administrators --- Dear Kenneth Tingey, 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 140772] Crash when working on QR-Codes
https://bugs.documentfoundation.org/show_bug.cgi?id=140772 --- Comment #2 from QA Administrators --- Dear Steve Lawson, 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 139013] ODS file takes forever to load. Loads fine if saved as XLSX.
https://bugs.documentfoundation.org/show_bug.cgi?id=139013 --- Comment #4 from QA Administrators --- Dear the988, 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 136091] When in a writer document on secondary display, text get's garbled
https://bugs.documentfoundation.org/show_bug.cgi?id=136091 --- Comment #4 from QA Administrators --- Dear RFEMN, 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 136086] Anchors interacting with each other
https://bugs.documentfoundation.org/show_bug.cgi?id=136086 --- Comment #6 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 136017] Image frame background set to white explicitly (instead of non) on DOC export
https://bugs.documentfoundation.org/show_bug.cgi?id=136017 --- Comment #5 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 136016] Image differently positioned after undo (in bulleted list); different anchor position
https://bugs.documentfoundation.org/show_bug.cgi?id=136016 --- Comment #9 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 117435] Firebird: Migration: data type Image [ LONGVARBINARY ] is not being migrated properly
https://bugs.documentfoundation.org/show_bug.cgi?id=117435 --- Comment #15 from QA Administrators --- Dear Drew Jensen, 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 98682] Wrong text direction after copy/paste from web browser to LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=98682 --- Comment #29 from QA Administrators --- Dear yousifjkadom, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89863] Calc: Long captions in chart are out of background - option should choose just the beginning or break text
https://bugs.documentfoundation.org/show_bug.cgi?id=89863 --- Comment #10 from QA Administrators --- Dear 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 74064] File Name detection with "File save as" should be last Period, not first Period (Linux only)
https://bugs.documentfoundation.org/show_bug.cgi?id=74064 --- Comment #32 from QA Administrators --- Dear Joel Madero, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 73933] TABLE: Numbers are shown from left to right in "Number range" variable when used in RTL scripts.
https://bugs.documentfoundation.org/show_bug.cgi?id=73933 --- Comment #10 from QA Administrators --- Dear safa alfulaij, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72341] Increase/Decrease font doesn't apply to bullet in RTL paragraph when text script isn't RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=72341 --- Comment #16 from QA Administrators --- Dear Faisal Menawer, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71037] FORMATTING: wrong page number direction in footnote's continuation notice
https://bugs.documentfoundation.org/show_bug.cgi?id=71037 --- Comment #14 from QA Administrators --- Dear safarzadeh.h, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68459] EDITING: frames are jumping and impossible to position correctly with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=68459 --- Comment #23 from QA Administrators --- Dear mango wodzak, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63847] Page number in TOC sometimes gets "CTL font" attribute in mixed LTR/RTL document
https://bugs.documentfoundation.org/show_bug.cgi?id=63847 --- Comment #10 from QA Administrators --- Dear Erwan, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57187] EDITING: Justified text looks wrong as right aligned when breaking line with shift+enter
https://bugs.documentfoundation.org/show_bug.cgi?id=57187 --- Comment #19 from QA Administrators --- Dear Marcin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47479] LibO Calc Macro .getCellRangeByName with named range
https://bugs.documentfoundation.org/show_bug.cgi?id=47479 --- Comment #8 from QA Administrators --- Dear Kossem, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127215] If saving a file.with.dots, ".odt" is not appended, so Export to PDF results in file.with.PDF instead of file.with.dots.PDF (KDE or OpenSuse?)
https://bugs.documentfoundation.org/show_bug.cgi?id=127215 --- Comment #12 from QA Administrators --- Dear gorgonz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122163] Calling a method on a COM object should not require Type Library, it's optional.
https://bugs.documentfoundation.org/show_bug.cgi?id=122163 --- Comment #6 from QA Administrators --- Dear himajin10, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119883] Migration dialog closing LibreOffice if a table has been copied previously
https://bugs.documentfoundation.org/show_bug.cgi?id=119883 --- Comment #6 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119365] Inconsistent cursor after using find & replace (and with undo/redo of the replacement)
https://bugs.documentfoundation.org/show_bug.cgi?id=119365 --- Comment #5 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117941] slash/X "striking" of text not shown for RTL text when exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=117941 --- Comment #9 from QA Administrators --- Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114911] Setting vertical orientation for first cell in table row shifts rendering of row on save & reopen
https://bugs.documentfoundation.org/show_bug.cgi?id=114911 --- Comment #10 from QA Administrators --- Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114193] Impress doesnt change behaviour when launched in RTL
https://bugs.documentfoundation.org/show_bug.cgi?id=114193 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108263] Comment is duplicated after copying sheet to new document (see comment 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=108263 --- Comment #16 from QA Administrators --- Dear Robert Monnier, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103099] Paragraph style - line spacing - proportional: wrong spacing when set to <100% on first line of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=103099 --- Comment #10 from QA Administrators --- Dear bugzilla, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144578] The outline numbering is showing all levels even though the "Show sublevels" is set as "1"
https://bugs.documentfoundation.org/show_bug.cgi?id=144578 Kevin Suo changed: What|Removed |Added CC||vasily.melenc...@cib.de Keywords||bibisected, regression --- Comment #1 from Kevin Suo --- Bibisected to the following range: 7c95c16deba9 tdf#143107 related: ensure correct order of which ids aa5c6d127559 new ODF numbered list parameter loext:num-list-format 99ef46fdb2a9 tdf#143105 Don't export empty URLs to PDF f79a8f578ab5 Update git submodules Within which aa5c6d127559 may be the only one related. commit aa5c6d127559912ad60a63fbd972b78fb8f9691b Author: Vasily Melenchuk Date: Mon Jun 14 14:27:56 2021 +0300 new ODF numbered list parameter loext:num-list-format Adding Vasily Melenchuk to CC list, would you please take a look? Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144578] New: The outline numbering is showing all levels even though the "Show sublevels" is set as "1"
https://bugs.documentfoundation.org/show_bug.cgi?id=144578 Bug ID: 144578 Summary: The outline numbering is showing all levels even though the "Show sublevels" is set as "1" Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Created attachment 175100 --> https://bugs.documentfoundation.org/attachment.cgi?id=175100&action=edit test odt file The attached ODT file contains outline numbering. The outline numbering is showing all sub-levels (e.g., "III.A.1."), even though the "Show sublevels" for each 1-3 levels are set to "1". Steps to Reproduce: 1. Open the attached ODT file. 2. Go to "Tools > Outline Numbering", observe in tab "Numbering" that the "Show sublevels" for both level 1, 2, 3 are set to "1". Current Result: The Numbering for this document is wrongly showing as : I. II. II.A. II.B. III. III.A. III.A.1. III.A.2. III.B. III.C. III.C.1. III.C.2. Expected: The Numbering for this document, when opened, should be: I. II. A. B. III. A. 1. 2. B. C. 1. 2. and adjusting the "Show sublevels" option in "Tools > Outline Numbering" dialog should work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101200] Two objects are not deleted after the uninstallation
https://bugs.documentfoundation.org/show_bug.cgi?id=101200
--- Comment #8 from Kalle Niemitalo ---
In LibreOffice_7.2.0_Win_x64.msi, cli_cppuhelper.dll has been built for amd64,
but the MsiAssemblyName table incorrectly claims processorArchitecture=x86. I
suspect that the Side-by-Side Assembly API ("Fusion") of Windows installs
cli_cppuhelper.dll to GAC_64 because of the content of the file, but when
Windows Installer later uninstalls the product, it passes
processorArchitecture=x86 to Fusion, which then doesn't find the assembly to
uninstall. This may get fixed as part of Bug#144405.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144577] MACRO RUN in Calc 6.4.7.2 but doesn't run in 7.1.5.2
https://bugs.documentfoundation.org/show_bug.cgi?id=144577 --- Comment #1 from Juan P. --- Created attachment 175099 --> https://bugs.documentfoundation.org/attachment.cgi?id=175099&action=edit Spreedsheet for fill "Diario" and "Mayor" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144577] New: MACRO RUN in Calc 6.4.7.2 but doesn't run in 7.1.5.2
https://bugs.documentfoundation.org/show_bug.cgi?id=144577 Bug ID: 144577 Summary: MACRO RUN in Calc 6.4.7.2 but doesn't run in 7.1.5.2 Product: LibreOffice Version: 7.1.5.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: juanpablomendo...@gmail.com Description: Macro (Contabilidad.ods/Standard/Modules/macro) perfectly in LibreOffice Calc 6.4.7.2 but, in LibreOffice 7.1.5.2 doesn't run without error message. Steps to Reproduce: 1. Open the spreadsheet "Contabilidad.ods" 2. Enable macros 3. click "DATOS" / EJECUTAR LIBROS CONTABLES 4. click "OK" Actual Results: In LibreOffice Calc 7.1.5.2 spreadsheets "Diafil", "Diario" and "Mayor" are empty. Expected Results: In LibreOffice Calc 6.4.7.2 spreadsheets "Diafil", "Diario" and "Mayor" are with same data of "Alimentación del diario" Reproducible: Always User Profile Reset: No Additional Info: N/A -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144405] cli_cppuhelper policy installed in GAC for wrong architecture
https://bugs.documentfoundation.org/show_bug.cgi?id=144405 --- Comment #12 from Kalle Niemitalo --- (In reply to Kalle Niemitalo from comment #0) > 1. The policy.1.0.cli_cppuhelper.dll file has been built for x86 I think this can be fixed by changing gb_CliNativeLibrary_PLATFORM_DEFAULT here: https://opengrok.libreoffice.org/xref/core/solenv/gbuild/CliNativeLibrary.mk?r=0adc9b61#12 The value is currently always x86. If the amd64 build of LibreOffice instead used amd64 here too, I think this setting would get passed to the "al" command and policy.1.0.cli_cppuhelper.dll would get the correct architecture in its headers, causing Fusion to install it to GAC_64 rather than GAC_32. It would still be possible to override this default by calling gb_CliNativeLibrary_set_platform for individual libraries, should that ever become necessary. > 2. ORCA shows that the MsiAssemblyName table of the MSI package has > processorArchitecture=x86 for both cli_cppuhelper and > policy.1.0.cli_cppuhelper. processorArchitecture of policy.1.0.cli_cppuhelper is defined for the MsiAssemblyName table here: https://opengrok.libreoffice.org/xref/core/scp2/source/ooo/ure.scp?r=0adc9b61#210 If gb_CliNativeLibrary_PLATFORM_DEFAULT is conditionally changed to "amd64", then the same change should be made here as well. processorArchitecture of cli_cppuhelper is defined for the MsiAssemblyName table here: https://opengrok.libreoffice.org/xref/core/scp2/source/ooo/ure.scp?r=0adc9b61#197 Correcting that might have no effect on cli_cppuhelper assembly loading, but it could instead fix Bug#101200 (cli_cppuhelper not uninstalled from GAC). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139164] Selection should not be activated in the print dialog for single objects
https://bugs.documentfoundation.org/show_bug.cgi?id=139164 --- Comment #15 from Michael Hendry --- First, apologies for deleting the screenshots from Dropbox in the process of migrating to a new computer. Second, I've realised that this feature often occurs when I've been deleting unwanted labels - either because I want fewer than 16, or because I'm printing on a partly used sheet of labels; ink printed on the backing isn't absorbed and causes smudges and inky fingers. Because the selection has been deleted, there is nothing for the "Print Selection" feature to print, there is no visibly selected area on the screen, and the print preview comes up blank. Now that I'm aware of this issue, I can work around it, but if "Print Selection" were switched to "Print All" after the deletion of a selection it would remove one source of confusion. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144576] New: Copy a table in Writer is not the same as Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=144576 Bug ID: 144576 Summary: Copy a table in Writer is not the same as Calc Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sr.enriq...@yahoo.com Description: The "table" format should be tab for new column and \n (new line) for new row. This format is correct in Calc, but not in Writer. Example: I've open 2 documents, one in Calc and other in Writer, both with a 2x2 table, and this is what happens when I copy these tables and paste it right here: Calc (correct): (1,1) (1,2) (2,1) (1,2) Writer (incorrect): (1,1) (1,2) (2,1) (1,2) Steps to Reproduce: 1.Open Writer 2.Create a table 3.Copy the table 4.Paste it in a text editor as notepad or this text boxes Actual Results: A non "table-formated" string. Cells separated only with new lines. Expected Results: A "table-formated" string. Cells separated with new lines and tabs. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144363] Experimental 4k+ columns bugs - 1) Merged / Big cells are confused in view, 2) cannot delete rows
https://bugs.documentfoundation.org/show_bug.cgi?id=144363 raal changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from raal --- I can reproduce the crash with Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: e7a40c0ded1ba26b6b8f3da5a0b894e9c7ee7a96 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140901] EDITING Crash when deleting rows that are referenced by a chart
https://bugs.documentfoundation.org/show_bug.cgi?id=140901 --- Comment #6 from Kohei Yoshida --- What that likely means is that there is a flaw in how formula groups are made in the XLS import filter code. What the code did prior to 80b18ee0affc1cfc2ceec3bf32ef65f481922efe was that it would scan the entire column to perform formula re-grouping (and/or repair any incorrect grouping) after the import is complete, which in theory should not be necessary. So, if that commits breaks this is an indication that there is a logic flaw in the XLS import filter code with respect to formula grouping. I don't have bandwidth to work on bug fixing for libreoffice these days, so I'll have to pass the torch to someone else for this one. Sorry. But hopefully this will be a helpful tip for anyone willing to dive in. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144506] LO Base PUBLIC schema table data window shows no records
https://bugs.documentfoundation.org/show_bug.cgi?id=144506 --- Comment #4 from Andrew Richardson --- I verified the following LO version does NOT have this issue, "PUBLIC" tables content is displayed as expected. So something changed in the LO 7.x timeframe. Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144363] Experimental 4k+ columns bugs - 1) Merged / Big cells are confused in view, 2) cannot delete rows
https://bugs.documentfoundation.org/show_bug.cgi?id=144363 elias estatistics changed: What|Removed |Added CC||elias__0...@yahoo.com --- Comment #2 from elias estatistics --- Created attachment 175098 --> https://bugs.documentfoundation.org/attachment.cgi?id=175098&action=edit delete rows as whole bug wtih 4k+ column enable delete rows as whole bug wtih 4k+ column enable Please select with mouse rows 37 to 52 and delete them as whole eg. Right click on selection of rows --> select DELETE ROWS. Libre calc is exited ONLY in 4k+ enable thing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144563] Fields referencing numbered lists now have "." in the generated text where they did not before
https://bugs.documentfoundation.org/show_bug.cgi?id=144563 Warren Young changed: What|Removed |Added CC||docfound2...@tangentsoft.co ||m --- Comment #1 from Warren Young --- Created attachment 175097 --> https://bugs.documentfoundation.org/attachment.cgi?id=175097&action=edit Screen capture showing the symptom Homebrew updated my installation to 7.2.1.2, and the symptom is still happening. The attached photo shows the unwanted dots in the gray "field" boxes. The old (and intended) behavior is that this bit of text was rendered as "[8, 15, 16]", being a list of references to numbered points later in the document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107642] [META] Paragraph dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107642 Bug 107642 depends on bug 139131, which changed state. Bug 139131 Summary: PARAGRAPH DIaLOG: Page style list (Text flow tab) is not in alphabetical order https://bugs.documentfoundation.org/show_bug.cgi?id=139131 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134283] "Show Page Variable" broken in 7.0Beta2
https://bugs.documentfoundation.org/show_bug.cgi?id=134283 --- Comment #6 from David Burleigh --- Is anyone working on this? It's a show-stopper for me. I can't use any version after 6.4.7.2 for the work I use LibreOffice for daily. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136091] When in a writer document on secondary display, text get's garbled
https://bugs.documentfoundation.org/show_bug.cgi?id=136091 --- Comment #3 from RFEMN --- Just tested with version 7.0.5.2 and it appears to be fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93901] "Edit Paragraph Style" dialog does not save changes after using "apply" button
https://bugs.documentfoundation.org/show_bug.cgi?id=93901 Justin L changed: What|Removed |Added CC||j...@pxlart.de --- Comment #13 from Justin L --- *** Bug 78959 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 107831] [META] Paragraph-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107831 Bug 107831 depends on bug 78959, which changed state. Bug 78959 Summary: Setting certain Font Effects, then unsetting them doesn't work without closing the dialog first. https://bugs.documentfoundation.org/show_bug.cgi?id=78959 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 78959] Setting certain Font Effects, then unsetting them doesn't work without closing the dialog first.
https://bugs.documentfoundation.org/show_bug.cgi?id=78959 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #10 from Justin L --- According to my bibisect-linux-51 this was fixed in the range https://cgit.freedesktop.org/libreoffice/core/log/?id=4f918cd5daed963287805da761e6983a392ae050&qt=range&q=240d1f289c5788845cd4336f223f2c4bc8975a99..4f918cd5daed963287805da761e6983a392ae050 and almost certainly by the fix for bug 93901. *** This bug has been marked as a duplicate of bug 93901 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144574] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=144574 The Cleaner changed: What|Removed |Added URL|https://www.sfwpexperts.com | |/website-design-los-angeles | |-california/| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144405] cli_cppuhelper policy installed in GAC for wrong architecture
https://bugs.documentfoundation.org/show_bug.cgi?id=144405 --- Comment #11 from Julien Nabet --- Kalle: reading your comments and seeing you've got some knowledge about Windows internals, perhaps you may be interested in contributing? If yes, here are 2 links: 1) general info about code contributing: https://wiki.documentfoundation.org/Development/GetInvolved 2) building on Windows: https://wiki.documentfoundation.org/Development/BuildingOnWindows if no or don't have time, you may also just take search keyword in the code here: https://opengrok.libreoffice.org/ to pinpoint pbs in LO code/propose some patches? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141495] CONFIGURATION = EOMONTH function corruption
https://bugs.documentfoundation.org/show_bug.cgi?id=141495 raal changed: What|Removed |Added Ever confirmed|1 |0 Status|NEW |UNCONFIRMED Keywords|regression | --- Comment #12 from raal --- (In reply to raal from comment #11) > I can confirm with Version: 7.3.0.0.alpha0+ / LibreOffice Community > Build ID: 55adeb1c3fbcf32c7c44a3f0c310b56298f551f9 > CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 > Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US > Calc: threaded Jumbo > > Works in LO 4.1, regression. > > Create file with Eomonth function, save as xlsx, open in excel 2010. I was wrong, cannot reproduce from scratch. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144575] New: Writer auto formats formula objects
https://bugs.documentfoundation.org/show_bug.cgi?id=144575
Bug ID: 144575
Summary: Writer auto formats formula objects
Product: LibreOffice
Version: 7.1.5.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: delaparra.dam...@gmail.com
When I open a previously saved document, the formula objects are reformatted
into a single line and all fractions written as a over b are changed to frac
{a}{b}. Also all multi-line objects made using newline command are changed to
stack{} command with # separating each line.
When making formula objects, there are extra spaces added unnecessarily when
typing parenthesis or brackets.
If this is not a bug, I think it should be a behavior that can be turned off.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126690] Bad default settings for nested/outline numbering indentations
https://bugs.documentfoundation.org/show_bug.cgi?id=126690 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #5 from Justin L --- Format -> Bullets and Numbering -> Outline: there are two pre-defined formats that include multi-level numberings. Because that causes a numbering string longer than the first tabstop, the first line gets pushed out to the second tabstop, and thus looks sloppy. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144574] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=144574 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144574] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=144574 Eike Rathke changed: What|Removed |Added Summary|8 Ways To Create Responsive |spam |Web Design For The Business | |In 2021 | Component|UI |deletionRequest Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116968] [META] Migrating existing embedded HSQLDB databases to Firebird
https://bugs.documentfoundation.org/show_bug.cgi?id=116968 Bug 116968 depends on bug 117435, which changed state. Bug 117435 Summary: Firebird: Migration: data type Image [ LONGVARBINARY ] is not being migrated properly https://bugs.documentfoundation.org/show_bug.cgi?id=117435 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117435] Firebird: Migration: data type Image [ LONGVARBINARY ] is not being migrated properly
https://bugs.documentfoundation.org/show_bug.cgi?id=117435 Robert Großkopf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #14 from Robert Großkopf --- (In reply to Alex Thurgood from comment #13) > No repro with > > Version: 7.1.5.2 / LibreOffice Community > Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 > CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR > Calc: threaded > > Using the first test file, the migration completes and I can see the images > when I navigate through the records via the form. > Also tested adding a new image record, this was saved and displayed. > The report also displayed the images. > > I would be inclined to mark this as WFM. Have tested with LO 6.1.5.2: No Images could be seen in the form. Then tested with LO 7.2.0.4: Images could be seen. All Test made with OpenSUSE 64bit rpm Linux. So something has been changed and the buggy behavior has been gone. I will set this one to WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144574] 8 Ways To Create Responsive Web Design For The Business In 2021
https://bugs.documentfoundation.org/show_bug.cgi?id=144574 webdev changed: What|Removed |Added URL||https://www.sfwpexperts.com ||/website-design-los-angeles ||-california/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144574] New: 8 Ways To Create Responsive Web Design For The Business In 2021
https://bugs.documentfoundation.org/show_bug.cgi?id=144574 Bug ID: 144574 Summary: 8 Ways To Create Responsive Web Design For The Business In 2021 Product: LibreOffice Version: 3.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: markleviseb...@gmail.com Description: Today every user searching for any kind of information and product looks to perform the searches from their nearest device. That is the reason why the number of mobile device users is continuously increasing. MaInly if your business falls in the health, financial or media sector then you might expect huge traffic on your website from mobile devices. Not only that but the ecommerce sector has also seen more traffic and conversion occurring on mobile devices. Visit site: https://www.sfwpexperts.com/ Actual Results: https://www.sfwpexperts.com/ Expected Results: https://www.sfwpexperts.com/ Reproducible: Always User Profile Reset: No Additional Info: https://www.sfwpexperts.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137335] FILEOPEN DOCX Whitespace should not define paragraph height
https://bugs.documentfoundation.org/show_bug.cgi?id=137335 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #3 from Justin L --- I'd say this is a duplicate of bug 127368. It seems the same as bug 117988, where we have some proof that the compat flag IgnoreTabsAndBlanksForLineCalculation already handles whitespace not defining the paragraph height. So the issue here really is that the pilcrow settings aren't able to define the paragraph height in LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89187] FORMATTING No date format options in Calc header/footer
https://bugs.documentfoundation.org/show_bug.cgi?id=89187 Michael Warner changed: What|Removed |Added CC||gbr...@gmx.net --- Comment #6 from Michael Warner --- *** Bug 144570 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 109087] [META] Calc sheet header and footer bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109087 Bug 109087 depends on bug 144570, which changed state. Bug 144570 Summary: CALC FOOTER DATE-FIELD https://bugs.documentfoundation.org/show_bug.cgi?id=144570 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144570] CALC FOOTER DATE-FIELD
https://bugs.documentfoundation.org/show_bug.cgi?id=144570 Michael Warner changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Michael Warner --- Hello George, Thanks for this request. I believe this is actually a duplicate of bug 89187. Please re-open if you disagree. *** This bug has been marked as a duplicate of bug 89187 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109087] [META] Calc sheet header and footer bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109087 Michael Warner changed: What|Removed |Added Depends on||144570 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144570 [Bug 144570] CALC FOOTER DATE-FIELD -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144570] CALC FOOTER DATE-FIELD
https://bugs.documentfoundation.org/show_bug.cgi?id=144570 Michael Warner changed: What|Removed |Added Severity|normal |enhancement Blocks||109087 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109087 [Bug 109087] [META] Calc sheet header and footer bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121313] paste image CTRL+V twice
https://bugs.documentfoundation.org/show_bug.cgi?id=121313 --- Comment #3 from Moshpirit --- This happens to me too with text on Calc and Writer. It does happen too with shift(↑)+Enter and Ctrl+Z. I use Manjaro (Linux 5.10.61-1-MANJARO with KDE Plasma); LibreOffice 7.2.0.4 20(Build:4) (also posted it on https://ask.libreoffice.org/t/lo-detects-ctrl-v-and-ctrl-z-twice/68041 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 78523] Improved commandline conversion - supply output filename and rename if exists
https://bugs.documentfoundation.org/show_bug.cgi?id=78523 --- Comment #2 from Michael Warner --- For this kind of control around the process, I suggest writing a script around the LO command. In my opinion this is a WF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141495] CONFIGURATION = EOMONTH function corruption
https://bugs.documentfoundation.org/show_bug.cgi?id=141495 raal changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||r...@post.cz Keywords||filter:xlsx, regression --- Comment #11 from raal --- I can confirm with Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 55adeb1c3fbcf32c7c44a3f0c310b56298f551f9 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo Works in LO 4.1, regression. Create file with Eomonth function, save as xlsx, open in excel 2010. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144573] SDK - on ARM Mac Silicon - failure to build CPP examples - Reason: unsafe use of relative rpath - cppumaker with restricted binary
https://bugs.documentfoundation.org/show_bug.cgi?id=144573 Alex Thurgood changed: What|Removed |Added Summary|SDK - on ARM Mac Silicon - |SDK - on ARM Mac Silicon - |failure to build CPP|failure to build CPP |example |examples - Reason: unsafe |complextoolbarcontrol |use of relative rpath - ||cppumaker with restricted ||binary -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144573] New: SDK - on ARM Mac Silicon - failure to build CPP example complextoolbarcontrol
https://bugs.documentfoundation.org/show_bug.cgi?id=144573 Bug ID: 144573 Summary: SDK - on ARM Mac Silicon - failure to build CPP example complextoolbarcontrol Product: LibreOffice Version: 7.2.1.1 rc Hardware: ARM OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: sdk Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ipla...@tuta.io Description: Using the aarch version of LibreOffice for Mac Silicon M1 ARM processor LO Version 7212 1) Set up the SDK 2) Change directory to the SDK examples 3) Try to build one of the CPP examples a) first problem is that macOS refuses to launch cppumaker - work around that by starting cppumaker a first time and forcing the "Open" switch to get around Apple Gatekeeper - cppumaker not signed, and not a recognized authorized app b) second problem is that even when cppumaker is subsequently called by make, the build of the example fails with : alex@MBPro13 complextoolbarcontrols % make mkdir -p /Users/alex/LibreOffice7.2_SDK/MACOSXexample.out/misc rm -f /Users/alex/LibreOffice7.2_SDK/MACOSXexample.out/misc/oosdk_cpp_types.flag "/Users/Shared/LibreOffice7.2_SDK/bin/cppumaker" -Gc -O/Users/alex/LibreOffice7.2_SDK/MACOSXexample.out/inc "/Applications/LO7212.app/Contents/Resources/ure/share/misc/types.rdb" "/Applications/LO7212.app/Contents/MacOS/../Resources/types/offapi.rdb" dyld: Library not loaded: @__VIA_LIBRARY_PATH__/libunoidllo.dylib Referenced from: /Users/Shared/LibreOffice7.2_SDK/bin/cppumaker Reason: unsafe use of relative rpath @__VIA_LIBRARY_PATH__/libunoidllo.dylib in /Users/Shared/LibreOffice7.2_SDK/bin/cppumaker with restricted binary make: *** [/Users/alex/LibreOffice7.2_SDK/MACOSXexample.out/misc/oosdk_cpp_types.flag] Abort trap: 6 Steps to Reproduce: See above Actual Results: Example fails to build from SDK environment Expected Results: Build should complete normally Reproducible: Always User Profile Reset: No Additional Info: "/Users/Shared/LibreOffice7.2_SDK/bin/cppumaker" -Gc -O/Users/alex/LibreOffice7.2_SDK/MACOSXexample.out/inc "/Applications/LO7212.app/Contents/Resources/ure/share/misc/types.rdb" "/Applications/LO7212.app/Contents/MacOS/../Resources/types/offapi.rdb" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144571] (FILTER) Selection of column constraints in AutoFilter is impossible because popup window disappears
https://bugs.documentfoundation.org/show_bug.cgi?id=144571 --- Comment #7 from Timur --- Is this resolved with bug 143580? Please test with master. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87720] Default insert image anchor, wrapping, and spacing (see comment #43 for summary at 2020-04-15)
https://bugs.documentfoundation.org/show_bug.cgi?id=87720 --- Comment #64 from al F --- After browsing several bug reports I am still not sure if this is the right place to post. Please point me to the right place if not. When inserting images, I expect that modifying the Frame style "Graphics" would change the defaults of the inserted image. That is true only to a certain degree. Settings for size are just ignored while settings for anchor is respected only when the anchor is Page. Expected behavior is that changing properties for the Graphics Frame style would have full impact when inserting images. Version: 7.2.0.2 / LibreOffice Community Build ID: 614be4f5c67816389257027dc5e56c801a547089 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: nb-NO (en_US.UTF-8); UI: en-US Calc: threaded Operating System: Kubuntu 20.04 with Ubuntu Studio KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-81-lowlatency OS Type: 64-bit Steps to reproduce: 0. Create a new document 1. Styles > Manage Styles > Frame Styles > Graphics 2. Modify settings and close 3. Insert > Image Modified settings example 1: Width: 9 cm (Height automatically changes to the same value) Keep ratio Anchor: To page Position: Center / Top to entire page Inserted image will have these properties: Width: 17 cm (same as text area on the page) Height: 22,67 cm Keep ratio Anchor: To page Position: Center / Top to entire page Modified settings example 2: Width: 9 cm / Autosize off Height: 9 cm / Autosize on Keep ratio Anchor: To paragraph Position: Center to paragraph area / Top to Paragraph text area Inserted image will have these properties: Width: 17 cm (same as text area on the page) Height: 22,67 cm Keep ratio Anchor: To character Position: Center / Top to page text area -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144363] Experimental 4k+ columns bugs - 1) Merged / Big cells are confused in view, 2) cannot delete rows
https://bugs.documentfoundation.org/show_bug.cgi?id=144363 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #1 from raal --- I can confirm first problem, but cannot reproduce second Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 55adeb1c3fbcf32c7c44a3f0c310b56298f551f9 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144536] Calc 'Function Wizard' provide alternative-linked non-localized version of the Function name
https://bugs.documentfoundation.org/show_bug.cgi?id=144536 --- Comment #12 from Karl --- Hi folks EVERY thing seem ON BOARD ! anyhow on BOARD. BAD in a BLOATED LIST:: SQRT() WURZEL() in a selection! --- GOOD in A TWO BODIES LIST: (the left displays the appropriate of the right synchron, if action is done at the right- the right displays the appropriate of the left, if // search / find / figure out // is done there as well WIZZARD :: SELECT/FIND/SEARCH(LEFT) | SELECT/FIND/SEARCH(RIGHT) s | w SQRT wurzel Super WHYNOT .... .... . . . . #NOW, im and the end: https://www.youtube.com/watch?v=ZeMlQEWEg2Q best wishes to all jk -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144432] Saving XLSX file looses markup/formatting after row 6223 out of 9933
https://bugs.documentfoundation.org/show_bug.cgi?id=144432 Timur changed: What|Removed |Added Summary|Saving XLSX file looses |Saving XLSX file looses |markup/formatting |markup/formatting after row ||6223 out of 9933 Keywords||filter:xlsx --- Comment #4 from Timur --- The last formatted row in the XLSX file is row 6223 out of 9933 in my LO 7.3+. I see an improvement over time, this was never OK, was up to 5223 before. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107830 Bug 107830 depends on bug 130487, which changed state. Bug 130487 Summary: PARAGRAPH DIALOG: Indent setting "Automatic" get's lost in a docx-file https://bugs.documentfoundation.org/show_bug.cgi?id=130487 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113546] [META] Paragraph indent bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113546 Bug 113546 depends on bug 130487, which changed state. Bug 130487 Summary: PARAGRAPH DIALOG: Indent setting "Automatic" get's lost in a docx-file https://bugs.documentfoundation.org/show_bug.cgi?id=130487 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107642] [META] Paragraph dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107642 Bug 107642 depends on bug 130487, which changed state. Bug 130487 Summary: PARAGRAPH DIALOG: Indent setting "Automatic" get's lost in a docx-file https://bugs.documentfoundation.org/show_bug.cgi?id=130487 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
