[Libreoffice-bugs] [Bug 151243] New: Setup auto run Pyspark notebook from Alteryx
https://bugs.documentfoundation.org/show_bug.cgi?id=151243 Bug ID: 151243 Summary: Setup auto run Pyspark notebook from Alteryx Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pavanind...@gmail.com Description: I need to schedule Pyspark notebook to run using Alteryx. There seems to be Python and Apache spark code options available in Alteryx but no Pyspark. Can anyone tell me how to set up automatic Pyspark-notebook run from Alteryx? https://hkrtrainings.com/alteryx-training Actual Results: unknown Expected Results: no Reproducible: Always User Profile Reset: No Additional Info: please resolve -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151242] New: to much clutter
https://bugs.documentfoundation.org/show_bug.cgi?id=151242 Bug ID: 151242 Summary: to much clutter Product: LibreOffice Version: 6.4.5.2 release Hardware: x86-64 (AMD64) URL: https://www.libreoffice.org/ OS: Windows (All) Status: UNCONFIRMED Keywords: accessibility Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: siddiquihamza...@gmail.com Created attachment 182744 --> https://bugs.documentfoundation.org/attachment.cgi?id=182744=edit the clutter -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151241] New: to much clutter
https://bugs.documentfoundation.org/show_bug.cgi?id=151241 Bug ID: 151241 Summary: to much clutter Product: LibreOffice Version: 7.0.4.2 release Hardware: x86-64 (AMD64) URL: https://www.libreoffice.org/ OS: Windows (All) Status: UNCONFIRMED Keywords: difficultyBeginner Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: siddiquihamza...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151240] New: to much clutter
https://bugs.documentfoundation.org/show_bug.cgi?id=151240 Bug ID: 151240 Summary: to much clutter Product: LibreOffice Version: 7.2.0.1 rc Hardware: x86-64 (AMD64) URL: https://www.libreoffice.org/ OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: siddiquihamza...@gmail.com Created attachment 182743 --> https://bugs.documentfoundation.org/attachment.cgi?id=182743=edit the clutter -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151182] Calc crash when cut-paste and drag cell
https://bugs.documentfoundation.org/show_bug.cgi?id=151182 --- Comment #7 from Tyr Antilles --- Thank you very much. :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46917] FORMATTING: Inserted 'Tables' in presentation respond poorly for configuration changes
https://bugs.documentfoundation.org/show_bug.cgi?id=46917 --- Comment #16 from pharmankur --- Dear QA team, Thanks for reporting. I have , 1) Tried with the test file attached already in this bug report. --- All issues were resolved. 2) Created large tables like 20 X 20 and tried to edit line colors, text fonts alignments and background colors etc. --- I found it becomes little slow and takes some time to respond, but finally it works and does the edits as desired. Tested with my version of LO -- Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-GB Ubuntu package version: 1:7.3.6~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded Also as requested, wanted to select status RESOLVED-WORKSFORME, but did not find this option in status dropdown ( It has only RESOLVED ). So leaving it untouched. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150743] [Editing] Horizontal line will disappear while setting position and height through sidebar if "Keep ratio" is set.
https://bugs.documentfoundation.org/show_bug.cgi?id=150743 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 150970] FILEOPEN DOCX padding of text box of shape is wrong for vertical text directions
https://bugs.documentfoundation.org/show_bug.cgi?id=150970 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 151236] Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151236] Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139251] Black text shadow not rendered correctly in exported gif and png files.
https://bugs.documentfoundation.org/show_bug.cgi?id=139251 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139251] Black text shadow not rendered correctly in exported gif and png files.
https://bugs.documentfoundation.org/show_bug.cgi?id=139251 --- Comment #10 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147720] Bullet points are very confusing to use and bug filled.
https://bugs.documentfoundation.org/show_bug.cgi?id=147720 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 147720] Bullet points are very confusing to use and bug filled.
https://bugs.documentfoundation.org/show_bug.cgi?id=147720 --- Comment #3 from QA Administrators --- Dear 073.josephb, 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 147709] Libreoffice freezes on Macbook Air M1, must be restarted with force close
https://bugs.documentfoundation.org/show_bug.cgi?id=147709 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 147709] Libreoffice freezes on Macbook Air M1, must be restarted with force close
https://bugs.documentfoundation.org/show_bug.cgi?id=147709 --- Comment #10 from QA Administrators --- Dear adrienne, 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 147518] Impossible to start Libreoffice 7.3.0.3 in any mode
https://bugs.documentfoundation.org/show_bug.cgi?id=147518 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 147518] Impossible to start Libreoffice 7.3.0.3 in any mode
https://bugs.documentfoundation.org/show_bug.cgi?id=147518 --- Comment #6 from QA Administrators --- Dear Davide Soresinetti, 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 147474] Math equations are converted to images
https://bugs.documentfoundation.org/show_bug.cgi?id=147474 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 147259] Sheet tab color
https://bugs.documentfoundation.org/show_bug.cgi?id=147259 --- Comment #3 from QA Administrators --- Dear René Dionne, 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 147474] Math equations are converted to images
https://bugs.documentfoundation.org/show_bug.cgi?id=147474 --- Comment #3 from QA Administrators --- Dear amanita+LIBREOFFICE, 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 145286] All LibreOffice applications freeze, "Not Responding", Base constantly writing to lock file
https://bugs.documentfoundation.org/show_bug.cgi?id=145286 --- Comment #5 from QA Administrators --- Dear David Yerger, 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 92873] UI Preview of 3D object doesn't resize w/ the dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=92873 --- Comment #8 from QA Administrators --- Dear Katarina Behrens (Inactive), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96614] Not possible to re-anchor the picture with footer involved
https://bugs.documentfoundation.org/show_bug.cgi?id=96614 --- Comment #11 from QA Administrators --- Dear szotsaki, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92595] Can't change paragraph spacing after printing preview on Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=92595 --- Comment #4 from QA Administrators --- Dear Damiano, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90273] Formatting Regression: Filling background page image can't be linked anymore, only embedded
https://bugs.documentfoundation.org/show_bug.cgi?id=90273 --- Comment #13 from QA Administrators --- Dear João Paulo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89699] Image anchored as 'as character' has unnecessary space above it
https://bugs.documentfoundation.org/show_bug.cgi?id=89699 --- 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81956] FILEOPEN: Z-ordering of shape not preserved properly for docx file.
https://bugs.documentfoundation.org/show_bug.cgi?id=81956 --- Comment #8 from QA Administrators --- Dear Sushil Shinde, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 79538] Calc: Images move when printing or exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=79538 --- Comment #25 from QA Administrators --- Dear Sašo Smolej, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 54768] Asking to restore image to original size gets wrong size when the image is clipped
https://bugs.documentfoundation.org/show_bug.cgi?id=54768 --- Comment #9 from QA Administrators --- Dear sergio.callegari, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49881] VML Autoshapes created in MS Office not imported at all in LO 3.5.3, FILEOPEN, FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=49881 --- Comment #13 from QA Administrators --- Dear Rahul Singh, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46917] FORMATTING: Inserted 'Tables' in presentation respond poorly for configuration changes
https://bugs.documentfoundation.org/show_bug.cgi?id=46917 --- Comment #15 from QA Administrators --- Dear pharmankur, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43364] Export to Hybrid PDF with "Always save as" option other than an ODF Text Document zip archive errors when reopening in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=43364 --- Comment #11 from QA Administrators --- Dear Edward Sanford Sutton, III, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136743] Toolbars have different height, cause the document area to jump
https://bugs.documentfoundation.org/show_bug.cgi?id=136743 --- Comment #4 from QA Administrators --- Dear Maxim Monastirsky, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136968] Pasting Writer's Table Content Creates Duplicated Linked Number in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=136968 --- Comment #3 from QA Administrators --- Dear Rizal Muttaqin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136738] Textflow break has an odd state (not checked/nor unchecked)/ and disabled (ODT)
https://bugs.documentfoundation.org/show_bug.cgi?id=136738 --- Comment #3 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135917] slow response after closing document if ftp document is in history
https://bugs.documentfoundation.org/show_bug.cgi?id=135917 --- Comment #2 from QA Administrators --- Dear Andrej, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135176] PDF Export - CALC - Push Button - Font Size of Push Button Label is modified ( increase )
https://bugs.documentfoundation.org/show_bug.cgi?id=135176 --- Comment #5 from QA Administrators --- Dear Hans-Werner, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133899] VIEWING: help lines do not appear when moving 3D objects in a group
https://bugs.documentfoundation.org/show_bug.cgi?id=133899 --- Comment #5 from QA Administrators --- Dear mat.venturini, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132139] Tabbed User Interface Hamburger menu outside of screen when window is maximized
https://bugs.documentfoundation.org/show_bug.cgi?id=132139 --- Comment #5 from QA Administrators --- Dear intelati26, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132194] Draw 3D Effects icon does not open 3D Effects dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=132194 --- Comment #24 from QA Administrators --- Dear PeeWee, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131994] FILEOPEN DOCX VML textbox is not rotated
https://bugs.documentfoundation.org/show_bug.cgi?id=131994 --- Comment #3 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131577] Texture filter in 3D-Effects dialog does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=131577 --- Comment #7 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131604] 3D rotation object with end angle has curious fill for front polygon
https://bugs.documentfoundation.org/show_bug.cgi?id=131604 --- Comment #3 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126256] FORMATTING, FILEOPEN: Plain text document in (codepage 437) with commercial font displays incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=126256 --- Comment #22 from QA Administrators --- Dear robert, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124775] Pasting 3D object to scene also inserts it back to its original position
https://bugs.documentfoundation.org/show_bug.cgi?id=124775 --- Comment #2 from QA Administrators --- Dear Buovjaga, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108994] FILESAVE: XLS: Shapes lost after Roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=108994 --- Comment #8 from QA Administrators --- Dear yoshioka digo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108763] non visible items in menu Styles in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=108763 --- Comment #12 from QA Administrators --- Dear Roman Kuznetsov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107384] Ctrl+V inserts into a locked layer
https://bugs.documentfoundation.org/show_bug.cgi?id=107384 --- Comment #15 from QA Administrators --- Dear prospero78su, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104435] FILEOPEN: DOCX: vertical text is cropped
https://bugs.documentfoundation.org/show_bug.cgi?id=104435 --- Comment #9 from QA Administrators --- Dear Ilario Gottardello, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
LibreOffice Extension - description of extension not updated
Hello! I uploaded the latest English Dictionary .oxt: https://extensions.libreoffice.org/extensions/english-dictionaries But the admin who approved it, forgot to approve the description changes: *Description** ** **English dictionaries for LibreOffice 4.0+.** ** **It includes:** **- en_AU (Australian) (updated: 2020-12-07)** **- en_CA (Canadian) (updated: 2020-12-07)** **- en_GB (British) (updated: 2022-09-01)** **- en_US (American) (updated: 2020-12-07)** **- en_ZA (South African) (updated: 2022-08-01)* The British should say: “2022-10-01” instead of “2022-09-01”. In the morning, I was at the infra IRC channel on Libera, but everyone was away. Can someone approve the change? Thanks! Kind regards, >Marco A.G.Pinto ---
[Libreoffice-bugs] [Bug 151239] New: image stretched upon file reopening
https://bugs.documentfoundation.org/show_bug.cgi?id=151239 Bug ID: 151239 Summary: image stretched upon file reopening Product: LibreOffice Version: 7.3.2.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tinom...@yahoo.com Description: LibreOffice was not responding, then after a force quit all the images on my 50-page drawing had become stretched. Can this be prevented in the future? Actual Results: not sure if i can reproduce, just reporting what happened. Expected Results: n/a Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: DrawingDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51203] Hyperlink Field Type in Base
https://bugs.documentfoundation.org/show_bug.cgi?id=51203 mhonline changed: What|Removed |Added CC||mh...@gmx.net --- Comment #15 from mhonline --- (In reply to Alex Thurgood from comment #14) > *** Bug 151125 has been marked as a duplicate of this bug. *** Hi @Alex: you said it, "4. Some sort of hard-coded implementation in Base for special treatment of a VARCHAR data type" Option (3) would seem most likely IMO. I still do not get, where the problem lays: Any text-field can hold the URL, there is no need for an extra data-type, the function must be part of the forms, in which the control of this field has the property of being a control of type Hyperlink, absolutly similar to the behavior of hyperlinks in word or calc. so, what is the problem? martin -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148806] FILEOPEN: Event-Driven Macros don't enable in DOCM, or after round-tripping in DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=148806
--- Comment #13 from Justin L ---
DOCX: in terms of sending DOCUMENT OPEN to VBA, all the plumbing looks to be in
place. The only problem is an exception in
mxVbaEvents.set( ooo::vba::createVBAUnoAPIServiceWithArgs(
mpDocShell, "com.sun.star.script.vba.VBATextEventProcessor" , aArgs )
because no hasServiceName("com.sun.star.script.vba.VBATextEventProcessor")
Somehow we need this?
extern "C" SAL_DLLPUBLIC_EXPORT css::uno::XInterface*
Writer_SwVbaEventsHelper_get_implementation(
css::uno::XComponentContext* context, css::uno::Sequence
const& args)
{
return cppu::acquire(new SwVbaEventsHelper(args, context));
}
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151238] New: Windows 11 Scroll bar arrows hidden when set visible
https://bugs.documentfoundation.org/show_bug.cgi?id=151238 Bug ID: 151238 Summary: Windows 11 Scroll bar arrows hidden when set visible Product: LibreOffice Version: 6.2.8.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: saywel...@gmail.com Created attachment 182742 --> https://bugs.documentfoundation.org/attachment.cgi?id=182742=edit Animated gif showing visibility of arrow In Windows 11 I have set `Start menu > Settings > Accessibility > Visual Effects > Always show scroll bars` to ON. Except for LibreOffice, all apps, including Edge, Word 2010, Thunderbird, & Firefox, show the up/down arrows on the scroll bar for scrolling a line at a time. On all programs within and all versions of LibreOffice I have installed 6.2.8.2 - 7.4.0.3 the arrows are no longer visible unless the arrows themselves are hovered over. You have to know exactly where the arrows because hovering elsewhere on the scrollbar does not show them. Expectation: The arrows are always visible when "Always show scroll bars" is set to on. Also see https://ask.libreoffice.org/t/disappearing-scrollbar-arrows/82321 Version: 7.4.0.3 (x64) / LibreOffice Community Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Rafael Lima changed: What|Removed |Added Depends on||151237 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151237 [Bug 151237] In the Properties sidebar the Style dropdown disappears upon clicking the down arrow (kf5 only) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151237] In the Properties sidebar the Style dropdown disappears upon clicking the down arrow (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=151237 Rafael Lima changed: What|Removed |Added Blocks||102495 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE VCL backend bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151237] In the Properties sidebar the Style dropdown disappears upon clicking the down arrow (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=151237 --- Comment #1 from Rafael Lima --- Created attachment 182741 --> https://bugs.documentfoundation.org/attachment.cgi?id=182741=edit Video in gtk3 (works fine) Here is the same thing in gtk3. It works as expected. I would also note that in kf5 the down arrow should be more visible, as it is in gen and gtk3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151237] New: In the Properties sidebar the Style dropdown disappears upon clicking the down arrow (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=151237 Bug ID: 151237 Summary: In the Properties sidebar the Style dropdown disappears upon clicking the down arrow (kf5 only) Product: LibreOffice Version: 7.3.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 182740 --> https://bugs.documentfoundation.org/attachment.cgi?id=182740=edit Video showing the problem In the "Properties" sidebar there is a Style section with a dropdown where the user can select one of the available cell styles. Note each entry in this dropdown has a down arrow to the right that is supposed to open a context menu with two options. In kf5 clicking the down arrow makes the dropdown unexpectedly disappear. In gen and gtk3 it works as expected. See the attached videos for more information. System info Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148806] FILEOPEN: Event-Driven Macros don't enable in DOCM, or after round-tripping in DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=148806 --- Comment #12 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/8253b8d6f1efb7fc3e2928d543c21a79c2cdc13f tdf#148806 docm: fix vba macro events without ScriptCodes It will be available in 7.5.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 148806] FILEOPEN: Event-Driven Macros don't enable in DOCM, or after round-tripping in DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=148806 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151236] Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 --- Comment #4 from Cesar Izurieta --- Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: es-EC (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: filter/source
filter/source/msfilter/msvbahelper.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 8253b8d6f1efb7fc3e2928d543c21a79c2cdc13f
Author: Justin Luth
AuthorDate: Thu Sep 29 15:27:47 2022 -0400
Commit: Justin Luth
CommitDate: Fri Sep 30 00:10:41 2022 +0200
tdf#148806 docm: fix vba macro events without ScriptCodes
Prior to this, none of the DOCM ActiveX macros were called.
Now, just like magic, it all works.
Already broken at commit c5fc57de562850a7d2f708e3936296d24677012d
Author: npower Developer on Tue Mar 2 15:04:15 2010 +
npower14miscfixes: #i109706# move back msvbahelper to the filter module
Change-Id: I25b25850b12609e5e00dd4bd5189a734abcbddd6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140750
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/filter/source/msfilter/msvbahelper.cxx
b/filter/source/msfilter/msvbahelper.cxx
index f43b121ecb67..95144adb6094 100644
--- a/filter/source/msfilter/msvbahelper.cxx
+++ b/filter/source/msfilter/msvbahelper.cxx
@@ -243,7 +243,7 @@ static void parseMacro( const OUString& sMacro, OUString&
sContainer, OUString&
{
sProcedure = sMacro.copy( nMacroDot + 1 );
-sal_Int32 nContainerDot = sMacro.lastIndexOf( '.', nMacroDot - 1 );
+const sal_Int32 nContainerDot = sMacro.lastIndexOf('.', nMacroDot);
if ( nContainerDot != -1 )
{
sModule = sMacro.copy( nContainerDot + 1, nMacroDot -
nContainerDot - 1 );
[Libreoffice-bugs] [Bug 151236] Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 --- Comment #3 from Cesar Izurieta --- Created attachment 182739 --> https://bugs.documentfoundation.org/attachment.cgi?id=182739=edit copy-paste-problem Original content at the top, next pasted with ctrl-v and then the dialog for paste special -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135987] FILEOPEN XLSX: Check boxes get lost when loading
https://bugs.documentfoundation.org/show_bug.cgi?id=135987 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |3610| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113610] FILEOPEN: checkboxes disappear on roundtrip as xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=113610 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |5987| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151236] Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 --- Comment #2 from Rafael Lima --- Sorry... I missed the information that you're using Gnome on openSuse. Anyways, can you share a screenshot of the problem? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151236] Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- Paste Special (Ctrl+Shift+V) should open a dialog in which you can choose what elements will be pasted, including formats and formulas. Can you share a screenshot of what you're seeing? Also, what is your OS and LO version? Copy and paste the info in Help - About LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143302] Detect switches between dark and light GTK themes and automatically switch to the corresponding icon set when available
https://bugs.documentfoundation.org/show_bug.cgi?id=143302 Jeff Fortin Tam changed: What|Removed |Added Blocks||143344 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143344 [Bug 143344] [META] Linux Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=143344 Jeff Fortin Tam changed: What|Removed |Added Depends on||143302 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143302 [Bug 143302] Detect switches between dark and light GTK themes and automatically switch to the corresponding icon set when available -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151227] LibreOffice Impress text box sizes changed
https://bugs.documentfoundation.org/show_bug.cgi?id=151227 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Rafael Lima --- Can you provide a sample file that is affected when comparing LO 7.3 and 7.4? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: icon-themes/sifr icon-themes/sifr_dark icon-themes/sifr_dark_svg icon-themes/sifr_svg
dev/null |binary icon-themes/sifr/cmd/32/dbclearquery.png |binary icon-themes/sifr/cmd/32/dbnewquery.png |binary icon-themes/sifr/cmd/32/dbnewqueryautopilot.png |binary icon-themes/sifr/cmd/32/dbnewreport.png |binary icon-themes/sifr/cmd/32/dbnewreportautopilot.png |binary icon-themes/sifr/cmd/32/dbquerydelete.png|binary icon-themes/sifr/cmd/32/dbqueryedit.png |binary icon-themes/sifr/cmd/32/dbquerypropertiesdialog.png |binary icon-themes/sifr/cmd/32/dbqueryrename.png|binary icon-themes/sifr/cmd/32/dbreportdelete.png |binary icon-themes/sifr/cmd/32/dbreportedit.png |binary icon-themes/sifr/cmd/32/dbreportrename.png |binary icon-themes/sifr/cmd/32/dbviewqueries.png|binary icon-themes/sifr/cmd/32/dbviewreports.png|binary icon-themes/sifr/cmd/32/definedbname.png |binary icon-themes/sifr/cmd/32/emojicontrol.png |binary icon-themes/sifr/cmd/32/executereport.png|binary icon-themes/sifr/cmd/32/freeline.png |binary icon-themes/sifr/cmd/32/freeline_unfilled.png|binary icon-themes/sifr/cmd/32/freezepanes.png |binary icon-themes/sifr/cmd/32/freezepanesfirstcolumn.png |binary icon-themes/sifr/cmd/32/freezepanesfirstrow.png |binary icon-themes/sifr/cmd/32/gotopage.png |binary icon-themes/sifr/cmd/32/leftpanedraw.png |binary icon-themes/sifr/cmd/32/reportnavigator.png |binary icon-themes/sifr/cmd/32/viewrowcolumnheaders.png |binary icon-themes/sifr/cmd/lc_dbclearquery.png |binary icon-themes/sifr/cmd/lc_dbnewquery.png |binary icon-themes/sifr/cmd/lc_dbnewqueryautopilot.png |binary icon-themes/sifr/cmd/lc_dbnewreport.png |binary icon-themes/sifr/cmd/lc_dbnewreportautopilot.png |binary icon-themes/sifr/cmd/lc_dbquerydelete.png|binary icon-themes/sifr/cmd/lc_dbqueryedit.png |binary icon-themes/sifr/cmd/lc_dbquerypropertiesdialog.png |binary icon-themes/sifr/cmd/lc_dbqueryrename.png|binary icon-themes/sifr/cmd/lc_dbreportdelete.png |binary icon-themes/sifr/cmd/lc_dbreportedit.png |binary icon-themes/sifr/cmd/lc_dbreportrename.png |binary icon-themes/sifr/cmd/lc_dbviewqueries.png|binary icon-themes/sifr/cmd/lc_dbviewreports.png|binary icon-themes/sifr/cmd/lc_definedbname.png |binary icon-themes/sifr/cmd/lc_documentation.png|binary icon-themes/sifr/cmd/lc_emojicontrol.png |binary icon-themes/sifr/cmd/lc_executereport.png|binary icon-themes/sifr/cmd/lc_freeline.png |binary icon-themes/sifr/cmd/lc_freeline_unfilled.png|binary icon-themes/sifr/cmd/lc_freezepanes.png |binary icon-themes/sifr/cmd/lc_freezepanesfirstcolumn.png |binary icon-themes/sifr/cmd/lc_freezepanesfirstrow.png |binary icon-themes/sifr/cmd/lc_gotopage.png |binary icon-themes/sifr/cmd/lc_leftpanedraw.png |binary icon-themes/sifr/cmd/lc_reportnavigator.png |binary icon-themes/sifr/cmd/lc_viewrowcolumnheaders.png |binary icon-themes/sifr/cmd/sc_dbclearquery.png |binary icon-themes/sifr/cmd/sc_dbnewfolder.png |binary icon-themes/sifr/cmd/sc_dbnewquery.png |binary icon-themes/sifr/cmd/sc_dbnewqueryautopilot.png |binary icon-themes/sifr/cmd/sc_dbnewreport.png |binary icon-themes/sifr/cmd/sc_dbnewreportautopilot.png |binary icon-themes/sifr/cmd/sc_dbquerydelete.png|binary icon-themes/sifr/cmd/sc_dbqueryedit.png |binary icon-themes/sifr/cmd/sc_dbquerypropertiesdialog.png |binary icon-themes/sifr/cmd/sc_dbqueryrename.png|binary icon-themes/sifr/cmd/sc_dbreportdelete.png |binary icon-themes/sifr/cmd/sc_dbreportedit.png |binary icon-themes/sifr/cmd/sc_dbreportrename.png |binary icon-themes/sifr/cmd/sc_dbviewqueries.png|binary icon-themes/sifr/cmd/sc_dbviewreports.png|binary icon-themes/sifr/cmd/sc_definedbname.png |binary icon-themes/sifr/cmd/sc_emojicontrol.png |binary
[Libreoffice-bugs] [Bug 151232] Lines in Special Characters dialog do not respect dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151232 --- Comment #2 from V Stuart Foote --- Created attachment 182738 --> https://bugs.documentfoundation.org/attachment.cgi?id=182738=edit SCD on Windows in Dark color theme -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150915] [META] Windows Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=150915 V Stuart Foote changed: What|Removed |Added Depends on||151232 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151232 [Bug 151232] Lines in Special Characters dialog do not respect dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151232] Lines in Special Characters dialog do not respect dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151232 V Stuart Foote changed: What|Removed |Added Blocks||150915 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150915 [Bug 150915] [META] Windows Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151233] Setting color of left border not working
https://bugs.documentfoundation.org/show_bug.cgi?id=151233 Rafael Lima changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #1 from Rafael Lima --- I'm not sure this is a bug, or if this is the way the function is designed to work. The reason is, when you try to apply border to a range, the right edge is not affected when it already has a border. However, considering that the command is called "Outer border and all inner lines", I understand why users would expect that all edges (including the right outer borders) would be formatted. Let's hear from the UX team. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151232] Lines in Special Characters dialog do not respect dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151232 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from V Stuart Foote --- Identical result for Windows 10 in Dark color theme mode, the grid lines in the SCD remain dark. But pretty trivial as they are visible... Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 0d3dd0aa54ad792f91d0905f3d46c13df3512d89 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151233] Setting color of left border not working
https://bugs.documentfoundation.org/show_bug.cgi?id=151233 Rafael Lima changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #1 from Rafael Lima --- I'm not sure this is a bug, or if this is the way the function is designed to work. The reason is, when you try to apply border to a range, the right edge is not affected when it already has a border. However, considering that the command is called "Outer border and all inner lines", I understand why users would expect that all edges (including the right outer borders) would be formatted. Let's hear from the UX team. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151220] LibreOffice Window Appears Extremely Small When Opened
https://bugs.documentfoundation.org/show_bug.cgi?id=151220 Rafael Lima changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Rafael Lima --- This is a duplicate of bug 150856. It affects only KDE users. A fix was pushed for the 7.4.2 release. *** This bug has been marked as a duplicate of bug 150856 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113610] FILEOPEN: checkboxes disappear on roundtrip as xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=113610 m.a.riosv changed: What|Removed |Added CC||rev.joehea...@gmail.com --- Comment #9 from m.a.riosv --- *** Bug 151235 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 151235] FILESAVE: Linked Cells to Checkboxes are lost on saving to XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=151235 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |DUPLICATE --- Comment #1 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 113610 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138805] LO label printer TERRIBLE
https://bugs.documentfoundation.org/show_bug.cgi?id=138805 --- Comment #4 from Buovjaga --- (In reply to Michael Potts from comment #3) > Per the request for more information: I wasn't so much reporting a bug as > suggesting that the methodology for LO's labels -- unlike SO MUCH of the > rest of this VERY EXCELLENT suite -- is needlessly complex and impossible to > explain to a normal clerical worker. I have my own How2 cheat sheet that > contains 21 steps! I stand by my original comment: > " TAKE A LOOK AT WORD PERFECT FOR THE WAY IT OUGHT TO WORK. " >I am unaware of any further "information or data" that I can provide, but > as a lover of the LO program and ideal, I would be happy to correspond with > any human addressing this needlessly complex method. Sure, I was human in April this year and I'm still human :) What I'm saying is that at the moment your report is not actionable as it is too vague, while we already have dozens of reports about labels. Of course it would be a bit tedious for you to review the existing reports, but I think you are the only one who could correlate them with what you have in mind. -- You are receiving this mail because: You are the assignee for the bug.
Re: Libreoffice issue reporting
On 29.9.2022 20.36, Paolo Barattini wrote: HI I cannot find a way to report an issue. I tried to find the way but I bounce between pages, sites, wikis etc. here my issue. A colleague sent me a file in ODT Libreoffice vesion 7.2 I am using the latest 7.4 version . The file contained ten images separated by returns (empty lines in other words). I could see only one image in a one page file. Then by try and error, I realised that the ten images well all superimposed one upon the other. That’s all Please find attached the file You can report it here after creating an account in our Bugzilla: https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice=guided Ilmari
[Libreoffice-bugs] [Bug 151236] New: Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 Bug ID: 151236 Summary: Copy-Paste only transfers plain-text Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ce...@ecuarock.net When copying and pasting inside Calc I can only get it to paste plain text, so no formatting or formulas are copied. Using paste-special only two options are presented: Unformatted text, Use text import dialog. This has been present for a long time through various versions, it's not a new issue. I'm using Gnome (tried with and without gpaste) on openSUSE Tumbleweed Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108226] [META] PPTX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108226 Bug 108226 depends on bug 149969, which changed state. Bug 149969 Summary: FILEOPEN PPTX: video stops after one iteration instead of playing in loop https://bugs.documentfoundation.org/show_bug.cgi?id=149969 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101522] [META] Media playback bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101522 Bug 101522 depends on bug 149969, which changed state. Bug 149969 Summary: FILEOPEN PPTX: video stops after one iteration instead of playing in loop https://bugs.documentfoundation.org/show_bug.cgi?id=149969 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151235] New: FILESAVE: Linked Cells to Checkboxes are lost on saving to XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=151235 Bug ID: 151235 Summary: FILESAVE: Linked Cells to Checkboxes are lost on saving to XLSX Product: LibreOffice Version: 7.3.6.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rev.joehea...@gmail.com Description: Check boxes that have a linked cell, and also have formatting (coloured background and coloured border) are lost when saving to a XLSX file. Steps to Reproduce: 1. Create a Check box in Calc linked to a Cell 2. Provide some formatting to the checkbox (e.g. coloured background, border, etc.) 3. Save to XLSX file Actual Results: The Check box is not linked to any cell All of the formatting of the checkbox is lost in the XLSX file. Expected Results: The linked cell and formatting should be retained. Reproducible: Always User Profile Reset: No Additional Info: The XLSX file when opened in Excel should have reproduced the checkbox as displayed in Calc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151234] Formatting Marks: Spurious letters introduced with formatting marks toggled on
https://bugs.documentfoundation.org/show_bug.cgi?id=151234 --- Comment #1 from Telesto --- Created attachment 182737 --> https://bugs.documentfoundation.org/attachment.cgi?id=182737=edit Example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151234] New: Formatting Marks: Spurious letters introduced with formatting marks toggled on
https://bugs.documentfoundation.org/show_bug.cgi?id=151234 Bug ID: 151234 Summary: Formatting Marks: Spurious letters introduced with formatting marks toggled on Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Formatting Marks: Spurious letters introduced with formatting marks toggled on Steps to Reproduce: 1. Open the attached file 2. Search for the black 'hello' [part of helloehello] 3. Toggle formatting marks off: name the same part shows hello hello (expected) 4. Turn formatting marks ON again 5. Select helloehello 6. Press CTRL+U -> Result: helloehelloe 7. Press CTRL+Z -> e at the end still visible Actual Results: Currently Master Build: helloehello With older builds the expected bullet for 'space' was missing with Formatting marks toggled on between "helloehello". But no spurious character Expected Results: Formatting marking indicating a space Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d3050ff4a1355f7ebd3d4e7ddc8fb64f2b8894dd CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151211] EDITING paste unformatted text, puts everything after column N in N
https://bugs.documentfoundation.org/show_bug.cgi?id=151211 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Status|NEW |ASSIGNED --- Comment #6 from Eike Rathke --- So, the shortest reproducer of the above data is (I hope the tab between those two is preserved here) 5'9"170 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151233] New: Setting color of left border not working
https://bugs.documentfoundation.org/show_bug.cgi?id=151233 Bug ID: 151233 Summary: Setting color of left border not working Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aguibou.ba...@gmail.com Steps to reproduce: - Select all the cells - Select white in border color picker menu icon - Apply color to all the borders using "Outer border and all inner lines" option - Select another color (e.g. blue) from the border color picker menu icon - Select only a few colonms e.g. one or two or three columns - Apply color (e.g. previously selected blue) to the select colomns the borders using "Outer border and all inner lines" option Expected outcome: - all the borders are colored (e.g. all outer and inner borders are blue) Observed outcome: - the left outer border is not colored. gDrive link to screen record showing the issue described above : https://drive.google.com/file/d/1pK2JJ8mjANjLGyJlAC0YmZK3DXwyT2Z5/view?usp=sharing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33201] UI: Highlight (not select) current row and column in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=33201 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #53 from Rafael Lima --- +1 to this request I have always felt the need for this feature when working with very long tables. I was about to report an enhancement request about this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=42082 Bug 42082 depends on bug 134655, which changed state. Bug 134655 Summary: MacOS: Square characters in style dialog on CKB https://bugs.documentfoundation.org/show_bug.cgi?id=134655 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134655] MacOS: Square characters in style dialog on CKB
https://bugs.documentfoundation.org/show_bug.cgi?id=134655 خالد حسني changed: What|Removed |Added Resolution|--- |DUPLICATE CC||kha...@aliftype.com Status|NEW |RESOLVED --- Comment #15 from خالد حسني --- *** This bug has been marked as a duplicate of bug 73494 *** -- You are receiving this mail because: You are the assignee for the bug.
Re: Libreoffice issue reporting
On 9/29/2022 10:36 AM, Paolo Barattini wrote: HI I cannot find a way to report an issue. I tried to find the way but I bounce between pages, sites, wikis etc. here my issue. A colleague sent me a file in ODT Libreoffice vesion 7.2 I am using the latest 7.4 version . Just downloaded your attached .odt file and opened it in Writer 7.3 and 7.4.1 (on Windows 10) just fine... R
[Libreoffice-bugs] [Bug 151223] let's drop "bold" and "italic", and assign CRTL+B to "strong", CRTL+i to emphasis
https://bugs.documentfoundation.org/show_bug.cgi?id=151223 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Keywords||needsUXEval Blocks||108816 --- Comment #1 from V Stuart Foote --- Not seeing an advantage to the pain this would cause. There are 4 UNO commands in this context--but there are other DF that have not corresponding ODF appropriate styles defined. .uno:Bold --> this is the +b shortcut (localized and customizable) .uno:Italic --> this is the +i shortcut (localized and customizable) .uno:EmphasisCharStyle .uno:StrongEmphasisCharStyle The first two are resident on the 'Formatting' toolbar and need the .uno:ResetAttributes assigned to +M to clear direct formatting with selection, or toolbar button action to directly toggle. The second two are resident on the 'Formatting (Styles)' toolbar. Along with the .uno:DefaultCharStyle which allows reset of selection to paragraph's default styles. Issues come in the resulting ODF archive (the actual document), direct formatting as Bold or Italic is recorded directly into the text runs (within T1, T2, T3... notations) in the content.xml While when the character style (Strong or Emphasis) is applied, those is defined as a style (in style.xml) that is then applied to the text runs (either as 'Standard' for the paragraph, or integrated with T1, T2, T3... direct formatting spans). Not much of an issue with a document prepared purely using styles--but major issues with import/export filtering to non-ODF formats and horrible fidelity issues for OOXML interoperability with MS Office users. So, if *you* need it--customize your Keyboard and Toolbar (Tools -> Customize) and assign the CharStyle commands as you need. But IMHO I don't think it would be helpful to change the action assignments for the shortcuts by default to be the CharStyle. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108816 [Bug 108816] [META] Writer toolbar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151223] let's drop "bold" and "italic", and assign CRTL+B to "strong", CRTL+i to emphasis
https://bugs.documentfoundation.org/show_bug.cgi?id=151223 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Keywords||needsUXEval Blocks||108816 --- Comment #1 from V Stuart Foote --- Not seeing an advantage to the pain this would cause. There are 4 UNO commands in this context--but there are other DF that have not corresponding ODF appropriate styles defined. .uno:Bold --> this is the +b shortcut (localized and customizable) .uno:Italic --> this is the +i shortcut (localized and customizable) .uno:EmphasisCharStyle .uno:StrongEmphasisCharStyle The first two are resident on the 'Formatting' toolbar and need the .uno:ResetAttributes assigned to +M to clear direct formatting with selection, or toolbar button action to directly toggle. The second two are resident on the 'Formatting (Styles)' toolbar. Along with the .uno:DefaultCharStyle which allows reset of selection to paragraph's default styles. Issues come in the resulting ODF archive (the actual document), direct formatting as Bold or Italic is recorded directly into the text runs (within T1, T2, T3... notations) in the content.xml While when the character style (Strong or Emphasis) is applied, those is defined as a style (in style.xml) that is then applied to the text runs (either as 'Standard' for the paragraph, or integrated with T1, T2, T3... direct formatting spans). Not much of an issue with a document prepared purely using styles--but major issues with import/export filtering to non-ODF formats and horrible fidelity issues for OOXML interoperability with MS Office users. So, if *you* need it--customize your Keyboard and Toolbar (Tools -> Customize) and assign the CharStyle commands as you need. But IMHO I don't think it would be helpful to change the action assignments for the shortcuts by default to be the CharStyle. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108816 [Bug 108816] [META] Writer toolbar bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 108816] [META] Writer toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108816 V Stuart Foote changed: What|Removed |Added Depends on||151223 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151223 [Bug 151223] let's drop "bold" and "italic", and assign CRTL+B to "strong", CRTL+i to emphasis -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/core/edit/edglss.cxx | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
New commits:
commit 74e2d6dca536fe670b125ee9ac1192f45166db6e
Author: Noel Grandin
AuthorDate: Thu Sep 29 18:53:54 2022 +0200
Commit: Noel Grandin
CommitDate: Thu Sep 29 20:14:29 2022 +0200
use more SwPosition::Assign
part of the process of hiding the internals of SwPosition
Change-Id: I5744c861a9996f4d6d710acf73720aae2af6d9fa
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140744
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/edit/edglss.cxx b/sw/source/core/edit/edglss.cxx
index ee848a206d44..82a11ddbfe9c 100644
--- a/sw/source/core/edit/edglss.cxx
+++ b/sw/source/core/edit/edglss.cxx
@@ -104,16 +104,14 @@ sal_uInt16 SwEditShell::SaveGlossaryDoc( SwTextBlocks&
rBlock,
if( !pNd )
pNd = pContentNd;
-pCursor->GetPoint()->nNode = *pNd;
-if( pNd == pContentNd )
-pCursor->GetPoint()->nContent.Assign( pContentNd, 0 );
+pCursor->GetPoint()->Assign(*pNd);
pCursor->SetMark();
// then until the end of the Node array
-pCursor->GetPoint()->nNode =
pMyDoc->GetNodes().GetEndOfContent().GetIndex()-1;
+
pCursor->GetPoint()->Assign(pMyDoc->GetNodes().GetEndOfContent().GetIndex()-1);
pContentNd = pCursor->GetPointContentNode();
if( pContentNd )
-pCursor->GetPoint()->nContent.Assign( pContentNd,
pContentNd->Len() );
+pCursor->GetPoint()->SetContent( pContentNd->Len() );
OUString sBuf;
GetSelectedText( sBuf, ParaBreakType::ToOnlyCR );
@@ -133,10 +131,10 @@ sal_uInt16 SwEditShell::SaveGlossaryDoc( SwTextBlocks&
rBlock,
aCpyPam.SetMark();
// then until the end of the nodes array
-aCpyPam.GetPoint()->nNode =
pMyDoc->GetNodes().GetEndOfContent().GetIndex()-1;
+
aCpyPam.GetPoint()->Assign(pMyDoc->GetNodes().GetEndOfContent().GetIndex()-1);
pContentNd = aCpyPam.GetPointContentNode();
-aCpyPam.GetPoint()->nContent.Assign(
- pContentNd, pContentNd ? pContentNd->Len() : 0);
+if(pContentNd)
+aCpyPam.GetPoint()->SetContent( pContentNd->Len() );
aStt = pGDoc->GetNodes().GetEndOfExtras();
pContentNd = pGDoc->GetNodes().GoNext( );
@@ -229,17 +227,18 @@ bool SwEditShell::CopySelToDoc( SwDoc& rInsDoc )
// but we want to copy the table and the start node
before
// the first cell as well.
// tdf#133982 tables can be nested
+const SwNode* pNode = ()->GetNode();
while (SwTableNode const* pTableNode =
-
aPaM.Start()->GetNode().StartOfSectionNode()->FindTableNode())
+pNode->StartOfSectionNode()->FindTableNode())
{
-aPaM.Start()->nNode = *pTableNode;
+pNode = pTableNode;
}
while (SwSectionNode const* pSectionNode =
-
aPaM.Start()->GetNode().StartOfSectionNode()->FindSectionNode())
+pNode->StartOfSectionNode()->FindSectionNode())
{
-aPaM.Start()->nNode = *pSectionNode;
+pNode = pSectionNode;
}
-aPaM.Start()->nContent.Assign(nullptr, 0);
+aPaM.Start()->Assign(*pNode);
}
bRet =
GetDoc()->getIDocumentContentOperations().CopyRange( aPaM, aPos,
SwCopyFlags::CheckPosInFly)
|| bRet;
[Libreoffice-commits] core.git: sw/source
sw/source/core/doc/doctxm.cxx |1 -
sw/source/core/doc/extinput.cxx |6 +++---
2 files changed, 3 insertions(+), 4 deletions(-)
New commits:
commit ab4c74241ddc1a09c82d5ef240a170b0dc38b31c
Author: Noel Grandin
AuthorDate: Thu Sep 29 18:38:41 2022 +0200
Commit: Noel Grandin
CommitDate: Thu Sep 29 20:14:05 2022 +0200
use more SwPosition::SetContent
part of the process of hiding the internals of SwPosition
Change-Id: I0efae00beb920aac21fc5c10b663570cecc681bf
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140742
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/doc/doctxm.cxx b/sw/source/core/doc/doctxm.cxx
index 215f9e9fb5c9..36c197732cd9 100644
--- a/sw/source/core/doc/doctxm.cxx
+++ b/sw/source/core/doc/doctxm.cxx
@@ -1123,7 +1123,6 @@ void SwTOXBaseSection::Update(const SfxItemSet* pAttr,
aInsPos = *pFirstEmptyNd;
{
SwPaM aCorPam( *pFirstEmptyNd );
-aCorPam.GetPoint()->nContent.Assign( pFirstEmptyNd, 0 );
if( !aCorPam.Move( fnMoveForward ) )
aCorPam.Move( fnMoveBackward );
SwNodeIndex aEndIdx( aInsPos, 1 );
diff --git a/sw/source/core/doc/extinput.cxx b/sw/source/core/doc/extinput.cxx
index 9bdcb1d4648d..c8563facbd85 100644
--- a/sw/source/core/doc/extinput.cxx
+++ b/sw/source/core/doc/extinput.cxx
@@ -143,7 +143,7 @@ SwExtTextInput::~SwExtTextInput()
{
SvxLanguageItem aLangItem( m_eInputLanguage, nWhich );
rPtPos.SetContent(nSttCnt);
-GetMark()->nContent = nEndCnt;
+GetMark()->SetContent(nEndCnt);
rDoc.getIDocumentContentOperations().InsertPoolItem(*this, aLangItem );
}
}
@@ -193,7 +193,7 @@ void SwExtTextInput::SetInputData( const
CommandExtTextInputData& rData )
pTNd->ReplaceText( aIdx, nReplace, rNewStr );
if( !HasMark() )
SetMark();
-GetMark()->nContent = aIdx;
+GetMark()->Assign(*aIdx.GetContentNode(), aIdx.GetIndex());
}
else
{
@@ -208,7 +208,7 @@ void SwExtTextInput::SetInputData( const
CommandExtTextInputData& rData )
SetMark();
}
-GetPoint()->nContent = nSttCnt;
+GetPoint()->SetContent(nSttCnt);
m_aAttrs.clear();
if( rData.GetTextAttr() )
