[Libreoffice-bugs] [Bug 133651] FORMATTING not saved on FILESAVE in columns 65+ when cells in column only have formatting and no content
https://bugs.documentfoundation.org/show_bug.cgi?id=133651 graphit...@yahoo.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #3 from graphit...@yahoo.com --- Not able to reproduce in 6.4.7.2, 7.1 or 7.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140750] FORMATTING in Writer - TABLES - Paragraph - All Selected Cells are not Formatted when Using Paragraph Formatting - Line Spacing - Fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=140750 Dieter changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143978] Calc: shrink to fit makes font size unnecessary small compared to cell width
https://bugs.documentfoundation.org/show_bug.cgi?id=143978 Tamo changed: What|Removed |Added CC||ttakah+...@gmail.com --- Comment #15 from Tamo --- Created attachment 175788 --> https://bugs.documentfoundation.org/attachment.cgi?id=175788=edit If the cell is aligned top and the width is just a little smaller Moreover, if the cell is top-aligned and the width is just a little smaller for the text, the content will overflow a half. See the screenshot (version 7.2.2.2). B2 is affected by both Bug 143659 and Bug 143978. C2 is sticking out of the top. D2 is Ok. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144548] Could not find Help page
https://bugs.documentfoundation.org/show_bug.cgi?id=144548 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144880] Image doesn't jump to next page or stops moving when pressing arrow down, but disappears behind the next page (DOCX only)
https://bugs.documentfoundation.org/show_bug.cgi?id=144880 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 144878] Space character replaced with negative space after a digit as the first character RTL line
https://bugs.documentfoundation.org/show_bug.cgi?id=144878 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 144866] Almost no contrast in hovered menu item's text on Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=144866 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 144869] Feature Request for export format Similar to SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=144869 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 144865] Writer is unable to custom line height for specific DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=144865 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 144863] Input components created in dark mode in Ubuntu retain dark mode properties when exported to PDF as a fillable form.
https://bugs.documentfoundation.org/show_bug.cgi?id=144863 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 145167] Send Create Master Document Fails When Saving Document
https://bugs.documentfoundation.org/show_bug.cgi?id=145167 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145148] Crash in: libstdc++.so.6
https://bugs.documentfoundation.org/show_bug.cgi?id=145148 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 145167] Send Create Master Document Fails When Saving Document
https://bugs.documentfoundation.org/show_bug.cgi?id=145167 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145148] Crash in: libstdc++.so.6
https://bugs.documentfoundation.org/show_bug.cgi?id=145148 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140804] LibreOffice Writer shows a box / border around embedded images
https://bugs.documentfoundation.org/show_bug.cgi?id=140804 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 140804] LibreOffice Writer shows a box / border around embedded images
https://bugs.documentfoundation.org/show_bug.cgi?id=140804 --- Comment #3 from QA Administrators --- Dear terrafrost, 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 141757] Bug d'affichage en mode contraste élevé
https://bugs.documentfoundation.org/show_bug.cgi?id=141757 --- Comment #3 from QA Administrators --- Dear titubasorciere, 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 141750] LibreOffice 7.1.2.2 Hangs
https://bugs.documentfoundation.org/show_bug.cgi?id=141750 --- Comment #2 from QA Administrators --- Dear flieger, 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 136285] In LO7, the macro inspector started working incorrectly.
https://bugs.documentfoundation.org/show_bug.cgi?id=136285 --- Comment #7 from QA Administrators --- Dear Kadet, 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 136052] Exporting multiple objects as selection to bitmap in Draw exports only one of them
https://bugs.documentfoundation.org/show_bug.cgi?id=136052 --- Comment #2 from QA Administrators --- Dear Maciej Lewandowski, 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 135820] bad pivot table sheet relative reference auto-correction
https://bugs.documentfoundation.org/show_bug.cgi?id=135820 --- Comment #2 from QA Administrators --- Dear Lyndon Brown, 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 133651] FORMATTING not saved on FILESAVE in columns 65+ when cells in column only have formatting and no content
https://bugs.documentfoundation.org/show_bug.cgi?id=133651 --- Comment #2 from QA Administrators --- Dear graphite37, 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 132652] Export an image at any resolution without affecting the size
https://bugs.documentfoundation.org/show_bug.cgi?id=132652 --- Comment #3 from QA Administrators --- Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99778] UI : Click on sheet name to activate it scroll the tabs whereas it's not necessary (specific file)
https://bugs.documentfoundation.org/show_bug.cgi?id=99778 --- Comment #9 from QA Administrators --- Dear eric.coutier, 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 95336] FILESAVE Saving a Document with "#" in name (libreoffice dialogs)
https://bugs.documentfoundation.org/show_bug.cgi?id=95336 --- Comment #11 from QA Administrators --- Dear Lukas, 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 78035] No clear distinction in grid settings, saved/loaded with document, and set in the options
https://bugs.documentfoundation.org/show_bug.cgi?id=78035 --- Comment #11 from QA Administrators --- Dear Miroslav Fitz, 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 45488] Impress FILEOPEN: fontart object incorrect in pptx presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=45488 --- Comment #12 from QA Administrators --- Dear sasha.libreoffice, 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 120586] A Track-Changes editing of a number can split it into two lines
https://bugs.documentfoundation.org/show_bug.cgi?id=120586 --- Comment #7 from QA Administrators --- Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 120311] Pivot table filter locked empty when zero rows returned
https://bugs.documentfoundation.org/show_bug.cgi?id=120311 --- Comment #10 from QA Administrators --- Dear besancon4me, 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 119986] FILESAVE DOCX The MatchEntry property of the list box ActiveX control is incorrectly saved
https://bugs.documentfoundation.org/show_bug.cgi?id=119986 --- Comment #5 from QA Administrators --- Dear Gabor Kelemen, 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 119984] FILESAVE DOCX The Enabled property of ActiveX controls is incorrectly saved
https://bugs.documentfoundation.org/show_bug.cgi?id=119984 --- Comment #3 from QA Administrators --- Dear Gabor Kelemen, 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 119982] FILEOPEN DOCX The BackColor property of ActiveX controls are incorrectly imported, when the BackStyle property: 0 – fmBackStyleTransparent
https://bugs.documentfoundation.org/show_bug.cgi?id=119982 --- Comment #5 from QA Administrators --- Dear Gabor Kelemen, 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 118300] Information related to a character is not according to the displayed character in a particular case.
https://bugs.documentfoundation.org/show_bug.cgi?id=118300 --- Comment #11 from QA Administrators --- Dear ricky.tigg, 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 112558] Single line spacing of Calibri and Times New Roman no longer calculated correctly in Calc compared to Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=112558 --- Comment #26 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140750] FORMATTING in Writer - TABLES - Paragraph - All Selected Cells are not Formatted when Using Paragraph Formatting - Line Spacing - Fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=140750 je...@iname.com changed: What|Removed |Added Resolution|INSUFFICIENTDATA|FIXED --- Comment #4 from je...@iname.com --- Tried in Version 7.1.6.2 for Linux - Bug Fixed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113506] EDITING: X axis editing problem in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=113506 --- Comment #20 from Ross Johnson --- Created attachment 175787 --> https://bugs.documentfoundation.org/attachment.cgi?id=175787=edit Line chart with x integer values The attachment, following Regina's [comment 6], shows the result choosing the "Date" category but then choosing "Day" resolution and maximum major tick interval of 100. This is not intended as a suggested workaround, just an exercise to see how close it is possible to get to a satisfying representation using the Line Chart style. It is still not a general solution but IMO proves there is no fundamental reason to prevent Line Charts representing any regular sequence of values, especially integers, preferably a new category altogether. Line Charts and Area Charts share the same underlying limitations and, while an X-Y Scatter Chart may offer a workaround for simple line chart X-axis formatting, it doesn't provide one for Area charts, which have the same limitations. An Area chart (2D and 3D) with regular interval values is a common chart presentation style that is not available in LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145168] Closing a document newly created from a template crashes LO (but no crash dump)
https://bugs.documentfoundation.org/show_bug.cgi?id=145168 --- Comment #2 from Jon R Kibler --- Note: I suspect that bugs 145167 https://bugs.documentfoundation.org/show_bug.cgi?id=145167 and 145168 https://bugs.documentfoundation.org/show_bug.cgi?id=145168 are related. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145167] Send Create Master Document Fails When Saving Document
https://bugs.documentfoundation.org/show_bug.cgi?id=145167 --- Comment #6 from Jon R Kibler --- Note: I suspect that bugs 145167 https://bugs.documentfoundation.org/show_bug.cgi?id=145167 and 145168 https://bugs.documentfoundation.org/show_bug.cgi?id=145168 are related. Comment on previous post about reproducibility... I forgot that after creating a new master document, you have to save it before applying a template, else it may randomly crash. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145167] Send Create Master Document Fails When Saving Document
https://bugs.documentfoundation.org/show_bug.cgi?id=145167 --- Comment #5 from Jon R Kibler --- I tried replying to the email requesting additional information, but bugzilla said I wasn't an authorized participant to this thread. So, here is what I tried to email: Hi, LO definitely has full access to the mac. The login used to document the bug owns the data directory's root file system and its entire directory hierarchy, and the LO installation is owned by that user, too. Additionally, I have other users on this mac and it fails similarly for all users. Finally, I create a master document successfully by: File-->New-->Master Document Styles-->Load Styles From Template Save And it works using the same template and saves to the same directory as I used in the bug example. That is my workaround, which adds an additional step. But, it still would be best if the actual bug was fixed. Question: Why don't I get a crash dump when LO crashes? What can I do to enable one? I don't even see a place in Advanced settings (but could have missed it). Thanks! Please let me know if I can supply any additional information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145148] Crash in: libstdc++.so.6
https://bugs.documentfoundation.org/show_bug.cgi?id=145148 --- Comment #2 from Kurt --- (In reply to Julien Nabet from comment #1) > I see accessibility part with gtk in bt. > > Could you test this: > - open a terminal/console > - export SAL_USE_VCLPLUGIN=gen > - launch LO > - try to reproduce the pb > > BTW, I think you should stick to LO packages provided by your distribution. > Indeed, rpm and deb packages are more for distrib maintainers who deal with > all dependencies issues. > > You can also try LO from ppa (see > https://launchpad.net/~libreoffice/+archive/ubuntu/ppa) > > Finally you can take a look at > https://wiki.documentfoundation.org/QA/FirstSteps, it may help. Julian, Thank you, you can close this. it's no longer crashing. I believe a system update that arrived on the 15th fixed the problem. See below. I have been suffering with Base just shutting down at random when editing forms since I started trying to make a database on September 23 ( Kept losing my work ). The version with Mint was 6.4.7. So I moved to 7.1 then 7.2.2.2 hoping to fix the problem. The system update that arrived later on the fifteenth contained. 2021-10-15 14:04:01 upgrade distro-info-data:all 0.43ubuntu1.8 0.43ubuntu1.9 2021-10-15 14:04:01 upgrade xapps-common:all 2.2.3+uma 2.2.4+uma 2021-10-15 14:04:02 upgrade libxapp1:amd64 2.2.3+uma 2.2.4+uma 2021-10-15 14:04:02 upgrade gir1.2-xapp-1.0:amd64 2.2.3+uma 2.2.4+uma 2021-10-15 14:04:02 upgrade bulky:all 1.7 1.8 2021-10-15 14:04:02 upgrade libcjs-dbg:amd64 5.0.0+uma 5.0.1+uma 2021-10-15 14:04:03 upgrade libcjs0f:amd64 5.0.0+uma 5.0.1+uma 2021-10-15 14:04:03 upgrade muffin-dbg:amd64 5.0.1+uma 5.0.2+uma 2021-10-15 14:04:03 upgrade muffin:amd64 5.0.1+uma 5.0.2+uma 2021-10-15 14:04:03 upgrade libmuffin0:amd64 5.0.1+uma 5.0.2+uma 2021-10-15 14:04:03 upgrade muffin-common:all 5.0.1+uma 5.0.2+uma 2021-10-15 14:04:03 upgrade nemo-dbg:amd64 5.0.3+uma 5.0.4+uma 2021-10-15 14:04:04 upgrade nemo:amd64 5.0.3+uma 5.0.4+uma 2021-10-15 14:04:04 upgrade libnemo-extension1:amd64 5.0.3+uma 5.0.4+uma 2021-10-15 14:04:04 upgrade nemo-data:all 5.0.3+uma 5.0.4+uma 2021-10-15 14:04:04 upgrade cinnamon-dbg:amd64 5.0.5+uma 5.0.6+uma 2021-10-15 14:04:04 upgrade gir1.2-meta-muffin-0.0:amd64 5.0.1+uma 5.0.2+uma 2021-10-15 14:04:04 upgrade cinnamon-common:all 5.0.5+uma 5.0.6+uma 2021-10-15 14:04:04 upgrade cinnamon-screensaver:amd64 5.0.6+uma 5.0.7+uma 2021-10-15 14:04:05 upgrade libcscreensaver0:amd64 5.0.6+uma 5.0.7+uma 2021-10-15 14:04:05 upgrade cjs:amd64 5.0.0+uma 5.0.1+uma 2021-10-15 14:04:05 upgrade cinnamon:amd64 5.0.5+uma 5.0.6+uma 2021-10-15 14:04:05 upgrade gir1.2-nemo-3.0:amd64 5.0.3+uma 5.0.4+uma 2021-10-15 14:04:05 upgrade mintreport:all 1.2.5 1.2.5.1 its now stable for me now, no crashes. I Actually finished the forms. Thank you, sorry to bother you. Kurt -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125637] names ending in underscore characters are allowed, but incorrectly handled at the end of a command line
https://bugs.documentfoundation.org/show_bug.cgi?id=125637 --- Comment #3 from Andreas Heinisch --- The problem lies in [1], because LO makes two rounds in order to parse and generate the underlying code for the macro. It could be solved in the easy way (just add a whitespace in the code after the underscore) or the hard and clean way (check where the line does not terminate if an underscore follows) [1] https://opengrok.libreoffice.org/xref/core/basic/source/comp/scanner.cxx?r=ef38b9af#300 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145157] Soft Edges effect distorting entire image in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145157 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||79045_79...@mail.ru --- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> --- Please add a simpler example, I don't see the problem in your files anyway -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||145163 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145163 [Bug 145163] master document crashes when repositioning inserted document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145163] master document crashes when repositioning inserted document
https://bugs.documentfoundation.org/show_bug.cgi?id=145163 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||102495 CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- No repro in Windows Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b1488cd6f008049a9aaff7350deeb73cbbd535b6 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE VCL backend bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47295] Default paragraph style should be "Text body" and not "Default"
https://bugs.documentfoundation.org/show_bug.cgi?id=47295 --- Comment #37 from Gustavo --- (In reply to rscra...@gmail.com from comment #36) > LO version 7.2.1.2 > > Note: this comment uses “DPS” to mean “Default Paragraph Style”. > > In the default template (and the “Modern” template, which I think came > bundled with LO on install), none of the 2nd-level paragraph styles (one > level below the DPS or inheriting directly from DPS) has DPS set as the > “Next style”. However, the Headings style (and the Text Body style) is set > by default to have Text Body as the next style. For people who use the > template as-is, this means that the order of composition of a document will > often determine its styling: > > 1. Users who start by writing a title or heading will likely have Text Body > styled paragraphs for the rest of the document. This outcome is probably > desired. > > 2. Users who start by writing a few paragraphs and then a heading and then > another paragraph will have a few paragraphs of DPS style and a few of Text > Body style. This outcome is not desired and may cause confusion. > > > Some principles I think most people would agree with: > > A. The default template should not be designed with the assumption that > users will understand the details of style inheritance > > B. The order of composition of a document should not determine its styling > > C. If the most-commonly-used paragraph styles are set to be followed by Text > Body, the template is pushing Text Body as the main style to use for most > paragraphs > > D. Most users who *do* understand the difference between DPS and Text Body > prefer to use Text Body for most text > > E. Users who do *not* understand the difference do not care much what style > they use and just want a consistent experience > > > All of this points to the conclusion that Text Body should be the default > style selected when the Default template and Modern template are used. (A > related issue is that the name “Default Paragraph Style” may confuse users, > who will wonder why LO keeps changing the style after Headings to Text Body. > Perhaps this should be renamed to something like “Master Paragraph Style”.) Well pointed. However, this issue is here since 2012... For some reason, developers don't take this serious because is still in LO 7.2.2, among with other issues related specially to academic work (what you relate will occurs usually). I have to say, sadly, that I have to work with MS Office and to advise everyone to do the same. Thought this issue is child of a parent issue that is not taking serious the academic text production. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143392] Title on Base-Window doesn't show the name of the database.
https://bugs.documentfoundation.org/show_bug.cgi?id=143392 m.a.riosv changed: What|Removed |Added CC||jcgeff...@free.fr --- Comment #4 from m.a.riosv --- *** Bug 145177 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 145177] LO7.2 BASE : The windows doesn't show the titles of the Files
https://bugs.documentfoundation.org/show_bug.cgi?id=145177 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |DUPLICATE --- Comment #1 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 143392 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145167] Send Create Master Document Fails When Saving Document
https://bugs.documentfoundation.org/show_bug.cgi?id=145167 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru Ever confirmed|0 |1 OS|All |Mac OS X (All) Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> --- no problem Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: b1488cd6f008049a9aaff7350deeb73cbbd535b6 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded Are you sure LibreOffice has a full access to hard drive in your mac OS? Please check Security options in your macOS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145173] Unrecognized locale en_IL
https://bugs.documentfoundation.org/show_bug.cgi?id=145173 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru, ||er...@redhat.com --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Eike, you know all about locales inside LibreOffice, could you please look at it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145177] New: LO7.2 BASE : The windows doesn't show the titles of the Files
https://bugs.documentfoundation.org/show_bug.cgi?id=145177 Bug ID: 145177 Summary: LO7.2 BASE : The windows doesn't show the titles of the Files Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jcgeff...@free.fr Description: When I open a BASE file with LO7.2, the upper part of the windows shows "LibreOffice Base" only. In version LO7.1 and older versions the names of the files appeared, e.g. "MyFile - LibreOffice" Steps to Reproduce: Open à BASE file Actual Results: The opened windows shows "LibreOffice Base" (upper left part) Expected Results: "MyFile - LibreOffice" in he upper left part of the window Reproducible: Always User Profile Reset: Yes Additional Info: Other applications of LO7.2 show the file title in the upper part of the window. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138071] "Save remote" fails with "This operation is not supported on this operating system"
https://bugs.documentfoundation.org/show_bug.cgi?id=138071 --- Comment #4 from Justin L --- Adding Ssh to urlobj does wonders in a few areas (like edit account and clicking on the breadcrumb path), but it doesn't seem to help very much with this particular issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145169] Remote Save: uses "seen in directory" filename instead of existing filename
https://bugs.documentfoundation.org/show_bug.cgi?id=145169 Caolán McNamara changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | --- Comment #2 from Caolán McNamara --- the "non-remote" built-in libreoffice file dialog. (tools, options, general, use LibreOffice dialog) is a similar creation, but without the initially described problem, there the difference is the focus is given to the edit box by default, which unselects the entry in the treeview. So currently its acting a little as if the user had explicitly clicked the first entry in the treeview. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143472] FILEOPEN: pdf fails to open in draw
https://bugs.documentfoundation.org/show_bug.cgi?id=143472 --- Comment #6 from himajin100...@gmail.com --- 504 0 obj << /Filter /Standard /V 4 /R 4 /Length 128 /StrF /StdCF /StmF /StdCF /CF << /StdCF << /AuthEvent /DocOpen /Length 16 /CFM /AESV2 >> >> (snip) << /Size 505 /Root 199 0 R /Info 200 0 R /ID [ ] /DocChecksum /F5A9B059D948568B44B739E345CFE935 /Encrypt 504 0 R >> https://opengrok.libreoffice.org/xref/core/sdext/source/pdfimport/pdfparse/pdfentries.cxx?r=776a1b9b#1311 https://opengrok.libreoffice.org/xref/core/sdext/source/pdfimport/pdfparse/pdfentries.cxx?r=776a1b9b#1212 I'm not so familiar with PDF stuffs, and I don't know whether LibreOffice is doing things correctly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144777] countifs() in Calc is slower than Excel's countifs()
https://bugs.documentfoundation.org/show_bug.cgi?id=144777 --- Comment #17 from adnanbal...@gmail.com --- The daily build shows some improvement, with total calculation time for 10,000 rows reduced from 238 seconds to 203 seconds. I have noticed that in some calculations, when the string "Adapt row height" appears, a green colored progress bar is shown. But with countifs, the green progress bar does not appear. Can this be fixed? Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 459f9de8a87373c826eadab142850cc3fa578fca CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-AE (en_AE); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134426] Changing Paragraph format, editing Text and changing back leaves edited text's format unchanged
https://bugs.documentfoundation.org/show_bug.cgi?id=134426 Mike Kaganski changed: What|Removed |Added CC||johnsmithbeat...@gmail.com --- Comment #26 from Mike Kaganski --- *** Bug 144638 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 144638] Writer unexpectedly and silently applies direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=144638 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #16 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 134426 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134426] Changing Paragraph format, editing Text and changing back leaves edited text's format unchanged
https://bugs.documentfoundation.org/show_bug.cgi?id=134426 Mike Kaganski changed: What|Removed |Added CC||norb...@gmail.com --- Comment #25 from Mike Kaganski --- *** Bug 145176 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 145176] Overtyping selection creates unintended direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=145176 Mike Kaganski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 134426 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145176] New: Overtyping selection creates unintended direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=145176 Bug ID: 145176 Summary: Overtyping selection creates unintended direct formatting Product: LibreOffice Version: 7.1.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: norb...@gmail.com Description: When selecting some text and then typing a replacement text the replacement text will receive direct formatting with the same font and font size as the underlying paragraph. However, selecting the text, pressing DEL and then inserting the replacement text will behave correctly and not create the direct formatting. Steps to Reproduce: 1. Create an empty document 2. Add some text by keyboard 3. Format the text Arial bold 10 pt 4. Create a new paragraph style from that paragraph, name it ProblemStyle 5. Select a word from your paragraph text by double clicking it 6. Type some other word to replace the selection 7. Open the style inspector and see that the replacement text is now formatted with direct formatting with the same font and size as before 8. Change the font size of the ProblemStyle paragraph style to 6 pt 9. Notice that the entire paragraph changes into 6pt, except for the replacement text (which is to be expected since it received a direct formatting, which is the actual but. This step is only mentioned to demonstrate how dangerous this bug is.) Actual Results: The replacement text received direct formatting with the same font and size. Thus, this bug is really hard to see on first sight! If someone wants to change the paragraph style later, all the places where such replacements have been done will not follow the new style! This can create huge problems for book authors! Expected Results: Instead, the replacement text should have been inserted without receiving direct formatting. Interesting enough, this is what happens if one carries out the same operation in a two-step manner: first delete the original text, then insert the replacement text. Thus, the problem seems to be connected with overtyping a selection. Reproducible: Always User Profile Reset: No Additional Info: The behavior could only be observed when working with a styled paragraph different from the default style and different from the default Body text style. Therefore steps 3 and 4 in the above reproduction list are important. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145171] Use of questionable polygon optimization on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=145171 Eyal Rozenberg changed: What|Removed |Added Summary|Repeated complaints about |Use of questionable polygon |"Optimizing could fail with |optimization on startup |beziers"| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145175] ConfigManager is not empty when quitting LO Writer (and LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=145175 --- Comment #1 from Eyal Rozenberg --- Build info: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: c998691e22ceda15c89d55cf7005201f0392dadb CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-14_11:54:20 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145174] Attempt to dlopen() a missing libgcc3_java.so + searching for an .so by dlopen()'s
https://bugs.documentfoundation.org/show_bug.cgi?id=145174 --- Comment #1 from Eyal Rozenberg --- Build info: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: c998691e22ceda15c89d55cf7005201f0392dadb CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-14_11:54:20 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145175] New: ConfigManager is not empty when quitting LO Writer (and LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=145175 Bug ID: 145175 Summary: ConfigManager is not empty when quitting LO Writer (and LO) Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Blocks: 140879 If you run a recent daily build of LO (see build info below), create a new LO writer document, then quite, you get a console message saying: warn:unotools.config:4895:4895:unotools/source/config/configmgr.cxx:153: ConfigManager not empty Now, either it's a problem that the ConfigManager is not empty, in which case it should be properly emptied; or it's not a problem in which case the warning needs to be removed as console noise. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140879 [Bug 140879] [META] Console noise -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Eyal Rozenberg changed: What|Removed |Added Depends on||145175 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145175 [Bug 145175] ConfigManager is not empty when quitting LO Writer (and LO) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Bug 140879 depends on bug 140883, which changed state. Bug 140883 Summary: textcvt.cxx is "Missing rtl_TextToUnicodeConverter" on startup https://bugs.documentfoundation.org/show_bug.cgi?id=140883 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140883] textcvt.cxx is "Missing rtl_TextToUnicodeConverter" on startup
https://bugs.documentfoundation.org/show_bug.cgi?id=140883 Eyal Rozenberg changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- --- Comment #5 from Eyal Rozenberg --- (In reply to Xisco Faulí from comment #4) > Closing as RESOLVED NOTABUG based on comment 3 Xisco, I explained why it is a bug in my opening comment. To reiterate in light of comment 3: Yes, it's ok to print warnings when something is wrong/missing. But - something being wrong/missing is a bug, by definition. And if the "unicode converter" isn't really missing, then the warning is just console noise and should be avoided. So the only question is which kind of bug this is, not whether it's a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145174] New: Attempt to dlopen() a missing libgcc3_java.so + searching for an .so by dlopen()'s
https://bugs.documentfoundation.org/show_bug.cgi?id=145174 Bug ID: 145174 Summary: Attempt to dlopen() a missing libgcc3_java.so + searching for an .so by dlopen()'s Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Blocks: 140879 When I run a daily build and create a new Writer document, I get, along with other console noise, two lines about failed attempts to open a Java-related shared object: warn:sal.osl:4895:4895:sal/osl/unx/module.cxx:155: dlopen(/opt/libreofficedev7.3/program/libjava_gcc3.so, 257): /opt/libreofficedev7.3/program/libjava_gcc3.so: cannot open shared object file: No such file or directory warn:sal.osl:4895:4895:sal/osl/unx/module.cxx:155: dlopen(/opt/libreofficedev7.3/program/libgcc3_java.so, 257): /opt/libreofficedev7.3/program/libgcc3_java.so: cannot open shared object file: No such file or directory dlopen should not be attempted on a non-existent file. Even if the file was expected to exist (which it shouldn't - everything under /opt/libreofficedev7.3/ was installed with LO 7.3's DEBs, so the contents of that directory should be known apriori) - there should still be an attempt to locate the file, then finally a dlopen() once the so has been found. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140879 [Bug 140879] [META] Console noise -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Eyal Rozenberg changed: What|Removed |Added Depends on||145174 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145174 [Bug 145174] Attempt to dlopen() a missing libgcc3_java.so + searching for an .so by dlopen()'s -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Eyal Rozenberg changed: What|Removed |Added Depends on||145173 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145173 [Bug 145173] Unrecognized locale en_IL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145173] New: Unrecognized locale en_IL
https://bugs.documentfoundation.org/show_bug.cgi?id=145173
Bug ID: 145173
Summary: Unrecognized locale en_IL
Product: LibreOffice
Version: 7.3.0.0 alpha0+ Master
Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
Severity: minor
Priority: medium
Component: LibreOffice
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: eyalr...@gmx.com
Blocks: 140879
When I start LO (using a daily build, see below) and create a new writer
document, the following is printed to the console about 13 times or so:
warn:svtools.misc:2814:2814:svtools/source/misc/langtab.cxx:239: Language: 0x9
with unknown name, so returning lang-tag of: English {en}
I'm not quite sure why that is; perhaps it has something to do with my locale,
en_IL (see build info below). I also don't know whether this is purely console
noise or whether it might be causing other problems.
Build info:
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: c998691e22ceda15c89d55cf7005201f0392dadb
CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: en-US (en_IL); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time:
2021-10-14_11:54:20
Calc: threaded
PS - en_IL is a "legit" locale; see
https://www.localeplanet.com/icu/en-IL/index.html
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=140879
[Bug 140879] [META] Console noise
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145172] New: URL not recognised when "autocorrection > detect url" is ON (both modes) and autocorrection is on
https://bugs.documentfoundation.org/show_bug.cgi?id=145172 Bug ID: 145172 Summary: URL not recognised when "autocorrection > detect url" is ON (both modes) and autocorrection is on Product: LibreOffice Version: 7.2.1.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nicolas.mic...@telecom-paris.fr Description: Every URLs i enter are not recognised (transformed to URL objects like Ctrl+k) when : - "autocorrection > detect url" is ON (both modes) - autocorrection is on (while typing) and also i tested "autocorrection > apply" URL DETECTION WORKS WHEN "ENTER" or "TAB", but not if i press "SPACE" Steps to Reproduce: 1. type an URL, then SPACE Actual Results: nothing Expected Results: url converts to url object (like if i have pressed Ctrl+K) Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.1.2 / LibreOffice Community Build ID: 2c9f9a7aa7c967a1b7ec3448959cff87b32f6580 CPU threads: 8; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded it worked on libreoffice writer 6 : i just updated to v7 few days ago, then it doesnt work anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145171] Repeated complaints about "Optimizing could fail with beziers"
https://bugs.documentfoundation.org/show_bug.cgi?id=145171 --- Comment #1 from Eyal Rozenberg --- Build info: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: c998691e22ceda15c89d55cf7005201f0392dadb CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-14_11:54:20 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145171] New: Repeated complaints about "Optimizing could fail with beziers"
https://bugs.documentfoundation.org/show_bug.cgi?id=145171 Bug ID: 145171 Summary: Repeated complaints about "Optimizing could fail with beziers" Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Blocks: 140879 What running a daily build (via the libreofficedev7.3 binary), I get - within some other console noise - this message, repeated 7 times: warn:legacy.tools:2814:2814:tools/source/generic/poly.cxx:1033: Optimizing could fail with beziers! Obviously this should not happen. I assume some polygons are being drawn - as part of the LO UI, not a document of mine. So, if LO is using some failure-prone polygon drawing routine - it should be fixed, or not used. And if it's not really failure-prone in this context, this should be determined and no warning issued. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140879 [Bug 140879] [META] Console noise -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Eyal Rozenberg changed: What|Removed |Added Depends on||145171 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145171 [Bug 145171] Repeated complaints about "Optimizing could fail with beziers" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124807] Cell formatting and calculations of Sexagesimal (base 60) angular measurement, aka DMS
https://bugs.documentfoundation.org/show_bug.cgi?id=124807 Wolfgang Jäger changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||1870 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141870] Fractional formatting: Sequence of preferred denominators (Base 2 mainly); also Writer TextFields
https://bugs.documentfoundation.org/show_bug.cgi?id=141870 Wolfgang Jäger changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||4807 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124807] Cell formatting and calculations of Sexagesimal (base 60) angular measurement, aka DMS
https://bugs.documentfoundation.org/show_bug.cgi?id=124807 --- Comment #5 from Wolfgang Jäger --- See tdf#141870 A sufficiently general implementation of the feature I requested there would include the enhancement requested here as a use-case. This way we wouldn't need a new formatting feature here and, one there, and probably... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140881] LO fails opening some WOFF and TTF files
https://bugs.documentfoundation.org/show_bug.cgi?id=140881 --- Comment #7 from Eyal Rozenberg --- With a newer build, I get a sequence of such warnings twice: ``` warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:429: Unimplemented mac encoding 18432 to unicode conversion for fontname Kammer warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_400ffc-webfont.woff": 6 warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_400ffc-webfont.woff2": 6 warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_r_600ffc-webfont.woff": 6 warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_r_600ffc-webfont.woff2": 6 warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_w_500ffc-webfont.woff": 6 warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_w_500ffc-webfont.woff2": 6 warn:sal.textenc:2797:2797:sal/textenc/textcvt.cxx:187: Missing rtl_TextToUnicodeConverter warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:429: Unimplemented mac encoding 18432 to unicode conversion for fontname YoavKtav Black warn:vcl.fonts:2797:2797:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/windows/ITC Zapf Dingbats.ttf": 6 warn:vcl.gdi:2814:2814:vcl/source/font/fontcharmap.cxx:223: Format 4 char should not be 0x warn:sal.textenc:2814:2814:sal/textenc/textcvt.cxx:187: Missing rtl_TextToUnicodeConverter warn:sal.textenc:2814:2814:sal/textenc/textcvt.cxx:187: Missing rtl_TextToUnicodeConverter warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:429: Unimplemented mac encoding 18432 to unicode conversion for fontname Kammer warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_400ffc-webfont.woff": 6 warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_400ffc-webfont.woff2": 6 warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_r_600ffc-webfont.woff": 6 warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_r_600ffc-webfont.woff2": 6 warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_w_500ffc-webfont.woff": 6 warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/freefonts.co.il/OS-Aran-Free-V2.00/OS-Aran-FFC-Webfonts/os_aran_w_500ffc-webfont.woff2": 6 warn:sal.textenc:2814:2814:sal/textenc/textcvt.cxx:187: Missing rtl_TextToUnicodeConverter warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:429: Unimplemented mac encoding 18432 to unicode conversion for fontname YoavKtav Black warn:vcl.fonts:2814:2814:vcl/unx/generic/fontmanager/fontmanager.cxx:665: Could not OpenTTFont "/usr/local/share/fonts/windows/ITC Zapf Dingbats.ttf": 6 ``` -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Bug 140879 depends on bug 140878, which changed state. Bug 140878 Summary: Config manager fails to parse registrymodifications.xcu https://bugs.documentfoundation.org/show_bug.cgi?id=140878 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140878] Config manager fails to parse registrymodifications.xcu
https://bugs.documentfoundation.org/show_bug.cgi?id=140878 Eyal Rozenberg changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #2 from Eyal Rozenberg --- Can no longer reproduce (with master build 2021-10-14_11.54.20), so resolving. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145169] Remote Save: uses "seen in directory" filename instead of existing filename
https://bugs.documentfoundation.org/show_bug.cgi?id=145169 --- Comment #1 from Justin L --- IMPL_LINK_NOARG ( RemoteFilesDialog, OkHdl, weld::Button&, void ) bSelected is pretty much always true. But it should be irrelevant, because the filename box is tied to it if a real file is selected. (For example, just browsing through the folders also ends up with strange results when a folder is automatically "selected".) It looks like this dialog is used for other things? Opening for one, and PATH-ONLY dialog somehow? Perhaps it needs to be: if( !bSelected || (m_eMode == REMOTEDLG_MODE_SAVE && m_eType == REMOTEDLG_TYPE_FILEDLG) ) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145170] Anomalous Behaviour Concerning Mixing Ctrl+F5 Keyboard Shortcut and Hide/Show Panel Button
https://bugs.documentfoundation.org/show_bug.cgi?id=145170 Radish changed: What|Removed |Added CC||babelfish0...@hotmail.com --- Comment #1 from Radish --- I should add that I'm a relatively new user of LibreOffice and that I really don't know if LibreOffice 7.2.1.2 is the earliest version which is affected by this behaviour. (Apologies.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145170] New: Anomalous Behaviour Concerning Mixing Ctrl+F5 Keyboard Shortcut and Hide/Show Panel Button
https://bugs.documentfoundation.org/show_bug.cgi?id=145170 Bug ID: 145170 Summary: Anomalous Behaviour Concerning Mixing Ctrl+F5 Keyboard Shortcut and Hide/Show Panel Button Product: LibreOffice Version: 7.2.1.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: babelfish0...@hotmail.com In Writer there are several ways that the Sidebar Panel can be hidden or shown. One of those ways is to use the keyboard shortcut Ctrl+F5 to toggle Hide/Show. Another way is to use the Panel Hide/Show button. However, there is what I would think is anomalous behaviour if these two methods are mixed as follows: 1. Hide the Panel using the Hide/Show button. This retracts the entire Panel with exception that the Hide/Show button is still visible. 2. Now lets say you want to open the Panel again but this time you use the Ctrl+F5 keyboard shortcut to show the Panel. What actually happens is as follows: (a) The first press of Ctrl+F5 causes the Panel to fully retract i.e. the Panel Hide/Show button is retracted. (b) You think something is wrong as you wanted to show the Panel so you press Ctrl+F5 a second time and then the Panel extends outwards and is shown again (which was what you were trying to achieve at the outset). So it would seem that the Ctrl+F5 shortcut interprets a Panel hidden via the Panel Hide/Show button as being a Panel that is not in fact hidden at all. So, in that instance the first Ctrl+F5 keypress hides the Panel. I don't think things should be happening in that way. Ctrl+F5 routine should recognise when the panel has already been hidden by the Panel Hide/Show button and should show the full Panel on the first Ctrl+F5 keypress. I would regard that as 'expected behaviour'. The same 'issue' occurs in at least Calc, Draw and Impress. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39936] UI: Right Click on Row/Column -> Insert Copied Cells... (paste + shift cells in one click)
https://bugs.documentfoundation.org/show_bug.cgi?id=39936 --- Comment #58 from dongshili --- Although this feature is added to "selective paste", when performing the cut operation, the original row or column is not deleted after the move. This should be improved, only the original row or column is deleted after the move. In addition, I hope to separate the secondary page from the selective paste and add it to the right menu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143886] Consider removing Attribute Blinking in Find and Replace dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=143886 lol changed: What|Removed |Added Summary|Remove Attribute Blinking |Consider removing Attribute |in Find and Replace dialog |Blinking in Find and ||Replace dialog --- Comment #2 from lol --- Yes, you are right. Blinking attributes are present in LO => 7. You can find them. Now the question is: Is that still needed? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144988] Fontwork has wrong size text, if it has more than one paragraph and font size is too large
https://bugs.documentfoundation.org/show_bug.cgi?id=144988 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de |desktop.org | Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144988] Fontwork has wrong size text, if it has more than one paragraph and font size is too large
https://bugs.documentfoundation.org/show_bug.cgi?id=144988 --- Comment #1 from Regina Henschel --- Created attachment 175786 --> https://bugs.documentfoundation.org/attachment.cgi?id=175786=edit Example for wrong rendering The two Fontwork shapes have the same geometry. Only difference is, that one has the long paragraph as first paragraph and the other the short paragraph. I think, the error is in lines #226 to #229 in EnhancedCustomShapeFontWork.cxx. There the value (<1.0) from the first paragraph in fScalingFactor is replaced with the value (>1.0) from the second paragraph. But the "<1.0" value in fScalingFactor needs to be kept, because it indicates, that the rendering font size has to be reduced. I have an idea for a solution, a patch will come. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142382] Bottom line of wrap 'Parallel' makes line break instead of gap
https://bugs.documentfoundation.org/show_bug.cgi?id=142382 --- Comment #5 from Marie Z --- Created attachment 175785 --> https://bugs.documentfoundation.org/attachment.cgi?id=175785=edit Video showing reproduction of the bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125257] [META] Tip of the day
https://bugs.documentfoundation.org/show_bug.cgi?id=125257 Bug 125257 depends on bug 143629, which changed state. Bug 143629 Summary: Multiple Tips of the day https://bugs.documentfoundation.org/show_bug.cgi?id=143629 What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143629] Multiple Tips of the day
https://bugs.documentfoundation.org/show_bug.cgi?id=143629 lol changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #3 from lol --- I mean if you open three files via Windows Explorer, you get three Totd. If you open 15 files, you get 15 Totd. So you have to close 15 Totd. Displaying one Todt should be enough. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142382] Bottom line of wrap 'Parallel' makes line break instead of gap
https://bugs.documentfoundation.org/show_bug.cgi?id=142382 --- Comment #4 from Marie Z --- Created attachment 175784 --> https://bugs.documentfoundation.org/attachment.cgi?id=175784=edit Screenshot of regular text wrapped around image -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142382] Bottom line of wrap 'Parallel' makes line break instead of gap
https://bugs.documentfoundation.org/show_bug.cgi?id=142382 --- Comment #3 from Marie Z --- Created attachment 175783 --> https://bugs.documentfoundation.org/attachment.cgi?id=175783=edit Screenshot of different positions of the rectangle -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142382] Bottom line of wrap 'Parallel' makes line break instead of gap
https://bugs.documentfoundation.org/show_bug.cgi?id=142382 --- Comment #2 from Marie Z --- I was able to reproduce this problem in 7.2.1.2 (x64) See attached video and screenshot. Steps to reproduce - using the original attached file: 1. Open the ParallelWrapNotLastLine.odt file in Writer 2. Left click on the blue rectangle shape to select it. 3. Use keyboard arrows to move the rectangle down 4. Observe that the lowest line affected by the wrap is correctly interrupted by the rectangle (same as all the affected lines of text above) but in most positions continues on a new line instead of on the other side of the rectangle. Actual result: see step 4 Expected result: Lowest affected line should always continue the other side of the object. I did some follow-up tests to provide more details: - Size and shape - changing size or shape of the inserted object has no significant effect. - Position of the rectangle: The problem appears if the rectangle barely touches the space of the lowest line. The problem disappears when the rectangle reaches lower – about halfway through the line space. See attached screenshots. - Line spacing. I was able to reproduce the bug only when using Fixed line spacing. - Font - I was able to see the problem in (about 20) different fonts. Seems like the problem is not dependent on font. - Font size - More significant is probably relationship between font size and fixed line spacing value. I can reproduce the issue when font size (converted to cm) is smaller than Fixed line spacing value. The bigger the difference the easier to reproduce the problem – finding the right position for the rectangle to see the failure is easier. For example: • 16pt font and 0.8cm line spacing • 8pt font and 0.6cm line spacing • 12pt font and 1.5cm line spacing Steps to reproduce – creating new document: 1. Create new document in Writer 2. Insert a page of some text. (I copied and pasted a news article) 3. Select the text and set line spacing as fixed with value to 0.8cm and font size to 12pt 4. Insert a shape or an image around about a middle of the page 5. Right click on the inserted object - set the Wrap for that object as Parallel 6. Left click on the object to select it 7. Use keyboard arrows to move the object up or down 8. You can observe that lowest line of text affected by the object is sometimes “broken” – doesn’t continue on the other side of the object, but on a new line. Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-US (cs_CZ); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125477] Tabbed Compact NB incorrect refresh after using the ">>" to show hidden controls
https://bugs.documentfoundation.org/show_bug.cgi?id=125477 --- Comment #5 from V Stuart Foote --- Issue of jumping NB still present, Tabbed NB and Tabbed Compact NB on Windows build of 7.2.2 Version: 7.2.2.1 (x64) / LibreOffice Community Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; 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 140557] NB Tabbed interface not using whole width of the NB to show controls
https://bugs.documentfoundation.org/show_bug.cgi?id=140557 V Stuart Foote changed: What|Removed |Added Summary|NB Tabbed interface not |NB Tabbed interface not |using whole width of the|using whole width of the NB |window to show icons when |to show controls |maximized. | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140557] NB Tabbed interface not using whole width of the window to show icons when maximized.
https://bugs.documentfoundation.org/show_bug.cgi?id=140557 --- Comment #9 from V Stuart Foote --- attachment 175773 of issue from dupe bug 145164 on Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.4.150-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 141465, which changed state. Bug 141465 Summary: Notebookbar items aren't shown by default even if they'd fit https://bugs.documentfoundation.org/show_bug.cgi?id=141465 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107190] [META] Notebookbar window resize issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107190 Bug 107190 depends on bug 141465, which changed state. Bug 141465 Summary: Notebookbar items aren't shown by default even if they'd fit https://bugs.documentfoundation.org/show_bug.cgi?id=141465 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140557] NB Tabbed interface not using whole width of the window to show icons when maximized.
https://bugs.documentfoundation.org/show_bug.cgi?id=140557 V Stuart Foote changed: What|Removed |Added CC||ba...@caesar.elte.hu --- Comment #8 from V Stuart Foote --- *** Bug 141465 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 141465] Notebookbar items aren't shown by default even if they'd fit
https://bugs.documentfoundation.org/show_bug.cgi?id=141465 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED CC||vstuart.fo...@utsa.edu --- Comment #5 from V Stuart Foote --- Not seeing with STR on Windows 10 build of 7.2.2, but this is affecting other os/DE *** This bug has been marked as a duplicate of bug 140557 *** -- You are receiving this mail because: You are the assignee for the bug.
