[Libreoffice-bugs] [Bug 106228] [META] Icon theme issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106228 Rizal Muttaqin changed: What|Removed |Added Depends on|146062 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146062 [Bug 146062] UI gets blocked while downloading new icon theme -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146062] UI gets blocked while downloading new icon theme
https://bugs.documentfoundation.org/show_bug.cgi?id=146062 Rizal Muttaqin changed: What|Removed |Added CC||riz...@libreoffice.org Blocks|106228 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106228 [Bug 106228] [META] Icon theme issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152222] Unsupported features saved to xlsx formatted file
https://bugs.documentfoundation.org/show_bug.cgi?id=15 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 155774] [Impress][new feature] masters hierarchy / inheritance
https://bugs.documentfoundation.org/show_bug.cgi?id=155774 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 145544] Newly created lists should utilize "List 1" paragrapsh style
https://bugs.documentfoundation.org/show_bug.cgi?id=145544 --- Comment #6 from QA Administrators --- Dear John, 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 152222] Unsupported features saved to xlsx formatted file
https://bugs.documentfoundation.org/show_bug.cgi?id=15 --- Comment #6 from QA Administrators --- Dear markballew, 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 145544] Newly created lists should utilize "List 1" paragrapsh style
https://bugs.documentfoundation.org/show_bug.cgi?id=145544 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 152692] Show Text Variables does not work in LO Writer 7.4 (FILEOPEN, EDITING, FORMATTING)
https://bugs.documentfoundation.org/show_bug.cgi?id=152692 --- Comment #3 from QA Administrators --- Dear Michael H, 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 148694] i liked 7.3.1.3 on Mac (intel) until I got to inserting page numbers in a book in docx format.
https://bugs.documentfoundation.org/show_bug.cgi?id=148694 --- Comment #3 from QA Administrators --- Dear Bruce Dickson, 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 91862] Format changes in DOC files are not displayed as tracked changes
https://bugs.documentfoundation.org/show_bug.cgi?id=91862 --- Comment #10 from QA Administrators --- Dear Pedro, 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 53501] Wrong line spacing when mixing large fonts with small ones near a box
https://bugs.documentfoundation.org/show_bug.cgi?id=53501 --- Comment #15 from QA Administrators --- Dear Ingo Ruhnke, 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 55956] FILESAVE: Circular Arrow broken after save as PPT/PPTX & reopening
https://bugs.documentfoundation.org/show_bug.cgi?id=55956 --- Comment #21 from QA Administrators --- Dear Pierre Martineau, 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 137111] Header has fixed minimum spacing on DOCX import
https://bugs.documentfoundation.org/show_bug.cgi?id=137111 --- Comment #12 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 135261] UI: Manage changes dialog is resizing for few seconds after every reject/clear formatting button press
https://bugs.documentfoundation.org/show_bug.cgi?id=135261 --- Comment #10 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108621] Form-Navigation: CTRL+TAB only works right with Design-Mode switched off
https://bugs.documentfoundation.org/show_bug.cgi?id=108621 --- Comment #12 from QA Administrators --- Dear Robert Großkopf, 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 116967] Textshape with "Rotated" transform from a Draw export to .svg -- valid SVG 1.2 transform syntax or not?
https://bugs.documentfoundation.org/show_bug.cgi?id=116967 --- Comment #7 from QA Administrators --- Dear Robert Helmkamp, 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 108727] sub bullet list point not indented on export to xhtml
https://bugs.documentfoundation.org/show_bug.cgi?id=108727 --- Comment #9 from QA Administrators --- Dear Robert Orzanna, 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 105350] Writer doesn't correctly open DOC with images from WPS (OK if first saved in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=105350 --- Comment #24 from QA Administrators --- Dear Maxim, 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 92311] raise the limit of collected entries for Word Completion
https://bugs.documentfoundation.org/show_bug.cgi?id=92311 Baole Fang changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com |desktop.org | --- Comment #18 from Baole Fang --- Please -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156056] Assertion failure when double-clicking element in master slide (debug build)
https://bugs.documentfoundation.org/show_bug.cgi?id=156056 Aron Budea changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Aron Budea changed: What|Removed |Added Depends on||156056 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156056 [Bug 156056] Assertion failure when double-clicking element in master slide (debug build) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156056] New: Assertion failure when double-clicking element in master slide (debug build)
https://bugs.documentfoundation.org/show_bug.cgi?id=156056 Bug ID: 156056 Summary: Assertion failure when double-clicking element in master slide (debug build) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aron.bu...@gmail.com Blocks: 102341, 105537 Created attachment 188085 --> https://bugs.documentfoundation.org/attachment.cgi?id=188085=edit Backtrace This can only be reproduced in a debug build. - Start an empty presentation, - Switch to master view eg. using Master View button on Properties sidebar, - In Footer Area, click at the beginning of the place holder. => Crash (assertion failure) with the following: xmloff/source/core/namespacemap.cxx:253: rtl::OUString SvXMLNamespaceMap::GetQNameByKey(sal_uInt16, const rtl::OUString&, bool) const: Assertion `false' failed Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102341 [Bug 102341] [META] Master slide view/mode bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=105537 [Bug 105537] [META] Assertion failed crashes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102341] [META] Master slide view/mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102341 Aron Budea changed: What|Removed |Added Depends on||156056 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156056 [Bug 156056] Assertion failure when double-clicking element in master slide (debug build) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103370] [META] Heading Numbering bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103370 Bug 103370 depends on bug 152605, which changed state. Bug 152605 Summary: Change "heading level" to "outline level" in UI and help pages for Writer (see comment 14) https://bugs.documentfoundation.org/show_bug.cgi?id=152605 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155471] Edit Index Entry dialog: Replace "Apply" button with "Reset" button and make "Close" apply automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=155471 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6055 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156055] Edit Index Entry dialog: Ask for Save on "Close". Remove "Apply" button. Add "Reset" button.
https://bugs.documentfoundation.org/show_bug.cgi?id=156055 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||122497 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4186, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5471 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122497 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||156055 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156055 [Bug 156055] Edit Index Entry dialog: Ask for Save on "Close". Remove "Apply" button. Add "Reset" button. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156055] New: Edit Index Entry dialog: Ask for Save on "Close". Remove "Apply" button. Add "Reset" button.
https://bugs.documentfoundation.org/show_bug.cgi?id=156055 Bug ID: 156055 Summary: Edit Index Entry dialog: Ask for Save on "Close". Remove "Apply" button. Add "Reset" button. Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Building further on bug 155471 and bug 154186 - The issue is the "Edit Index Entry" dialog. Proposal 1. Modify the "Close" button functionality so that when it is applied, and the current modification in the dialog has not been saved, then a warning message would appear, asking whether to "save" or "not save" the current entry before closing. (and no message if nothing needs to be saved.) Proposal 2. If Proposal 1 is implemented, then the "Apply" button can be removed, because it would have no practical or necessary function. Proposal 3. Add a "Reset" button that returns the current entry in the dialog to its initial values when the entry was opened. (The purpose: If a change is accidently made, or a change was started, but then regretted, it provides an easy way to return to the initial state. Alternatively (but less convenient), if Proposal 1 is implemented, then one could "close" (answer "no save"), and then reopen the dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156050] Multiple squiggly lines under misspelled words in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156050 Hossein changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1968 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156050] Multiple squiggly lines under misspelled words in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156050 Hossein changed: What|Removed |Added Keywords||bibisected, regression Regression By||Khaled Hosny --- Comment #3 from Hossein --- Result of my bisect on Linux: 74b6c5ea3c333de7c5e7ef8636732edadd9083f2 is the first bad commit commit 74b6c5ea3c333de7c5e7ef8636732edadd9083f2 Author: Khaled Hosny Date: Thu Jun 8 16:41:18 2023 +0300 tdf#151968: Fix vertical position of RTL spelling wavy line -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156054] Word count should also consider text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156054 Hossein changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Hossein --- Confirming as per user's request in Ask LO: Include text boxes in Word Count https://ask.libreoffice.org/t/include-text-boxes-in-word-count/25929 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156054] New: Word count should also consider text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156054 Bug ID: 156054 Summary: Word count should also consider text boxes Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Description: LibreOffice Writer does not count the text inside text boxes. In the possible implementation, it would be good to make it optional as described in tdf#99189. Steps to Reproduce: 1. Open LibreOffice writer 2. Add a text box using "Insert > Text Box" 3. Enter some text in the text box Actual Results: Word count in the status bar is all zero (words / characters). Also in "File > Properties > Statistics", everything (except number of pages) is zero. Expected Results: Word count should also consider the text boxes in the document Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bea05a79c8ed565909e341a24b298d8deab7e042 CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95433] EDITING autocorrect option "Apply styles" causes Default Style paragraphs to change to "Text Body" paragraph style while typing
https://bugs.documentfoundation.org/show_bug.cgi?id=95433 sdc.bla...@youmail.dk changed: What|Removed |Added CC||sdc.bla...@youmail.dk --- Comment #15 from sdc.bla...@youmail.dk --- may be fixed in 7.6 -- possibly by bug 90507 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Bug 103341 depends on bug 59036, which changed state. Bug 59036 Summary: EDITING AutoCorrect: "Remove blank paragraphs" will work for all styles, other "[M]" options only for Default https://bugs.documentfoundation.org/show_bug.cgi?id=59036 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59036] EDITING AutoCorrect: "Remove blank paragraphs" will work for all styles, other "[M]" options only for Default
https://bugs.documentfoundation.org/show_bug.cgi?id=59036 sdc.bla...@youmail.dk changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from sdc.bla...@youmail.dk --- This limitation was removed by commit 1cff5c9db7e0d7cf7ae45b306deb963d95926d99 for bug 128192. Tested with the test document attachment 72524 and Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 069c7dc4e9706b40ca12d83d83f90f41cec948f8 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL threaded The initial capitals are corrected and the first letter of the sentence is capitalized, so closing this ticket as FIXED. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155912] Rendering problems in conversion of internal vcl bitmap formats transparency->alpha
https://bugs.documentfoundation.org/show_bug.cgi?id=155912 --- Comment #7 from Patrick Luby --- Created attachment 188084 --> https://bugs.documentfoundation.org/attachment.cgi?id=188084=edit Sample file with overlapping, multi-colored transparent gradients -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Bug 103341 depends on bug 59034, which changed state. Bug 59034 Summary: EDITING AutoCorrect's "Replace while modifying existing text" works only for Default style https://bugs.documentfoundation.org/show_bug.cgi?id=59034 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59034] EDITING AutoCorrect's "Replace while modifying existing text" works only for Default style
https://bugs.documentfoundation.org/show_bug.cgi?id=59034 sdc.bla...@youmail.dk changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from sdc.bla...@youmail.dk --- This limitation was removed by commit 1cff5c9db7e0d7cf7ae45b306deb963d95926d99 for bug 128192, so closing this ticket as FIXED. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139951] Some "replace dashes" options do not work with Tools -AutoCorrect - Apply
https://bugs.documentfoundation.org/show_bug.cgi?id=139951 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6046 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156046] Autocorrect replaces " - " with " – " instead of " — " (en-dash instead of em-dash)
https://bugs.documentfoundation.org/show_bug.cgi?id=156046 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||9951 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140024] "replace custom styles" option in AutoCorrect should be removed
https://bugs.documentfoundation.org/show_bug.cgi?id=140024 sdc.bla...@youmail.dk changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Summary|"replace custom styles" |"replace custom styles" |option in AutoCorrect needs |option in AutoCorrect |critical review |should be removed --- Comment #6 from sdc.bla...@youmail.dk --- Now that bug 90507 is fixed and Tools - AutoCorrect - Apply no longer converts "Default Paragraph Style" to "Body Text", it seems time to also remove "Replace Custom Styles" from the [M] options. Will ask UXEval -- also because maybe it is an EasyHack. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99649] [META] Improve Connector handling
https://bugs.documentfoundation.org/show_bug.cgi?id=99649 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|154345 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154345 [Bug 154345] Lines are displayed differently than MS Office -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154345] Lines are displayed differently than MS Office
https://bugs.documentfoundation.org/show_bug.cgi?id=154345 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.5.1.2 release |7.4.0.0 alpha0+ CC||stephane.guillou@libreoffic ||e.org Status|NEW |RESOLVED Blocks|99649 | Keywords|bibisectRequest |bibisected, bisected Resolution|--- |DUPLICATE --- Comment #8 from Stéphane Guillou (stragu) --- Bibisected with linux-64-7.4 repo to first bad commit f0f89cb5c7211e1a166266b7b7a083d685005230 which points to core commit: commit cbf66ec3e60d07efb7c3cceed9b4f0fb4f0510c8 author Tibor Nagy Thu Mar 10 08:42:12 2022 +0100 committer László NémethTue Mar 29 16:12:45 2022 +0200 tdf#89449 PPTX import: fix line connectors Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131303 Regression by same commit as bug 152211. Fixed by 5308d68a7cc0a4b38216438150adba2ac62e2bbe (checked with linux-64-7.5 bibisect repo). Same fix as for bug 149756. Let's mark as a duplicate. (Kalkulator, if you really still see the issue in a recent version, please report the full version info, including last commit, and attach a screenshot.) *** This bug has been marked as a duplicate of bug 149756 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99649 [Bug 99649] [META] Improve Connector handling -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156053] New: CTRL + MouseWheel not targeting cursor location
https://bugs.documentfoundation.org/show_bug.cgi?id=156053 Bug ID: 156053 Summary: CTRL + MouseWheel not targeting cursor location Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jonco...@gmail.com Description: CTRL + Mouse wheel to zoom and unZoom in Calc is not centering on cursor location. Actual Results: Create a large sheet that is larger than your screen size so you have to use the scroll bars. Zoom out and back in using CTRL and the Mouse Wheel and it prefers the upper left corner instead of cursor location. Expected Results: The zoom is centered on the upper left visible area Reproducible: Always User Profile Reset: No Additional Info: Zoomed in with the center being the cursor location. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 --- Comment #17 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/help/commit/a12f65df843f2cd8f2c6a04e41c981c753c3d5bf (related) tdf#90507,tdf#154933 Text Body -> Body Text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 --- Comment #16 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/62a280c3b288b30ac34f68e4665c76369336cda1 (related) tdf#90507,tdf#154933 Text Body -> Body Text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155834] Unnumbered entries do not move together with their main entry, when list's "move item up / down" commands are used
https://bugs.documentfoundation.org/show_bug.cgi?id=155834 --- Comment #15 from Mike Kaganski --- (In reply to Heiko Tietze from comment #13) > MSO behaves the same as LibreOffice. I have tested this, and yes, using Move Up/Down function in MS Word 2016 does behave the same way. However, it is completely unrelated. In Word (and in its file format), there is no proper notion of *list item*, which would include several paragraphs. The list like 1. a 2. b c 3. d 4. e would be represented by this OOXML markup: a b c d e so the "list item" feature of Writer doesn't exist in Word, and so it's incorrect to consider how Word behaves in this regard. The "unnumbered entries" in Word are ordinary paragraphs, just having the same paragraph style as numbered entries, to have the same indentation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 --- Comment #8 from Doug --- Well excussseee me! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 --- Comment #7 from Mike Kaganski --- When you save as DOCX, it warns you that not all formatting may be saved in that format. Of course, you may disable this warning, if you know what you do, but then it's not a question why it happens. Writer allows you to use all features, no matter what was the original format from which current document was imported. Writer doesn't try to read user's mind, guessing which file format they will be using for save; if user wants this feature, it is here; if user then wants to save in an external format, being warned about consequences - user is the master. Again: what would be your expectation when opening TXT? Would you expect Writer to disable Bold/Italics/font selector? please try to find a word processor that behaves like that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 --- Comment #6 from Doug --- The option to use newlines in chapter numbering was available to me in the menu without any warning that .docx doesn't support it. Why wasn't it greyed out if i couldn't/shouldn't use it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 --- Comment #5 from Mike Kaganski --- I do not understand your question. What specifically is available? DOCX? Or newline? And would you expect Writer to keep this formatting, if you chose TXT as save format? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 --- Comment #4 from Doug --- OK, then why is it available as an option? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #3 from Mike Kaganski --- DOCX is a file format that does not support this kind of chapter formatting. It only supports what MS Word supports. This is not a bug. Please use native file format (ODT) to be able to store all features that Writer supports. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 --- Comment #2 from Doug --- .docx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 --- Comment #1 from Mike Kaganski --- Which file format do you use for saving? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156046] Autocorrect replaces " - " with " – " instead of " — " (en-dash instead of em-dash)
https://bugs.documentfoundation.org/show_bug.cgi?id=156046 --- Comment #4 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #3) > Hmm, but when is it a minus vs. a dash? That is a bit of a red herring. We are already replacing it with a dash; this bug is about the question of _which_ dash... > Folks writing text runs as in-line formulas won't appreciate an U+2014 EM > DASH when they really need a U+2212 MINUS They don't need that, because: 1. We are talking about runs of text. When we are in something which is in some way designated as math formula, then we can talk. If you suggest we use some heuristic to detect that - please open a bug and we'll discuss it :-) 2. There are no spaces before and after minuses in a proper formula. > so not converting the - is probably more helpful. No > unexpected conversion, and they have to adjust the U+002d. Absolutely disagree. That is a niche use case, and even for that niche, using a formula editor (or a TeX add-on etc.) is the more appropriate thing to do. > IMHO the -- conversion to U+2013 EN DASH while keeping the > spaces is probably incorrect. Suggest we should instead be droping the > spaces and convert the run to a single EM DASH? No. Why? Because both the with-spaces and without-spaces styles are common. See this question on Writing.SX: https://writing.stackexchange.com/q/8555 > ... Chicago Style dictates that you must not have spaces before and > after the em dash, while AP Style dictates that you should have > spaces before and after... > Folks needing an EM DASH with surrounding white space can use the :---: > emoji syntax? We should be thinking about people who don't type syntax aiming for replacement, but about the typical author, who just writes using a single dash/hyphen and are not thinking about it. That is the typical use case we need to cater to. Nobody will know about this syntax nor use it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154266] Files not visible in LibreOffice's own file dialogs (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=154266 --- Comment #10 from Stéphane Guillou (stragu) --- Thanks Caolán. Pierre and Buovjaga, regarding the UI issue, are you able to five us the OS / Desktop Environment / Theme combination that makes the non-selected items disappear in that dialog? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156046] Autocorrect replaces " - " with " – " instead of " — " (en-dash instead of em-dash)
https://bugs.documentfoundation.org/show_bug.cgi?id=156046 --- Comment #3 from V Stuart Foote --- Hmm, but when is it a minus vs. a dash? Folks writing text runs as in-line formulas won't appreciate an U+2014 EM DASH when they really need a U+2212 MINUS, so not converting the - is probably more helpful. No unexpected conversion, and they have to adjust the U+002d. IMHO the -- conversion to U+2013 EN DASH while keeping the spaces is probably incorrect. Suggest we should instead be droping the spaces and convert the run to a single EM DASH? Closing the whitespace gap (catch a leading but no closing, or closing but no leading, along with the bracketed spaces). Folks needing an EM DASH with surrounding white space can use the :---: emoji syntax? Otherwise our "no spaces" conversion of two keyboard U+002d HYPHEN-DASH to EM DASH is appropriate. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155745] In Libre Writer the 'typing cursor' and 'I bar' need improved contrast to Application Color "Document background"
https://bugs.documentfoundation.org/show_bug.cgi?id=155745 V Stuart Foote changed: What|Removed |Added OS|Windows (All) |All Summary|In Libre Writer make the|In Libre Writer the 'typing |'typing cursor' and 'I bar' |cursor' and 'I bar' need |more visible. |improved contrast to ||Application Color "Document ||background" CC||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- The text cursor does toggle color in response Application Colors 'Document background' set. Easier to see the effect if the document background is selected across the range of the Standard palette's gray scale. It is not the size or shape of the text cursor (and do not think we need to follow any os/DE settings cross platform). Rather, issue is that the transition of text cursor's gray scale color against background color does not auto-adjust well and you *can* end up with "invisible" Grey cursor on Grey 'Document background' and similar low contrast values around the gray-scale mid-range. Suggests there should be a test of text cursor contrast against document background for auto-adjust. Also in addition to contrast testing for automatic values, I would love to be able to directly set the text cursor and pointer color as Application color elements. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156052] New: NEW Chapter Number Using Followed by Newline is not persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156052 Bug ID: 156052 Summary: NEW Chapter Number Using Followed by Newline is not persistent Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: douglas.mar...@gmail.com Description: I am writing a book using LibreOffice Writer 7.5.3.2 X86_64. I have to use the chapter number followed by newline since I'm using a narrow page size and sometimes chapter titles are too long to fit the page width with the chapter number too. The new line works for a while, then like after a save or something, it reverts back to a tab stop. Steps to Reproduce: 1.Chapter numbering using English numbers and newline separator 2. I believe it resets after a save. 3. Actual Results: Chapter numbering uses tab stop Expected Results: Chapter numbering continues to use newline Reproducible: Always User Profile Reset: No Additional Info: ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154266] Files not visible in LibreOffice's own file dialogs (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=154266 --- Comment #9 from Caolán McNamara --- Oh good, so it does look like the scenario was the same as mine then. Headless mode switching on this internal file dialog and some crash or other failure making the reset to "normal" not happen. So that trigger is fixed at least. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156046] Autocorrect replaces " - " with " – " instead of " — " (en-dash instead of em-dash)
https://bugs.documentfoundation.org/show_bug.cgi?id=156046 --- Comment #2 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #1) > Not clear we are doing it incorrectly. ... > A single keyboard hyphen dash (U+002d) with spaces is converted to a single > U+2013 (EN DASH). This is the bug. A user that's not well aware of dashes and their importance is likely to use a space hyphen space sequence, and we should interpret that as "I don't know what kind of dash I want", and enter an Em dash. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156050] Multiple squiggly lines under misspelled words in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156050 --- Comment #2 from Hossein --- Two notes: 1. The problem is not reproducible with LO 7.5, so it is a regression. Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded 2. To test LO dev, you need to have spell checker for Persian, or other languages you want to test. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148006] Export to SVG broken, when exporting rotated objects with multiple lines of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148006 --- Comment #6 from Galuxttor --- Confirm in Version: 7.5.4.2 (x86) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 4; OS: Windows; UI render: default; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156003] In bugzilla search option will be not working.
https://bugs.documentfoundation.org/show_bug.cgi?id=156003 Julien Nabet changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156003] In bugzilla search option will be not working.
https://bugs.documentfoundation.org/show_bug.cgi?id=156003 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156051] libreoffice-gtk3 package impairs SLIDESHOW of imported MPEG4 and AVI videos by IMPRESS
https://bugs.documentfoundation.org/show_bug.cgi?id=156051 --- Comment #1 from Dave Poole --- Created attachment 188083 --> https://bugs.documentfoundation.org/attachment.cgi?id=188083=edit Screen capture of slideshow showing the effect of libreoffice-gtk3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156051] New: libreoffice-gtk3 package impairs SLIDESHOW of imported MPEG4 and AVI videos by IMPRESS
https://bugs.documentfoundation.org/show_bug.cgi?id=156051 Bug ID: 156051 Summary: libreoffice-gtk3 package impairs SLIDESHOW of imported MPEG4 and AVI videos by IMPRESS Product: LibreOffice Version: 7.3.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dlpoole.i...@gmail.com Description: Mint 21.1 by default installs LibreOffice with libreoffice-gtk3 1:7.3.7-0ubuntu0.22. As long as this package is present, IMPRESS slideshows MPEG4 and AVI videos in left-justified monochrome, even though the default Celluloid viewer and VLC display them perfectly. Removing the subject package changes Impress' UI’s as expected, then mpeg4 and avi videos in the same presentation SLIDESHOW display and play properly. Steps to Reproduce: 1.Install libreoffice-gtk3 1:7.3.7-0ubuntu0.22 if not already present 2.Attempt slideshow of a presentation with an imported mpeg4 or avi video 3.Remove the subject package with APT, etc. 4.Restart Impress, load presentation with video, and repeat Actual Results: While libreoffice-gtk3 1:7.3.7-0ubuntu0.22 is present, IMPRESS slideshows imported MPEG4 and AVI videos in left-justified monochrome, sometimes over a color still of the first frame as shown prior to starting the SLIDESHOW. Expected Results: After the subject package is removed and Impress is restarted, the same presentation file with imported videos slideshows perfectly. Reproducible: Always User Profile Reset: Yes Additional Info: 7.3.7.2 / LibreOffice Community CPU threads:4;OS:Linux 5.15 UI render:default; VCL:gtk3 en-US(en_US.UTF-8;UI:en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.3 Calc:threaded Same with the subject package removed except VCL:x11 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89466] [META] SIDEBAR: Slide content panel in Properties tab in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=89466 Regina Henschel changed: What|Removed |Added Depends on||145130 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145130 [Bug 145130] Changing an LO Draw's background gradient color resets its gradient type, angle, and other properties -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145130] Changing an LO Draw's background gradient color resets its gradient type, angle, and other properties
https://bugs.documentfoundation.org/show_bug.cgi?id=145130 Regina Henschel changed: What|Removed |Added Blocks||89466 --- Comment #8 from Regina Henschel --- The problem is not solved with multicolor gradient (MCGR). Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89466 [Bug 89466] [META] SIDEBAR: Slide content panel in Properties tab in Impress -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66241] FILEOPEN: cannot open file
https://bugs.documentfoundation.org/show_bug.cgi?id=66241 --- Comment #10 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f95c213cc9107e25f78e25c6a1bdfb8a5a61be2a crashtesting: crash seen on exporting fdo66241-1.ods to xlsx It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66241] FILEOPEN: cannot open file
https://bugs.documentfoundation.org/show_bug.cgi?id=66241 Commit Notification changed: What|Removed |Added Whiteboard|target:4.2.0|target:4.2.0 target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155854] Mail Merge hangs after connecting to the mailserver
https://bugs.documentfoundation.org/show_bug.cgi?id=155854 Aron Budea changed: What|Removed |Added Resolution|FIXED |WORKSFORME CC||aron.bu...@gmail.com --- Comment #2 from Aron Budea --- Let's use state WORKSFORME, as the fixing change isn't known. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76334] LO4.3 writes svg:viewBox="0 0 0 0" when convert a shape in pptx to odp.
https://bugs.documentfoundation.org/show_bug.cgi?id=76334 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||9425 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139425] FILEOPEN PPTX: strange polygon artefact
https://bugs.documentfoundation.org/show_bug.cgi?id=139425 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=76 ||334 --- Comment #8 from Regina Henschel --- LO generates a wrong viewBox. The problem is related to bug 76334, might be duplicate. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156050] Multiple squiggly lines under misspelled words in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156050 --- Comment #1 from Hossein --- The problem is reproducible with the latest LO 24.2 dev master: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bea05a79c8ed565909e341a24b298d8deab7e042 CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156050] New: Multiple squiggly lines under misspelled words in text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156050 Bug ID: 156050 Summary: Multiple squiggly lines under misspelled words in text boxes Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 188082 --> https://bugs.documentfoundation.org/attachment.cgi?id=188082=edit ODT file containing a text box with misspelled words Description: After fixing tdf#151968, a new problem appeared: drawing multiple squiggly lines under misspelled words in text box. Steps to Reproduce: 1. Open the attachment 2. Double click on the text Actual Results: Multiple squiggly line segments are drawn below many words, creating clutter. Expected Results: Squiggly line segments should be drawn below the wrong words, exactly one squiggly line segment under one misspelled word. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156049] New: Mouse Cursor freezing when Acrobat open in another visible window.
https://bugs.documentfoundation.org/show_bug.cgi?id=156049 Bug ID: 156049 Summary: Mouse Cursor freezing when Acrobat open in another visible window. Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ara...@hostman.us Description: Mouse cursor stops responding to mouse movement, while not affecting the touchscreen. Lid triggered sleep resets it. Steps to Reproduce: 1. Open PDF in Acrobat reader 2. Open document in Libre Office Writer 3. Edit document for about an hour Actual Results: This has happened repeatedly (5 times in last 24 hours). Mouse cursor stops responding, but trackpad clicks still got to current cursor location. Note that touchscreen remains unaffected. Expected Results: It should mot lock the cursor. Reproducible: Sometimes User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155706] Page number dialog should have OK as default button (so Enter work)
https://bugs.documentfoundation.org/show_bug.cgi?id=155706 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Dieter --- (In reply to Timur from comment #0) > Insert-Page number dialog should have OK as default button, so that Enter > works in the most simple case to insert page number. I agree with this suggestion. Actually no button is defined as default button -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155739] Writer crashed while writing
https://bugs.documentfoundation.org/show_bug.cgi?id=155739 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| --- Comment #1 from Dieter --- Michael, thank your for reporting the crash. Could you please a) Retest with LO 7.5? b) have a look at your recovery settings in tools -> options -> Load/Save -> General -> "Save autorecovery information every XXX minutes" Does this solve your problem? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114857] EDITING Can't see cursor when background is dark/black
https://bugs.documentfoundation.org/show_bug.cgi?id=114857 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5745 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116143] [META] Text cursor (caret) bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=116143 Dieter changed: What|Removed |Added Depends on||155745 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155745 [Bug 155745] In Libre Writer make the 'typing cursor' and 'I bar' more visible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149397] FILEOPEN 78-pages .DOC opens with much more pages since Lo 5.3
https://bugs.documentfoundation.org/show_bug.cgi?id=149397 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5745 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142074] [META] Application Colours settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142074 Dieter changed: What|Removed |Added Depends on||155745 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155745 [Bug 155745] In Libre Writer make the 'typing cursor' and 'I bar' more visible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108430] [META] Mouse cursor bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108430 Dieter changed: What|Removed |Added Depends on||155745 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155745 [Bug 155745] In Libre Writer make the 'typing cursor' and 'I bar' more visible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155745] In Libre Writer make the 'typing cursor' and 'I bar' more visible.
https://bugs.documentfoundation.org/show_bug.cgi?id=155745 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| Blocks||116143, 108430, 142074 Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||4857, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9397 Keywords||needsUXEval CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Status|UNCONFIRMED |NEW --- Comment #1 from Dieter --- I confirm it with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 069c7dc4e9706b40ca12d83d83f90f41cec948f8 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded Steps: 1. Tools -> Options -> LibreOffice -> Application Colours 2. Change colour of dicument background to #7B7B7B 3. Write some wrds and plac cursor behind a word and move with mouse or touchpad over document Actual result Cursor almost unvisible Expected result Cursor should be visible So for me it's a valid enhancemnet request, but I add design-team to find a solution here. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108430 [Bug 108430] [META] Mouse cursor bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=116143 [Bug 116143] [META] Text cursor (caret) bugs https://bugs.documentfoundation.org/show_bug.cgi?id=142074 [Bug 142074] [META] Application Colours settings bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33590] Add MathType 4+ support for .doc and .docx
https://bugs.documentfoundation.org/show_bug.cgi?id=33590 --- Comment #19 from Hossein --- LO 24.2 dev master still does not support MathType 4+: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bea05a79c8ed565909e341a24b298d8deab7e042 CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_DE); UI: en-US Calc: CL threaded By double clicking the formula, I get this error: Error Error activating object: General OLE error. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139425] FILEOPEN PPTX: strange polygon artefact
https://bugs.documentfoundation.org/show_bug.cgi?id=139425 --- Comment #7 from Regina Henschel --- The problem still exists in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d4ee93a54e790acab470667591d61d424831e665 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107940] XHTML export cannot handle setting "show sublevels"
https://bugs.documentfoundation.org/show_bug.cgi?id=107940 --- Comment #9 from Regina Henschel --- The problem still exists in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d4ee93a54e790acab470667591d61d424831e665 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156048] New: bash script for installation for selectable versions and packages of LibreOffice suite
https://bugs.documentfoundation.org/show_bug.cgi?id=156048 Bug ID: 156048 Summary: bash script for installation for selectable versions and packages of LibreOffice suite Product: LibreOffice Version: unspecified Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rich.li...@demattio.co.at Today I received an eMail about a bug, where you try to motivate us updating bug status and to retest the bug on different versions of LibreOffice. To make life easier (on Linux), I wrote a bash script to support the installation of selectable versions and packages. I would like to provide this script to the community. see the web site https://codeberg.org/demattio/LibreOffice_Package_Download_Script.git I hope, this is a good place to make the script public and please appologize, if this is a misuse of the bug tracker. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102998] [META] Mail merge bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102998 Bug 102998 depends on bug 155854, which changed state. Bug 155854 Summary: Mail Merge hangs after connecting to the mailserver https://bugs.documentfoundation.org/show_bug.cgi?id=155854 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155854] Mail Merge hangs after connecting to the mailserver
https://bugs.documentfoundation.org/show_bug.cgi?id=155854 Bernard Decock changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Bernard Decock --- Problem solved with LO 7.5.4.2 -- You are receiving this mail because: You are the assignee for the bug.
