[Libreoffice-bugs] [Bug 151124] Outline folding state change does not set dirty file flag
https://bugs.documentfoundation.org/show_bug.cgi?id=151124 --- Comment #4 from Jim Raykowski --- Here is a link to a patch that sets the document as modified when outline folding state is changed: https://gerrit.libreoffice.org/c/core/+/140855 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151005] With "Option VBASupport 1" arguments should be treated as ByValue by default (not as ByRef)
https://bugs.documentfoundation.org/show_bug.cgi?id=151005 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 151028] Sparkline cell reference formula erroneous
https://bugs.documentfoundation.org/show_bug.cgi?id=151028 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 151027] Sparkline formula restrict use
https://bugs.documentfoundation.org/show_bug.cgi?id=151027 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 151193] Couldn't establish data source connection when Java 18 is installed.
https://bugs.documentfoundation.org/show_bug.cgi?id=151193 --- Comment #12 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151193] Couldn't establish data source connection when Java 18 is installed.
https://bugs.documentfoundation.org/show_bug.cgi?id=151193 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 147768] le kb de microsoft ne s'installe pas
https://bugs.documentfoundation.org/show_bug.cgi?id=147768 --- Comment #3 from QA Administrators --- Dear markus, 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 147768] le kb de microsoft ne s'installe pas
https://bugs.documentfoundation.org/show_bug.cgi?id=147768 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147756] Save docx as html: tags are not terminated, superfluous used for formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=147756 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 147756] Save docx as html: tags are not terminated, superfluous used for formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=147756 --- Comment #3 from QA Administrators --- Dear Frank Griswold, 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 147750] Font changes format in tables
https://bugs.documentfoundation.org/show_bug.cgi?id=147750 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147750] Font changes format in tables
https://bugs.documentfoundation.org/show_bug.cgi?id=147750 --- Comment #3 from QA Administrators --- Dear Adrián Martínez Mañas, 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 147747] FILESAVE PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=147747 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 147747] FILESAVE PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=147747 --- Comment #5 from QA Administrators --- Dear Gio, 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 148362] Writer changes saved files, changes have to be made every time I open a document
https://bugs.documentfoundation.org/show_bug.cgi?id=148362 --- Comment #4 from QA Administrators --- Dear Tom, 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 148347] In logical operators AND + OR blanks are inserted when cells are addressed.
https://bugs.documentfoundation.org/show_bug.cgi?id=148347 --- Comment #3 from QA Administrators --- Dear tumann2002, 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 99192] SIDEBAR: Drop down lists buttons in content panels sometimes disappear behind tab bar when resizing the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=99192 --- Comment #15 from QA Administrators --- Dear Henrik, 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 95568] FILEOPEN Calc seems to swap width and height of picture
https://bugs.documentfoundation.org/show_bug.cgi?id=95568 --- Comment #10 from QA Administrators --- Dear GUTH Christophe, 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 89816] Image anchored to paragraph doesn't move back after entering and deleting a new paragraph above
https://bugs.documentfoundation.org/show_bug.cgi?id=89816 --- Comment #11 from QA Administrators --- Dear rbruenner, 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 87828] Partial circular objects incorrectly positioned on page
https://bugs.documentfoundation.org/show_bug.cgi?id=87828 --- Comment #7 from QA Administrators --- Dear Jozef Riha, 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 86126] ODT blank pages appearing, possibly related to images anchor
https://bugs.documentfoundation.org/show_bug.cgi?id=86126 --- Comment #26 from QA Administrators --- Dear Nikos, 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 49075] EDITING: mouse selection is cleared on mouse click (Mouse button 2 pasting)
https://bugs.documentfoundation.org/show_bug.cgi?id=49075 --- Comment #6 from QA Administrators --- Dear q9, 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 48761] text overflows the shape margin in imported ms word document
https://bugs.documentfoundation.org/show_bug.cgi?id=48761 --- Comment #10 from QA Administrators --- Dear Jozef Riha, 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 136389] Selection drag-and-drop with Option key copying instead of shifting cells in Calc on Mac 6.4.6
https://bugs.documentfoundation.org/show_bug.cgi?id=136389 --- Comment #2 from QA Administrators --- Dear JerryS, 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 135658] Column width value on side bar is larger than table size, as single column table and alignment to center
https://bugs.documentfoundation.org/show_bug.cgi?id=135658 --- Comment #5 from QA Administrators --- Dear sawakaze, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128622] Impress: Increase indent has different effect on list items than in Writer --> cannot demote/promote
https://bugs.documentfoundation.org/show_bug.cgi?id=128622 --- Comment #6 from QA Administrators --- Dear kdedk, 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 133512] Animation controls: a disabled option can be activated through the dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=133512 --- Comment #3 from QA Administrators --- Dear JBrown, 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 151203] Inconsistence behaviour of tab-key
https://bugs.documentfoundation.org/show_bug.cgi?id=151203 Dieter changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #3 from Dieter --- Not a duplicate of 150848. Back to UNCONFIRMED. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151262] Crash on justified Arabic/Persian text in Impress exported to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151262 Hossein changed: What|Removed |Added Keywords||haveBacktrace --- Comment #1 from Hossein --- Tested with the latest LO Dev 7.5 master (debug build): Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 2a7fcaf582df3ada57ca519b50e29011973a1b6f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Backtrace created using Qt Creator: 1 __pthread_kill_implementation pthread_kill.c 44 0x779e1a7c 2 __pthread_kill_internal pthread_kill.c 78 0x779e1a7c 3 __GI___pthread_kill pthread_kill.c 89 0x779e1a7c 4 __GI_raise raise.c 26 0x7798d476 5 __GI_abort abort.c 79 0x779737f3 6 __assert_fail_base assert.c 92 0x7797371b 7 __GI___assert_fail assert.c 101 0x77984e96 8 ImplSubPixelToLogic map.cxx 290 0x7fffeef06406 9 OutputDevice::SubPixelToLogic map.cxx 1189 0x7fffeef0b8e9 10 vcl::PDFWriterImpl::drawHorizontalGlyphs pdfwriter_impl.cxx 6373 0x7fffef101c19 11 vcl::PDFWriterImpl::drawLayout pdfwriter_impl.cxx 6745 0x7fffef103c25 12 vcl::PDFWriterImpl::drawTextArray pdfwriter_impl.cxx 6957 0x7fffef104fa4 13 vcl::PDFWriter::DrawTextArray pdfwriter.cxx 89 0x7fffef0c51fe 14 vcl::PDFWriterImpl::playMetafile pdfwriter_impl2.cxx 816 0x7fffef0cb959 15 vcl::PDFWriter::PlayMetafile pdfwriter.cxx 466 0x7fffef0c63bf 16 PDFExport::ImplExportPage pdfexport.cxx 1139 0x7fffc56abdb5 17 PDFExport::ExportSelection pdfexport.cxx 248 0x7fffc56a6714 18 PDFExport::Export pdfexport.cxx 994 0x7fffc56aabd3 19 PDFFilter::implExport pdffilter.cxx 185 0x7fffc56bc2ae 20 PDFFilter::filter pdffilter.cxx 248 0x7fffc56bce8b 21 SfxObjectShell::ExportTo objstor.cxx 2494 0x74b927db 22 SfxObjectShell::SaveTo_Impl objstor.cxx 1562 0x74b8c1f4 23 SfxObjectShell::PreDoSaveAs_Impl objstor.cxx 2981 0x74b95670 24 SfxObjectShell::CommonSaveAs_Impl objstor.cxx 2771 0x74b940d8 25 SfxObjectShell::APISaveAs_Impl objserv.cxx 318 0x74b711b3 26 SfxBaseModel::impl_store sfxbasemodel.cxx 3146 0x74bef95c 27 SfxBaseModel::storeToURL sfxbasemodel.cxx 1782 0x74be6c30 28 SfxStoringHelper::GUIStoreModel guisaveas.cxx 1678 0x74b4bbee 29 SfxObjectShell::ExecFile_Impl objserv.cxx 970 0x74b758e0 30 SfxStubSfxObjectShellExecFile_Impl sfxslots.hxx 207 0x74b70452 31 SfxDispatcher::Call_Impl dispatch.cxx 254 0x7482ee0c 32 SfxDispatcher::Execute_ dispatch.cxx 753 0x74832340 33 SfxBindings::Execute_Impl bindings.cxx 1060 0x7481d8af 34 SfxDispatchController_Impl::dispatch unoctitm.cxx 701 0x748ec1ae 35 SfxOfficeDispatch::dispatch unoctitm.cxx 263 0x748e9fb9 36 framework::GenericToolbarController::ExecuteHdl_Impl generictoolbarcontroller.cxx 332 0x75dc40bb 37 framework::GenericToolbarController::LinkStubExecuteHdl_Impl generictoolbarcontroller.cxx 323 0x75dc4055 38 Link::Call link.hxx 111 0x7fffeeccc923 39 ImplHandleUserEvent winproc.cxx 2287 0x7fffeecc9704 40 ImplWindowFrameProc winproc.cxx 2857 0x7fffeeccb5b2 41 SalFrame::CallCallback salframe.hxx 306 0x7fffef779b56 42 SalGenericDisplay::ProcessEvent gendisp.cxx 66 0x7fffef7a19e5 43 operator() salusereventlist.cxx 119 0x7fffef34c70a 44 SalUserEventList::DispatchUserEvents salusereventlist.cxx 120 0x7fffef34c9e3 45 SalGenericDisplay::DispatchInternalEvent gendisp.cxx 51 0x7fffef7a1951 46 SalX11Display::Yield saldisp.cxx 1896 0x7fffe4ef0b09 47 DisplayYield saldisp.cxx 381 0x7fffe4ee84f3 48 (anonymous namespace)::YieldEntry::HandleNextEvent saldata.cxx 562 0x7fffe4ee30ef 49 SalXLib::Yield saldata.cxx 658 0x7fffe4ee3983 50 X11SalInstance::DoYield salinst.cxx 192 0x7fffe4f06ec5 51 ImplYield svapp.cxx 475 0x7fffef40dbfc 52 Application::Yield svapp.cxx 559 0x7fffef40e8de 53 Application::Execute svapp.cxx 453 0x7fffef40d89c 54 desktop::Desktop::Main app.cxx 1604 0x77bf7e44 55 ImplSVMain svmain.cxx 203 0x7fffef42d5df 56 SVMain svmain.cxx 235 0x7fffef42d708 57 soffice_main sofficemain.cxx 94 0x77c62323 58 sal_main main.c 51 0x4a60 59 main main.c 49 0x4a42 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151262] Crash on justified Arabic/Persian text in Impress exported to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151262 Hossein changed: What|Removed |Added Blocks||150285, 105537 CC||kha...@aliftype.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105537 [Bug 105537] [META] Assertion failed crashes https://bugs.documentfoundation.org/show_bug.cgi?id=150285 [Bug 150285] [META] Problems with Justified Arabic/Persian text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150285] [META] Problems with Justified Arabic/Persian text
https://bugs.documentfoundation.org/show_bug.cgi?id=150285 Hossein changed: What|Removed |Added Depends on||151262 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151262 [Bug 151262] Crash on justified Arabic/Persian text in Impress exported to PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Hossein changed: What|Removed |Added Depends on||151262 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151262 [Bug 151262] Crash on justified Arabic/Persian text in Impress exported to PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151262] New: Crash on justified Arabic/Persian text in Impress exported to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151262 Bug ID: 151262 Summary: Crash on justified Arabic/Persian text in Impress exported to PDF Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 182777 --> https://bugs.documentfoundation.org/attachment.cgi?id=182777=edit justified Arabic/Persian text in an Impress slide Description: When exporting an Impress file containing justified Arabic/Persian text to PDF, LibreOffice Impress crashes. Steps to Reproduce: 1. Open the attached "justified-test.odp" file 2. Export it to PDF Alternatively, you can run this from command line: instdir/program/soffice --headless --convert-to pdf justified-test.odp Actual Results: LibreOffice Impress crashes Expected Results: LibreOffice should not crash, and a PDF output should be generated Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Fun fact: This was a slide with the justified Arabic/Persian text inside my presentation on Justified Arabic/Persian text for LibOCon 2022. :-) Console output: soffice.bin: /home/hossein/Projects/libreoffice/core/vcl/source/outdev/map.cxx:290: tools::Long ImplSubPixelToLogic(bool, double, tools::Long, tools::Long, tools::Long): Assertion `!bCheck || rtl_math_approxValue(n) == rtl_math_approxValue(static_cast(nRet) * nMapNum * nDPI / nMapDenom)' failed. Unspecified Application Error Fatal exception: Signal 6 Stack: /home/hossein/Projects/libreoffice/core/instdir/program/libuno_sal.so.3(+0xae2e3)[0x7f54f38ca2e3] /home/hossein/Projects/libreoffice/core/instdir/program/libuno_sal.so.3(+0xae51b)[0x7f54f38ca51b] /home/hossein/Projects/libreoffice/core/instdir/program/libuno_sal.so.3(+0xae860)[0x7f54f38ca860] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f54f332d520] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7f54f3381a7c] /lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f54f332d476] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7f54f33137f3] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0xdd67b2)[0x7f54eaceb7b2] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x26)[0x7f54eadac8aa] /home/hossein/Projects/libreoffice/core/instdir/program/libsofficeapp.so(+0x3a225)[0x7f54f3596225] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0xeb834e)[0x7f54eadcd34e] /home/hossein/Projects/libreoffice/core/instdir/program/libuno_sal.so.3(+0x2039d)[0x7f54f383c39d] /home/hossein/Projects/libreoffice/core/instdir/program/libuno_sal.so.3(+0xae825)[0x7f54f38ca825] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f54f332d520] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7f54f3381a7c] /lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f54f332d476] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7f54f33137f3] /lib/x86_64-linux-gnu/libc.so.6(+0x2871b)[0x7f54f331371b] /lib/x86_64-linux-gnu/libc.so.6(+0x39e96)[0x7f54f3324e96] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0x991406)[0x7f54ea8a6406] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0x9968e9)[0x7f54ea8ab8e9] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0xb8cc19)[0x7f54eaaa1c19] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0xb8ec25)[0x7f54eaaa3c25] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0xb8ffa4)[0x7f54eaaa4fa4] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(_ZN3vcl9PDFWriter13DrawTextArrayERK5PointRKN3rtl8OUStringEN4o3tl4spanIKiEENS9_IKhEEii+0x66)[0x7f54eaa651fe] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(+0xb56959)[0x7f54eaa6b959] /home/hossein/Projects/libreoffice/core/instdir/program/libvcllo.so(_ZN3vcl9PDFWriter12PlayMetafileERK11GDIMetaFileRKNS0_19PlayMetafileContextEPNS_16PDFExtOutDevDataE+0x45)[0x7f54eaa663bf] /home/hossein/Projects/libreoffice/core/instdir/program/../program/libpdffilterlo.so(+0x48db5)[0x7f54d47a1db5] /home/hossein/Projects/libreoffice/core/instdir/program/../program/libpdffilterlo.so(+0x43714)[0x7f54d479c714] /home/hossein/Projects/libreoffice/core/instdir/program/../program/libpdffilterlo.so(+0x47bd3)[0x7f54d47a0bd3] /home/hossein/Projects/libreoffice/core/instdir/program/../program/libpdffilterlo.so(+0x592ae)[0x7f54d47b22ae] /home/hossein/Projects/libreoffice/core/instdir/program/../program/libpdffilterlo.so(+0x59e8b)[0x7f54d47b2e8b] /home/hossein/Projects/libreoffice/core/instdir/program/libsfxlo.so(_ZN14SfxObjectShell8ExportToER9SfxMedium+0xc75)[0x7f54f05327db]
[Libreoffice-bugs] [Bug 140881] LO fails opening WOFF and WOFF2 fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=140881 --- Comment #20 from Eyal Rozenberg --- (In reply to خالد حسني from comment #19) > Supporting such fonts will require at least a couple of > extra dependencies for very little gain since Linux system are the only > systems that allow installing these fonts. I don't have a strong opinion on this. Although - the dependency could be in Linux only, i.e. only use the dependencies when building on Linux. > FontConfig does not provide a way to distinguish WOFF/WOFF2 from regular > fonts, they are reported as their contained font >,we have no way to > filter them out... other than sniffing the fonts And would it not makes sense to do this sniffing when we fail to load TTF fonts? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151193] Couldn't establish data source connection when Java 18 is installed.
https://bugs.documentfoundation.org/show_bug.cgi?id=151193 --- Comment #11 from Rajasekaran Karunanithi --- (In reply to Timur from comment #10) > Both JRE 8 and JDK 18 and 19 are detected and work in my Win 10. > Missing is a result of LO user profile folder rest, rename or delete. > https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile Which build are you using LO 7.4 or 7.5 alpha.Because in 7.4 it works fine but only I am facing this problem in 7.5 alpha. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125110] CalcSpreadsheet: issues converting broken .CSV of a bad generator
https://bugs.documentfoundation.org/show_bug.cgi?id=125110 Eike Rathke changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125110] CalcSpreadsheet: issues converting broken .CSV of a bad generator
https://bugs.documentfoundation.org/show_bug.cgi?id=125110 Eike Rathke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1211 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151261] FILEOPEN DOCX STD Drop Down List does not work with "Choose an item." default entry
https://bugs.documentfoundation.org/show_bug.cgi?id=151261 --- Comment #1 from Regina Henschel --- "If you insert a drop-drop-list content control in Writer" should be "If you insert a drop-drop-list content control in Word" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151261] New: FILEOPEN DOCX STD Drop Down List does not work with "Choose an item." default entry
https://bugs.documentfoundation.org/show_bug.cgi?id=151261 Bug ID: 151261 Summary: FILEOPEN DOCX STD Drop Down List does not work with "Choose an item." default entry Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de CC: vmik...@collabora.com Created attachment 182776 --> https://bugs.documentfoundation.org/attachment.cgi?id=182776=edit Drop-down-list which does not work If you insert a drop-drop-list content control in Writer, you get a list with "Choose an item." as display name and empty Value. Add some items with Display Name and Value. Save it in Word. Such document is attached. Open the document in Writer. The drop-down-list does not work. Resave the file to docx and open the document in Word. The content control is no longer a drop-down-list. This problem does not exist, if all entries in the list have Display Name and Value. The case with no Value is in the UI of Word only possible with the default item "Choose an item." Tested with Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: c3b5eea4304ad6815b491f549fce008a9630c213 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #13 from tor...@yahoo.com --- *** Bug 151203 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 151203] Inconsistence behaviour of tab-key
https://bugs.documentfoundation.org/show_bug.cgi?id=151203 tor...@yahoo.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from tor...@yahoo.com --- This bug will disappear if TabKey ignores indent —bug-enhancement 150848 *** This bug has been marked as a duplicate of bug 150848 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151260] New: Crash in: SfxItemPool::SetDefaults(std::vector > *)
https://bugs.documentfoundation.org/show_bug.cgi?id=151260 Bug ID: 151260 Summary: Crash in: SfxItemPool::SetDefaults(std::vector > *) Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rmkurz...@gmail.com This bug was filed from the crash reporting server and is br-3e94367b-89a3-420e-91e6-cb635d8dce00. = Libre Office Base crashes every time, when use report builder then selecting menu Format --> Page... This is happening on ever odb file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114039] [META] Field dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114039 Bug 114039 depends on bug 143158, which changed state. Bug 143158 Summary: Alphabetical index field: allow "Edit Index Entry" to open on double-click https://bugs.documentfoundation.org/show_bug.cgi?id=143158 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108018] [META] Writer UX bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108018 Bug 108018 depends on bug 143158, which changed state. Bug 143158 Summary: Alphabetical index field: allow "Edit Index Entry" to open on double-click https://bugs.documentfoundation.org/show_bug.cgi?id=143158 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150505] Row protections applied in 7.3.5.2 are corrupted by 7.4.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=150505 --- Comment #5 from Daniel Baran --- Some additional information: In an attempt to work around this issue, I have tried the following. Open a new blank workbook in 7.4.1.2 and unprotect an entire row. Protect the sheet then save. Opening that same file in 7.3.6.2. produces the following error: "The data could not be loaded completely because the maximum number of columns per sheet was exceeded". The file has no data yet added to it. There is no data in the "exceeded" ranges. While this is not too surprising, and does not prevent further use of the file, it might be a point of confusion regarding file sharing or exchange between users of these different program versions. Additionally, if the file from 7.4.1.2 is then saved while in 7.3.6.2, the unprotected row is then seen again as protected (i.e. no row delete option) when reopened in 7.4.1.2. So the main point here is that I cannot employ settings that work as expected in both program versions. This is the case even though none of the files contain data in the newly extended ranges. I'm willing to try further tests if anyone has suggestions. Version: 7.3.6.2 (x64) / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136612] Some Draw objects inserted into Writer's table cells move down when user adds/removes rows/cols
https://bugs.documentfoundation.org/show_bug.cgi?id=136612 --- Comment #5 from Ivan Yugov --- The problem still remains in 7.4.1.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46579] Form fields 'Image Button' do not work in Forms
https://bugs.documentfoundation.org/show_bug.cgi?id=46579
Tom changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #31 from Tom ---
More information and correction:
Correction: The mentioned workaroud does work but with restrictios, see below.
Other findings:
1. Unlike implemented for push-buttons, no "click-effect" is implemented for
image-buttons. User therefore does not clearly see whether or not a button has
been used.
2. Image-buttons used for navigation are not disabled when not applicable (i.e.
first and previous record buttons are not disabled when record-pointer at first
record of a recordset). This is working correctly when using push-buttons with
a navigation action.
3. When opening a second form without closing the current form, and then using
the first form again, navigation does not work anymore when using
image-buttons. It seems the form has lost its record-pointer.
4. When using image-buttons in combination with a called macro to perform the
required record action everything works correctly, except disabling as
mentioned before.
Used coding in that case:
sFormName = Split(thiscomponent.Title," : ")(1)'required?
oForm = thisComponent.drawpage.forms.getByName(sFormName) 'required?
oDocument = ThisComponent.CurrentController.Frame
oDispatcher = createUnoService("com.sun.star.frame.DispatchHelper")
oDispatcher.executeDispatch(oDocument ,".uno:FirstRecord","",0,Array())
Interesting finding: if in addition to image-buttons also push-buttons are
defined with action navigation on the form disabling reacts for these buttons
if the image-buttons are used.
I do realize that these issues have mainly a "cosmetic" character, since
push-buttons can be used instead, but the concerned functionality should for
image-buttons either be corrected or not made available.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147709] Libreoffice freezes on Macbook Air M1, must be restarted with force close
https://bugs.documentfoundation.org/show_bug.cgi?id=147709 --- Comment #15 from adrie...@freudianslit.com --- good idea. i will try and let you know. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151259] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=151259 V Stuart Foote changed: What|Removed |Added Component|UI |deletionRequest Summary|***SPAM*** loading issue|spam -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147709] Libreoffice freezes on Macbook Air M1, must be restarted with force close
https://bugs.documentfoundation.org/show_bug.cgi?id=147709 --- Comment #14 from Julien Nabet --- Ok and now can you reproduce the freeze and if yes, can you provide the steps it requires to reproduce this? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149000] PDF Accessibility: Checker dialog should have a "Print report" button
https://bugs.documentfoundation.org/show_bug.cgi?id=149000 --- Comment #7 from Cor Nouws --- The use of printing (to paper or PDF) is limited when the report is not clear. So the use of such a feature, depends on improving the report as such. ... separate issue But then, when improving the report, adding a 'goto' button is useful. ... separate issue Still, a pdf-report of the issues, can help with evaluation of the work (learning experience..) @olivier: do you have additional ideas? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147709] Libreoffice freezes on Macbook Air M1, must be restarted with force close
https://bugs.documentfoundation.org/show_bug.cgi?id=147709 --- Comment #13 from adrie...@freudianslit.com --- Yea not sure about that. Perhaps there were multiple causes of the crash (Skia for instance) and I deselected it while experimenting. In fact I am not sure if I have any JRE installed. The list beneath is empty. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101435] [META] Template manager bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101435 Bug 101435 depends on bug 132576, which changed state. Bug 132576 Summary: Template Dialog Category names are not intuitive https://bugs.documentfoundation.org/show_bug.cgi?id=132576 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147709] Libreoffice freezes on Macbook Air M1, must be restarted with force close
https://bugs.documentfoundation.org/show_bug.cgi?id=147709 --- Comment #12 from Julien Nabet --- (In reply to adrienne from comment #11) > So, I may have found the culprit, or perhaps its a coincidence. > LO was crashing still but I noticed I had "Use a Java runtime environment" > deselected. > > Once I selected it, no more crashing. It's quite strange that Java was unselected since when you renamed your LO directory profile (see comments 3 and 4), LO should have detected itself all the Java stuff. Of course, I suppose Java was already installed when you created the bugtracker and you had the same version as now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151259] ***SPAM*** loading issue
https://bugs.documentfoundation.org/show_bug.cgi?id=151259 m.a.riosv changed: What|Removed |Added Status|RESOLVED|CLOSED CC|miguelangelrv@libreoffice.o | |rg | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151259] ***SPAM*** loading issue
https://bugs.documentfoundation.org/show_bug.cgi?id=151259 m.a.riosv changed: What|Removed |Added Summary|loading issue |***SPAM*** loading issue CC||miguelangelrv@libreoffice.o ||rg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151259] loading issue
https://bugs.documentfoundation.org/show_bug.cgi?id=151259 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID URL|http://www.amazon.in/ | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147709] Libreoffice freezes on Macbook Air M1, must be restarted with force close
https://bugs.documentfoundation.org/show_bug.cgi?id=147709 adrie...@freudianslit.com changed: What|Removed |Added Resolution|INSUFFICIENTDATA|--- Status|RESOLVED|REOPENED --- Comment #11 from adrie...@freudianslit.com --- So, I may have found the culprit, or perhaps its a coincidence. LO was crashing still but I noticed I had "Use a Java runtime environment" deselected. Once I selected it, no more crashing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69724] There is no ability to set/configure the default number/bullet styles
https://bugs.documentfoundation.org/show_bug.cgi?id=69724 Cor Nouws changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #16 from Cor Nouws --- Hi, (In reply to al F from comment #15) > To sum up: > When using F12, AutoCorrect or the toolbar button to insert a list, numbered > (ordered) or not, we would like that list to default to one of the editable > styles accessible through F11 or the Styles menu. So most logic would be to have: - F12linked toNumbering 123 - Shft-F12 linked toBullet ● > In addition, it would be nice if the list styles could have a "list parent", > just like "Text Body" and other paragraph styles have "Default paragraph > style" as a parent. I for one would like the ability to set position and tab > stops for all of the list styles at once. Interesting idea. Could you please file a separate issue for that? (version field: Inherited from OOo) and mention the bug here? - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151259] New: loading issue
https://bugs.documentfoundation.org/show_bug.cgi?id=151259 Bug ID: 151259 Summary: loading issue Product: LibreOffice Version: 3.5 all versions Hardware: x86-64 (AMD64) URL: http://www.amazon.in/ OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sarahsaima...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151234] Formatting Marks: Spurious letters introduced with formatting marks toggled on
https://bugs.documentfoundation.org/show_bug.cgi?id=151234 خالد حسني changed: What|Removed |Added CC||kha...@aliftype.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from خالد حسني --- Fixed in https://gerrit.libreoffice.org/c/core/+/140582 *** This bug has been marked as a duplicate of bug 150726 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151256] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=151256 Eike Rathke changed: What|Removed |Added URL|http://mu.ac.in/portal/ | Component|UI |deletionRequest Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151254] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=151254 Eike Rathke changed: What|Removed |Added Attachment #182762|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90273] Formatting Regression: Filling background page image can't be linked anymore, only embedded
https://bugs.documentfoundation.org/show_bug.cgi?id=90273 --- Comment #14 from Cor Nouws --- bug still present in Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 100dc387ffd7df84199dae51abd9de35440905f1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151257] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=151257 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID Summary|too much clutter|spam -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151256] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=151256 Rafael Lima changed: What|Removed |Added Resolution|--- |INVALID Summary|too much clutter|spam Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113338] [META] Embedded fonts bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113338 Bug 113338 depends on bug 72456, which changed state. Bug 72456 Summary: Font Embedding does not work on MacOS https://bugs.documentfoundation.org/show_bug.cgi?id=72456 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=42082 Bug 42082 depends on bug 72456, which changed state. Bug 72456 Summary: Font Embedding does not work on MacOS https://bugs.documentfoundation.org/show_bug.cgi?id=72456 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94048] Calc is too restrictive with naming cell ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=94048 --- Comment #8 from Cor Nouws --- (In reply to Markus Mohrhard from comment #2) > Problem is in ScRangeData::IsNameValid > > The code has been changed as part of > https://bz.apache.org/ooo/show_bug.cgi?id=87171 > > Any change here needs to add a number of tests making sure that we are not > introducing regressions for that bug again. Looks as if https://bz.apache.org/ooo/show_bug.cgi?id=87171#c16 comes with some info/start for that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47295] Paragraph style used for the single paragraph in a new Writer file, should be "Text body" and not "Default"
https://bugs.documentfoundation.org/show_bug.cgi?id=47295 Cor Nouws changed: What|Removed |Added Summary|Default paragraph style |Paragraph style used for |should be "Text body" and |the single paragraph in a |not "Default" |new Writer file, should be ||"Text body" and not ||"Default" CC||michael.st...@allotropia.de ||, vmik...@collabora.com --- Comment #43 from Cor Nouws --- (In reply to Rūdolfs from comment #40) > In any case, even after 10 years, I still think that for a new document, the > first paragraph should have "Text Body" style. Clarc has given more than > enough reasons to make the change. I've just again read all comments in this bug. - There is no technical reason given: nothing will break. - It will improve the use of text documents. So from there: let's do it. However, I think some caution is needed: I remember once have seen an issue where some default style/setting (in Calc, Writer..?) did have influence on some import activities. - Hence adding Miklos and Michael in CC to ask: do you expect any issue around this? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140491] Specific DOCX exported from Writer opens modified when reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=140491 Justin L changed: What|Removed |Added CC||tele...@surfxs.nl --- Comment #7 from Justin L --- *** Bug 143845 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 143845] FILEOPEN DOCX: File marked as changed after opening
https://bugs.documentfoundation.org/show_bug.cgi?id=143845 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Justin L --- *** This bug has been marked as a duplicate of bug 140491 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116625] [META] Bugs where document modification status is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=116625 Bug 116625 depends on bug 143845, which changed state. Bug 143845 Summary: FILEOPEN DOCX: File marked as changed after opening https://bugs.documentfoundation.org/show_bug.cgi?id=143845 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112797] FILEOPEN: DOCX - Document set to modified on opening ( PAGEREF \h )
https://bugs.documentfoundation.org/show_bug.cgi?id=112797 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0491 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140491] Specific DOCX exported from Writer opens modified when reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=140491 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||2797 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131937] Removing "Freeze Rows and Columns" and adding or removing "Split Window" does not flag the file as changed
https://bugs.documentfoundation.org/show_bug.cgi?id=131937 Justin L changed: What|Removed |Added Hardware|x86-64 (AMD64) |All OS|Windows (All) |All CC||jl...@mail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112797] FILEOPEN: DOCX - Document set to modified on opening ( PAGEREF \h )
https://bugs.documentfoundation.org/show_bug.cgi?id=112797 Justin L changed: What|Removed |Added Summary|FILEOPEN: DOCX - Document |FILEOPEN: DOCX - Document |set to modified on opening |set to modified on opening ||( PAGEREF \h ||) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86821] canceled actions set "document modified" flag
https://bugs.documentfoundation.org/show_bug.cgi?id=86821 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=93 ||519 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93519] Impress: Should reset the modified flag after undoing all changes
https://bugs.documentfoundation.org/show_bug.cgi?id=93519 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=86 ||821 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116625] [META] Bugs where document modification status is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=116625 Bug 116625 depends on bug 91218, which changed state. Bug 91218 Summary: FILEOPEN: File opens with modified flag already set https://bugs.documentfoundation.org/show_bug.cgi?id=91218 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91218] FILEOPEN: File opens with modified flag already set
https://bugs.documentfoundation.org/show_bug.cgi?id=91218 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #13 from Justin L --- fixed in LO 7.1.3 by commit ed12e778bffd38bf9691981436f912ff199e8ec8 Author: Mike Kaganski on Mon Apr 26 16:14:07 2021 +0300 tdf#141914: Allow to unset modified anyway *** This bug has been marked as a duplicate of bug 141914 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105389] Font size for Heading 1-10 are displayed in percentages and not in points
https://bugs.documentfoundation.org/show_bug.cgi?id=105389 Cor Nouws changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1258 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151258] Writer Header1, Header2, .. font size is no longer defined as a percentage of style 'Heading'
https://bugs.documentfoundation.org/show_bug.cgi?id=151258 Cor Nouws changed: What|Removed |Added CC||info@friprogramvarusyndikat ||et.se See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||5389 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151258] Writer Header1, Header2, .. font size is no longer defined as a percentage of style 'Heading'
https://bugs.documentfoundation.org/show_bug.cgi?id=151258 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl Keywords||bibisectRequest, regression --- Comment #1 from Cor Nouws --- additional info: Wrong in Version: 7.3.5.2 / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: nl-NL (en_US.UTF-8); UI: nl-NL Calc: threaded still OK in 7.3.0alpha1 .. didn't check other versions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151258] New: Writer Header1, Header2, .. font size is no longer defined as a percentage of style 'Heading'
https://bugs.documentfoundation.org/show_bug.cgi?id=151258 Bug ID: 151258 Summary: Writer Header1, Header2, .. font size is no longer defined as a percentage of style 'Heading' Product: LibreOffice Version: 7.3.5.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: c...@nouenoff.nl New writer document Enter Heading 1 Check style's properties, tab Font -> size is 18 pts This is a change from the known situation (since Muthusalem) that the font size of the styles Header1, Header2 is defined as a percentage of style 'Heading' -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88559] Display of inherited attributes from parent styles in Styles dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=88559 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl Version|unspecified |Inherited From OOo --- Comment #24 from Cor Nouws --- Hi Mike, (In reply to Mike Kaganski from comment #21) > Created attachment 166403 [details] > Mockup with small buttons at labels Thanks :) Has it been considered to have one 'revert to inherited' button per tab page? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151257] New: too much clutter
https://bugs.documentfoundation.org/show_bug.cgi?id=151257 Bug ID: 151257 Summary: too much clutter Product: cppunit Version: 1.12 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ariba07akh...@gmail.com CC: markus.mohrh...@googlemail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151256] too much clutter
https://bugs.documentfoundation.org/show_bug.cgi?id=151256 ariba07akh...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151256] New: too much clutter
https://bugs.documentfoundation.org/show_bug.cgi?id=151256 Bug ID: 151256 Summary: too much clutter Product: LibreOffice Version: 3.3.0 release Hardware: x86-64 (AMD64) URL: http://mu.ac.in/portal/ OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ariba07akh...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72456] Font Embedding does not work on MacOS
https://bugs.documentfoundation.org/show_bug.cgi?id=72456 خالد حسني changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |kha...@aliftype.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143133] LibreOffice leaks embedded Fonts between documents
https://bugs.documentfoundation.org/show_bug.cgi?id=143133 خالد حسني changed: What|Removed |Added CC||kha...@aliftype.com --- Comment #5 from خالد حسني --- We register embedded fonts the same way we register bundled fonts. I don’t think we have a way to limit fonts to a single document (I think our font list is global, but don’t quote me on it). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140881] LO fails opening WOFF and WOFF2 fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=140881 خالد حسني changed: What|Removed |Added CC||kha...@aliftype.com --- Comment #19 from خالد حسني --- WOFF and WOFF2 are compressed OpenType/TrueType fonts for use on the web (where file size matters). While WOFF uses GZIP for compression and is somewhat relatively easy to decompress, WOFF2 uses Brotli compression and on top of that many font tables are transformed to compress better and need to de-transformed back (I wrote the WOFF2 test suite for the W3C webfonts working group). Supporting such fonts will require at least a couple of extra dependencies for very little gain since Linux system are the only systems that allow installing these fonts. Also installing WOFF/WOFF2 files is a bad idea, if your distribution did this report it as a bug, and installing multiple formats of the same fonts is even worse, also report to your distribution. FontConfig does not provide a way to distinguish WOFF/WOFF2 from regular fonts, they are reported as their contained font, so we have no way to filter them out as we do with Type 1 and bitmap fonts other than sniffing the fonts (I don’t even think FontConfig intentionally support WOFF/WOFF2, it just happens to work for it because it uses FreeType to identify the fonts and FreeType supports them). My suggestion is WONTFIX unless someone has a clear idea what to do here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72456] Font Embedding does not work on MacOS
https://bugs.documentfoundation.org/show_bug.cgi?id=72456 خالد حسني changed: What|Removed |Added Whiteboard|confirmed:4.3.0.0a0+:OSX10. |target:7.5.0 |9 target:7.5.0 | Keywords|implementationError | CC||kha...@aliftype.com --- Comment #24 from خالد حسني --- I can now embed fonts in documents, but opening a document with embedded fonts does not activate the fonts until the file is opened again, without closing the application. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72456] Font Embedding does not work on MacOS
https://bugs.documentfoundation.org/show_bug.cgi?id=72456 --- Comment #23 from Commit Notification --- Khaled Hosny committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d7083fe6dd383ac4144fbe53e300bc3d34f26ef6 tdf#72456: Support font embedding on macOS It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72456] Font Embedding does not work on MacOS
https://bugs.documentfoundation.org/show_bug.cgi?id=72456 Commit Notification changed: What|Removed |Added Whiteboard|confirmed:4.3.0.0a0+:OSX10. |confirmed:4.3.0.0a0+:OSX10. |9 |9 target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148251] Use std::swap instead of using temporary values
https://bugs.documentfoundation.org/show_bug.cgi?id=148251 Hossein changed: What|Removed |Added Status|ASSIGNED|NEW --- Comment #6 from Hossein --- Resetting the issue status back to NEW. This is a multi-hacker EasyHack. Multiple people can work on it at the same time. Please work on it without assigning it to yourself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135176] PDF Export - CALC - Push Button - Font Size of Push Button Label is modified ( increase )
https://bugs.documentfoundation.org/show_bug.cgi?id=135176 --- Comment #16 from Hans-Werner --- LibreOffice used for testing: Version: 7.4.2.1 (x64) / LibreOffice Community Build ID: 681d65acd9ede00dd724d6716f21cabfdcc95bd2 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL THE BUG IS STILL PRESENT ! It seems to be, that the cells on the right side of the push buttons cause the bug. After having deleted ALL the formatting and cell content of these cells, the bug disappeared: + CALC_0_nothing modified_ERROR.pdf + CALC_1_only_deleted_cell_background_ERROR.pdf + CALC_2_only_deleted_cell_contents_ERROR.pdf + CALC_3_only_unmerged cells_ERROR.pdf + CALC_4_did_1+2+3_OKAY.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135176] PDF Export - CALC - Push Button - Font Size of Push Button Label is modified ( increase )
https://bugs.documentfoundation.org/show_bug.cgi?id=135176 --- Comment #15 from Hans-Werner --- Created attachment 182775 --> https://bugs.documentfoundation.org/attachment.cgi?id=182775=edit CALC_4_did_1+2+3_OKAY.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135176] PDF Export - CALC - Push Button - Font Size of Push Button Label is modified ( increase )
https://bugs.documentfoundation.org/show_bug.cgi?id=135176 --- Comment #14 from Hans-Werner --- Created attachment 182774 --> https://bugs.documentfoundation.org/attachment.cgi?id=182774=edit CALC_4_did_1+2+3_OKAY.ods -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135176] PDF Export - CALC - Push Button - Font Size of Push Button Label is modified ( increase )
https://bugs.documentfoundation.org/show_bug.cgi?id=135176 --- Comment #13 from Hans-Werner --- Created attachment 182773 --> https://bugs.documentfoundation.org/attachment.cgi?id=182773=edit CALC_3_only_unmerged cells_ERROR.pdf -- You are receiving this mail because: You are the assignee for the bug.
