[Libreoffice-bugs] [Bug 144973] Start center not painted in background when Alt-Tabbing away and back with dialog open
https://bugs.documentfoundation.org/show_bug.cgi?id=144973 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||6282 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Whiteboard| QA:needsComment| CC||matt...@gmail.com, ||mikekagan...@hotmail.com Keywords|bibisectRequest |bibisected, bisected --- Comment #1 from Aron Budea --- Regression introduced by the following commit, bibisected using repo bibisect-win64-7.2. Adding CC: to Matt K. https://cgit.freedesktop.org/libreoffice/core/commit/?id=1c1226709c6be39c5462f5e6e1262ca630b30b34 author Matt K 2021-04-21 17:34:16 -0500 committer Mike Kaganski 2021-04-22 22:20:55 +0200 tdf#106282 Change Windows File Dialog to run on the main thread -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Bug 83066 depends on bug 144222, which changed state. Bug 144222 Summary: Vertical Japanese character strings are misaligned when exporting PDF. https://bugs.documentfoundation.org/show_bug.cgi?id=144222 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144222] Vertical Japanese character strings are misaligned when exporting PDF.
https://bugs.documentfoundation.org/show_bug.cgi?id=144222 Mark Hung changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113174] Formula Input Line does not save the size if you increase it
https://bugs.documentfoundation.org/show_bug.cgi?id=113174 --- Comment #6 from Evan --- Bug still present. Linux Mint 20.2 Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.1 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145289] New: Charts fail to update by dragging data selection handles
https://bugs.documentfoundation.org/show_bug.cgi?id=145289 Bug ID: 145289 Summary: Charts fail to update by dragging data selection handles Product: LibreOffice Version: 6.0.7.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rwp...@yahoo.com We are used to updating a chart in Excel by dragging the data selection handle when a new line of data is added. Libre's method is painfully tedious, slow and error-prone. Why can't you do it like Excel does? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144979] Function XSystemChildFactory::createSystemChild() hangs
https://bugs.documentfoundation.org/show_bug.cgi?id=144979 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 144391] Calc: link to files management.
https://bugs.documentfoundation.org/show_bug.cgi?id=144391 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 145022] Collabora Office: bug of comment appearing when added to a table cell
https://bugs.documentfoundation.org/show_bug.cgi?id=145022 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 145021] Collabora Office: on Android splitting cells in Writer does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=145021 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 145020] Collabora Office on Android freezes while creating editable copy of a temporary file
https://bugs.documentfoundation.org/show_bug.cgi?id=145020 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 145017] [Calc] The action of the New button in the Data Form seemed illogical
https://bugs.documentfoundation.org/show_bug.cgi?id=145017 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 145014] Collabora Office: on Android the automatic font color does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=145014 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 145270] LO files should have a macro module by default
https://bugs.documentfoundation.org/show_bug.cgi?id=145270 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 145270] LO files should have a macro module by default
https://bugs.documentfoundation.org/show_bug.cgi?id=145270 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141270] Wide vertical spacing when using a custom font.
https://bugs.documentfoundation.org/show_bug.cgi?id=141270 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 141270] Wide vertical spacing when using a custom font.
https://bugs.documentfoundation.org/show_bug.cgi?id=141270 --- Comment #3 from QA Administrators --- Dear noel, 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 141208] Editing a LibreOffice Calc spreadsheet and was trying to find the Freeze Rows/Columns command. Calc crashed
https://bugs.documentfoundation.org/show_bug.cgi?id=141208 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 141208] Editing a LibreOffice Calc spreadsheet and was trying to find the Freeze Rows/Columns command. Calc crashed
https://bugs.documentfoundation.org/show_bug.cgi?id=141208 --- Comment #5 from QA Administrators --- Dear clearlyseen, 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 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 140948, which changed state. Bug 140948 Summary: Undo doesn't restore original layout https://bugs.documentfoundation.org/show_bug.cgi?id=140948 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140948] Undo doesn't restore original layout
https://bugs.documentfoundation.org/show_bug.cgi?id=140948 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 140948] Undo doesn't restore original layout
https://bugs.documentfoundation.org/show_bug.cgi?id=140948 --- Comment #9 from QA Administrators --- Dear Telesto, 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 140842] Styles & Formatting Character Style: font weight resets to Regular every time document is closed
https://bugs.documentfoundation.org/show_bug.cgi?id=140842 --- Comment #4 from QA Administrators --- Dear Violet, 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 72456] Font Embedding does not work on MacOS
https://bugs.documentfoundation.org/show_bug.cgi?id=72456 --- Comment #21 from QA Administrators --- Dear Italo Vignoli, 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 140842] Styles & Formatting Character Style: font weight resets to Regular every time document is closed
https://bugs.documentfoundation.org/show_bug.cgi?id=140842 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 61393] PDF: Missing objects editing a PDF coming from Winword
https://bugs.documentfoundation.org/show_bug.cgi?id=61393 --- Comment #18 from QA Administrators --- Dear pruello, 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 58082] Warning message "do you want to recalculate ..." when copy-paste cells from Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=58082 --- Comment #10 from QA Administrators --- Dear Rusbearing, 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 46177] EDITING: Incorrect Behaviour of Direct Cursor in Right-Aligned Paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=46177 --- Comment #13 from QA Administrators --- Dear Harald Koester, 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 34955] Deleting numbering item which restarts numbering fails to retain restart
https://bugs.documentfoundation.org/show_bug.cgi?id=34955 --- 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 128378] FILEOPEN: Linked Unicode text files - characters looks wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=128378 --- Comment #2 from QA Administrators --- Dear John, 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 113174] Formula Input Line does not save the size if you increase it
https://bugs.documentfoundation.org/show_bug.cgi?id=113174 --- Comment #5 from QA Administrators --- Dear Evan, 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 106472] Headless printing ignores macro
https://bugs.documentfoundation.org/show_bug.cgi?id=106472 --- Comment #6 from QA Administrators --- Dear macau, 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 145267] Writer crashes when docking or undocking sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=145267 benr...@gmail.com changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #4 from benr...@gmail.com --- Indeed, disabling "Use Skia for all rendering" does not produce the crash anymore. So, is this a bug in the AMD driver? Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144853] Sentence case not undone when cycling case
https://bugs.documentfoundation.org/show_bug.cgi?id=144853 --- Comment #7 from V Stuart Foote --- (In reply to Michael Warner from comment #6) > > I am starting to think there is no completely consistent behavior with > Sentence Case in the cycle case rotation at all. Right. Which was basis for my suggestion to eliminate the expand to sentence bound (which I'm not sure our ICU lib tests even do correctly) leaving either transliterate exactly the selection--or--expand only to the word bound (for title, sentence, upper, lower) when no selection was made. Making an exact selection for word, sentence, or paragraph is now trivial--it was not before the UNO commands were implemented and made available to keyboard or mouse click actions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145288] UI - File>New while function wizard is open creates unresponsive sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=145288 Steve Edmonds changed: What|Removed |Added CC||st...@edmondsfamily.co.nz --- Comment #3 from Steve Edmonds --- (In reply to m.a.riosv from comment #2) > Sorry, not able to insert data, and toolbars and many menu options are not > available. Can you close the window when it is in that state. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145288] UI - File>New while function wizard is open creates unresponsive sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=145288 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from m.a.riosv --- Sorry, not able to insert data, and toolbars and many menu options are not available. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145288] UI - File>New while function wizard is open creates unresponsive sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=145288 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- No repro. Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144853] Sentence case not undone when cycling case
https://bugs.documentfoundation.org/show_bug.cgi?id=144853 --- Comment #6 from Michael Warner --- My understanding of what was desired in Comment 3 is that if there was no selection and user selected Format -> Text -> Sentence Case, it would continue to affect the entire sentence as before. It would only be restricted to the current word if there was no selection and user pressed Shift+F3. My point from Comment 4 is that by continuing to apply Sentence Case to the current word when cycling without selection, now the user will see the same result twice in the cycle, once from the Title Case action, and once from the Sentence Case action. This will appear to be a bug to that person. The downside to skipping Sentence Case when cycling without selection is there will appear to be three states; and when cycling WITH selection, there will appear to be four states, which would also seem like an issue, if there is only one word selected, then the user sees the same thing in twice again, so it doesn't fully solve that problem either. I am starting to think there is no completely consistent behavior with Sentence Case in the cycle case rotation at all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145288] New: UI - File>New while function wizard is open creates unresponsive sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=145288 Bug ID: 145288 Summary: UI - File>New while function wizard is open creates unresponsive sheet. Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: st...@edmondsfamily.co.nz To reproduce; Open a calc sheet. Open the function wizard. Go to the sheet above, File>New>Spreadsheet (not using Ctl-N) A a new sheet opens with the toolbar greyed out. This new sheet cannot be edited Closing the function wizard does not make the sheet editable. Closing the initial sheet does not make the sheet editable. The new uneditable sheet cannot be closed. I have to kill the process to get the sheet to exit. Could be related to bug 70513 As Ctl-N seems disabled when the function editor is open, I suggest also disabling File>New>Spreadsheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145287] New: detached tool bars no longer can me moved
https://bugs.documentfoundation.org/show_bug.cgi?id=145287 Bug ID: 145287 Summary: detached tool bars no longer can me moved Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: and...@laposte.net Description: Before version 7.2.2.2, detached tool bars could be moved, and closed by the "X" in the upper right corner. That is no longer the case with version 7.2.2.2 Steps to Reproduce: 1. If no tool bar is detached, detach a tool bar. To detach a tool bar, ensure that menu/display/tool_bars/block_tool_bars check box is unchecked. (The English may be somewhat different. French is menu/affichage/barres d'outils/bloquer barres d'outils.) 2. With the mouse, try to move the tool bar. It may move for a moment, to be subsequently fixed in place. 3. With the mouse, click on the "X" at upper right of the tool bar. No effect. 4. with the menu, close the tool bar. Then reopen. It displays in the same location. The mouse can not move or close the tool bar. Actual Results: See above. Expected Results: The tool par can be readily moved and/or closed with the mouse. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.2.2 Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: fr-CA (fr_CA.UTF-8); UI: fr-FR Calc: threaded Built by Mageia (Linux) A recent update to 7.2.2.2 showed the problem. No problem before the update. Resetting the profile had no effect, except that it required undoing full screen and unclicking menu/display/tool_bars/block_tool_bars to be able to confirm the problem with a new profile. Since I have considerable customization of my profile, it is important to keep most of the configuration of my profile. However, for my tests, only the 2 changes indicated were made to the default profile. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130320] LibO 6: Windows 10 content indexing does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=130320 --- Comment #37 from Gilward Kukel --- When I save an ODT file with WordPad, its contents are found. When I save one with LibreOffice Writer, its contents are not found. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 74604] UI: Make Navigation toolbar work on Hyperlinks and (Field) Cross-references too.
https://bugs.documentfoundation.org/show_bug.cgi?id=74604 --- Comment #8 from Jim Raykowski --- (In reply to V Stuart Foote from comment #7) > Sure, "somewhere" in the hyperlink is the cursor the recency stack receives > after a + launch of the hyperlink, and after exiting the object > moving forward or backward in the recency stack. Specific cursor seems a > little vague. Thanks for the explanation. For me, the "somewhere" is where the pointer is positioned on the hyperlink when + is done or where the cursor is at when the .uno:OpenHyperlinkOnCurs command is used. > > But I wouldn't expect the target of the hyperlink to reopen with recency > navigation, or do you think it should? No opinion. I was just trying understand your comment to see if there may be something else needed to resolve this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133156] Improved help information needed for Calc Solvers
https://bugs.documentfoundation.org/show_bug.cgi?id=133156 --- Comment #3 from Olivier Hallot --- errata: bug#81599 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133156] Improved help information needed for Calc Solvers
https://bugs.documentfoundation.org/show_bug.cgi?id=133156 --- Comment #2 from Olivier Hallot --- (In reply to Steve Fanning from comment #0) > The Help system currently provides minimum information about Calc's Solvers. > See the file at > https://help.libreoffice.org/7.0/en-US/text/scalc/01/solver. > html?DbPAR=CALC#bm_id7654652. > > We should consider improving this aspect of the Help. > > For example: > (1) Should it mention that the available Solver engines seem to be dependent > on whether you've enabled a JRE or not. Tested in LO 7.2: The linear solver, CoinMP, and swarm algorithm are available even is a JRE is not enabled. the DEPS and SCO algorithms are added when a JRE is enabled. If you disable the JRE in LibreOffice, a prompt will show to inform that some algorithms require a JRE. But you can continue anyway. DEPS and SCO algorithms are unavailable then. > (2) The default engine isn't always a linear one (as stated in the last note > of the page). Can't see this note... > (3) Could an example be included? I am reluctant to transform the Help into an encyclopaedia. The example in comment#1 is a great piece of documentation, better fit in the wiki instead. A link to the wiki in the Help page is OK, as we did in the Calc Functions. > (4) Is the help page at scalc/01/solver_options.xhp accessible to a user? I > couldn't find any description on the Options dialog when I tried with the > current 7.0 help. It has been fixed since then. - bug#84599 - https://gerrit.libreoffice.org/c/help/+/94703 > (5) Can we use anything from > https://opengrok.libreoffice.org/xref/core/nlpsolver/ to improve the help > pages? We used info from the help pages pointed here -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144013] FILESAVE DOCX: "Same content on first page" is checked after saving as docx, when document contains a table on the page which spreads across two pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144013 --- Comment #9 from Justin L --- I don't think there is any point in filing a bug about it. The scope is huge, so it will never get handled by a volunteer, only by a company. And in that case you don't need a bug report, you need money. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144013] FILESAVE DOCX: "Same content on first page" is checked after saving as docx, when document contains a table on the page which spreads across two pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144013 --- Comment #8 from Luke --- Justin, I like your idea of warning the user when LO's features don't map one-to-one to MSO's. It's a good stop-gap until this is fixed. What you think of adding support to LO's layout engine to support a Page Styles mode that matches MSO's? Should I file an enhancement request for either one or both. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145286] New: All LibreOffice applications freeze, "Not Responding", Base constantly writing to lock file
https://bugs.documentfoundation.org/show_bug.cgi?id=145286 Bug ID: 145286 Summary: All LibreOffice applications freeze, "Not Responding", Base constantly writing to lock file Product: LibreOffice Version: 7.0.6.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: yergerda...@gmail.com Seems to be triggered by power events - usually sleep/resume, today just by disconnecting AC adapter on my laptop. Application windows freeze, colors go pale, mouse pointer changes to hourglass/throbber/Whirligig of Waiting, (Not Responding) on toolbar. Only activity is .odb.lck being written to according to Process Monitor looking at soffice process, offsets 8-15 inclusive, then repeating. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144853] Sentence case not undone when cycling case
https://bugs.documentfoundation.org/show_bug.cgi?id=144853 --- Comment #5 from V Stuart Foote --- (In reply to Michael Warner from comment #4) > (In reply to Heiko Tietze from comment #3) > > >+ the ideal behavior would be as OP suggest, only change current word > > if no selection is done (Sascha) > > If this is the decision then I submit that we should just skip applying > sentence case formatting if cycling without selection, because applying > sentence case only to the current word is equivalent to applying title case > in this situation. No, the cycle case is four distinct actions [1]. For consistency, with or without selection must still be four states. So, logic for Sentence case without selection would need to apply at the word bound holding the cursor, just as TITLE_CASE. So, either test that we are in the cycle case loop--and modify the SENTENCE_CASE handling, or fully remove the expanded run passed to the SENTENCE_CASE transliteration [2]. Put another way, SENTENCE_CASE would *require* a selection (now trivial to make at sentence bounds via mouse or keyboard) that would be honored exactly with no expansion. Otherwise it would no longer expand beyond word holding text cursor and behave like TITLE_CASE. Probably simpler to do the later. The Format -> Text -> Sentence case would be minimally effected--maybe adjust do nothing with out a selection. While the cycle case mode would gain consistency (with or without selection), the main complaint. =-ref-= [1] https://opengrok.libreoffice.org/xref/core/unotools/source/i18n/caserotate.cxx?r=84f8e28d#25 [2] https://opengrok.libreoffice.org/xref/core/editeng/source/editeng/impedit4.cxx?r=6af0da48#2774 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144013] FILESAVE DOCX: "Same content on first page" is checked after saving as docx, when document contains a table on the page which spreads across two pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144013 Justin L changed: What|Removed |Added Blocks|136472 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136472 [Bug 136472] Same content on left/right pages/ Same content on first page checked on file open DOCX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136472] Same content on left/right pages/ Same content on first page checked on file open DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=136472 Justin L changed: What|Removed |Added Depends on|144013 | Assignee|arato.dan...@nisz.hu|libreoffice-b...@lists.free ||desktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144013 [Bug 144013] FILESAVE DOCX: "Same content on first page" is checked after saving as docx, when document contains a table on the page which spreads across two pages -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145232] The Danish LibreOffice Help does not show index (offline as well as online)
https://bugs.documentfoundation.org/show_bug.cgi?id=145232 Buovjaga changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145232] The Danish LibreOffice Help does not show index (offline as well as online)
https://bugs.documentfoundation.org/show_bug.cgi?id=145232 --- Comment #10 from Commit Notification --- Ilmari Lauhakangas committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/fb9c746f6aaae147aa16b1f2b682e01d07003d03 tdf#145232 get_bookmark.xsl: Use normalize-space() -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145232] The Danish LibreOffice Help does not show index (offline as well as online)
https://bugs.documentfoundation.org/show_bug.cgi?id=145232 Commit Notification changed: What|Removed |Added Whiteboard||target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144853] Sentence case not undone when cycling case
https://bugs.documentfoundation.org/show_bug.cgi?id=144853 --- Comment #4 from Michael Warner --- (In reply to Heiko Tietze from comment #3) >+ the ideal behavior would be as OP suggest, only change current word > if no selection is done (Sascha) If this is the decision then I submit that we should just skip applying sentence case formatting if cycling without selection, because applying sentence case only to the current word is equivalent to applying title case in this situation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145285] Cannot export!! Exporting Drawing Crashes EVERY time
https://bugs.documentfoundation.org/show_bug.cgi?id=145285 --- Comment #2 from Jon R Kibler --- Created attachment 175891 --> https://bugs.documentfoundation.org/attachment.cgi?id=175891=edit Next crash dump next, but slightly different crash dump under identical circumstances -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145285] Cannot export!! Exporting Drawing Crashes EVERY time
https://bugs.documentfoundation.org/show_bug.cgi?id=145285 Jon R Kibler changed: What|Removed |Added CC||jrk1231...@nym.hush.com --- Comment #1 from Jon R Kibler --- Created attachment 175890 --> https://bugs.documentfoundation.org/attachment.cgi?id=175890=edit Crash dump 1 First crash dump -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145285] New: Cannot export!! Exporting Drawing Crashes EVERY time
https://bugs.documentfoundation.org/show_bug.cgi?id=145285 Bug ID: 145285 Summary: Cannot export!! Exporting Drawing Crashes EVERY time Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jrk1231...@nym.hush.com Created attachment 175889 --> https://bugs.documentfoundation.org/attachment.cgi?id=175889=edit screen cap showing action attempted to cause crash Attempting to export a drawing. 1) Open Drawing 2) File-->Export 3) Dialogue opens. At top of window, click on directory name to change directory. 4) Get spinning pinwheel of death followed by a crash--including CRASH DUMP!! Annotated dialogue window attached here. Crash dumps attached in updates. Other specifics: macOS 10.14.6 (fully patched) LO has full disk access -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144261] Bad cursor positioning with Chinese input
https://bugs.documentfoundation.org/show_bug.cgi?id=144261 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru, ||suokunl...@126.com Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Whiteboard| QA:needsComment| --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- Please attach some file example here -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144391] Calc: link to files management.
https://bugs.documentfoundation.org/show_bug.cgi?id=144391 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 CC||79045_79...@mail.ru Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- Please attach your files here -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145284] New: Print and export to PDF include original filename extension before ".pdf"
https://bugs.documentfoundation.org/show_bug.cgi?id=145284 Bug ID: 145284 Summary: Print and export to PDF include original filename extension before ".pdf" Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Mac OS X (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: a8c97...@opayq.com Description: If I print/export an open file, say, "document.otd", to PDF, the dialog autofills the name "document.odt.pdf". Expected behavior is for the extension to be replaced and not left, resulting in "document.pdf". Steps to Reproduce: 1. Open a document 2. Select Export to PDF menu item 3. See filename in dialog Actual Results: filename contains original extension and pdf. Expected Results: filename contains only "pdf" extension Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Mac OS X 10.15.7; UI render: default; VCL: osx 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 144399] Impress: FILESAVE to ODP as read-only with additional password protection for editing not working
https://bugs.documentfoundation.org/show_bug.cgi?id=144399 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Version|7.3.0.0 alpha0+ Master |7.1.3.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144399] Impress: FILESAVE to ODP as read-only with additional password protection for editing not working
https://bugs.documentfoundation.org/show_bug.cgi?id=144399 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru Keywords||bibisectRequest, regression Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Whiteboard| QA:needsComment| --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Confirm in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f8bb970fd385c80b085a071da0f8acc119498005 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 and in 7.1 but not in Version: 7.0.0.2 (x64) Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c Потоков ЦП: 4; ОС: Windows 10.0 Build 19043; Отрисовка ИП: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); ИП: ru-RU Calc: threaded it's a regression another problem is even in 7.0 you don't see LO opens the password protected file as read-only, there is no any InfoBar for example -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145270] LO files should have a macro module by default
https://bugs.documentfoundation.org/show_bug.cgi?id=145270 --- Comment #4 from Frederic Parrenin --- > I think, having always a macro module would be no good idea, because files, > which have a macro module will produce a security warning when opening the > file, even if the module is empty. In this case, we can produce a warning only when the module is not empty. I think this is what MS Office does. The other possibility would be to make it easier to create a new module from the module tree view. For example, right clicking "Standard" and then "Create new module". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139950] MAC OS 11 Big Sur - Window content not correctly refreshing in Write and Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=139950 Igor changed: What|Removed |Added Whiteboard||ubnormal fast ||blinking/flashing cursor, ||symbols are invisible while ||typing Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #2 from Igor --- ubnormal fast blinking/flashing cursor, symbols are invisible while typing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139898] [META] PPTX Master slides / notes / handouts related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139898 Bug 139898 depends on bug 142221, which changed state. Bug 142221 Summary: FILEOPEN PPTX Slide header-footer settings imported incorrectly https://bugs.documentfoundation.org/show_bug.cgi?id=142221 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144593] Other cell selected when column is marked
https://bugs.documentfoundation.org/show_bug.cgi?id=144593 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Whiteboard| QA:needsComment| --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- Looks as a bug but I'm not sure UX-team, we need your opinion here ps: Excel moves the cursor to A1 cell in that case >_< -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142010] Inserting a column in a sheet causes erroneus rewriting of the formulas in a old Excel 97-2003 xls formatted file
https://bugs.documentfoundation.org/show_bug.cgi?id=142010 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Whiteboard|QA:needsComment | Keywords||bibisectRequest, ||filter:xls, regression CC||79045_79...@mail.ru --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- repro in 7.3 and in Версия: 4.4.7.2 ID сборки: f3153a8b245191196a4b6b9abd1d0da16eead600 Локаль: ru_RU but not in Version: 4.3.7.2 Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba it's a regression If resave this XLS file to XLSX in the MS Excel and open that XLSX in LO, then LO works as should -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Michael Warner changed: What|Removed |Added Depends on||144982 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144982 [Bug 144982] Export unicode in pdf-file using Ubuntu (Linux) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144982] Export unicode in pdf-file using Ubuntu (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=144982 Michael Warner changed: What|Removed |Added Blocks||103378 CC||michael.warner.ut+libreoffi ||c...@gmail.com Status|NEEDINFO|NEW --- Comment #7 from Michael Warner --- I can confirm with Linux Mint: Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135282] A showcase of HTML import, editing and export bugs in an HTML5 era
https://bugs.documentfoundation.org/show_bug.cgi?id=135282 --- Comment #13 from Eyal Rozenberg --- (In reply to Michael Warner from comment #12) > There is pandoc (https://pandoc.org/) which claims to support both html5 and > odt, but I have not used it myself, so I have no idea how well it works. Perhaps someone closer to LO development than I am might want to open an issue about exploring the possibility of integrating some pandoc import-filter+ODT-output-filter pairs into LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143761] Enhancement: PLEASE revert location of RGB controls in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=143761 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Whiteboard| QA:needsComment| Severity|normal |enhancement OS|Windows (All) |All Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145283] Impress crashes upon mouseclick + large zoom
https://bugs.documentfoundation.org/show_bug.cgi?id=145283 --- Comment #1 from Mateusz Łącki --- Created attachment 175888 --> https://bugs.documentfoundation.org/attachment.cgi?id=175888=edit backtrace this is gdb backtrace with libreoffice-*-dbgsym installed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145283] New: Impress crashes upon mouseclick + large zoom
https://bugs.documentfoundation.org/show_bug.cgi?id=145283 Bug ID: 145283 Summary: Impress crashes upon mouseclick + large zoom Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mateusz.la...@gmail.com Description: I have an presentation where I have pasted a screenshot generated with Ubuntu 21.10 screenshot tool. I am able to trigger a crash (3 times already), by zooming in to the figure (zoom level 750% will do - didn't test much other values). Then clicking on the pasted figure 2-5 times impress quits. I have captured the backtrace using the "coredumpctl gdb" tool. Turning off "use hardware acceleration if available" changes nothing. I have restarted in safe mode, clicked both fields in "restoore to factory settings" - changes nothing. Steps to Reproduce: 1. Paste figure from screenshot tool 2. Apply 750% zoom (at this maginification single pixels clearly visible and large) 3. Click on the figure a few times, trying to drag it. Actual Results: Impress Crashes Expected Results: Figure moved Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.2.2.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.2.2-0ubuntu0.21.10.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144979] Function XSystemChildFactory::createSystemChild() hangs
https://bugs.documentfoundation.org/show_bug.cgi?id=144979 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru, ||mikekagan...@hotmail.com --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Mike may be you have some ideas about this problem or may be some questions to the bug reporter? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145267] Writer crashes when docking or undocking sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=145267 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- It seems as AMD driver's Skia problem can you please disable Skia rendering in LibreOffice's Options dialog? Select Tools-Options-LibreOffice-View and uncheck Skia options there -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141908] CppUnittests: replace usage of sal_Int32 with colors
https://bugs.documentfoundation.org/show_bug.cgi?id=141908 --- Comment #9 from Rishav Chattopadhya --- (In reply to Buovjaga from comment #8) Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135282] A showcase of HTML import, editing and export bugs in an HTML5 era
https://bugs.documentfoundation.org/show_bug.cgi?id=135282 --- Comment #12 from Michael Warner --- (In reply to Eyal Rozenberg from comment #10) > If there's a tool which takes an HTML and produces an ODT, maybe we can just > use it / its code for importing? :-| There is pandoc (https://pandoc.org/) which claims to support both html5 and odt, but I have not used it myself, so I have no idea how well it works. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141908] CppUnittests: replace usage of sal_Int32 with colors
https://bugs.documentfoundation.org/show_bug.cgi?id=141908 --- Comment #8 from Buovjaga --- (In reply to Rishav Chattopadhya from comment #7) > (In reply to Xisco Faulí from comment #0) > I have submitted a patch related to this. Please review it. It is my first > time submitting a patch on gerrit. You forgot to mention the link, but here it is https://gerrit.libreoffice.org/c/core/+/124091 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141908] CppUnittests: replace usage of sal_Int32 with colors
https://bugs.documentfoundation.org/show_bug.cgi?id=141908 --- Comment #7 from rishavchatterjee1...@gmail.com --- (In reply to Xisco Faulí from comment #0) I have submitted a patch related to this. Please review it. It is my first time submitting a patch on gerrit. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144065] add RTF \page control as an option for inserting page breaks in RTF documents
https://bugs.documentfoundation.org/show_bug.cgi?id=144065 --- Comment #5 from Michael Warner --- Created attachment 175887 --> https://bugs.documentfoundation.org/attachment.cgi?id=175887=edit RTF with manual page break File saved as RTF where I inserted a manual page break before the word "faucibus". In the RTF code it created a new paragraph tagged with \pagebb. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145277] Vertical orientated text has wiggling letters
https://bugs.documentfoundation.org/show_bug.cgi?id=145277 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu --- Comment #2 from V Stuart Foote --- Not seeing any h-spacing or baseline alignment deviations in the run of vertical text. Windows 10 (21H1) with Intel Iris GPU Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 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 Nor with Skia/Raster nor with default GDI rendering. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119745] Scrolling with a laptop touchpad in Libreoffice way too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=119745 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu OS|Windows (All) |All --- Comment #33 from V Stuart Foote --- Guess this needs to be set ALL since the Linux os/DE issues are being pointed here as well, and we are treating bug 85677 for touch gestures as generic even though solutions for each os will require native code. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145117] XML Source not imported if tags is non-ASCII symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=145117 Kevin Suo changed: What|Removed |Added See Also||https://gitlab.com/orcus/or ||cus/-/issues/143 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145248] EDITING CELL contents in the contents/formula bar produces unexpected result
https://bugs.documentfoundation.org/show_bug.cgi?id=145248 --- Comment #4 from Colin --- (In reply to Colin from comment #3) > Created attachment 175886 [details] > Supplement or potential replacement for attachment 175856 [details] Both attachments appear to be labelled 175856 - not sure how that works. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111951] [META] HTML import bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=111951 Michael Warner changed: What|Removed |Added Depends on||95861 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=95861 [Bug 95861] Writer Web -- rework HTML export and import filters to use HTML 5 and inline CSS3 styles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95861] Writer Web -- rework HTML export and import filters to use HTML 5 and inline CSS3 styles
https://bugs.documentfoundation.org/show_bug.cgi?id=95861 Michael Warner changed: What|Removed |Added Blocks||111951 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=111951 [Bug 111951] [META] HTML import bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 74604] UI: Make Navigation toolbar work on Hyperlinks and (Field) Cross-references too.
https://bugs.documentfoundation.org/show_bug.cgi?id=74604 --- Comment #7 from V Stuart Foote --- (In reply to Jim Raykowski from comment #6) > (In reply to V Stuart Foote from comment #5) > > (though hyperlink into > > Drawing objects get cursor position at middle of the hyperlink text, but > > drawing object can be reopened, e.g. assign a keyboard shortcut to > > .uno:OpenHyperlinkOnCurs, or +click with mouse). > Stuart, thanks for verifying. I don't follow the "though hyperlink into > Drawing objects get cursor position at middle of the hyper link text..." > Maybe you speak of drawing objects not being selected on recency navigation > stop? Sure, "somewhere" in the hyperlink is the cursor the recency stack receives after a + launch of the hyperlink, and after exiting the object moving forward or backward in the recency stack. Specific cursor seems a little vague. But I wouldn't expect the target of the hyperlink to reopen with recency navigation, or do you think it should? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145248] EDITING CELL contents in the contents/formula bar produces unexpected result
https://bugs.documentfoundation.org/show_bug.cgi?id=145248 --- Comment #3 from Colin --- Created attachment 175886 --> https://bugs.documentfoundation.org/attachment.cgi?id=175886=edit Supplement or potential replacement for attachment 175856 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145248] EDITING CELL contents in the contents/formula bar produces unexpected result
https://bugs.documentfoundation.org/show_bug.cgi?id=145248 --- Comment #2 from Colin --- With further experiments, I am now able to demonstrate the additional anomalous behaviour to which I alluded in the original report. I've attached a replacement archive with a modified sheet containing some numerical cells and a formula together with a new .mp4. Whilst I feel this archive makes the first attachment redundant I have not marked it as such because somebody may still wish to refer to the anomaly pertaining to the simple text editing. Perhaps one of the "Big Boys" could make that judgement call. I have "undone" the change I edited into the formula cell to enable you to replicate my amendments or indeed contrive a few of your own. I would also observe that it's possibly related to my earlier report 144914 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144982] Export unicode in pdf-file using Ubuntu (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=144982 --- Comment #6 from Willem --- Created attachment 175885 --> https://bugs.documentfoundation.org/attachment.cgi?id=175885=edit output in MAC OS X output in iOS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144982] Export unicode in pdf-file using Ubuntu (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=144982 --- Comment #5 from Willem --- Created attachment 175884 --> https://bugs.documentfoundation.org/attachment.cgi?id=175884=edit output in windows output in windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144982] Export unicode in pdf-file using Ubuntu (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=144982 --- Comment #4 from Willem --- Created attachment 175883 --> https://bugs.documentfoundation.org/attachment.cgi?id=175883=edit output in ubuntu output in ubuntu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117462] FORMATING: Rendering of svg file (LO-Logo) is incorrect and corrupt after rotation
https://bugs.documentfoundation.org/show_bug.cgi?id=117462 Buovjaga changed: What|Removed |Added Keywords|regression | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144982] Export unicode in pdf-file using Ubuntu (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=144982 --- Comment #3 from Willem --- Created attachment 175882 --> https://bugs.documentfoundation.org/attachment.cgi?id=175882=edit source source with unicode characters -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145282] Group of objects doesn't retain its position when page is moved up
https://bugs.documentfoundation.org/show_bug.cgi?id=145282 --- Comment #1 from phv --- Created attachment 175881 --> https://bugs.documentfoundation.org/attachment.cgi?id=175881=edit Testcase for complex group of object bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145282] New: Group of objects doesn't retain its position when page is moved up
https://bugs.documentfoundation.org/show_bug.cgi?id=145282 Bug ID: 145282 Summary: Group of objects doesn't retain its position when page is moved up 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: libreoffice@phv.email Description: Complex group of drawing object is losing its position, either referenced to a paragraph or a page, when the page which contains the group is moved up. I can reproduce this bug by removing pages before the group, or by updating the index in large document. Steps to Reproduce: >From the Writer document posted as attachement: 1. Delete the first page. Actual Results: The group on the second page is moved down the page. Expected Results: The group on the second page should keep its position on the page. Reproducible: Always User Profile Reset: Yes Additional Info: It seems that the group first keeps its position as defined but, for some unexplained reason, is then moved to the bottom (and sometimes to the right) of the page afterwards. This bug is reproduced only on version 7.3 dev, version 7.2.2.2 is not affected. Strangely enough, not all my flowcharts are moved down. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131025] Writer document with tables lost data in cells (apparently) replacing with 0
https://bugs.documentfoundation.org/show_bug.cgi?id=131025 --- Comment #52 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3e1d316734354c6b49696c8904e0fc431cfb5143 tdf#131025 ODF import: recognize SV_COUNTRY_LANGUAGE_OFFSET It will be available in 7.3.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 131025] Writer document with tables lost data in cells (apparently) replacing with 0
https://bugs.documentfoundation.org/show_bug.cgi?id=131025 Commit Notification changed: What|Removed |Added Whiteboard||target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145281] [COLLABORA ONLINE] Error in writing sub-document content.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=145281 Julien Nabet changed: What|Removed |Added Summary|Error in writing|[COLLABORA ONLINE] Error in |sub-document content.xml|writing sub-document ||content.xml -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145281] New: Error in writing sub-document content.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=145281 Bug ID: 145281 Summary: Error in writing sub-document content.xml Product: LibreOffice Version: 6.4 all versions Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@bebendorf.eu We are using Collabora Online and we ran into the "Error in writing sub-document content.xml" error quite often when trying to save an odt document. We've already filed an issue with them and they confirmed that this error is produced by the LibreOffice core (see https://github.com/CollaboraOnline/online/issues/3457). We are running the collabora/code:6.4.13.3 docker image which ships with LibreOffice core commit 70f6522 (6.4-49) according to the help dialog. Unfortunately we tried a lot of things but didn't find a reliable way to reproduce it. We also tried different documents from our LMS, locally generated and even sample files from the internet and they all have a chance to run into this issue. We tested editing the same file with multiple people and while some could save it, for others nothing happened and the error appeared in the logs. The error isn't saying too much about what exactly went wrong so I'm not sure what additional information I could provide that are helpful. If there is anything I can provide please let me know. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119745] Scrolling with a laptop touchpad in Libreoffice way too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=119745 --- Comment #32 from PolGZ --- Same bug on Asus ROG flow x13 running Windows 10 v. 10.0.1943 Build 19043 using LibreOffice v. 7.2.1.2. Same LibreOffice version on the same laptop on Arch runs perfectly with smooth consistent (with the rest of the system) scrolling. -- You are receiving this mail because: You are the assignee for the bug.
