[Libreoffice-bugs] [Bug 156515] Writer tables exit from table shortcut Alt+Enter must be type twice to exit table
https://bugs.documentfoundation.org/show_bug.cgi?id=156515 --- Comment #2 from Davide --- Steps have been described: A text flow contains a table with 1 row with 2 columns and a row with single column I need to exit the table to continue to write into the text flow I put the cursor at the end of the last cell of the table and type Alt+Enter A new empty paragraph is generated I type again Allt+Enter A new paragraoh is generated outside the table. Note that this doesn't happen inside a single or multiple columns table, I mean, not a table with 1 row with 2 columns and a row with single column. I should send an attachment to better explain but I don't know wether thie is possible. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156521] Blue Screen Of Death
https://bugs.documentfoundation.org/show_bug.cgi?id=156521 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142543] Selecting cells holding Shift in Impress tables does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=142543 Adam664 changed: What|Removed |Added CC||adamsesku...@gmail.com Version|4.2.0.4 release |Inherited From OOo --- Comment #4 from Adam664 --- Reproduce in Libreoffice 3.3.0 Changing version to "inherited from OOo" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156313] 'General error.General input/output error.'was reported when loading a .pdf file.
https://bugs.documentfoundation.org/show_bug.cgi?id=156313 --- Comment #1 from 2318494...@qq.com --- Humm.After so many times of tests ,I found that libreoffice cannot load Encrypted PDF document……but unfortunately,I have lost these documents.I will try find them form my backup. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156313] 'General error.General input/output error.'was reported when loading a .pdf file.
https://bugs.documentfoundation.org/show_bug.cgi?id=156313 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 156314] corrupt database
https://bugs.documentfoundation.org/show_bug.cgi?id=156314 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 94155] EDITING Cell highlightning depends on cell name
https://bugs.documentfoundation.org/show_bug.cgi?id=94155 --- Comment #8 from QA Administrators --- Dear Martin Lorscheid, 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 156521] Blue Screen Of Death
https://bugs.documentfoundation.org/show_bug.cgi?id=156521 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 156521] Blue Screen Of Death
https://bugs.documentfoundation.org/show_bug.cgi?id=156521 --- 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 148733] The active font isn't filtered in the Character dialog on open
https://bugs.documentfoundation.org/show_bug.cgi?id=148733 --- Comment #3 from QA Administrators --- Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 84747] EDITING typed characters inserted into wrong sheet when defined name selected
https://bugs.documentfoundation.org/show_bug.cgi?id=84747 --- Comment #12 from QA Administrators --- Dear B.J. Herbison, 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 84694] Select the whole sheet when a picture was prior selected, then copy or cut, only the prior selected picture was copied/cut, not the whole sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=84694 --- Comment #9 from QA Administrators --- Dear Yoswin Prajuabmoh, 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 57981] French : spaces before exclamation/question marks in brackets deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=57981 --- Comment #22 from QA Administrators --- Dear didi, 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 143587] Latest *Dev Release appears to magnify autofilter buttons
https://bugs.documentfoundation.org/show_bug.cgi?id=143587 --- Comment #7 from QA Administrators --- Dear Colin, 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 143351] Conditional format rule "range" part couldn't be imported.
https://bugs.documentfoundation.org/show_bug.cgi?id=143351 --- Comment #4 from QA Administrators --- Dear Gülşah Köse, 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 143029] [PPT] FILEOPEN incorrect 'connectors'
https://bugs.documentfoundation.org/show_bug.cgi?id=143029 --- Comment #5 from QA Administrators --- Dear Valek Filippov, 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 142408] [DOCX] vert="vert270" is handled as vert="vert"
https://bugs.documentfoundation.org/show_bug.cgi?id=142408 --- Comment #10 from QA Administrators --- Dear Valek Filippov, 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 122890] Launching LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=122890 --- Comment #6 from QA Administrators --- Dear Vasyl, 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 140855] Calc Row conditional colour formatting corrupted by column sort with alternate conditional colour format
https://bugs.documentfoundation.org/show_bug.cgi?id=140855 --- Comment #13 from QA Administrators --- Dear Colin, 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 140687] Incorrect formula in Conditional formatting after moving cells
https://bugs.documentfoundation.org/show_bug.cgi?id=140687 --- Comment #5 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108273] FORMATING: Tabstops behave strange when paragraph is right or middle aligned
https://bugs.documentfoundation.org/show_bug.cgi?id=108273 --- Comment #7 from QA Administrators --- Dear David Fritzsch_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 156161] Organise Macros > Python requires JRE
https://bugs.documentfoundation.org/show_bug.cgi?id=156161 Mike Kaganski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | --- Comment #6 from Mike Kaganski --- https://gerrit.libreoffice.org/c/core/+/155078 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34882] Special character dialog rework (comment 28 for scope)
https://bugs.documentfoundation.org/show_bug.cgi?id=34882 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||9232 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109232] [META] Special character dialog and toolbar group button bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109232 V Stuart Foote changed: What|Removed |Added URL|http://nabble.documentfound |https://design.blog.documen |ation.org/GSOC-work-on-Spec |tfoundation.org/2018/12/14/ |ial-Character-dialog-tc4217 |special-characters-the-fina |853.html|l-touch/ See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=34 ||882 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156538] Insert Special Character TB splitbutton should indicate glyph names
https://bugs.documentfoundation.org/show_bug.cgi?id=156538 V Stuart Foote changed: What|Removed |Added Version|Inherited From OOo |6.0.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103429] [META] Split and group buttons in toolbar and sidebar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103429 V Stuart Foote changed: What|Removed |Added Depends on||156538 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156538 [Bug 156538] Insert Special Character TB splitbutton should indicate glyph names -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156538] Insert Special Character TB splitbutton should indicate glyph names
https://bugs.documentfoundation.org/show_bug.cgi?id=156538 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Blocks||103429 Summary|Insert Symbol menubutton|Insert Special Character TB |should indicate symbol name |splitbutton should indicate ||glyph names --- Comment #1 from V Stuart Foote --- Not clear "on-mouseover" triggers are feasible given the way the split button entries for the "Favorites" and "Recent characters" are overloaded, but sure worth a look. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103429 [Bug 103429] [META] Split and group buttons in toolbar and sidebar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103342] [META] Font substitution bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103342 Bug 103342 depends on bug 31072, which changed state. Bug 31072 Summary: Impress not showing Unicode characters correctly when in fullscreen/run mode https://bugs.documentfoundation.org/show_bug.cgi?id=31072 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 31072] Impress not showing Unicode characters correctly when in fullscreen/run mode
https://bugs.documentfoundation.org/show_bug.cgi?id=31072 خالد حسني changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED CC||kha...@libreoffice.org --- Comment #26 from خالد حسني --- The original issue seems to be long fixed. The pixelated glyphs come from unifont, if this is the only font installed that supports these characters (or for some reason FontConfig prefers it over other fonts) you will get the bad looking glyphs, but there is no bug here, it is just a and outdated-looking font. Closing as I don’t think there is anything remaining to fix here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156535] Continual crashing if I select Language/for all text
https://bugs.documentfoundation.org/show_bug.cgi?id=156535 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please test in safe mode, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156512] Base don't refresh inserted row when using an updatable XResultSet
https://bugs.documentfoundation.org/show_bug.cgi?id=156512 --- Comment #5 from prrv...@gmail.com --- > Normally, at least with JDBC, when you switch to insert mode you can no longer > move in the resultset until you exit insert mode. That's not what Base > does It seems the UNO documentation states the same thing[1]: > Only the updateXXX , getXXX , and XResultSetUpdate::insertRow() methods may be > called when the cursor is on the insert row. All of the columns in a result > set > must be given a value each time this method is called before calling > insertRow. > The method updateXXX must be called before a getXXX method can be called on a > column value. [1] https://www.openoffice.org/api/docs/common/ref/com/sun/star/sdbc/XResultSetUpdate.html#moveToInsertRow This would confirm that Base switch to insert mode when it shouldn't... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156470] Writer+Calc spinwheels and crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=156470 --- Comment #17 from Patrick Luby --- I forgot to include the link to the logging patch: https://gerrit.libreoffice.org/c/core/+/155072 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156543] New: [Feature Request] "Mono" feature for the Asian Phonetic Guide
https://bugs.documentfoundation.org/show_bug.cgi?id=156543 Bug ID: 156543 Summary: [Feature Request] "Mono" feature for the Asian Phonetic Guide Product: LibreOffice Version: unspecified Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hayakawake...@gmail.com Created attachment 188666 --> https://bugs.documentfoundation.org/attachment.cgi?id=188666=edit Screenshots of the "Mono" feature in Microsoft Word This is a request for a feature which exists in Microsoft Word but doesn't in LibreOffice Writer. When adding the Asian Phonetic Guide in Microsoft Word, the "Mono" button divides the base text into single characters. This is immensely useful for Japanese-language users including myself. In LibreOffice Writer, this feature doesn't exist, meaning whenever we want to add phonetic guides by character, we either have to select each character individually or select multiple characters and then re-enter each character manually. Both options significantly slow down the workflow. If you could add the "Mono" feature for LibreOffice Writer, that would be fantastic. Let me know if anything is unclear. Please see attachment for more details. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156522] Macro recording disabled on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=156522 m.a.riosv changed: What|Removed |Added Resolution|FIXED |NOTABUG --- Comment #4 from m.a.riosv --- Like in other OS. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156511] interface XStorage no more usable on odb with 7.6 and 7.7
https://bugs.documentfoundation.org/show_bug.cgi?id=156511 --- Comment #1 from prrv...@gmail.com --- Work on: Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.3 Calc: threaded Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Ubuntu package version: 4:7.5.5~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 2; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded LibreOffice freezes on: Version: 7.6.0.1 (X86_64) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded Version: 7.6.0.1 (X86_64) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 2; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153032] Writer crashes after few hours of editing large (~3000 pages, 20 MB size) DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=153032 --- Comment #11 from Ziggy_N --- I would like to add that Writer has not crashed for the last few days, from the moment that I have decided to untick all the options in Tools/Options/LibreOffice Writer/Compatibility (see attached pic). Hopefully I have found a workaround. As to sanitization of the example file, still no luck. I can't publish the graphics included in the document, the file sanitized without graphics seems to work fine, and I haven't found a way to sanitize the graphics included in the file (I mean making the image content random while maintaining the same size/characteristics of the PNG/JPEG files included). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153032] Writer crashes after few hours of editing large (~3000 pages, 20 MB size) DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=153032 --- Comment #10 from Ziggy_N --- Created attachment 188665 --> https://bugs.documentfoundation.org/attachment.cgi?id=188665=edit Options to unselect to prevent crashing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156470] Writer+Calc spinwheels and crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=156470 --- Comment #16 from Patrick Luby --- Thank you for your spin dump for 24.2. Unfortunately, it looks the same to me as the earlier spin dumps. After looking through the spin dumps earlier today, it appears to me that LibreOffice is spending a lot of time in GetTextArray() in SvxFont::QuickGetTextSize() so I have uploaded the following patch that adds optional logging before and after the GetTextArray() calls in SvxFont::QuickGetTextSize(): When this new logging is enabled and you run LibreOffice in a Terminal, it will display pairs of messages for each GetTextArray() call when you double click in the frame and when you save with the cursor in the frame like below: info:editeng.quicktextsize:22053:7678595:editeng/source/items/svxfont.cxx:482: SvxFont::QuickGetTextSize before GetTextArray(): Case map: 0 Fix kerning: 0 info:editeng.quicktextsize:22053:7678595:editeng/source/items/svxfont.cxx:485: SvxFont::QuickGetTextSize after GetTextArray(): Text length: 222 Text size: 31119x295 What will be interesting to see is if the bug filer sees any pauses between the "before" and "after" messages or if the "Text size" returned has any unusual (e.g. negative) values. I will post again when the logging code is in the nightly 24.2 build along with instructions on how to enable this new logging in a Terminal. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156542] New: FORMATTING - Writer applies inconsistent auto-correction to hyphenation as punctuation.
https://bugs.documentfoundation.org/show_bug.cgi?id=156542 Bug ID: 156542 Summary: FORMATTING - Writer applies inconsistent auto-correction to hyphenation as punctuation. Product: LibreOffice Version: 6.4.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sad_bu...@hotmail.com Description: When writing a block of text and wanting to punctuate it with a pair of hyphens, writer will correctly replace the first interest hyphen [entered as a minus sign] to a hyphen, but will ignore the second. Consider:- This is, as you might imagine, rather annoying. This is - as you might imagine - rather annoying. With Writer, the first hyphen in the second line of text above will be amended from a regular minus sign to a formal hyphen... but the second on [in the example the one between "imagine" and "rather", remains as a minus sign. Writer should be able to tell that this is grammatical punctuation and correct consistently... Steps to Reproduce: 1.Simply enter any sentence that uses a pair of hyphens as punctuation 2. If using the minus sign on the keyboard, note the auto-correct of the first instance and nothing happening with the second 3.Issue is 100% repeatable Actual Results: I observe the first hyphen being auto-corrected by Writer from a short, thicker dash [the minus sign] to a slightly elongated and thinner dash - a textual hyphen. Expected Results: I would like to see both submitted values treated consistently, ideally with both being converted from the mathematical minus sign to the textual hyphen. Reproducible: Always User Profile Reset: Yes Additional Info: I am not sure if the components involved are going to let me do this, but I'm going to try and copy and paste, in to this text box, the two character [correctly transformed and incorrectly left as-is], as auto-edited by Writer. The correctly converted character is "–" The incorrectly ignored character is "-" On my screen, the above examples are visibly different. I'm hoping you might know how to reverse engineer this text back to the relevant UTF-8 character... I don't know how! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156540] Fade in effect shows white artifacts/wrong color of shape in presentation mode (Skia)
https://bugs.documentfoundation.org/show_bug.cgi?id=156540 Patrick Luby changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Patrick Luby --- I can reproduce this bug with both Skia/Metal and Skia/Raster. Interestingly, with Skia disabled, the right colors are used by instead of fading in, it fades out. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156306] tagged PDF export of odt document runs in a loop (hangs)
https://bugs.documentfoundation.org/show_bug.cgi?id=156306 --- Comment #4 from stefan_lange...@t-online.de --- (In reply to Stéphane Guillou (stragu) from comment #3) > Confirmed that it is related to tagged PDF: if turned off in the PDF export > dialog, no hang. This is a very good and for me useful information, many thanks! First I did not know what setting in the german version of PDF export dialog concerns tagged PDF but in trys I have found it is the setting "Indiziertes PDF". I have switched it off and the export to PDF works - my problem seems to be solved. Currently I have no idea why the setting was switched on. Maybe I have switched it on when I started to export documents with a table of contents because the setting "Gliederung exportieren" (Export strcture [?]) is currently switched on too. But it seems both settings are not needed for a working table of contents in the exported PDF document - and it becomes significantly smaller. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156541] Fontwork increases in size when pasting the same fontwork multiple times from Impress to Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156541 --- Comment #1 from Telesto --- Created attachment 188664 --> https://bugs.documentfoundation.org/attachment.cgi?id=188664=edit Sample -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156541] New: Fontwork increases in size when pasting the same fontwork multiple times from Impress to Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156541 Bug ID: 156541 Summary: Fontwork increases in size when pasting the same fontwork multiple times from Impress to Writer Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Fontwork increases in size when pasting the same fontwork multiple times from Impress to Writer Steps to Reproduce: 1. Open the attached file 2. Copy the fontwork 3. Open New Writer document 4. Press and hold CTRL+V Actual Results: The fontwork increases in size Expected Results: The fontwork increases in size Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e26aeb882dd236adf19679d5df9b7ba5da1ed226 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156539] Fontwork with transparency won't be visible in presentation mode with Skia Raster
https://bugs.documentfoundation.org/show_bug.cgi?id=156539 Patrick Luby changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from Patrick Luby --- (In reply to Telesto from comment #2) > There actually two issues > 1) Gradient fill doesn't render in presentation mode > 2) With transparency set to the fontwork -> No fontwork in presentation mode I can reproduce the first case with Skia/Metal, Skia/Raster, and Skia disabled. I can also reproduce the second case with Skia/Raster. However, when I set the fontwork transparency to 50% (see screen snapshot in https://bugs.documentfoundation.org/attachment.cgi?id=188663), the gradient properly renders in a slideshow with Skia/Metal and Skia disabled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156539] Fontwork with transparency won't be visible in presentation mode with Skia Raster
https://bugs.documentfoundation.org/show_bug.cgi?id=156539 --- Comment #3 from Patrick Luby --- Created attachment 188663 --> https://bugs.documentfoundation.org/attachment.cgi?id=188663=edit Sidebar showing 50% transparency set for fontwork -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156540] Fade in effect shows white artifacts/wrong color of shape in presentation mode (Skia)
https://bugs.documentfoundation.org/show_bug.cgi?id=156540 --- Comment #2 from Telesto --- Created attachment 188662 --> https://bugs.documentfoundation.org/attachment.cgi?id=188662=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156539] Fontwork with transparency won't be visible in presentation mode with Skia Raster
https://bugs.documentfoundation.org/show_bug.cgi?id=156539 --- Comment #2 from Telesto --- There actually two issues 1) Gradient fill doesn't render in presentation mode 2) With transparency set to the fontwork -> No fontwork in presentation mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156539] Fontwork with transparency won't be visible in presentation mode with Skia Raster
https://bugs.documentfoundation.org/show_bug.cgi?id=156539 --- Comment #1 from Telesto --- Created attachment 188661 --> https://bugs.documentfoundation.org/attachment.cgi?id=188661=edit Sample -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156540] Fade in effect shows white artifacts/wrong color of shape in presentation mode (Skia)
https://bugs.documentfoundation.org/show_bug.cgi?id=156540 --- Comment #1 from Telesto --- Created attachment 188660 --> https://bugs.documentfoundation.org/attachment.cgi?id=188660=edit Sample -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156540] New: Fade in effect shows white artifacts/wrong color of shape in presentation mode (Skia)
https://bugs.documentfoundation.org/show_bug.cgi?id=156540 Bug ID: 156540 Summary: Fade in effect shows white artifacts/wrong color of shape in presentation mode (Skia) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Fade in effect shows white artifacts/wrong color of shape in presentation mode (Skia) Steps to Reproduce: 1. Open the attached file 2. Press F5 3. Mouse click to start the effect Actual Results: See screenshot Expected Results: Proper color and background during animation Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e26aeb882dd236adf19679d5df9b7ba5da1ed226 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156539] New: Fontwork with transparency won't be visible in presentation mode with Skia Raster
https://bugs.documentfoundation.org/show_bug.cgi?id=156539 Bug ID: 156539 Summary: Fontwork with transparency won't be visible in presentation mode with Skia Raster Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Fontwork with transparency won't be visible in presentation mode with Skia Raster. Didn't test Vulkan Steps to Reproduce: 1. Open the attached file 2. Press F5 Actual Results: No fontwork in presentation mode Expected Results: Should be visible Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e26aeb882dd236adf19679d5df9b7ba5da1ed226 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156531] Unable to create container Window
https://bugs.documentfoundation.org/show_bug.cgi?id=156531 prrv...@gmail.com changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from prrv...@gmail.com --- I'm sorry for the disturbance but after several tests this strange behavior seems related to my test environment (Ubuntu 22.04 - VirtualBox 6.1.38) and has nothing to do with LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156538] Insert Symbol menubutton should indicate symbol name
https://bugs.documentfoundation.org/show_bug.cgi?id=156538 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval Blocks||109232 CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109232 [Bug 109232] [META] Special character dialog and toolbar group button bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109232] [META] Special character dialog and toolbar group button bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109232 Eyal Rozenberg changed: What|Removed |Added Depends on||156538 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156538 [Bug 156538] Insert Symbol menubutton should indicate symbol name -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156538] New: Insert Symbol menubutton should indicate symbol name
https://bugs.documentfoundation.org/show_bug.cgi?id=156538 Bug ID: 156538 Summary: Insert Symbol menubutton should indicate symbol name Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com The Insert Symbol dialog lets one see the name of the selected character (under the enlarged view rectangle). This is often important, especially for: * Distinguishing glpyhs which look similar (e.g. en-dash vs em-dash vs horizontal bar), * Inserting characters in languages foreign to yours, where you identify glyphs only by name * Non-printing characters However - using the Insert Symbol _menubutton_ on the toolbars, there is no indication of the character names. We should add such indication in one, or both, of the following ways: 1. Add a framed label which shows the name of the hovered-over character. 2. Have tooltips for the characters with their names Bikeshedding: Perhaps show the Unicode hex value as well has the name -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156522] Macro recording disabled on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=156522 M-Rick changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #3 from M-Rick --- Ha thank you. LibreOffice > Preferences > Advanced features > Enable Macro recorder. Why is it unactivated by default on macOS ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154625] Every time you start LibreOffice - "Security Warning: The document contains macros."
https://bugs.documentfoundation.org/show_bug.cgi?id=154625 --- Comment #6 from ramirez@outlook.com --- greetings We have just migrated to version 7.5. A Solution to this Problem would also be in our interest because the warning creates uncertainty for the users. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156537] View > Toolbars > Customize... prefers last chosen tab rather than Toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=156537 Eyal Rozenberg changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156537] View > Toolbars > Customize... prefers last chosen tab rather than Toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=156537 Eyal Rozenberg changed: What|Removed |Added Blocks||103238 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103238 [Bug 103238] [META] Customize dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103238] [META] Customize dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103238 Eyal Rozenberg changed: What|Removed |Added Depends on||156537 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156537 [Bug 156537] View > Toolbars > Customize... prefers last chosen tab rather than Toolbars -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156537] New: View > Toolbars > Customize... prefers last chosen tab rather than Toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=156537 Bug ID: 156537 Summary: View > Toolbars > Customize... prefers last chosen tab rather than Toolbars Product: LibreOffice Version: 7.6.0.0 alpha1+ Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com When I use the menus and open View > Toolbars > Customize... - I expect to get a dialog which lets me customize the toolbars. Instead, I get a dialog for customizing all sorts of things - which is ok, as long as the Toolbars pane of this dialog is selected/active. Except that the chosen tab is the persisted one, i.e. the one I last had selected when closing the dialog. This is confusing, and may lead users to try to look for their toolbar of interest in the list of menus, and even customize their menus instead of the toolbar they wanted if they have the same name. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156536] Support ranges / multi-selection for cross-referencing
https://bugs.documentfoundation.org/show_bug.cgi?id=156536 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156536] New: Support ranges / multi-selection for cross-referencing
https://bugs.documentfoundation.org/show_bug.cgi?id=156536 Bug ID: 156536 Summary: Support ranges / multi-selection for cross-referencing Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com At the moment, the Insert | Cross-Reference... dialog only lets you select a single item. However, one often wants to refer to several items, or a range of items. For example: "See clauses 4--6". It would be convenient if the dialog would allow selecting a contiguous sequence of items, and insert two cross-references with an en-dash between then (or the appropriately-localized range signifier). One could go further and support an arbitrary selection, which would be treated as a sequence of single references and ranges of references; each ref or range-of-refs would be treated as usual or as per the above respectively, and be followed by a comma, e,g, "4--6, 10" with 4, 6 and 10 being references. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156535] New: Continual crashing if I select Language/for all text
https://bugs.documentfoundation.org/show_bug.cgi?id=156535 Bug ID: 156535 Summary: Continual crashing if I select Language/for all text Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Linguistic Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: fent...@gmail.com CC: so...@libreoffice.org Description: If I select Language/for all text (but not "for paragraph" or "selection") LO gives the spinning wheel and crashes. Repeatedly. Also, LO will sometimes also not select the language when attempting a simple language check. I've already tried resetting to the default language under "Preferences". No change. Steps to Reproduce: 1. Open odt file 2. Select Tools/Language/for all text/English (USA) 3. Spinning wheel, Mac reports crash under Force Quit/restart Actual Results: Sequentially: Crash, spinning wheel, restart LO, request to restore document, changes (just before the crash) aren't saved. Expected Results: It should have loaded the requested dictionary (either standard English, German or user-created technical dictionaries). When I try tools/spelling, LO refuses to upload any language and no corrections are implemented. Reproducible: Always User Profile Reset: No Additional Info: It doesn't crash when I select Tools/Language/For Selection (or For Paragraph). But is also doesn't check the spelling. "resetting UserProfile"? I have no such profile. I just start the program. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108844] [META] Cut/copy bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108844 Bug 108844 depends on bug 156506, which changed state. Bug 156506 Summary: Cells not marked by marching ants when they were copied https://bugs.documentfoundation.org/show_bug.cgi?id=156506 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156501] Calc View Headers setting is not saved to file
https://bugs.documentfoundation.org/show_bug.cgi?id=156501 ady changed: What|Removed |Added Keywords||dataLoss -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156534] Firebirds DATEADD function can't be executed in Design View, only can be executed in SQL direcct
https://bugs.documentfoundation.org/show_bug.cgi?id=156534 jcs...@libreoffice.org changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jcs...@libreoffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156501] Calc View Headers setting is not saved to file
https://bugs.documentfoundation.org/show_bug.cgi?id=156501 --- Comment #6 from ady --- (In reply to Colin from comment #5) > Is this related Bug 137717 No. The problem described in bug 156501 started in 7.6. If there is some relation, it would be only indirect. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156534] Firebirds DATEADD function can't be executed in Design View, only can be executed in SQL direcct
https://bugs.documentfoundation.org/show_bug.cgi?id=156534 jcs...@libreoffice.org changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||4918 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153295] CALC VIEW Inconsistent file save trigger upon exit if there have been presentation but NO processing changes
https://bugs.documentfoundation.org/show_bug.cgi?id=153295 ady changed: What|Removed |Added Version|4.1.0.4 release |Inherited From OOo --- Comment #15 from ady --- (In reply to Colin from comment #14) > I suspect this is related Bug 137717 Already mentioned in comment 0. And no, the QR code feature is much newer than the problem reported in this bug 153295. BTW, changing the version field to inherited. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156534] Firebirds DATEADD function can't be executed in Design View, only can be executed in SQL direcct
https://bugs.documentfoundation.org/show_bug.cgi?id=156534 --- Comment #1 from jcs...@libreoffice.org --- Created attachment 188659 --> https://bugs.documentfoundation.org/attachment.cgi?id=188659=edit Simple database to test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156534] New: Firebirds DATEADD function can't be executed in Design View, only can be executed in SQL direcct
https://bugs.documentfoundation.org/show_bug.cgi?id=156534 Bug ID: 156534 Summary: Firebirds DATEADD function can't be executed in Design View, only can be executed in SQL direcct Product: LibreOffice Version: 7.6.0.1 rc Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jcs...@libreoffice.org Description: Firebird's DATEADD function can't be executed in Design View, only can be executed in SQL direct, so can't be used in editable queries, because SQL Direct don't generate editable queries Steps to Reproduce: 1. Create a table with at least one date field 2. Create a query in SQL View similar to this: SELECT "ID", "F1", DATEADD( DAY, 5, "F1" ) "F1+5" FROM "T1" 3. Execute the query in with *Run SQL command directly* activated 4. Try to execute the query with *Run SQL command directly* desactivated Actual Results: In 3. It runs, but the result query is not editable In 4. It don't run Expected Results: In 4. It Should run and produce an editable query Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.1 (X86_64) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150748] Indentation when creating a list fails on c) and d)
https://bugs.documentfoundation.org/show_bug.cgi?id=150748 --- Comment #7 from dant...@duck.com --- Perhaps I'm off a bit with prior comment about increase/decrease indent, and I should use Promote and Demote outline level for this purpose - menus and keyboard commands. Nonetheless, I find the promote/demote outline level equally unreliable and inconsistent. I think an overhaul for paragraph indentation, outline level promotion/demotion, with or without subpoints would greatly improve this basic functionality. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150748] Indentation when creating a list fails on c) and d)
https://bugs.documentfoundation.org/show_bug.cgi?id=150748 --- Comment #6 from dant...@duck.com --- Created attachment 188658 --> https://bugs.documentfoundation.org/attachment.cgi?id=188658=edit icons for working with lists - unreliable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156533] Links NOT All Functional
https://bugs.documentfoundation.org/show_bug.cgi?id=156533 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- Could you give a try at last LO version 7.5.5 ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150748] Indentation when creating a list fails on c) and d)
https://bugs.documentfoundation.org/show_bug.cgi?id=150748 --- Comment #5 from dant...@duck.com --- It seems relevant to add here that there inconsistencies between text and associated functionality between Menu Items (like Format > Spacing > "Increase indent") and Tools > Customize > Keyboard commands (like "Indent") Specifically related to this existing report, I tried to set "CTRL + >" and "CTRL + <" to Increase and Decrease list indent, respectively. 1 - you can't find that Keyboard command searching for "indent", yet there are 3 distinct "Increase" options - confusing 2 - the "Increase indent" functionality, through this function .uno:IncreaseIndent does something quite different and unreliable in the doc, compared with the menu option to "Increase indent" noted above It would be nice to have really consistent and reliable nested-list functionality, to easily achieve nested (un-)ordered lists, whether from the menu or keyboard shortcuts. Lists like 1. one 2. two • two-detail • two-detail a. two-detail-a i. two-detail-a-i Right now in this version, such nested lists are really difficult to achieve -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155952] WRITER: Absatzkontrolle in Tabellen wirkt nicht
https://bugs.documentfoundation.org/show_bug.cgi?id=155952 Carsten_M. changed: What|Removed |Added Ever confirmed|1 |0 Assignee|libreoffice-b...@lists.free |c.muel...@tankanlagenbau.de |desktop.org | Status|NEEDINFO|UNCONFIRMED CC||c.muel...@tankanlagenbau.de --- Comment #2 from Carsten_M. --- Created attachment 188657 --> https://bugs.documentfoundation.org/attachment.cgi?id=188657=edit example-file Hello Dieter, thanks for your answer! Enclosed is an example file. It is set that paragraphs should not be separated. However, as you can see, paragraphs will be separated if the text is in a table and the table row is broken across the page. So the paragraph setting does not work here as would be expected. Hope this helps. Regards, Carsten -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156533] New: Links NOT All Functional
https://bugs.documentfoundation.org/show_bug.cgi?id=156533 Bug ID: 156533 Summary: Links NOT All Functional Product: LibreOffice Version: 7.4.5.1 release Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: n...@grumpie.ca Description: I have a LARGE PDF Document that is utilized to store our fave Recipes or External Links to them. While working inside LibreOffice, EVERYTHING works as expected, However, when I Exoprt as a PDF document (to share with Family & Friends) RANDOM Links no longer function. The current PDF is 42.6 MB! Would it be better to Split this set of Recipes, into an INDEX Page with references to Individual Documents for each Recipe Category (with a Link back to the INDEX Page. OS version is 13.3.1 VENTURA (NOT Listed in teh DropDown box) Steps to Reproduce: 1.Edit LibreOffice Document 2.EXPORT as PDF 3.Open the PDF 4.Try the Cross-References * External Links Actual Results: Random FAILURE to Link Properly. Expected Results: Links should work the SAME iin the PDF as in the OF document. Reproducible: Always User Profile Reset: Yes Additional Info: Perform the "LINK" functions the SAME WAY, inside the PDF file as it does in LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104918] LibreOffice SQL parser chokes on Firebird's DATEDIFF syntax, making use impossible in normal (non-direct SQL) queries
https://bugs.documentfoundation.org/show_bug.cgi?id=104918 jcs...@libreoffice.org changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jcs...@libreoffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156161] Organise Macros > Python requires JRE
https://bugs.documentfoundation.org/show_bug.cgi?id=156161 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Mike Kaganski --- Repro. Steps: 1. Have a JRE/JDK of properarchitecture. 2. In LO, make sure to enableuse of JRE, *and select a JRE from the list* (i.e., a dot must be displayed on the radiobutton next to that JRE under options->LibreOffice->advanced). 3. Open Tools->Macros->Organize Macros->Python => See that there's no warning 4. Close LibreOffice 5. Uninstall the chosen JRE from system. 6. Open LibreOffice, and checkstep 3. => The "JRE missing" warning appears. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156528] Very wide page affects following pages' objects size
https://bugs.documentfoundation.org/show_bug.cgi?id=156528 Mike Kaganski changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Mike Kaganski --- https://gerrit.libreoffice.org/c/core/+/155025 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156532] UI: Slide panel sizes changes width when applying a template style
https://bugs.documentfoundation.org/show_bug.cgi?id=156532 --- Comment #1 from Telesto --- Still OK with Version: 7.0.7.0.0+ (x64) Build ID: 626ea4e62a3e5005fe9825923a1c0c5bdb61cc08 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156532] New: UI: Slide panel sizes changes width when applying a template style
https://bugs.documentfoundation.org/show_bug.cgi?id=156532 Bug ID: 156532 Summary: UI: Slide panel sizes changes width when applying a template style Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: UI: Slide panel sizes changes width when applying a template style Steps to Reproduce: 1. Open LibreOffice start center 2. Launch Impress (assuming template wizard turned ON) 3. Cancel the template wizard 4. Expand size of the slide panel to maximum 5. Close Impress (back to Start Center) 6. Open Impress again 7. Select a template & press OK -> Width of the slide panel changes -- addition 8. Expand the slide panel to maximum again 9. File -> Templates -> Manage templates (press Open) 10. Select a template -> Width shrinks 11. File -> Templates -> Manage templates 12. Select a template and press Open (now it's OK) Actual Results: The width is inconsistent. Expected Results: The width of the side panel shouldn't be 'arbitrary'. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e26aeb882dd236adf19679d5df9b7ba5da1ed226 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136615] Re-consider date/time parts calculation for functions and formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=136615 --- Comment #27 from Regina Henschel --- Hi Eike, you have worked on it. Do the results in LibreOffice match the definitions in upcoming ODF 1.4? The draft of the upcoming ODF 1.4 is in https://github.com/oasis-tcs/odf-tc/tree/master/docs/odf1.4/part4-formula Here an extract: Second = MOD(ROUND(T * 86400) ; 60) Minute = (MOD(ROUND(T * 86400) ; 3600) - Second) / 60 Hour = (MOD(ROUND(T * 86400) ; 86400) - Minute * 60 - Second) / 3600 DAY( DateParam D ); Returns the day portion of D after first rounding (using ROUND()) to the nearest second. MONTH( DateParam D ); Returns the month portion of D after first rounding (using ROUND()) to the nearest second. YEAR( DateParam D ); Returns the year portion of D after first rounding (using ROUND()) to the nearest second. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156531] New: Unable to create container Window
https://bugs.documentfoundation.org/show_bug.cgi?id=156531 Bug ID: 156531 Summary: Unable to create container Window Product: LibreOffice Version: 7.5.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: prrv...@gmail.com Description: I use the service: com.sun.star.awt.ContainerWindowProvider to create child windows. All my windows are created by the same function getContainerWindow() (https://github.com/prrvchr/SQLiteOOo/blob/main/uno/lib/uno/unotool/unotool.py#L251) Steps to Reproduce: 1. Install jdbcDriverOOo extension (https://prrvchr.github.io/jdbcDriverOOo/) 2. Install SQLiteOOo extension (https://prrvchr.github.io/SQLiteOOo/) 3. Go to: Tools -> Options -> Base drivers -> JDBC Driver -> Embedded SQLite driver Actual Results: The logs window is not displayed and an error occurs when creating it: uno.com.sun.star.lang.WrappedTargetRuntimeException: at ./scripting/source/dlgprov/dlgprov.cxx:588 Expected Results: The logs window is displayed Reproducible: Always User Profile Reset: No Additional Info: Occur on: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Ubuntu package version: 4:7.5.5~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded under VirtualBox 6.1.38 No problem on: Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb) Locale: en-US (fr_FR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 Frie changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 --- Comment #3 from Frie --- I have used the following workaround: copy the table to calc end then copy the calc selection of the table to the new database (append data). The table must exist with the same specifications in the new destination database -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||7618 Keywords||dataLoss --- Comment #2 from Robert Großkopf --- Bug appears in LO 7.5.5.2 on OpenSUSE, but also in older versions of LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127618] can't copy a table with a row of 'numeric, 2 dec' into a new tabel in 'base'.
https://bugs.documentfoundation.org/show_bug.cgi?id=127618 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6530 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 --- Comment #1 from Robert Großkopf --- Created attachment 188656 --> https://bugs.documentfoundation.org/attachment.cgi?id=188656=edit Target database file to insert data from copied table. Same bug has been reported at https://bugs.documentfoundation.org/show_bug.cgi?id=127618 but this bug has been closed as WORKSFORME. Seems reporter didn't notice he first used Firebird (was the default for some years) and the used HSQLDB (Firebird back to experimental). As we see: Firebird is still experimental … -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] New: FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 Bug ID: 156530 Summary: FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers. Product: LibreOffice Version: 7.5.5.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 188655 --> https://bugs.documentfoundation.org/attachment.cgi?id=188655=edit Source database file for copying a table with decimal places Take the two attached databases. Copy the table from "DecimalCopy.odb" to "DecimalCopyTarget.odb". You could add the data to the table in "DecimalCopyTarget.odb" or let the wizard create a new table. No actions needed, so choose "Create" in the wizard. Have a look at the original table and to the result. Field with 2 decimal places: 123.45 will copied to 1.23 (divided by 100) Field with 3 decimal places: 123.456 will copied to 0.123 (divided by 1000) Filed with 4 decimal places: 123.4567 will copied to 0.0123 (divided by 1) Note: 1. If the data will be pasted to Calc the numbers will be pasted with right values. 2. If the data will be pasted to the same *.odb-file as table source it will also be pasted right. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156512] Base don't refresh inserted row when using an updatable XResultSet
https://bugs.documentfoundation.org/show_bug.cgi?id=156512 --- Comment #4 from prrv...@gmail.com --- I don't know how to force Base to use updatable resultset with a driver other than jdbcDriverOOo. I don't even know if this other driver exists. On the other hand, it is possible for me to record in a log file all the activity of the ResultSet and therefore to know exactly how Base proceeds with an updatable resultset. Wouldn't that be a good starting point for resolving this issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156529] New: ODF: element as child of is not implemented (title of legend)
https://bugs.documentfoundation.org/show_bug.cgi?id=156529 Bug ID: 156529 Summary: ODF: element as child of is not implemented (title of legend) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: low Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 188654 --> https://bugs.documentfoundation.org/attachment.cgi?id=188654=edit Legend with title ODF has an optional child element of the element. If it exists, it is a title of the legend. LibreOffice currently ignores this legend title. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156506] Cells not marked by marching ants when they were copied
https://bugs.documentfoundation.org/show_bug.cgi?id=156506 Patrick Luby changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |plub...@neooffice.org |desktop.org | --- Comment #9 from Patrick Luby --- (In reply to Michael Weghorn from comment #8) > See tdf#155414 comment 26: > This is a Windows-only regression from > > commit 9d68c794d67259a38de1465090f6f1e7fb588d62 > Author: Patrick Luby > Date: Fri Jul 21 19:55:02 2023 -0400 > I have reverted the portion of the above commit that stops the animated border when a copy action is performed in a different document by cancelling the animated border. I'll post again when the fix is in the nightly master build. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156528] New: Very wide page affects following pages' objects size
https://bugs.documentfoundation.org/show_bug.cgi?id=156528 Bug ID: 156528 Summary: Very wide page affects following pages' objects size Product: LibreOffice Version: 7.0.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Created attachment 188653 --> https://bugs.documentfoundation.org/attachment.cgi?id=188653=edit A very wide first page, and not-so-wide second The attached FODT has two pages, first having width 5100 mm, height 210 mm; and the second having width 210, height 297 mm. Both pages contain a rectangle, extending the whole area inside the pages' 20mm margins. Exporting the document to PDF makes the rectangle on the second page to be around 1/2 linear size (1/4 area size) of what it should be. This started after commit 4830592b780833cf5eee2aef30bc9c5d444dfb24 (PDF export: fix handling of page sizes larger than 508 cm, 2020-04-16). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156513] AutoIncrementIsPrimaryKey is no longer considered in Base 7.5 and above
https://bugs.documentfoundation.org/show_bug.cgi?id=156513 --- Comment #16 from prrv...@gmail.com --- I confirm that if I install the libreoffice-qt5 package then it changes my VCL version and it works... Work on: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Ubuntu package version: 4:7.5.5~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded How to get the same result: VCL: qt5 (cairo+xcb) by compiling the gerrit version? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156527] New: ODF: Remove deprecated presentation animations
https://bugs.documentfoundation.org/show_bug.cgi?id=156527 Bug ID: 156527 Summary: ODF: Remove deprecated presentation animations Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: lowest Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de ODF 1.4 will deprecate the element and its child elements. Those correspond to animations in sxi format from OOo1. In my tests I see that when elements in sxi files or odp files are imported, they are converted to SMIL animations and saved as such. But I have not examined the code, whether that really happens in all cases. Task is to verify that in all cases elements are converted to SMIL animations and that a element is never written on save. No longer used code has to be removed. This is not urgent, because ODF 1.4 only deprecates the elements. And the remove in ODF 1.5 will not be in near future. This bug report is only to not forget it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156239] Entry for loext:num-list-format it missing in List of LibreOffice ODF Extensions
https://bugs.documentfoundation.org/show_bug.cgi?id=156239 --- Comment #1 from Dieter --- (In reply to Regina Henschel from comment #0) > This should have been done by the developer. Vasily, can you have a look at it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155870] Format Word 2003 XML not supported
https://bugs.documentfoundation.org/show_bug.cgi?id=155870 --- Comment #6 from Dieter --- (In reply to Harry Fischer from comment #5) > Created attachment 188351 [details] > Sample DOCX with defect Header > > I know it is off topic, but here is a file "sample.docx", were the header is > not displayed with LibreOffice I confirm this. Header in MS word shows address and header in LO shows only Logo. Do you want to narrow down bug report to that problem? "Sometimes it pdisplays documents wrong" is too global. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155741] Allow insertion of items into master without a selected item
https://bugs.documentfoundation.org/show_bug.cgi?id=155741 --- Comment #3 from Dieter --- Created attachment 188652 --> https://bugs.documentfoundation.org/attachment.cgi?id=188652=edit Screenshot of Navigator in empty master document (In reply to Eyal Rozenberg from comment #2) > But initially, I don't even have any items in the master document. Screenshot shows how it looks for me. If you click on insert icon there is the message "[no selection possible]". Perhaps there could be an improvement to make it more clear, that you first have to select an item -- You are receiving this mail because: You are the assignee for the bug.
