[Libreoffice-bugs] [Bug 144940] Calc disables header/footer or looses footer content when saves a spreadsheet ( part 2 )
https://bugs.documentfoundation.org/show_bug.cgi?id=144940 --- Comment #11 from Timur --- In addition to steps from scratch, also sample can be used. Open ODS attachment 174988 [details] from bug 144368, confirm F/H turned on (regardless if content changed) and save, on reopen they are turned off. -- 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 --- Comment #1 from Igor --- Created attachment 175606 --> https://bugs.documentfoundation.org/attachment.cgi?id=175606=edit Sample data https://ask.libreoffice.org/t/can-the-data-form-be-modified/69062 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145017] New: [Calc] The action of the New button in the Data Form seemed illogical
https://bugs.documentfoundation.org/show_bug.cgi?id=145017 Bug ID: 145017 Summary: [Calc] The action of the New button in the Data Form seemed illogical Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eei...@inbox.ru Description: New button (guide): fill the record (table row cells) with the form fields contents and jump to the next record (?) or add a new record in the bottom of the table. 1. The action of the New button seemed illogical to me. There should be a transition to a new record, but this button first works as Next. If you go to a new record (use the scroll bar for a large list) and enter it, and then go to the previous one, the new record will not be saved, which is also incorrect (contradicts the principle of working with a record in the database). It is necessary to press the New button again or the Enter key. 2. If a certain record is selected on the sheet, it should be displayed when the form is opened. But the first record always opens. And how do I go to a new record without a mouse? Press and hold the Enter button. Wait… In this case, the same New button will be used with repetition. Steps to Reproduce: 1.As described... 2. 3. Actual Results: Illogical behavior Expected Results: Logical behavior Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.4 / LibreOffice Community Build ID: ce769e3009755dcf0082844e386f5dca4c8ecb2f CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61715] [suggestion] Smooth animations for the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=61715 --- Comment #5 from george --- Smooth cursor animation would be great, so more people could migrate from MS Office to Libre Office. Please consider this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144696] Protected table cells may be formatted in *some* workflows
https://bugs.documentfoundation.org/show_bug.cgi?id=144696 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 144686] UI: comment box oversized on file open until click in document (triggering a resize)
https://bugs.documentfoundation.org/show_bug.cgi?id=144686 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 140947] Missing window redraw
https://bugs.documentfoundation.org/show_bug.cgi?id=140947 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 140947] Missing window redraw
https://bugs.documentfoundation.org/show_bug.cgi?id=140947 --- Comment #8 from QA Administrators --- Dear Sandro Santilli, 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 140944] can't paste anything onto writer but can to other things
https://bugs.documentfoundation.org/show_bug.cgi?id=140944 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 140944] can't paste anything onto writer but can to other things
https://bugs.documentfoundation.org/show_bug.cgi?id=140944 --- Comment #3 from QA Administrators --- Dear cromaat93, 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 140937] LibreOffice slow on MacBook Air M1
https://bugs.documentfoundation.org/show_bug.cgi?id=140937 --- Comment #4 from QA Administrators --- Dear and...@lohesurf.eu, 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 140937] LibreOffice slow on MacBook Air M1
https://bugs.documentfoundation.org/show_bug.cgi?id=140937 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 140929] Crash in: SwContentNode::GetAttr(SfxItemSet &)
https://bugs.documentfoundation.org/show_bug.cgi?id=140929 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 140929] Crash in: SwContentNode::GetAttr(SfxItemSet &)
https://bugs.documentfoundation.org/show_bug.cgi?id=140929 --- Comment #6 from QA Administrators --- Dear teamholly, 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 140904] crashing
https://bugs.documentfoundation.org/show_bug.cgi?id=140904 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 140904] crashing
https://bugs.documentfoundation.org/show_bug.cgi?id=140904 --- Comment #3 from QA Administrators --- Dear flyingchicken3000, 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 140897] Copy Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=140897 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 140897] Copy Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=140897 --- Comment #4 from QA Administrators --- Dear Ash, 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 141620] Crash in: libc-2.27.so
https://bugs.documentfoundation.org/show_bug.cgi?id=141620 --- Comment #2 from QA Administrators --- Dear Colin, 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 141604] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=141604 --- Comment #3 from QA Administrators --- Dear midgley.tom, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141595] libreoffice crashed
https://bugs.documentfoundation.org/show_bug.cgi?id=141595 --- Comment #2 from QA Administrators --- Dear w scott, 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 133219] Calc Conditional formatting breaks/not saved correct
https://bugs.documentfoundation.org/show_bug.cgi?id=133219 --- Comment #12 from QA Administrators --- Dear e688497, 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 84507] FORMATING: Text does not fit to contour in rotated polygon or bézier curve
https://bugs.documentfoundation.org/show_bug.cgi?id=84507 --- Comment #14 from QA Administrators --- Dear Janusz, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 49306] FILEOPEN Writer shows hidden graphics that's not visible in Word from header in strange .doc
https://bugs.documentfoundation.org/show_bug.cgi?id=49306 --- Comment #21 from QA Administrators --- Dear Lionel Elie Mamane, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 46798] FORMATTING: Hard coded "Text Centered" in new Shapes, Text boxes and Drawing objects
https://bugs.documentfoundation.org/show_bug.cgi?id=46798 --- Comment #7 from QA Administrators --- Dear nomnex, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 37937] Saving file dialog, no warning about restricted chars in filename
https://bugs.documentfoundation.org/show_bug.cgi?id=37937 --- Comment #15 from QA Administrators --- Dear Michal (JabLuszko) Karwowski, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 118667] Heading numbering is not continuous for the second and more RTF-paste, when pasting the same content (per Comment 6)
https://bugs.documentfoundation.org/show_bug.cgi?id=118667 --- Comment #7 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#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 117479] File size of the presentation file doesn't shrink when saving a file with the image Converted to 3D Rotation object removed
https://bugs.documentfoundation.org/show_bug.cgi?id=117479 --- Comment #3 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#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 107439] librelogo does not work with language set to Finnish
https://bugs.documentfoundation.org/show_bug.cgi?id=107439 --- Comment #10 from QA Administrators --- Dear Ari Latvala, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 100576] Changing text direction moves object on page
https://bugs.documentfoundation.org/show_bug.cgi?id=100576 --- Comment #4 from QA Administrators --- Dear fiftyigfuci_f_mi, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 145016] UI: Selection of cells in left-side of the freezed area selects cells outside of the selection range
https://bugs.documentfoundation.org/show_bug.cgi?id=145016 Kevin Suo changed: What|Removed |Added CC||szymon.k...@collabora.com OS|All |Linux (All) Keywords||bibisected, regression --- Comment #1 from Kevin Suo --- Bibisected to range: 8ede76d9accc8e3b1ea2c8e332cbb373a1b4d9cf..2dfe1726d5262820c910d810b955ea73d3c7ae95 In which the following commit is suspicious: author Szymon Kłos 2021-08-17 16:56:22 +0200 commit 57a628d540287c4bfa8251e50279f4879faa184d (patch) calc: get rects faster for simple selection Adding Szymon Kłos to cc: could you please take a look? Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145016] New: UI: Selection of cells in left-side of the freezed area selects cells outside of the selection range
https://bugs.documentfoundation.org/show_bug.cgi?id=145016 Bug ID: 145016 Summary: UI: Selection of cells in left-side of the freezed area selects cells outside of the selection range Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Steps to Reproduce: 1. New Calc, put cursor at cell B3. 2. Click the "Freeze Row/Column" toolbar button. 3. Select range A3:A10. Expected Result: It should indicate that cells A3:A10 are selected. Current Result: It is indicated that cells A3:B10 are selected. This bug seems to only affect UI appearance, and not affecting editing, as when I paste sth into the selected cells only A3:A10 are pasted. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 418e56997c9e63a5bc669c1b79157b2a4dbf6a2c CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.3-CN Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144903] (spam)
https://bugs.documentfoundation.org/show_bug.cgi?id=144903 Aron Budea changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144903] (spam)
https://bugs.documentfoundation.org/show_bug.cgi?id=144903 Aron Budea changed: What|Removed |Added Resolution|--- |INVALID CC||ba...@caesar.elte.hu Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71481] Clone formatting appends copied formatting rather than overwriting applied formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=71481 Aron Budea changed: What|Removed |Added CC||brian.giff...@eastlink.ca --- Comment #23 from Aron Budea --- *** Bug 144809 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144809] Clone formatting does not work in some cases in LibreWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=144809 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||ba...@caesar.elte.hu Resolution|--- |DUPLICATE --- Comment #2 from Aron Budea --- This looks like a duplicate of bug 71481. *** This bug has been marked as a duplicate of bug 71481 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145011] libreoffice won't launch
https://bugs.documentfoundation.org/show_bug.cgi?id=145011 --- Comment #1 from rachel...@gmail.com --- By a very odd twist of fate, I have a second hard drive with a nearly unused windows install. The install's from the factory restore disks that I made when I got this thing. It's got a few browsers loaded but I barely used it. It was a backup, I guess. Anyway, I tried loading the same version of LO on that and got the same error. I have no personal files on that drive, and barely any apps. No years of loading and uninstalling apps. Couldn't ask for a better sandbox. I realize that the number of people who are experiencing this problem may not be huge and will understand if your attention is needed more elsewhere. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145010] Invisible animations in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145010 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from Regina Henschel --- Please attach a presentation that has the described problems. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142344] Navigator jumps to table while navigating over headings
https://bugs.documentfoundation.org/show_bug.cgi?id=142344 --- Comment #11 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a5ba8d94e6c36a7d79276416cc5acad9a1f6e54e tdf#142344 SwNavigator: Keep heading selected after navigating to 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 142344] Navigator jumps to table while navigating over headings
https://bugs.documentfoundation.org/show_bug.cgi?id=142344 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 145015] WordArt type "Button" from section "Follow Path" has wrong middle part
https://bugs.documentfoundation.org/show_bug.cgi?id=145015 --- Comment #1 from Regina Henschel --- Created attachment 175605 --> https://bugs.documentfoundation.org/attachment.cgi?id=175605=edit Screenshot of rendering in PowerPoint and LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145015] New: WordArt type "Button" from section "Follow Path" has wrong middle part
https://bugs.documentfoundation.org/show_bug.cgi?id=145015 Bug ID: 145015 Summary: WordArt type "Button" from section "Follow Path" has wrong middle part Product: LibreOffice Version: Inherited From OOo Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 175604 --> https://bugs.documentfoundation.org/attachment.cgi?id=175604=edit WordArt shape 'Button' Open attached document. It contains a shape type "Button" from section "Follow Path" in "abc Transform" (=WordArt) in PowerPoint. The shapes form section "Follow Path" are imported with ScaleX=true in property 'TextPath' in 'CustomShapeGeometry'. That means, that the text keeps its original font size as long as there is enough place. That happens for the two arcs of the shape, but in the middle part, the text is stretched. The second attachment has a screenshot with comparison of rendering in PowerPoint and LibreOffice. This is not an import error but likely a error somewhere in EnhancedCustomShapeFontWork.cxx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145014] New: Collabora Office: on Android the automatic fontcolor does ot work
https://bugs.documentfoundation.org/show_bug.cgi?id=145014 Bug ID: 145014 Summary: Collabora Office: on Android the automatic fontcolor does ot work Product: LibreOffice Version: 6.4 all versions Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.ku...@gmail.com When I set black or any dark backround color and automatic font color, the font color does not automatically adjust to the backround color, as it does in the desktop version of Libre Office. 1) open any text document 2) select any text 3) set black backround color 4) set automatic font color System information: OS: Android Device: Lenovo TB-7304F App version: 6.4.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145013] New: Collabora Office: in submenus the panel with formating buttons dissapears
https://bugs.documentfoundation.org/show_bug.cgi?id=145013 Bug ID: 145013 Summary: Collabora Office: in submenus the panel with formating buttons dissapears Product: LibreOffice Version: 6.4 all versions Hardware: ARM OS: Android Status: UNCONFIRMED Severity: minor Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.ku...@gmail.com When taping on buttons for changing font size in submenus the entire panel with font formating buttons dissapear. Steps to reproduce: 1) open any text document 2) on the botton right corner tap on the edit button 3) tap on the button whith framed A 4) tap on any submmenu button (f.e. styles) 5) tap on button for increasing or decreasing font size System information: OS: Android Device: Lenovo TB-7304F App version: 6.4.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145012] New: Collabora Office: chaotical possition of button for creating indexes
https://bugs.documentfoundation.org/show_bug.cgi?id=145012 Bug ID: 145012 Summary: Collabora Office: chaotical possition of button for creating indexes Product: LibreOffice Version: 6.4 all versions Hardware: ARM OS: Android Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.ku...@gmail.com Through the menus, in my opinion there are chaotically placed buttons for index settting. For example on the main menu for character formating (button with a framed A leads here), the buttons are on the bottom of the function list. While in the submenu with font styles, the are the buttons placed next to the button for increasing and decreasing font size, which I think is the most logic possition. 1) open any text document 2) on the botton right corner tap on the edit button 3) tap on the button whith framed A 4) go through all submenus 5) you will see differenct positions of buttons for index setting between the submenus System information: OS: Android Device: Lenovo TB-7304F App version: 6.4.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145010] Invisible animations in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145010 --- Comment #1 from ns-libreoffice-91...@jonny007-mkd.de --- I upgraded to version 7.0.4 and the issue is still the same. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145011] New: libreoffice won't launch
https://bugs.documentfoundation.org/show_bug.cgi?id=145011 Bug ID: 145011 Summary: libreoffice won't launch Product: LibreOffice Version: 7.1.6.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rachel...@gmail.com Description: libreoffice won't launch. Problem Event Name: APPCRASH Application Name: soffice.bin Application Version: 7.1.6.2 Application Timestamp:6135e2a5 Fault Module Name:skialo.dll Fault Module Version: 7.1.6.2 Fault Module Timestamp: 61353cf8 Exception Code: c01d Exception Offset: 0052b9c0 OS Version: 6.1.7601.2.1.0.768.3 Locale ID:1033 Additional Information 1: 5a41 Additional Information 2: 5a41c51d9bd69181daf1841feb241a4e Additional Information 3: 9293 Additional Information 4: 9293315362e95195c47ac496cb014c8d Uninstalled, rebooted, reinstalled. Safe mode works. video drivers are up to date. Running Win7 and it's as up to date as it can be. Steps to Reproduce: Click on Libreoffice icon. Watch it crash. Actual Results: Libreoffice crashes without opening. Expected Results: Libreoffice opens. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.1.6.2 (x64) / LibreOffice Community Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3 CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108908] [META] Visual Basic for Applications (VBA) macro issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108908 Bug 108908 depends on bug 76104, which changed state. Bug 76104 Summary: VBA: set font color in cell https://bugs.documentfoundation.org/show_bug.cgi?id=76104 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76104] VBA: set font color in cell
https://bugs.documentfoundation.org/show_bug.cgi?id=76104 Andreas Heinisch changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #13 from Andreas Heinisch --- Tested again. It seems both error are gone in: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: a4c11b853febd073d310251a4891cdc0ac54e0fa CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145010] New: Invisible animations in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145010 Bug ID: 145010 Summary: Invisible animations in Impress Product: LibreOffice Version: 6.1.5.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ns-libreoffice-91...@jonny007-mkd.de I am seeing weird behavior in Impress which can be best explained with invisible animations, i.e. animations that exist but are not shown in the animation list and don’t have a visible effect during presentation. What I did - I created a couple of slides - and added Fade In animation for the text fields. - Then I copied all the slides and adjusted the animations (from “On Click” to “With Previous” and adjustments for Delays etc.). - Finally I saved the file and opened it again. What I observe 1. Many of my animations on the text bodies were gone, i.e. the text was immediately visible in presentation mode. 2. So I created the animations again. But when shifting them in the order, there seems to be an invisible element in the list which I have to pass. What do I mean with this: I have animations A, B and C (in this order), and I want to shift C above B. To achieve this, I have to click “Move Up” twice. I can move B above A with another “Move Up”, so it is not a general problem. It is the same when moving it back down: I can move B below A with one “Move Down”, and need two more “Move Downs” to move B below C. There seems to be an invisible animation item in the list above C! 3. During presentation, I have to click once after the B animation, and one more time to start C. So this invisible animation seems to start On Click, but there is nothing that happens. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76104] VBA: set font color in cell
https://bugs.documentfoundation.org/show_bug.cgi?id=76104 --- Comment #12 from Andreas Heinisch --- It seems the bug is gone in: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: a4c11b853febd073d310251a4891cdc0ac54e0fa CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-US Calc: CL However, the font weight error remains. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144940] Calc disables header/footer or looses footer content when saves a spreadsheet ( part 2 )
https://bugs.documentfoundation.org/show_bug.cgi?id=144940 Mike Kaganski changed: What|Removed |Added CC||marce...@zonnet.nl --- Comment #10 from Mike Kaganski --- *** Bug 145007 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145007] LibreOffice doesn't keep footers
https://bugs.documentfoundation.org/show_bug.cgi?id=145007 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 144940 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145009] New: After changing font in Collabora office for Android, the font list jump back to its begining
https://bugs.documentfoundation.org/show_bug.cgi?id=145009 Bug ID: 145009 Summary: After changing font in Collabora office for Android, the font list jump back to its begining Product: LibreOffice Version: 6.4 all versions Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.ku...@gmail.com When I change font in Android version of collabora office, the font list jumps back to its begining. So when I want to use another font I have to scroll through the whole list again. Steps to reproduce: 1) open any text document 2) on the botton right corner tap on the edit button 3) tap on the button whith framed A 4) in the menu tap on "Font name" 4) scroll the font list and select any font System information: OS: Android Device: Lenovo TB-7304F App version: 6.4.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145002] Crash when type command
https://bugs.documentfoundation.org/show_bug.cgi?id=145002 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Julien Nabet --- On pc Debian x86-64 with master sources updated today + gen rendering, I don't reproduce this. Do you reproduce this with any pdf file? Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145008] New: Deleting a symbol next to the inserted picture deletes the picture and symbol
https://bugs.documentfoundation.org/show_bug.cgi?id=145008 Bug ID: 145008 Summary: Deleting a symbol next to the inserted picture deletes the picture and symbol Product: LibreOffice Version: 7.0.4.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: blbulyandavbul...@gmail.com Description: I inserted a picture in the document. After it I wrote a symbol. When I deleted the symbol, then a picture deleted also. Steps to Reproduce: 1.Insert a picture in the document 2.Write a symbol 3.Delete symbol Actual Results: Picture delete and symbol delete Expected Results: Symbol will delete, picture will not delete Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); ИП: ru-RU Debian package version: 1:7.0.4-4 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145007] New: LibreOffice doesn't keep footers
https://bugs.documentfoundation.org/show_bug.cgi?id=145007 Bug ID: 145007 Summary: LibreOffice doesn't keep footers Product: LibreOffice Version: 7.2.1.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: marce...@zonnet.nl I've noticed that LibreOffice Calc disables the footer settings when you want to make use of it in a Calc document. When you enable the footer function and make use of it, it disables it every time when you restart a saved document. Re-saving the document again and re-opening it gives the same result: the footers are disabled again. It just doesn't remember the setting. Info about LibreOffice: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: nl-NL (nl_NL.UTF-8); UI: nl-NL Ubuntu package version: 1:7.2.1-0ubuntu0.20.04.1~lo1 Calc: threaded Cheers! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144995] FILEOPEN ODT: Slow opening (220 seconds to screen with 7.3; 60 seconds with 4.4.7.2 ) for a large document with lots of changes tracked (in shown mode), and being combi
https://bugs.documentfoundation.org/show_bug.cgi?id=144995 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||noelgran...@gmail.com Ever confirmed|0 |1 --- Comment #2 from Julien Nabet --- Noel: I attached a Flamegraph in my previous comment, thought you might be interested in this one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144995] FILEOPEN ODT: Slow opening (220 seconds to screen with 7.3; 60 seconds with 4.4.7.2 ) for a large document with lots of changes tracked (in shown mode), and being combi
https://bugs.documentfoundation.org/show_bug.cgi?id=144995 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- Created attachment 175603 --> https://bugs.documentfoundation.org/attachment.cgi?id=175603=edit perf flamegraph Here's a Flamegraph retrieved on pc Debian x86-64 with master sources updated today. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121010] [META] Font size bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=121010 Bug 121010 depends on bug 83090, which changed state. Bug 83090 Summary: UI: Entered font sizes (e.g., 12.4 pt, 12.7 pt) are being rounded off (rather than up) in the toolbar / sidebar https://bugs.documentfoundation.org/show_bug.cgi?id=83090 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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 See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |7674| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89297] Header, footer and page number missing on second page when saved as docx (continuous section breaks enhancement request)
https://bugs.documentfoundation.org/show_bug.cgi?id=89297 Justin L changed: What|Removed |Added CC||dsik...@hotmail.com --- Comment #23 from Justin L --- *** Bug 137674 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137674] Page margins are wrong in a specific DOC with small margin that overlaps footer
https://bugs.documentfoundation.org/show_bug.cgi?id=137674 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |4013| --- Comment #10 from Justin L --- This document has two continuous section breaks on the first page. LO has absolutely nothing resembling continuous breaks. That makes this a duplicate of bug 89297. *** This bug has been marked as a duplicate of bug 89297 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145006] New: LO Writer PDF print bug
https://bugs.documentfoundation.org/show_bug.cgi?id=145006 Bug ID: 145006 Summary: LO Writer PDF print bug Product: LibreOffice Version: 7.1.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: walt.tuv...@gmail.com Description: PDF generated by LO Writer prints buggily. Steps to Reproduce: 1. Retrieve the LO Writer file: https://f002.backblazeb2.com/file/PublicSharedFiles/MullingSpices.odt. 2. Generate PDF (default settings) from it: https://f002.backblazeb2.com/file/PublicSharedFiles/MullingSpices.pdf. 3. Compare them. They look identical. 4. But now, PRINT hardcopies of those 2 docs. 5. The Writer printed copy looks OK. 6. But the PDF printed copy (using Okular) is buggy: the "F" char at the beginning of the final 2 paragraphs (both columns) is wonky. Actual Results: See above. Expected Results: See above. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.6.2.0+ Environment: CPU threads: 8; OS: Linux 5.14 User Interface: default; VCL; kf5 Locale: en-US (en_US.UTF-8); UI: en-US Misc: Calc: threaded NOTE: I've seen similar bugginess before, but only in very large docs (so I didn't report it), but this time I've got a minimal example. -- 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 #5 from Justin L --- How to fix? I don't think the computer can do that. 1.) If the follow style doesn't have a separate first header/footer, then the first section's header/footer could be moved to the follow style - but that would lose any special margins on the first page. 2.) The two page styles (aka sections) could remain separate, but in that case we have no ability to know when to apply the second section (since there is no explicit page break). [I believe this is the current implementation.] [One complication here is that DOCX import STILL uses First Page style instead of "different content on first" (bug 136472), so care is needed not to break the import side, because we don't know if the First Page usage comes from import or from user design.] AFAIK, at present, the First Page settings will apply to the rest of the document. Whether that is appropriate depends on the document itself. [Note that "First Page" is simply an implementation of a generic first-follow, so unless the built-in "First Page" style is treated as a special edge case, we can't make assumptions about how the first-follow style should work. I suppose a case could be made that in these cases the FOLLOW style's settings should take priority. I believe at present the FIRST style's settings are the ones being applied.] I think my personal take is that we should NOT try to improve the current experience. Since this is all guesswork, a poor response is best since then the user is more clearly alerted that they need to play with the settings. Nevertheless here is something that does just that - implementing option 1. http://gerrit.libreoffice.org/c/core/+/123271 tdf#144013 ms export: prefer follow page-style over first -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145005] New: Second change of font name or font size disables keyboard entry
https://bugs.documentfoundation.org/show_bug.cgi?id=145005 Bug ID: 145005 Summary: Second change of font name or font size disables keyboard entry Product: LibreOffice Version: 7.2.1.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: david@symplectic.email Description: Open Writer or Calc. Select a different font using the drop-down menu. Now select another different font using that menu. The cursor disappears (in Writer) and no keyboard input is possible (in either component). The same thing happens if you change the font size twice. In Writer, the same thing happens if you change the paragraph style twice. This happens in both blank documents and in documents with existing text (Writer) or entries (Calc). Using the Edit/Undo from the menu allows keyboard input again. (Using the Ctrl-Z alternative is, of course, impossible as keyboard input has been disabled.) Steps to Reproduce: 1.Change the font size twice. 2. 3. Actual Results: Software becomes unusable because keyboard entry is disabled. Expected Results: Keyboard entry should not have been disabled. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5 (qfont+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.2.1-0ubuntu0.20.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145004] WordArt kind "Follow Path" are rendered with additional space
https://bugs.documentfoundation.org/show_bug.cgi?id=145004 --- Comment #1 from Regina Henschel --- Created attachment 175602 --> https://bugs.documentfoundation.org/attachment.cgi?id=175602=edit Screenshot of PowerPoint and LibreOffice side-by-side -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145004] New: WordArt kind "Follow Path" are rendered with additional space
https://bugs.documentfoundation.org/show_bug.cgi?id=145004 Bug ID: 145004 Summary: WordArt kind "Follow Path" are rendered with additional space Product: LibreOffice Version: Inherited From OOo Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 175601 --> https://bugs.documentfoundation.org/attachment.cgi?id=175601=edit Document with shape with ScaleX=true Open attached document. It contains a WordArt of type 'Circle'. That is available in PowerPoint in section "Follow Path" in "abc Transform". The types 'Arch' and 'Arch Down' in that section have the same problem. Error: It has a large gap at the left edge, which should not be there, see attached screenshot. In LibreOffice these kind of shapes become a Fontwork with ScaleX=true in the TextPath property in the CustomShapeGeometry property. ScaleX=true means, that the text is not stretched to the path length but keeps its font size as far as possible. This is not an error in the import filter, but such gap exists too in shapes from ODF documents. This gap is produced in method CalculateHorizontalScalingFactor in EnhancedCustomShapeFontWork.cxx Our own Fontwork preset shapes are not affected, because they always use ScaleX=false. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145003] New: File>Properties Dialog should not guess the file type by extension
https://bugs.documentfoundation.org/show_bug.cgi?id=145003 Bug ID: 145003 Summary: File>Properties Dialog should not guess the file type by extension Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ville...@t-online.de Assuming a file with a wrong name extension (quite often .xls instead of .csv), menu:File>Properties guesses the file type by name extension whereas menu:File>Save As... indicates the actual file type that has been detected when loading the file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144986] Formula to Value renders a blank non-empty cell
https://bugs.documentfoundation.org/show_bug.cgi?id=144986
--- Comment #5 from LeroyG ---
=CELL("CONTENTS";A1) gives nothing
=CELL("TYPE";A1) gives "l" (for label, text)
=CELL("FORMAT";A1) gives "F0" (number without thousands separator and 0 decimal
places)
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145002] New: Crash when type command
https://bugs.documentfoundation.org/show_bug.cgi?id=145002 Bug ID: 145002 Summary: Crash when type command Product: LibreOffice Version: 7.2.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: giovibik...@hotmail.it Description: I notice that probably bug. When want open a pdf file the opening be done,but if you select on the pointer for zoom page (hand lans icon) the program crashes. I hope give you an help. Thankfs a lot Steps to Reproduce: 1.OPEN FILE (PDF) 2.SELECT ON HAND LENS ICON 3.DO A ZOOM + 4.IF DONT SEE ANY CRASH,DO A ZOOM + , ZOOM - , ZOOM + Actual Results: SCREEN FREEZING AND APP CRASHES Expected Results: APP CRASH Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: MAYBE REDUCING ANY CODE PAIRS OR CHECK THE CODE FOR FIND ANY SEMANTIC ERRORS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144986] Formula to Value renders a blank non-empty cell
https://bugs.documentfoundation.org/show_bug.cgi?id=144986 --- Comment #4 from LeroyG --- Thanks Miguel and Eike. After reading comments 1 to 3, I agree that this type(?) of content "should be searchable" (comment 2). So, what is next? Change the bug title to reflect that? Close this bug and post an enhancement request for the search issue? After apply Formula to Value in A1: ="" =ISBLANK(A1) gives FALSE. =ISFORMULA(A1) gives FALSE. =ISLOGICAL(A1) gives FALSE. =ISNONTEXT(A1) gives FALSE. =ISNUMBER(A1) gives FALSE. =ISTEXT(A1) gives TRUE. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145000] Shadow distance for shapes mismatches locale length unit
https://bugs.documentfoundation.org/show_bug.cgi?id=145000 --- Comment #1 from phv --- This bug is more complex than I thought. It only happens when Writer is loading a document after a fresh LibreOffice start: Writer systematically resets the shadow distance in inch unit, even if it's not the locale length unit or after the user has modified and saved the measurement in centimeter. I added steps to reproduce: 1. Set a locale setting with metric unit. 2. Close LibreOffice. 3. Create Writer document and insert a shape. 4. Open the Area window and enable the shadow: its distance is in centimeter. 5. Save. 6. Close LibreOffice (important!) 7. Load the previous document. Actual Result: Shadow distance is now using inch length unit instead of the locale length unit. Expected Result: Shadow distance should use the locale length unit by default. What I have tested so far after having saved a shape with a shadow distance in centimer: - Closing Writer and loading the document: still in centimeter. - Closing LibreOffice and loading the document: now in inch. - Inserting a new shape in a new Writer document after closing Writer or LibreOffice: in centimeter. To resume, Writer fails to load the locale shadow distance unit at startup but the setting is called when a shape is created or modified from a window (but not manually for whatever reason). Also to be noted, neither Draw or Impress are affected by this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144975] LibreCalc macro loop always freezes within 4295 seconds.
https://bugs.documentfoundation.org/show_bug.cgi?id=144975 --- Comment #5 from Craig --- I tried to reproduce the bug on a Raspberry Pi4 that was running the beta 64 bit Buster ( 2021-05-07-raspios-buster-arm64). The bug did not occur. It shows up on the standard latest version of the 32bit operating system: PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139736] Images and frames in header violate PDF/UA
https://bugs.documentfoundation.org/show_bug.cgi?id=139736 --- Comment #5 from niels.gie...@gmail.com --- The same issues arise when defining borders for paragraph or page styles. This yields Path Object not tagged errors. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 78427] FILEOPEN PDF Import: sometimes bold and italic font properties are imported incorrectly (see comment 34 for TODO list)
https://bugs.documentfoundation.org/show_bug.cgi?id=78427
Kevin Suo changed:
What|Removed |Added
Status|REOPENED|NEW
Assignee|suokunl...@126.com |libreoffice-b...@lists.free
||desktop.org
Summary|FILEOPEN PDF Import:|FILEOPEN PDF Import:
|sometimes bold and italic |sometimes bold and italic
|font properties are |font properties are
|imported incorrectly|imported incorrectly (see
|(because of toUnicode map |comment 34 for TODO list)
|in the pdf font file) |
--- Comment #34 from Kevin Suo ---
Despite the various commits merged above, below are some TODO list related to
this bug:
1. To correctly parse documents like attachment 155937 (which contains fonts
with Semibold / Light features), the current way of font handling in
sdext/pdfimport need to be reworked. E.g., the FontAttributes model in
sdext/source/pdfimport/inc/contentsink.hxx need to be improved to include
semibold, light etc features, but I think a better way would be to replace
those FontAttributes with the more feature-rich vcl::Font type).
2. To correctly parse attachment 98668, we need to be able to detect Type 1C
font. My understanding is thatcurrently LibreOffice can only detect TrueType
font and Type 1 font, but an not detect Type 1C ("C" means compressed?) font.
The italic font in attachment 98668 is named "CairoFont-1-0" - although we can
guess that the font name is CairoFont, there is no indication from the name
that it is italic, thus the only way to let it show as italic is to detect from
the embeded Type 1C font.
While I will continue to try to fix #1, I don't think I can handle #2.
As a result, I set status back to NEW and set ASSIGNEE to default, so that
others can continue to contribute their effort to fix this bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145001] sometimes graphics don't work when printed
https://bugs.documentfoundation.org/show_bug.cgi?id=145001 --- Comment #3 from James Falksen --- Created attachment 175600 --> https://bugs.documentfoundation.org/attachment.cgi?id=175600=edit scanned printed result this is what the printed output looks like -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145001] sometimes graphics don't work when printed
https://bugs.documentfoundation.org/show_bug.cgi?id=145001 James Falksen changed: What|Removed |Added CC||jfalk...@yahoo.com --- Comment #2 from James Falksen --- Created attachment 175599 --> https://bugs.documentfoundation.org/attachment.cgi?id=175599=edit the exported result this is the result of exporting to PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145001] sometimes graphics don't work when printed
https://bugs.documentfoundation.org/show_bug.cgi?id=145001 --- Comment #1 from James Falksen --- Created attachment 175598 --> https://bugs.documentfoundation.org/attachment.cgi?id=175598=edit the source file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145001] New: sometimes graphics don't work when printed
https://bugs.documentfoundation.org/show_bug.cgi?id=145001 Bug ID: 145001 Summary: sometimes graphics don't work when printed Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jfalk...@yahoo.com Description: Occasionally, a writer document looks fine on the screen, looks fine on the print preview, looks fine when exported to pdf, but comes out wrong on paper. I have not seen this in Calc and haven't used other components much. I have done over 100 of this ilk, but this failure has happened only 3 or 4 times. In one instance, changing the page area from a solid color to a crosshatch gave a good print. Have even tried protecting contents, position, and size -- to no avail. Mostly, the graphics are PNG. On an instance where it fails, it always fails. Steps to Reproduce: 1. load the odt file 2. print 3. Actual Results: At least 1 of the graphics prints out of place and the wrong size. The page area is incomplete. Expected Results: The printed image matches the print preview. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103184 V Stuart Foote changed: What|Removed |Added Depends on||141986 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141986 [Bug 141986] Improve current LO Application Colors theme handling to support a LibreOffice "dark" color scheme mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144037] kf5: Unable to insert table from toolbar button
https://bugs.documentfoundation.org/show_bug.cgi?id=144037 --- Comment #33 from Caolán McNamara --- (In reply to Julien Nabet from comment #32) > I mean perhaps fixing the pb of parent window at least for tab user > interface may help a bit. I don't think this has a bearing on the main problem, its used for "taskpanelist" which is kind of obscure I feel, https://gerrit.libreoffice.org/c/core/+/123258 will silence the warning nevertheless -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135604] Invalid multiple XAdES Digital Signature in LibreOffice 7.0
https://bugs.documentfoundation.org/show_bug.cgi?id=135604 --- Comment #10 from Andrii Melashchenko --- Up -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=125823 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||144990 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144990 [Bug 144990] Menu bar does not work on Windows with high contrast themes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85811] [META] Main menu bar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85811 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||144990 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144990 [Bug 144990] Menu bar does not work on Windows with high contrast themes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144990] Menu bar does not work on Windows with high contrast themes
https://bugs.documentfoundation.org/show_bug.cgi?id=144990 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||125823, 85811 CC||79045_79...@mail.ru Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=85811 [Bug 85811] [META] Main menu bar bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=125823 [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||144994 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144994 [Bug 144994] libreoffice crashes with kf5-wayland -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||144994 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144994 [Bug 144994] libreoffice crashes with kf5-wayland -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||100156, 102495 CC||79045_79...@mail.ru Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100156 [Bug 100156] [META] Wayland-related bugs https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE VCL backend bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144996] FILEOPEN XLSX Read-only passwords on XLSX files are not working
https://bugs.documentfoundation.org/show_bug.cgi?id=144996 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 CC||79045_79...@mail.ru Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- I tried to open the file in MS Excel 2016. It didn't ask any password for editing. Why should LO do it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144999] Writer Navigator: Add a toggle button to Expand entries / Show only top-level items
https://bugs.documentfoundation.org/show_bug.cgi?id=144999 Rafael Lima changed: What|Removed |Added Summary|Writer Navigator: Add a |Writer Navigator: Add a |toggle to Expand entries / |toggle button to Expand |Show only top-level items |entries / Show only ||top-level items -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144999] Writer Navigator: Add a toggle to Expand entries / Show only top-level items
https://bugs.documentfoundation.org/show_bug.cgi?id=144999 Rafael Lima changed: What|Removed |Added Keywords||needsUXEval -- 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 Keywords|regression | --- Comment #4 from Justin L --- Page styles are always complicated because MS has a completely different paradigm than LO, so everything is based on emulation. Any monkeying around here likely has some bad side effects. In this case, LO ODT has a First-Page style that defines the same header for all pages. However, by definition it can only apply to the first page because it rolls over to another style - a concept that MS does not have at all. (So one way OP can work around this is to NOT use the First Page style, but just use the Default style with a different first header.) A complication here is that the First Page has different margins from the next pages, so IsPlausableSingleWordSection is false. So we can't combine these two styles into a single one. (If they were identical, then it would have worked, so that is another way OP could get the desired results.) [In DOC format, they fudge adding in a section page break in this case, but that also adds all kinds of issues (like breaking a single paragraph into two), so it is not a good idea to try to port that hack to DOCX. See for instance the (poorly titled) bug 132149.] There were a lot of page style changes happening in 4.0 and 4.1 it seems like, so what may seem "correct" for this particular document is likely just a coincidence. For example, the margins on page 2 were not correct - they more closely match the settings from the first page. So, I'm removing the REGRESSION flag. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144999] New: Writer Navigator: Add a toggle to Expand entries / Show only top-level items
https://bugs.documentfoundation.org/show_bug.cgi?id=144999 Bug ID: 144999 Summary: Writer Navigator: Add a toggle to Expand entries / Show only top-level items Product: LibreOffice Version: 7.2.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 175596 --> https://bugs.documentfoundation.org/attachment.cgi?id=175596=edit Image explaining the new feature By default the Navigator shows all entries of various categories by default (f.i. tables, frames, images, etc). This is okay for short documents, but when I am reading very long documents (e.g. dissertation, thesis or writing a book), this becomes an issue because suppose I wanted to scroll down to the "Comments" section; then I would have to scroll down a lot till I get to the Comments section in the navigator. What I would like to propose is to add a toggle button to the Navigator that simply alternates between (i) expanding all items, which is the default behavior, and (ii) showing only top level items in the navigator (see attached image). Another aspect that could be improved in the navigator is when the user selects an item type in the "Navigate by" drop-down list. For example, when "Comments" is selected in "Navigate by", the selection in the Navigator could be updated by going to the "Comments" section... and using the navigation arrows could reflect the selection in the navigator as well (since the cursor position in the text is also updated). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144835] EDITING Increasing indent on a paragraph is not recorded as tracked change
https://bugs.documentfoundation.org/show_bug.cgi?id=144835 László Németh changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |nem...@numbertext.org |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133494] Improve word completion suggestions
https://bugs.documentfoundation.org/show_bug.cgi?id=133494 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2214 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144630] 7.2.1 is crashing on launch.
https://bugs.documentfoundation.org/show_bug.cgi?id=144630 --- Comment #10 from JJ --- Still seeing this issue with 7.2.2.2 on the same AMD drivers 21.5.2 (latest legacy drivers) on Windows 11. Faulting application name: soffice.bin, version: 7.2.2.2, time stamp: 0x615daec6 Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9 Exception code: 0xc409 Fault offset: 0x0007dd7e Faulting process id: 0xd2c Faulting application start time: 0x01d7bc3f09a7a21b Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin Faulting module path: C:\WINDOWS\System32\ucrtbase.dll -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128397] Crashes after chart manipulation in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=128397 --- Comment #12 from Nicole Botello --- Celebrity clothing in leather jacket Dwayne Johnson could easily become the biggest celebrity of his day. If there was an example of graceful aging, it would be. His leather jackets are just extraordinary and we can't get enough of them. The biggest secret of his always charming good looks is that he tries his best. Another celebrity who is killing leather jacket imagery is our very own Jennifer Aniston, who empowers supermodels in their 20s to get their jobs done with her demeanor. Gorgeous and extremely talented, this woman impressed us with her amazing flair for clothes. Take notes, ladies! https://realleathergarments.co.uk/men/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144920] Selecting text BOLD makes bold numbering as well
https://bugs.documentfoundation.org/show_bug.cgi?id=144920 --- Comment #10 from Telesto --- (In reply to Orwel from comment #7) > Thank you, this seems to work, but as I had defined a lot of own numbering > styles, this means to edit each one. I do see a lot of number styles in your sample document. So I do see the problem you're encountering. A Document Template with correct settings would obviously be an approach. Preventing this to be setup multiple times. Another partly fix would maybe be the clone/copy existing style the reduce to need to setup a style from scratch (only applies for styles without hierarchy) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64679] [META] Printer settings related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=64679 V Stuart Foote changed: What|Removed |Added URL|https://digitalmarketingint | |elugu.in/digital-marketing- | |course-training-in-hyderaba | |d/ | -- You are receiving this mail because: You are the assignee for the bug.
