[Libreoffice-bugs] [Bug 151023] Can't edit Python scripts in "APSO - Alternative Script Organizer for Python"
https://bugs.documentfoundation.org/show_bug.cgi?id=151023 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- Thanks Rafael. Closed as NAB -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148511] Dragging top handle of the table border to increase the size of table refuses
https://bugs.documentfoundation.org/show_bug.cgi?id=148511 --- Comment #3 from Ezinne --- Not reproducible in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: c54c576a5043dc5a0cc01f8c71897373516ae091 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-NG (en_NG); UI: en-US Calc: threaded Can you test again, Telesto? Please attach a screen recording if it is still reproducible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150664] Formula bar in Calc is moved to down
https://bugs.documentfoundation.org/show_bug.cgi?id=150664 --- Comment #8 from r435g391b823-comp176...@yahoo.com.au --- Hi, I have this bug in latest release 7.4.1 too, as seen in Roman's screenshot, however unlike Eike in comment 7, nothing I do makes the input line change position back into alignment or become its proper single-line height. Entering formula in cells, clicking on the formula input line and typing, or using the mouse-drag option [found by hovering the mouse between the formula bar and cell column headers]. The input line is either obscured or 2+line height and still out of vertical alignment. The Formula Bar Input Line textbox remains a few pixels lower than it should be, making it largely unreadable unless you increase the formula bar height. This's a really weird thing to break in a new release.. good luck, and thanks in advance for fixing this you fantastic Dev People. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147678] Can not select initial characters in the formula bar
https://bugs.documentfoundation.org/show_bug.cgi?id=147678 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 147678] Can not select initial characters in the formula bar
https://bugs.documentfoundation.org/show_bug.cgi?id=147678 --- 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 147624] Screen is magnified to unusable degree
https://bugs.documentfoundation.org/show_bug.cgi?id=147624 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147624] Screen is magnified to unusable degree
https://bugs.documentfoundation.org/show_bug.cgi?id=147624 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 147418] Libreoffice Calc cannot start
https://bugs.documentfoundation.org/show_bug.cgi?id=147418 --- Comment #5 from QA Administrators --- Dear karim, 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 147418] Libreoffice Calc cannot start
https://bugs.documentfoundation.org/show_bug.cgi?id=147418 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 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Bug 43808 depends on bug 144965, which changed state. Bug 144965 Summary: TopDown RTL on screen o, printing rotates characters wrongly and kerning messed up as well https://bugs.documentfoundation.org/show_bug.cgi?id=144965 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144965] TopDown RTL on screen o, printing rotates characters wrongly and kerning messed up as well
https://bugs.documentfoundation.org/show_bug.cgi?id=144965 --- Comment #4 from QA Administrators --- Dear Tolstoy, 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 144965] TopDown RTL on screen o, printing rotates characters wrongly and kerning messed up as well
https://bugs.documentfoundation.org/show_bug.cgi?id=144965 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 148077] When pasting several paragraphs, all 'adopt' the list style of the point of paste
https://bugs.documentfoundation.org/show_bug.cgi?id=148077 --- Comment #2 from QA Administrators --- Dear Eyal Rozenberg, 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 147816] LibreOffice UpGrade / Functionality Downgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=147816 --- Comment #5 from QA Administrators --- Dear nik, 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 138525] CALC - Recording Cut Paste Cell Macro creates code written in wrong order causing it to fail
https://bugs.documentfoundation.org/show_bug.cgi?id=138525 --- Comment #3 from QA Administrators --- Dear Dave Green, 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 142063] Writer and Calc macro problems with update to LO 7.1.2.2
https://bugs.documentfoundation.org/show_bug.cgi?id=142063 --- Comment #6 from QA Administrators --- Dear Lew, 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 97166] Fileopen: .docx: Some formulas with wrong syntax aren't correctly imported (OK in Word)
https://bugs.documentfoundation.org/show_bug.cgi?id=97166 --- Comment #15 from QA Administrators --- Dear Rolle, 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 90903] FILESAVE: OOXML files saved by LO do not detect with Linux file command
https://bugs.documentfoundation.org/show_bug.cgi?id=90903 --- Comment #11 from QA Administrators --- Dear Dan, 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 60835] External links saved in xls format
https://bugs.documentfoundation.org/show_bug.cgi?id=60835 --- Comment #12 from QA Administrators --- Dear teemoz, 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 62325] EDITING: Deleting selected text leaves unexpected font under cursor
https://bugs.documentfoundation.org/show_bug.cgi?id=62325 --- Comment #20 from QA Administrators --- Dear Matthew Francis, 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 55307] Drawing Object Copied Using Ctrl+[Mouse-Drag] Is Not Immediately Displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=55307 --- Comment #12 from QA Administrators --- Dear preechaw, 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 47596] FILEOPEN: rotated and cropped or scaled PNG/JPG/WMF image in MSO .DOC not rotated and wrongly scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=47596 --- Comment #30 from QA Administrators --- Dear grofaty, 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 47545] FILEOPEN: ODT from OO opens with wrong size of frame set as character
https://bugs.documentfoundation.org/show_bug.cgi?id=47545 --- Comment #19 from QA Administrators --- Dear Terrence Enger, 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 136827] Crash: Several repeat apply Pop Art Filter to shape which is converted to Bitmap
https://bugs.documentfoundation.org/show_bug.cgi?id=136827 --- Comment #4 from QA Administrators --- Dear sawakaze, 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 136064] FILESAVE RTF: Export of shape broken (not resemblance of the shape at all)
https://bugs.documentfoundation.org/show_bug.cgi?id=136064 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 135618] Image moved with between table cells depend on cell start position and document format (ODT/DOC/DOCX/RTF)
https://bugs.documentfoundation.org/show_bug.cgi?id=135618 --- Comment #4 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 133082] Navigator: Range names' sheet is not updated after undo
https://bugs.documentfoundation.org/show_bug.cgi?id=133082 --- Comment #3 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127699] trail left by objects while dragging them with arrow keys in LibreOffice Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=127699 --- Comment #14 from QA Administrators --- Dear mirko.pieropan, 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 123158] isNumeric returns false if number is passed as String
https://bugs.documentfoundation.org/show_bug.cgi?id=123158 --- Comment #13 from QA Administrators --- Dear Leos Pohl, 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 111956] .pdb plucker file crashes on 5.4
https://bugs.documentfoundation.org/show_bug.cgi?id=111956 --- Comment #4 from QA Administrators --- Dear vihsa, 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 104486] FILEOPEN: DOCX: shadow for text in shape not applied (WPS)
https://bugs.documentfoundation.org/show_bug.cgi?id=104486 --- Comment #9 from QA Administrators --- Dear Mikhail Novosyolov, 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 125595] FORMATTING: Validity cell range with invisible characters (e.g. newline) stripped
https://bugs.documentfoundation.org/show_bug.cgi?id=125595 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #6 from Justin L --- I expect there is a real problem here. Perhaps it was fixed with https://gerrit.libreoffice.org/c/core/+/140110. However, in Linux I couldn't reproduce the problem. Newlines seem to exist, and validity reports the correct entry every time I select something in the dropdown. Tested in master, 7.3, and 7.0. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151034] Background on navigation menu too dark to read text
https://bugs.documentfoundation.org/show_bug.cgi?id=151034 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||vstuart.fo...@utsa.edu --- Comment #2 from V Stuart Foote --- Looks like you've set Windows 10 to Color theme to the 'Dark' mode please set Tools -> Options -> Application Colors "Liberation Dark" Color scheme. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108198] [META] ODF export is unsuitable or invalid XML
https://bugs.documentfoundation.org/show_bug.cgi?id=108198 Bug 108198 depends on bug 151031, which changed state. Bug 151031 Summary: FILESAVE XLS->ODS: use-optimal-row-height wrong on first save https://bugs.documentfoundation.org/show_bug.cgi?id=151031 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88174] [META] Binary XLS format limitations
https://bugs.documentfoundation.org/show_bug.cgi?id=88174 Bug 88174 depends on bug 151031, which changed state. Bug 151031 Summary: FILESAVE XLS->ODS: use-optimal-row-height wrong on first save https://bugs.documentfoundation.org/show_bug.cgi?id=151031 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151031] FILESAVE XLS->ODS: use-optimal-row-height wrong on first save
https://bugs.documentfoundation.org/show_bug.cgi?id=151031 m.a.riosv changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 130383 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130383] Filesave ODS: Row height after Optimal Height still opens as 1 line instead of 2 in cell F5 (not with XLS/X)
https://bugs.documentfoundation.org/show_bug.cgi?id=130383 m.a.riosv changed: What|Removed |Added CC||jl...@mail.com --- Comment #20 from m.a.riosv --- *** Bug 151031 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 150913] Writer: Spurious page break when forcing page style and resetting page number
https://bugs.documentfoundation.org/show_bug.cgi?id=150913 m.a.riosv changed: What|Removed |Added CC||no_re...@slugbandit.co.uk --- Comment #1 from m.a.riosv --- *** Bug 151036 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 151036] Writer: Manual page break adds extra spurious page count
https://bugs.documentfoundation.org/show_bug.cgi?id=151036 m.a.riosv changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 150913 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113337] FILEOPEN: XLSX - Hyperlinks always displayed as blue, even if style uses different font colour
https://bugs.documentfoundation.org/show_bug.cgi?id=113337 stragu changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||4456 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134456] Document what Calc's Hyperlink cell style is designed for
https://bugs.documentfoundation.org/show_bug.cgi?id=134456 stragu changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3337 Hardware|x86-64 (AMD64) |All Summary|Hyperlink colours cannot be |Document what Calc's |changed by changing |Hyperlink cell style is |Hyperlink style |designed for CC||stephane.guil...@member.fsf ||.org --- Comment #14 from stragu --- I agree that it's hard to know where this information could be added, but I think the idea here is to document the Hyperlink style available in Calc. Maybe this page, but it's specifically the cell style editing dialog: https://help.libreoffice.org/7.5/en-US/text/scalc/01/cell_styles.html Or this one, about Calc styles in general: https://help.libreoffice.org/7.5/en-US/text/scalc/01/0510.html An extra info box could do? Note that the issue related to changing the colour of a hyperlink is talked about in Bug 113337. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151013] Revise Sifr Icon Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=151013 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #2 from Rafael Lima --- I use the Sifr Dark icon theme in KDE Plasma and it looks very good. I'd like to start by saying that I really like this icon theme. (In reply to Galdam Jitsu from comment #0) > 1. Sifr dark icons don't look bright enough to make good contrast with the > background, at least on Gtk/GNOME. Thus there Sifr dark icons should be > remade with a brighter color. Actually I think they look bright enough in KDE. One thing I like about Sifr dark is that it is soft on the eyes (when compared to Colibre). However, one thing I find strange is that "disabled" icons are lighter than "enabled" icons, which seems counter intuitive. So sometimes it's hard to tell which icons are enabled just by looking at the toolbar, I always have to hover with the mouse to see if they're enabled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151023] Can't edit Python scripts in "APSO - Alternative Script Organizer for Python"
https://bugs.documentfoundation.org/show_bug.cgi?id=151023 --- Comment #2 from Rafael Lima --- As Roman pointed out, you need to define an external text editor to be used by APSO. To do that: 1) Go to Tools - Extension Manager 2) Click on the installed APSO entry 3) At the bottom left corner of the dialog, an "Options" button will appear; click it 4) In the Options dialog, fill the "Editor" field with the path to the executable of the editor you want to use (if it is in your current PATH, simply type the command name) I am using KDE and I use Kate for editing, so I simply type "kate" in the Editor option above. I'd say this is NAB or NOTOURBUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 44189] FORMATTING: visited hyperlinks do not change color
https://bugs.documentfoundation.org/show_bug.cgi?id=44189 stragu changed: What|Removed |Added Hardware|x86 (IA32) |All OS|Windows (All) |All Summary|FORMATTING: The hyperlinks |FORMATTING: visited |visited not change the |hyperlinks do not change |color. |color CC||stephane.guil...@member.fsf ||.org --- Comment #9 from stragu --- To test this, go to "Tools > Options > LibreOffice > Application Colours > Custom Colours > General", tick both custom colours for hyperlinks and change them to obviously different colours. Bug is still reproduced in Calc: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 3752e8eaa81a50b018669d03dc59b3753a5248ef CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But clicking a link in Writer does respect the visited link colour as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151012] Msgbox Button parameter isn't optional
https://bugs.documentfoundation.org/show_bug.cgi?id=151012 --- Comment #5 from Rafael Lima --- BTW, I forgot to mention in Comment #4 that I'm using LO 7.4.1 Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 16; 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.4.1~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151012] Msgbox Button parameter isn't optional
https://bugs.documentfoundation.org/show_bug.cgi?id=151012 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #4 from Rafael Lima --- I am not sure I understood correctly, but the following code works for me: Sub test MsgBox "Message", Title := "Dialog title" End Sub I did not have to specify the Buttons argument. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151036] New: Writer: Manual page break adds extra spurious page count
https://bugs.documentfoundation.org/show_bug.cgi?id=151036 Bug ID: 151036 Summary: Writer: Manual page break adds extra spurious page count Product: LibreOffice Version: 6.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: no_re...@slugbandit.co.uk Description: Page count is incorrectly indexed by 1 Steps to Reproduce: 1. Create a new doc, [insert Field>Page count] 2. insert More Breaks>Manual Break>Page Break>check Change Page Number. Insert or check Page Number. Actual Results: Page Count shows "3" but only 2 pages exist. If alternatively a 'standard' Ctrl+Enter is set it correctly displays 2. Expected Results: Display "2" Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.4 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80040] FILESAVE: XLSX - Hyperlinks don't show up in Excel in blue or underlined
https://bugs.documentfoundation.org/show_bug.cgi?id=80040 stragu changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3337 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113337] FILEOPEN: XLSX - Hyperlinks always displayed as blue, even if style uses different font colour
https://bugs.documentfoundation.org/show_bug.cgi?id=113337 stragu changed: What|Removed |Added Version|unspecified |6.0 all versions Summary|FILEOPEN: XLSX - Hyperlinks |FILEOPEN: XLSX - Hyperlinks |always displayed as blue|always displayed as blue, ||even if style uses ||different font colour See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=80 ||040 CC||stephane.guil...@member.fsf ||.org --- Comment #6 from stragu --- Reproduced in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 3752e8eaa81a50b018669d03dc59b3753a5248ef CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Notice that this happens even if "Tools > Options > LibreOffice > Application Colours > Custom Colours > General" has link colours unticked. Both OnlyOffice and MS Office 365 respect the red style of attachment 137197. But I don't think this is specific to XLSX, as saving as ODS doesn't use the colour either. (However, the link is red if saved as XLS). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150905] Drawing Dimensions are NEGATIVE - Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=150905 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #4 from raal --- No repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: e46f9cc4b506c325cbe1060777bbc81fd1630f49 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Please could you test it with dev version? You can download it here: http://dev-builds.libreoffice.org/daily/master/ Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150823] Track changes: list of > 20 registered changes; vanishing after rejecting one change
https://bugs.documentfoundation.org/show_bug.cgi?id=150823 raal changed: What|Removed |Added Regression By||Michael Stahl Keywords|bibisectRequest |bibisected, bisected CC||michael.st...@allotropia.de --- Comment #7 from raal --- This seems to have begun at the below commit. Adding Cc: to Michael Stahl ; Could you possibly take a look at this one? Thanks 3a18e777db90da2eae71753e96b24415239c7596 is the first bad commit commit 3a18e777db90da2eae71753e96b24415239c7596 Author: Jenkins Build User Date: Wed Aug 17 14:17:40 2022 +0200 source sha:7d730cd580e957ab06b0c7f020ac37dd0c337aa2 https://git.libreoffice.org/core/+/7d730cd580e957ab06b0c7f020ac37dd0c337aa2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 65136] FILESAVE, FILEOPEN: XLS, XLSX partial-cell hyperlink is reloaded as full-cell hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=65136 --- Comment #13 from stragu --- still reproducible in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 3752e8eaa81a50b018669d03dc59b3753a5248ef CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded ... for both XLSX and XLS. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64431] FILESAVE: Broken hyperlink to another file in PPT
https://bugs.documentfoundation.org/show_bug.cgi?id=64431 stragu changed: What|Removed |Added CC||stephane.guil...@member.fsf ||.org --- Comment #12 from stragu --- Bug still present in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 3752e8eaa81a50b018669d03dc59b3753a5248ef CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Link works in PPTX and ODP but not in PPT. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150823] Track changes: list of > 20 registered changes; vanishing after rejecting one change
https://bugs.documentfoundation.org/show_bug.cgi?id=150823 raal changed: What|Removed |Added Keywords||regression Ever confirmed|0 |1 CC||r...@post.cz Status|UNCONFIRMED |NEW --- Comment #6 from raal --- Hello Telesto, I suppose you provided two sets of steps of one bug: 1-6 and 7-13 1. Open the attached file 2. Make sure track changes record being enabled 3. Place cursor at the end of the line 4. Press and hold backspace until everything being deleted 5. Edit -> track changes -> Manage 6. Press reject change a single time --> now there is lots of entries in Manage changes dialog. Is this the bug you have at mind? I can confirm it. The second steps 7-13 seems to be fixed in LO 7.5 Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: e46f9cc4b506c325cbe1060777bbc81fd1630f49 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120543] [META] Bugs and enhancements around hyperlinks in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=120543 Bug 120543 depends on bug 45435, which changed state. Bug 45435 Summary: XSLX format breaks relative hyperlink path when document is moved (comment 9) https://bugs.documentfoundation.org/show_bug.cgi?id=45435 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113335] [META] XLSX (OOXML) hyperlink bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=113335 Bug 113335 depends on bug 45435, which changed state. Bug 45435 Summary: XSLX format breaks relative hyperlink path when document is moved (comment 9) https://bugs.documentfoundation.org/show_bug.cgi?id=45435 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45435] XSLX format breaks relative hyperlink path when document is moved (comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=45435 stragu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #17 from stragu --- Using steps in comment 9, I can reproduce the bug in: Version: 6.3.6.2 Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded But it works as expected since at least: Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.4 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded Marking as "works for me". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119421] Documentation for "Formula is" in Conditional Formatting is wrong (and info missing).
https://bugs.documentfoundation.org/show_bug.cgi?id=119421 --- Comment #5 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/7c924256f4ea9c328d7b384b2cff31829399decd tdf119421 - More on conditional formatting/Icon sets -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150616] FILESAVE PDF Table row disappears from complex table after CLI PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=150616 raal changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||r...@post.cz Ever confirmed|0 |1 --- Comment #4 from raal --- Confirm with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: e46f9cc4b506c325cbe1060777bbc81fd1630f49 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150520] Add to dictionary does not work from context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=150520 raal changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED CC||r...@post.cz --- Comment #5 from raal --- Works in Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: e46f9cc4b506c325cbe1060777bbc81fd1630f49 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150551] Exporting shape with gradient fill as PDF results in wrong output
https://bugs.documentfoundation.org/show_bug.cgi?id=150551 raal changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||r...@post.cz Ever confirmed|0 |1 Version|7.3.5.2 release |4.2.0.4 release --- Comment #5 from raal --- Confirm with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: e46f9cc4b506c325cbe1060777bbc81fd1630f49 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150812] Rename the "Search Commands" menu item
https://bugs.documentfoundation.org/show_bug.cgi?id=150812 --- Comment #10 from Eyal Rozenberg --- (In reply to Adolfo Jayme Barrientos from comment #9) > If we are going to modify this string and have it go again through the > translation process, this change is too subtle and, in my experience, I’ve > seen that many teams will simply not see the subtlety and submit an > identical translation from their TM. 1. Don't they see that _some_ change has happened? 2. Won't they notice the ellipsis? 3. Aren't there reviews on translation changes? Finally, if they translate to the same thing, then - maybe they have already corrected the ambiguity in their language to begin with. > It is better to use this opportunity to > have LO match most other software: it should be “Command Palette”. I would not know for sure what a Command Palette is, and that doesn't sound like something which would let me search. Also, my suggestion here was inspired somewhat by the CLion IDE, where the menu item reads "Find Action...". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145815] Scrollbar on hidpi screen is too thin and click area too small
https://bugs.documentfoundation.org/show_bug.cgi?id=145815 --- Comment #2 from Sulphur --- If the GTK VCL plugin is used instead of the kf5 VCL plugin (SAL_USE_VCLPLUGIN=gtk3), this issue does not occur. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145201] UI: Context Menu does not appear if user clicks on the top-left sheet corner.
https://bugs.documentfoundation.org/show_bug.cgi?id=145201 --- Comment #5 from Van --- Consider simpler scenarios: In the beginning of each scenario, make sure there is no columns or rows selected. Cell: Click with a *second* mouse button on a cell: the cell is selected *and* the context menu is appeared. Column: Click with a *second* mouse button on a column header: the column is selected *and* the context menu is appeared. Row: Click with a *second* mouse button on a row header: the row is selected *and* the context menu is appeared. Up to now, the second mouse button click behavior is consistent: it selects the object *and* shows the context menu. Sheet: Click with a *second* mouse button on a sheet top-left corner: the sheet is selected and… oops, this is all. The context menu is *not* appear. I see no reason why the same action (the second mouse button click) gives different result. I do not know if MS Excel is an argument for you, but the second mouse button click behavior in MS Excel is consistent in all *four* scenarios. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145816] Cursor duplicates when new place is clicked, does not disappear from old location when scaling is 200% or more
https://bugs.documentfoundation.org/show_bug.cgi?id=145816 --- Comment #11 from Sulphur --- I can confirm that you are correct! If the VCL plugin is set to gtk3, the cursor issue does not occur. (I did have to make sure the libreoffice-gtk3 package was installed to get that to work.) The cursor problem (using the kf5 VCL plugin) does sometimes take a bit of clicking around to appear. But sometimes as soon as you open up LibreOffice it's visible: the cursor is blinking but when it "blinks out" a thin cursor remains. It's not consistent whether or not the issues appear immediately or not. The downside with the gtk3 VCL plugin is that obviously some KDE integration is dropped (e.g., file picker is GTK's), and the toolbar icons are blurrier. But no issue with the cursor that I can see. (I also realized then that when kf5 VCL plugin is the cause of this scrollbar issue, which also does not occur when using the gtk3 VCL: https://bugs.documentfoundation.org/show_bug.cgi?id=145815.) (In reply to Michael Weghorn from comment #10) > (In reply to Sulphur from comment #7) > > A bit more information: my original description of the bug appearing only on > > HiDPI screen was incorrect: all that matters is that the system's scaling is > > set to 200% or more. > > Thanks for the additional testing and information! > Indeed, I could reproduce this now with QT_SCALE_FACTOR=2.0 set and the > attached sample doc. It happens very rarely for me, though, usually takes me > about 30-60 seconds of clicking around to trigger the issue. The > "additional" cursor disappears when a repaint is triggered, e.g. by > scrolling a bit. > > (In reply to Sulphur from comment #9) > > The bug seems to have been introduced in the 7 series of LibreOffice. It > > does not occur in the 6.4 series of LibreOffice (6.4.7 tested). In the first > > stable version of the 7 series (7.0.0.1) it is present. > > > > I have also tested this in the newest daily build (dev > > 7.5.0.0.alpha0_2022-09-04); the bug is still present. > > > > I could not, however, reproduce the issue in Gnome (tested in Ubuntu > > 22.04.1), only in KDE (tested in Kubuntu 22.04.1, the newest dev build of > > KDE Neon, as well as current stable Manjaro). Is it possible that it is an > > issue with KDE? I'm not a programmer, so I'm not sure, but since the > > LibreOffice 6 series does not have the bug in even the newest versions of > > the Plasma Desktop (5.25, recently released), while the LibreOffice 7 series > > always does, some change to LibreOffice seems to have triggered it. > > This sounds like this might be specific to the so-called "kf5" VCL plugin, > which is selected by default when in a Plasma session, but not GNOME. The > "kf5" VCL plugin did not exist in older LO versions. > > Can you double-check whether the issue is gone when you start LO with the > environment variable SAL_USE_VCLPLUGIN=gtk3 set (and double-check that > "Help" -> "About LibreOffice" now displays "VCL: gtk3" instead of "VCL: kf5 > ..."? > > > > Version: 7.5.0.0.alpha0+ / LibreOffice Community > Build ID: c317f0adb308b1ece3bfa8bdffb4d0bcb1478d30 > CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) > Locale: en-GB (en_GB.UTF-8); UI: en-US > Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106773] [META] Writer document canvas view / viewport jump issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106773 Bug 106773 depends on bug 150589, which changed state. Bug 150589 Summary: Deleting a drawing object kicks you back to the last position of the text cursor instead of the anchor. Ctrl-X does not. https://bugs.documentfoundation.org/show_bug.cgi?id=150589 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 150589, which changed state. Bug 150589 Summary: Deleting a drawing object kicks you back to the last position of the text cursor instead of the anchor. Ctrl-X does not. https://bugs.documentfoundation.org/show_bug.cgi?id=150589 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151003] With many fonts, LibreOffice takes over 20 minutes to start in --safe-mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151003 --- Comment #7 from Timur --- Unfortunately, TDF doesn't supply fresh AppImage, see the date. If that one older is better, this would be a regression. You may create fresh AppImage with the following: https://wiki.documentfoundation.org/Installing_in_parallel/Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92499] Start Center GUI for the Templates button dropdown needs alignment and proper styling
https://bugs.documentfoundation.org/show_bug.cgi?id=92499 Adolfo Jayme Barrientos changed: What|Removed |Added Whiteboard||target:7.5.0 Resolution|WORKSFORME |FIXED Component|LibreOffice |UI --- Comment #18 from Adolfo Jayme Barrientos --- The commit solving it is 164a1f4c3315fc44161128d3d9ca886f767f7d30 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149897] Mail client cannot run if set on Ubuntu 22.04
https://bugs.documentfoundation.org/show_bug.cgi?id=149897 Timur changed: What|Removed |Added Summary|Claws-mail cannot run if|Mail client cannot run if |set on Ubuntu 22.04 |set on Ubuntu 22.04 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149897] Claws-mail cannot run if set on Ubuntu 22.04
https://bugs.documentfoundation.org/show_bug.cgi?id=149897 Timur changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Timur --- New by duplicate. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149897] Claws-mail cannot run if set on Ubuntu 22.04
https://bugs.documentfoundation.org/show_bug.cgi?id=149897 Timur changed: What|Removed |Added CC||haveng...@gmail.com --- Comment #2 from Timur --- *** Bug 151032 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 151032] emailing from libreoffice does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=151032 Timur changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Timur --- I think this may be marked duplicate. *** This bug has been marked as a duplicate of bug 149897 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150812] Rename the "Search Commands" menu item
https://bugs.documentfoundation.org/show_bug.cgi?id=150812 --- Comment #9 from Adolfo Jayme Barrientos --- If we are going to modify this string and have it go again through the translation process, this change is too subtle and, in my experience, I’ve seen that many teams will simply not see the subtlety and submit an identical translation from their TM. It is better to use this opportunity to have LO match most other software: it should be “Command Palette”. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139723] Tabbed UI buttons have black text which go invisible or lack contrast in OS-level dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=139723 --- Comment #13 from Thorsten Wagner --- (In reply to Timur from comment #10) > Bibisect 7.0 Linux.. so not just MacOS commit. > > authorThorsten Wagner2020-02-23 > committer Tomaž Vajngerl2020-03-06 > commit 8d11b953c0a69f4f5eb5ca42dec3812a62d0cd0f (patch) > tree 4061d4c9cd64871154a1fc843eae5cfbb6d22788 > parent 4ba09be7e260ce2a79a23465db7b2837422cde30 (diff) > tdf#125532: White text on default/action buttons and selected tabs on macOS > > CC Thorsten please check. By commit above, additional colors had to be defined. Obviously there is another part of code which has to be supplemented with definitions for the additional colors in dark mode. This has been done to fix tdf#137341. For tdf#137341 GTK has been fixed only. Screenshots attached to this issue look like QT. Probably QT has to be fixed too. Currently I am not building for QT, so I am not able to check this further. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151035] Spell checking doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=151035 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Mike Kaganski --- The Ask topic that you referenced does not contain anything useful. 1. Please check this FAQ: https://wiki.documentfoundation.org/Faq/General/116 2. If it doesn't work, please describe exactly how do you set up your spell checker: if you have respective dictionaries installed; if you mark respective text as using that language; provide screenshots as needed. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123225] Loss of functions in XLSX pivot table's context menu until refreshed (see comment 18)
https://bugs.documentfoundation.org/show_bug.cgi?id=123225 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||thomasji...@geotab.com --- Comment #21 from Roman Kuznetsov <79045_79...@mail.ru> --- *** Bug 150954 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 150954] Pivot table is gone after the file is saved in xlsx file
https://bugs.documentfoundation.org/show_bug.cgi?id=150954 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||79045_79...@mail.ru Keywords||dataLoss Resolution|--- |DUPLICATE --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- Confirm in 7.5 and it looks like a dupe of bug 123225 *** This bug has been marked as a duplicate of bug 123225 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151035] New: Spell checking doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=151035 Bug ID: 151035 Summary: Spell checking doesn't work Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: y...@rawbw.com When it is enabled like described here: https://ask.libreoffice.org/t/spell-check-not-working-in-libre-office-writer/51543 automatic and manual spell check doesn't work. FreeBSD 13.1 STABLE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150194] Restore document dialog: Progress bar never finishes (misleading)
https://bugs.documentfoundation.org/show_bug.cgi?id=150194 BogdanB changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151003] With many fonts, LibreOffice takes over 20 minutes to start in --safe-mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151003 --- Comment #6 from Stirling Westrup --- I have done the test and the latest build is much improved. (ie LibreOfficeDev-7.4.0.0.alpha0_2022-01-23.standard-x86_64.AppImage). By my timing it took just over 5 minutes to load, which is not wonderful, but is certainly something I can live with, especially considering the number of fonts I have. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147678] Can not select initial characters in the formula bar
https://bugs.documentfoundation.org/show_bug.cgi?id=147678 --- Comment #4 from DErik --- While downloading version 7.4.1 to test this again, noticed that version 7.3.0 appears to not have the problem anymore. Now this is some time later, and perhaps a Mac update fixed the problem. But you can close this as I can not reproduce the problem anymore (on a Mac). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147624] Screen is magnified to unusable degree
https://bugs.documentfoundation.org/show_bug.cgi?id=147624 --- Comment #3 from DErik --- While downloading version 7.4.1 to test this again, noticed that version 7.3.0 appears to not have the problem anymore. Now this is some time later, and perhaps a Mac update fixed the problem. But you can close this as I can not reproduce the problem anymore (on a Mac). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151012] Msgbox Button parameter isn't optional
https://bugs.documentfoundation.org/show_bug.cgi?id=151012 --- Comment #3 from Julien Nabet --- (In reply to Julien Nabet from comment #1) > Reading > https://learn.microsoft.com/en-us/office/vba/language/reference/user- > interface-help/msgbox-function, it seems all args after first one are > optional. > > Any thoughts here? Sorry, the last comment was for Mike and Andreas, I should have put: Andreas/Mike: any thoughts here? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151012] Msgbox Button parameter isn't optional
https://bugs.documentfoundation.org/show_bug.cgi?id=151012 --- Comment #2 from TISSENDIER Pierre --- (In reply to Julien Nabet from comment #1) > Reading > https://learn.microsoft.com/en-us/office/vba/language/reference/user- > interface-help/msgbox-function, it seems all args after first one are > optional. > > Any thoughts here? OK for the link Indeed the arguments after the first must be optional. It's like that from the origin of LO! But in version 7.4 it doesn't work anymore Have you really tested in version 7.4? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112810] [META] Arabic & Farsi language-specific RTL issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112810 Eyal Rozenberg changed: What|Removed |Added Depends on||149457 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149457 [Bug 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 Eyal Rozenberg changed: What|Removed |Added Blocks||149457 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149457 [Bug 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Eyal Rozenberg changed: What|Removed |Added Depends on|149457 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149457 [Bug 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112810] [META] Arabic & Farsi language-specific RTL issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112810 Bug 112810 depends on bug 149457, which changed state. Bug 149457 Summary: Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw https://bugs.documentfoundation.org/show_bug.cgi?id=149457 What|Removed |Added Status|VERIFIED|REOPENED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149457] Arabic Text Scrambled and Unreadable in PDF Files Opened by LibreOffice Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=149457 Eyal Rozenberg changed: What|Removed |Added Depends on||104597 Blocks|43808 |112810 Status|VERIFIED|REOPENED Resolution|DUPLICATE |--- --- Comment #3 from Eyal Rozenberg --- While this bug is about PDF import of RTL language text runs - it is not the same problem described in 104597. There, the problem is the reversal of order in text runs. Here we have additional problems, like character repetitions, shifting, excessive and insufficient (horizontal) spacing. So, this is not clearly a dupe. Perhaps the fix for 104597 will resolve this one as well, but - perhaps not. I think the more careful relation between the bugs is dependence. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43808 [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL) https://bugs.documentfoundation.org/show_bug.cgi?id=104597 [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving https://bugs.documentfoundation.org/show_bug.cgi?id=112810 [Bug 112810] [META] Arabic & Farsi language-specific RTL issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150664] Formula bar in Calc is moved to down
https://bugs.documentfoundation.org/show_bug.cgi?id=150664 --- Comment #7 from Eike Rathke --- >From bug 99708 comment 8: When loading a document the (one line) Input Line (aka Formula Bar) height appears too small by a few pixels, but in fact is shifted down by that amount and cut at the bottom, until clicked into then it gets positioned and as tall as it should. Same for F2 edit cell. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151003] With many fonts, LibreOffice takes over 20 minutes to start in --safe-mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151003 --- Comment #5 from Ming Hua --- (In reply to Stirling Westrup from comment #4) > I'll try to find time to do that this weekend. Where would I find the LO > profile that I should rename for the tests? https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150564] Background color of drop down menus change after resume
https://bugs.documentfoundation.org/show_bug.cgi?id=150564 --- Comment #7 from John Schuetz --- Created attachment 182529 --> https://bugs.documentfoundation.org/attachment.cgi?id=182529=edit Shows dark menu when dark color theme is chosen in Windows Thank you for looking at this! Please let me know if I can provide more info. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151030] When Calc document is open, Open Recent tries to import txt files rather than open
https://bugs.documentfoundation.org/show_bug.cgi?id=151030 --- Comment #3 from V Stuart Foote --- (In reply to Michael Bauer from comment #2) > E that's bizarre and hardly obvious to any end user who wasn't involved > in writing the code. At the very least I'd expect to see some sort of > over-ride in the UI offering to "Open as txt instead" Makes perfect sense if you think about folks working with delimited text (CSV,TSV etc.) in a file with a .txt extension. Having import behave based on active LO module is very efficient filtering. Rename/reformat the text file to ODF compliant, or when needing to open text shift to WRiter (use an existing session or just open wtih File -> New). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151003] With many fonts, LibreOffice takes over 20 minutes to start in --safe-mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151003 --- Comment #4 from Stirling Westrup --- I'll try to find time to do that this weekend. Where would I find the LO profile that I should rename for the tests? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113638] [META] Fonts listed in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=113638 Michael Warner changed: What|Removed |Added Depends on||151003 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151003 [Bug 151003] With many fonts,LibreOffice takes over 20 minutes to start in --safe-mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102985] [META] Font bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102985 Michael Warner changed: What|Removed |Added Depends on||151003 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151003 [Bug 151003] With many fonts,LibreOffice takes over 20 minutes to start in --safe-mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151003] With many fonts, LibreOffice takes over 20 minutes to start in --safe-mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151003 Michael Warner changed: What|Removed |Added Blocks||102985, 113638 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102985 [Bug 102985] [META] Font bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=113638 [Bug 113638] [META] Fonts listed in LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151034] Background on navigation menu too dark to read text
https://bugs.documentfoundation.org/show_bug.cgi?id=151034 --- Comment #1 from bestmatchh...@gmail.com --- Created attachment 182528 --> https://bugs.documentfoundation.org/attachment.cgi?id=182528=edit Image of what it looks like -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151012] Msgbox Button parameter isn't optional
https://bugs.documentfoundation.org/show_bug.cgi?id=151012 Julien Nabet changed: What|Removed |Added CC||andreas.heini...@yahoo.de, ||mikekagan...@hotmail.com, ||serval2...@yahoo.fr See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||7529 --- Comment #1 from Julien Nabet --- Reading https://learn.microsoft.com/en-us/office/vba/language/reference/user-interface-help/msgbox-function, it seems all args after first one are optional. Any thoughts here? -- You are receiving this mail because: You are the assignee for the bug.
