[Libreoffice-bugs] [Bug 143881] FORMULA: abs{x}^2 is formatted with unexpected operator precedence
https://bugs.documentfoundation.org/show_bug.cgi?id=143881 --- Comment #9 from Mike Kaganski --- (In reply to dante19031999 from comment #8) There's no thread-safety problem, if each *formula* (with its own ODF settings) is managed by a single thread. The flag should be per-document (i.e., per *formula* document) setting. But your proposal about changing braces around auto-inserted text looks safer and easier. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143971] LibreOffice 7.2 introduced addition popup for read only file that shouldn't be showing
https://bugs.documentfoundation.org/show_bug.cgi?id=143971 Mike Kaganski changed: What|Removed |Added CC||matt...@gmail.com --- Comment #2 from Mike Kaganski --- (In reply to Roman Kuznetsov from comment #1) > it was your own commit Please be precise in what you state ;) it was not "my" commit, but only what I merged, as already stated at the Ask question: > I myself helped that change by reviewing and approving it. The author of the commit is Matt K. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127146] Footnotes "After" space disappears while saving as DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=127146 --- Comment #6 from Justin L --- (In reply to Julien Nabet from comment #5) > Perhaps we lose "Before" and "After" info because doc and docx format don't > have these notions? It should be possible to emulate this. I managed to add a bunch of junk using Word's "Custom mark". It ends up just being a normal run of text using the FootnoteReference character style. before Here is my footnote. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142614] [META] PPTX Slideshow settings
https://bugs.documentfoundation.org/show_bug.cgi?id=142614 Bug 142614 depends on bug 143624, which changed state. Bug 143624 Summary: FILESAVE PPTX Slideshow setting “Manual forwarding” is not saved https://bugs.documentfoundation.org/show_bug.cgi?id=143624 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144015] New: In Calc secondary X axis position is referring to primary Y axis
https://bugs.documentfoundation.org/show_bug.cgi?id=144015 Bug ID: 144015 Summary: In Calc secondary X axis position is referring to primary Y axis Product: LibreOffice Version: 7.1.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: g...@gavron.com Description: In Calc secondary X axis position is referring to primary Y axis. Expected: Should referring to Secondary Y axis value. Steps to Reproduce: 1.In chart create Secondary X and Y axis. 2.Select X Secondary axis 3.In "Positioning" select "Cross other axis at Value" 4.Secondary X axis will be moved to Primary Y axis value , instead Secondary Y axis value Actual Results: Secondary X axis will be moved to Primary Y axis value Expected Results: Secondary X axis should be moved to Secondary Y axis value Reproducible: Always User Profile Reset: No Additional Info: No more info -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41638] FILESAVE: Black character shadows will be shown grey by MS PPT Viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=41638 --- Comment #11 from Rainer Bielefeld Retired --- Google Sliedes viewer shows .pdp AND .ppt AND .potx (from Version: 7.1.5.2 (x64) Build: 85f04e9f809797b8199d13c421bd8a2b025d52b5) from kit without shadow. This might indicate that it's a bit more complicated that simply "filesafe LibO-bug". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144014] I cannot create a New Style for internet links, without the system Internet Link overriding my style.
https://bugs.documentfoundation.org/show_bug.cgi?id=144014 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #2 from BogdanB --- Try this: select the link with problem and pres Ctrl+M. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144008] LO crashes when macro tries to start a form document in Base (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139859] Incorrect handling of blank cells
https://bugs.documentfoundation.org/show_bug.cgi?id=139859 --- Comment #3 from QA Administrators --- Dear AB, 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 142952] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=142952 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 139848] #VALUE! thrown repeatedly with the exact same text inserted manually and via copy and paste despite it originally working with the exact same cell input originally
https://bugs.documentfoundation.org/show_bug.cgi?id=139848 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 139852] Crash if I close and try to re-open it
https://bugs.documentfoundation.org/show_bug.cgi?id=139852 --- Comment #3 from QA Administrators --- Dear Arminius Ungeist, 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 139859] Incorrect handling of blank cells
https://bugs.documentfoundation.org/show_bug.cgi?id=139859 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 139852] Crash if I close and try to re-open it
https://bugs.documentfoundation.org/show_bug.cgi?id=139852 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 139831] Libreoffice Calc keeps crashing when macros are executed.
https://bugs.documentfoundation.org/show_bug.cgi?id=139831 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 139831] Libreoffice Calc keeps crashing when macros are executed.
https://bugs.documentfoundation.org/show_bug.cgi?id=139831 --- Comment #3 from QA Administrators --- Dear pekon, 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 139848] #VALUE! thrown repeatedly with the exact same text inserted manually and via copy and paste despite it originally working with the exact same cell input originally
https://bugs.documentfoundation.org/show_bug.cgi?id=139848 --- Comment #3 from QA Administrators --- Dear faxorol116, 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 139776] FILEOPEN - item added when opening an Excel 2003 spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=139776 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 139776] FILEOPEN - item added when opening an Excel 2003 spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=139776 --- Comment #7 from QA Administrators --- Dear Leo, 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 138886] LibreOffice 7.0 crashes when I attempt to open it after installing it. This is before i can choose a component such as Calc or Base
https://bugs.documentfoundation.org/show_bug.cgi?id=138886 --- Comment #4 from QA Administrators --- Dear rbaksa, 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 139257] Crash of LibreOffice deletes non saved work
https://bugs.documentfoundation.org/show_bug.cgi?id=139257 --- Comment #5 from QA Administrators --- Dear sirihuet, 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 138376] The attached spread sheet frequently crashes after saving during closing.
https://bugs.documentfoundation.org/show_bug.cgi?id=138376 --- Comment #7 from QA Administrators --- Dear Nick Hildebrand, 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 132196] Rewrite of mailmerge.py
https://bugs.documentfoundation.org/show_bug.cgi?id=132196 --- Comment #10 from QA Administrators --- Dear prrvchr, 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 47997] FILESAVE PPT Indent of paragraph is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=47997 --- Comment #9 from QA Administrators --- Dear sasha.libreoffice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 47730] Editing pdf in Draw corrupts text justification
https://bugs.documentfoundation.org/show_bug.cgi?id=47730 --- Comment #15 from QA Administrators --- Dear books, 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 44731] PDF import problems with gradients and patterns
https://bugs.documentfoundation.org/show_bug.cgi?id=44731 --- Comment #37 from QA Administrators --- Dear mathog, 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 44729] PDF import problems with opacity from Inkscape PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=44729 --- Comment #18 from QA Administrators --- Dear mathog, 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 43806] Line style of imported PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=43806 --- Comment #37 from QA Administrators --- Dear mathog, 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 41638] FILESAVE: Black character shadows will be shown grey by MS PPT Viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=41638 --- Comment #10 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 113936] Importing a PDF is slower compared to 5.4
https://bugs.documentfoundation.org/show_bug.cgi?id=113936 --- Comment #9 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 144014] I cannot create a New Style for internet links, without the system Internet Link overriding my style.
https://bugs.documentfoundation.org/show_bug.cgi?id=144014 --- Comment #1 from nirodh...@gmail.com --- Created attachment 174485 --> https://bugs.documentfoundation.org/attachment.cgi?id=174485=edit Internet Link Style Override Just a jpg of my bug description. Notice how the Styles pane shows Earthy Hyperlink in Brown, but the document does not. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144014] New: I cannot create a New Style for internet links, without the system Internet Link overriding my style.
https://bugs.documentfoundation.org/show_bug.cgi?id=144014 Bug ID: 144014 Summary: I cannot create a New Style for internet links, without the system Internet Link overriding my style. Product: LibreOffice Version: 6.2 all versions Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nirodh...@gmail.com Description: Normally Internet Link uses a Navy Blue font. If I create new style that uses say a brown font, it won't work. The Internet Link font color will predominate. I can change Internet Link font to brown, but then it changes every other hyperlink in my document to brown. Bottom line? I can't create a new hyperlink style. Steps to Reproduce: 1.Write a sentence in Writer as follows: Here are 2 hyperlinks: Hyperlink1 and Hyperlink2. 2.Format Hyperlink1 with Standard Internet Link (Blue Color, Times New Roman 12. 3.Create New Hyperlink Style. Name it EarthyLink. (Brown Color, Tahoma, 15. Format Hyperlink2 with EarthyLink. 4. Notice that the Font and font size change, but the color does not. Actual Results: The new style shows up in my Style window as brown, but it does not work. Color remains the same color defined by Standard Internet Link (Blue). Expected Results: It should have used EarthyLink as defined with BROWN color. Reproducible: Always User Profile Reset: Yes Additional Info: The software should give me the ability to style hyperlinks the way I choose, with the color I choose and not have the Standard Internet Link style override my self-created style. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112765] [META] RTF (text) table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112765 Bug 112765 depends on bug 108974, which changed state. Bug 108974 Summary: [RTF] Table not properly displayed https://bugs.documentfoundation.org/show_bug.cgi?id=108974 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97895] [META] FILEOPEN RTF layout problem with table, footers, extra pages
https://bugs.documentfoundation.org/show_bug.cgi?id=97895 Bug 97895 depends on bug 108974, which changed state. Bug 108974 Summary: [RTF] Table not properly displayed https://bugs.documentfoundation.org/show_bug.cgi?id=108974 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108974] [RTF] Table not properly displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=108974 Aron Budea changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Aron Budea --- This was actually fixed in LO 6.1.0.3, at least the Technologie table not having borders, changing status to WFM. Mike, if you're still seeing some kind of issue there, please open a separate bug report on that. The diagram at the end has been missing the lines since the following commit in 7.0: https://cgit.freedesktop.org/libreoffice/core/commit/?id=dd117712bd5692f7bf3870ba91572a0bab54ab86 author Armin Le Grand 2020-03-05 19:24:30 +0100 committer Armin Le Grand 2020-03-06 10:10:55 +0100 tdf#124848 partial refactor hairline logic -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144013] When "Same content on first page" is unchecked, and there is a table on the page which spreads across two pages, the first page header content also goes to the second p
https://bugs.documentfoundation.org/show_bug.cgi?id=144013 Kevin Suo changed: What|Removed |Added Version|unspecified |7.2.0.3 rc OS|All |Linux (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144013] New: When "Same content on first page" is unchecked, and there is a table on the page which spreads across two pages, the first page header content also goes to the sec
https://bugs.documentfoundation.org/show_bug.cgi?id=144013 Bug ID: 144013 Summary: When "Same content on first page" is unchecked, and there is a table on the page which spreads across two pages, the first page header content also goes to the second page Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Created attachment 174484 --> https://bugs.documentfoundation.org/attachment.cgi?id=174484=edit test odt file Steps to Reproduce: 1. Open the attached odt file. Observe that it has "same content on the first page" unchecked in page properties, so that the header logo is only shown on the first page but not on the 2nd page. Also observe that there is a table which spread across the first and the 2nd page. 2. Save as docx, then open the saved docx file with Writer or MS Word. --> Bug: the header logo appears on both the 1st and the 2nd page. It should appear only on the first page. 3. Try to delete some table rows in the odt file so that the table fit only on the 1st page, then save as docx and reopen with Writer or MS Word. --> OK, as expected. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: cb2827f5f65324f309fa0e3c30d0b19ad237410e 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 also on 7.2 branch. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108974] [RTF] Table not properly displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=108974 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu --- Comment #4 from Aron Budea --- Created attachment 174483 --> https://bugs.documentfoundation.org/attachment.cgi?id=174483=edit PDF exported from Word -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144012] Password protected .odt file show mostly empty
https://bugs.documentfoundation.org/show_bug.cgi?id=144012 Satoru Kengaku changed: What|Removed |Added Summary|Password set .odt file show |Password protected .odt |mostly empty|file show mostly empty -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144012] New: Password set .odt file show mostly empty
https://bugs.documentfoundation.org/show_bug.cgi?id=144012 Bug ID: 144012 Summary: Password set .odt file show mostly empty Product: LibreOffice Version: 7.2.0.4 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: satoru.keng...@gmail.com Description: Open my password protected .odt file with 7.2.0.4, it shows the header and some lines only, contents are mostly empty. Tried to change character color, but it was not the cause. Steps to Reproduce: 1.Open a password protected .odt file 2. 3. Actual Results: The header is shown. Some under lines are shown, but the rest is empty. Expected Results: My contents should be shown. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: It's OK with 7.1.5.2 (x64) So I uninstalled 7.2.0.4 and reinstalled 7.1.5.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143881] FORMULA: abs{x}^2 is formatted with unexpected operator precedence
https://bugs.documentfoundation.org/show_bug.cgi?id=143881 --- Comment #8 from dante19031...@gmail.com --- > 2. Introduce a compatibility flag, that would signal that abs priority is > changed. That's no so easy. The token list is hardcoded into the code. It's set up on program initialization, even before the SMMOD even exists. It could be accessed from a static function, using a bad hack ( const cast + search for TABS, not 100% sure it won't break ). In that case we would add that flag to SmModel::_getPropertyValues and SmModel::_setPropertyValues . It would be initialized as "new mode". And add a trigger on the importer that would set it up to "old mode". It would need a second flag to check if the first one has the default value or actually was set by the document. However, there are some things that I'm not confident about. How will this react while using multiple thread (multiple formulas at same time). If it has to be thread safe, then I'm not confident it can be done. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131531] FILESAVE DOCX: Header height of first page is not reserved
https://bugs.documentfoundation.org/show_bug.cgi?id=131531 Kevin Suo changed: What|Removed |Added CC||l...@deller.id.au --- Comment #7 from Kevin Suo --- Luke would you please take a look as you have worked on bug 19080? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144011] New: LibreOffice Writer crashed when right clicking "word not dictionary" and selecting "Ignore All"
https://bugs.documentfoundation.org/show_bug.cgi?id=144011 Bug ID: 144011 Summary: LibreOffice Writer crashed when right clicking "word not dictionary" and selecting "Ignore All" 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: resti...@gmail.com Description: After crash file was recovered correctly by LibreOffice. Word not in dictionary was still not in dictionary (squiggly underline). https://crashreport.libreoffice.org/stats/crash_details/b9973f1f-090e-4868-a8c0-be26248e071a Steps to Reproduce: 1.right click word not in dictionary (squiggly underline) 2.select "Ignore all" 3.LibreOffice crashes Actual Results: LibreOffice crashes but successfully recovers file. Crash report created. https://crashreport.libreoffice.org/stats/crash_details/b9973f1f-090e-4868-a8c0-be26248e071a Expected Results: Word ignored and squiggly underline disappears. Reproducible: Always User Profile Reset: No Additional Info: Tried 3 times. Crashed 3 times. Did not try resetting my UserProfile. Will try and update bug report. I have no idea what OpenGL is. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64991] RTL: open RTL doc is extremely slow
https://bugs.documentfoundation.org/show_bug.cgi?id=64991 --- Comment #11 from Aron Budea --- Created attachment 174482 --> https://bugs.documentfoundation.org/attachment.cgi?id=174482=edit DOC from description (In reply to Fahad Al-Saidi from comment #10) > today I had a chance to test the fix. It took 5 minutes to open the file in > my new machine (16 threads). Yeah, unfortunately that fix, done for bug 104254 had to be reverted before 7.2.0 release. But anyway, I checked from the state when that fix was still in, and apparently it didn't affect this document. Thanks for pointing to the doc again, I'm attaching it this time. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101280] [META] Layout loops
https://bugs.documentfoundation.org/show_bug.cgi?id=101280 Bug 101280 depends on bug 76219, which changed state. Bug 76219 Summary: HANG i#84870: WW8: large objects in Russian text / DOC with complex header / ... may cause loop (see comment 7 and 8) https://bugs.documentfoundation.org/show_bug.cgi?id=76219 What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104848] [META] DOC (binary) file opening issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104848 Bug 104848 depends on bug 76219, which changed state. Bug 76219 Summary: HANG i#84870: WW8: large objects in Russian text / DOC with complex header / ... may cause loop (see comment 7 and 8) https://bugs.documentfoundation.org/show_bug.cgi?id=76219 What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 76219, which changed state. Bug 76219 Summary: HANG i#84870: WW8: large objects in Russian text / DOC with complex header / ... may cause loop (see comment 7 and 8) https://bugs.documentfoundation.org/show_bug.cgi?id=76219 What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76219] HANG i#84870: WW8: large objects in Russian text / DOC with complex header / ... may cause loop (see comment 7 and 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=76219 Aron Budea changed: What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- --- Comment #30 from Aron Budea --- Since that commit has been reverted, let's set this back to NEW. We can't know if another fix there will fix this for sure. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142580] FILEOPEN XLSX Conditional text format colors not considered by color filter
https://bugs.documentfoundation.org/show_bug.cgi?id=142580 Ming Hua changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4010 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142579] FILEOPEN XLSX Conditional format background colors not considered by color filter
https://bugs.documentfoundation.org/show_bug.cgi?id=142579 Ming Hua changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4010 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142076] [META] Color filtering in Autofilter bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142076 Ming Hua changed: What|Removed |Added Depends on||144010 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144010 [Bug 144010] Filter by Background / Text Colour does not work for cells formatted by condition -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144010] Filter by Background / Text Colour does not work for cells formatted by condition
https://bugs.documentfoundation.org/show_bug.cgi?id=144010 Ming Hua changed: What|Removed |Added Severity|normal |enhancement OS|Linux (All) |All CC||ming.v@qq.com Blocks||142076 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2579, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2580 --- Comment #1 from Ming Hua --- Thanks for reporting. The issue with supporting colors from conditional formatting has been raised in bug 142579 and bug 142580. But since those are about XLSX compatibility specifically, I'm not marking any duplicates yet, and let the developers or senior QA people decide. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142076 [Bug 142076] [META] Color filtering in Autofilter bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143103] Support Color Filter in "Standard Filter" dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=143103 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2522 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142522] Filter By Color: allow multiple selection
https://bugs.documentfoundation.org/show_bug.cgi?id=142522 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3103 --- Comment #11 from Regina Henschel --- I think this is connected to the request to allow color filter in Standard-Filter (bug 143103) because the latter has already the option in the UI to define several conditions. If color in Standard-Filter is implemented, then it might be not necessary to allow multi-selection in the UI of Autofilter. LibreOffice is not a clone of Excel. The fact, that Excel does not have a feature is no reason, that LibreOffice does not get it too. For me this is a valid enhancement request. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143980] Add numpy to LibreOffice\program\python
https://bugs.documentfoundation.org/show_bug.cgi?id=143980 Ming Hua changed: What|Removed |Added CC||ming.v@qq.com --- Comment #5 from Ming Hua --- While I would welcome addition of Numpy to LibreOffice's bundled Python, I don't see it happening without a dramatic change of the current practice of python module packaging. We don't even ship the full core library of Python. To use the Windows installer as an example (I assume TDF's RPM and DEB packages are similar), I think we build python without Tcl/Tk and the accompanying tkinter graphic UI module, and we strip a lot of modules LO doesn't use when bundling python into the installer. As a result, the whole program\python-core-3.8.10\lib directory (with .pyc cache files generated) for installed 7.2.0 on my system is 28 MB with 1,225 files. As a comparison, the official python.org installation's python38\Lib directory here (excluding subdirectory site-packages\) is 115 MB with 7,183 files, also with .pyc files generated. And Numpy alone on my system is 56 MB. It also links to BLAS/LAPACK and maybe many other C/C++ libraries, so building it correctly is going to be tricky, too. And by adding it we are more and more like shipping a custom python distribution, instead of an office suite bundling python. Without discouraging anyone who want to work on this, I personally feel the developers' efforts would be better put into making installing external modules from PyPI and building virtual environments easier with LO's bundled python. Then we can avoid frustrated users like in bug 143867. Maybe starting with adding "ensurepip" module into our bundle, and writing a good tutorial about setting up PIP and installing packages from PyPI with LO-bundled python? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142965] There is no way to select cells without color text or color filling in Autofilter
https://bugs.documentfoundation.org/show_bug.cgi?id=142965 Regina Henschel changed: What|Removed |Added Keywords||implementationError --- Comment #10 from Regina Henschel --- The attribute fo:background-color in file source can have the value "transparent" in addition to rgb- color values. Transparent is missing in the list of color values in the Autofilter. LibreOffice writes attribute style:use-window-fontcolor="true" in case "Automatic" was chosen in the UI. Which means, that the font color is White if the background is too dark. The item "Automatic" is missing in the list of color values in the Autofilter. This situation is not yet included in the proposal for ODF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144010] New: Filter by Background / Text Colour does not work for cells formatted by condition
https://bugs.documentfoundation.org/show_bug.cgi?id=144010 Bug ID: 144010 Summary: Filter by Background / Text Colour does not work for cells formatted by condition Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bug2...@johnmurrell.org.uk Description: The latest update of LibreOffice calc introduced the ability to filter by Background or text colour which works if you manually change the cell colours. If the Background or text colour are changed by conditional formatting this does not show in the filter selection so you cannot filter by it. Steps to Reproduce: 1.Create a list of numbers with some duplicates 2.used the conditional format - condition to format the duplicate values as 'errors' which have white text on a red background. 3.Apply an auto filter to the list. 4:Neither the red background or white text appear in the Text Colour or Background colour in the filter selection. Actual Results: Background & text colour not shown in filter selection Expected Results: Background & Text colour should appear in filter selector allowing cells formatted by conditional formatting to be filtered. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: SpreadsheetDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes https://gerrit.libreoffice.org/gitweb?p=core.git;a=log;h=9a9c6381e3f7a62afc1329bd359cc48accb6435b (the rest will not copy) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143899] FILEOPEN DOCX Shapes overlap margin in CompatibilityMode15
https://bugs.documentfoundation.org/show_bug.cgi?id=143899 Ezinne changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||nnamani.ezi...@collabora.co ||m --- Comment #4 from Ezinne --- Reproducible in: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 7c1bad415ae48635dc67041c413bb7b76a530c22 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-07-05_06:55:03 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144008] LO crashes when macro tries to start a form document in Base (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 CC||m.wegh...@posteo.de Keywords||haveBacktrace Status|UNCONFIRMED |NEW --- Comment #2 from Julien Nabet --- Michael: since it's specific to kf5, thought you might be interested in this one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144008] LO crashes when macro tries to start a form document in Base (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 Julien Nabet changed: What|Removed |Added Summary|LO crashes when macro tries |LO crashes when macro tries |to start a form document in |to start a form document in |Base|Base (kf5 only) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144008] LO crashes when macro tries to start a form document in Base
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- Created attachment 174481 --> https://bugs.documentfoundation.org/attachment.cgi?id=174481=edit bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this but only with kf5 rendering, not with gtk3 or gen rendering. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143980] Add numpy to LibreOffice\program\python
https://bugs.documentfoundation.org/show_bug.cgi?id=143980 --- Comment #4 from e...@helpidea.net --- Thanks, I use Range.DataArray in Basic, so I have Variant Array of Arrays, and this is one parameter to deliver to Python def, that take this as tuple of tuples. Will be Python to transform this in numpy array, and then work with. At end, must return a tuple of tuples for copy this to a Calc Range. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143980] Add numpy to LibreOffice\program\python
https://bugs.documentfoundation.org/show_bug.cgi?id=143980 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- Set to NEW by Comment 2 Thanks Andreas -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144005] crash when moving a media shape in debug build
https://bugs.documentfoundation.org/show_bug.cgi?id=144005 Julien Nabet changed: What|Removed |Added CC||michael.st...@allotropia.de ||, t...@libreoffice.org, ||vasily.melenc...@cib.de --- Comment #3 from Julien Nabet --- Assert instructions added with: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=d39651a69d789522b2faffd01879db25354b9a22 "author Vasily Melenchuk 2020-08-27 15:13:08 +0300 committer Thorsten Behrens 2020-09-15 11:04:25 +0200 commit d39651a69d789522b2faffd01879db25354b9a22 (patch) treee3852c43ba713ed8d6d8305aeaa8cd6b35dfa148 parent 315919306c7b6e95db6a280c4aa8d2203970e292 (diff) sw: additional asserts/warns to diagnose empty style names Since undo/redo is using format name instead of old approach with pointers (which can point to invalid/removed style) it is a problem when we trying to use any style without name: it will be not resolved and undo/redo will work incorrectly: it can apply invalid attributes or apply style to another random objects." Vasily/Thorsten/Michael: thought you might be interested in this one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144005] crash when moving a media shape in debug build
https://bugs.documentfoundation.org/show_bug.cgi?id=144005 Julien Nabet changed: What|Removed |Added OS|Windows (All) |All Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords||haveBacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144005] crash when moving a media shape in debug build
https://bugs.documentfoundation.org/show_bug.cgi?id=144005 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- Created attachment 174480 --> https://bugs.documentfoundation.org/attachment.cgi?id=174480=edit bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this and had an assertion. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143971] LibreOffice 7.2 introduced addition popup for read only file that shouldn't be showing
https://bugs.documentfoundation.org/show_bug.cgi?id=143971 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=47 ||065 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143971] LibreOffice 7.2 introduced addition popup for read only file that shouldn't be showing
https://bugs.documentfoundation.org/show_bug.cgi?id=143971 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||bibisected, bisected CC||79045_79...@mail.ru Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- I confirm the problem in 7.3 Ok Mike, if you think it's a bug, then I bisected it and it was your own commit 95eb088802562b75f8b299908160145c7e88d763 https://gerrit.libreoffice.org/c/core/+/111654 https://git.libreoffice.org/core/commit/95eb088802562b75f8b299908160145c7e88d763 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143750] Missing or extra parentheses and/or quotation marks function no longer works in version 7.2.0.2.
https://bugs.documentfoundation.org/show_bug.cgi?id=143750 --- Comment #3 from Eek! A Bug. Kill it! --- Interesting oddity concerning the missing/unpaired parentheses issue. With only one unpaired parentheses in a line of text (see ordered number list item 1) and 2) below), the grammatical checking works. However, when an unpaired parentheses is combined with one or more paired parentheses (see ordered number list item 3)), it does NOT work. Example: 1) to draw a rectangle, first make a square shape, then press the shift key and drag a side of the square to make a rectangle 2) double click a selection to be able to use it repeatedly without having to re-select it each time 3) to make copies of an object, select it, R-click, Copy, Paste (will paste over top of original, so then move to new location) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144004] Having problems printing a LibreOffice Calc document in Landscape.
https://bugs.documentfoundation.org/show_bug.cgi?id=144004 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Have you set up 'Landscape' in the page style, Menu/Format/Page/Page? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143980] Add numpy to LibreOffice\program\python
https://bugs.documentfoundation.org/show_bug.cgi?id=143980 --- Comment #2 from Andreas Heinisch --- Imho numpy is a very popular library for python, but I don't know if it requires something special in order to work with the uno arrays. We could add the library and make some experiments. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143977] In “View” menus and "Tabbed" toolbars, be consistent about “hide / show”
https://bugs.documentfoundation.org/show_bug.cgi?id=143977 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added OS|Linux (All) |All Version|unspecified |7.1.5.2 release Component|Writer |UI CC||79045_79...@mail.ru, ||heiko.tietze@documentfounda ||tion.org --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- I think it was made advisedly Heiko, do you remember something related? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143990] Multilevel outline numbers not showing
https://bugs.documentfoundation.org/show_bug.cgi?id=143990 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||bibisected, bisected, ||regression Status|UNCONFIRMED |NEW CC||79045_79...@mail.ru, ||t...@libreoffice.org, ||vasily.melenc...@cib.de Ever confirmed|0 |1 --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- confirm in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4677345e3695bac158bb04048b4d5c608ed764b4 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL but not in 7.1 => regression I bibisected it and got a sha for a bad commit: sha is 9987b518fca1476bd0ce8c86bcf6ac7c81f7b580 https://gerrit.libreoffice.org/c/core/+/118040 https://git.libreoffice.org/core/commit/9987b518fca1476bd0ce8c86bcf6ac7c81f7b580 Added to CC: Thorsten Behrens and Vasily Melenchuk -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127593] [META] Python Macro bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=127593 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||143980 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143980 [Bug 143980] Add numpy to LibreOffice\program\python -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143980] Add numpy to LibreOffice\program\python
https://bugs.documentfoundation.org/show_bug.cgi?id=143980 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru, ||andreas.heini...@yahoo.de, ||libreoffici...@sfr.fr Blocks||127593 --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Andreas, Alain, what do you think? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127593 [Bug 127593] [META] Python Macro bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||143991 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143991 [Bug 143991] The imported text in the SVG image is partially invisible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143991] The imported text in the SVG image is partially invisible.
https://bugs.documentfoundation.org/show_bug.cgi?id=143991 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Blocks||88278 CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Confirm in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4677345e3695bac158bb04048b4d5c608ed764b4 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL ps: I think Inkscape can export images to PNG too Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=88278 [Bug 88278] [META] SVG import image filter (all modules) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104185] Better Autoinput for functions (or different default than ENTER)
https://bugs.documentfoundation.org/show_bug.cgi?id=104185 --- Comment #9 from Joshua Coppersmith --- Some alternatives: 1) Change auto entry to use tab, the default in almost every other system out there from Eclipse clear down to MS Hotmail. Obviously, my choice and Mieszko's but another idea is... 2) Don't kick in auto entry after backspace...per other suggestions already given. 3) Don't kick in auto entry until at least two (even three) letters have been typed. That would at least avoid the mess for simple column reference situations in the vast majority of cases. 4) Put "Tab to ignore" in bold at the end of the auto entry popup text tip while not changing the behavior at all. I think this is more than a preference question. If you, for example, have =($A:$A) in column C then go to change that to =($B:$B) you get into a morass of =($B:$B()), etc., when doing the obvious and pressing Enter. Here is the thing: Anyone wanting auto entry will be able to see clearly if that function has popped up, and will probably have to keep typing awhile before the drill down matches what they want, anyway. Meanwhile, the person expecting enter to do as it says and enter the edited value into the cell is left trapped, having to re-edit, and having to click into the end of the line or having to figure out to use tab to do what enter says right on the key, "Enter". The popup tip for the auto entry feature could have a bold "then Tab" at the end of it if switched to tab. MS Hotmail does something like this. Or...if the behavior isn't changed, what about putting "Tab to ingore" at the end of the tip? In any case, most intense users of LibreOffice Calc probably have the basic familiarity with tab for autocomplete, not enter. Tab for autocomplete is very mainstream. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144005] crash when moving a media shape in debug build
https://bugs.documentfoundation.org/show_bug.cgi?id=144005 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Summary|crash when moving a media |crash when moving a media |shape |shape in debug build CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- No crash in daily build Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4677345e3695bac158bb04048b4d5c608ed764b4 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144006] Shortcut for Formula object insertion
https://bugs.documentfoundation.org/show_bug.cgi?id=144006 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- There is the same shortcut in 7.2 But there is no predefined shortcut for it in 7.1. But I see the Formula item in Command list in the Customize dialog anyway. Just move the mouse cursor on Formula item and look at tooltip. You should see the same UNO as on my attach. Close as WFM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144006] Shortcut for Formula object insertion
https://bugs.documentfoundation.org/show_bug.cgi?id=144006 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Created attachment 174479 --> https://bugs.documentfoundation.org/attachment.cgi?id=174479=edit Screenshot with InsertObjectStarMath in Customize dialog in 7.3 I see Ctrl+Alt+= shortcut inserts a Math object into Writer document and I see the UNO in Customize dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143090] Add custom path to paths options gives open dialog instead of select folder (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=143090 Caolán McNamara changed: What|Removed |Added Status|NEW |RESOLVED Keywords|bibisectRequest | Resolution|--- |DUPLICATE --- Comment #3 from Caolán McNamara --- fix https://gerrit.libreoffice.org/c/core/+/120853 makes this work too *** This bug has been marked as a duplicate of bug 143993 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143090] Add custom path to paths options gives open dialog instead of select folder (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=143090 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3993 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144009] LibreOffice 7.2, Impress, Edit Styles and Formating, Notes, Filesave Doesn't not save
https://bugs.documentfoundation.org/show_bug.cgi?id=144009 --- Comment #1 from Mike Reardon --- Created attachment 174478 --> https://bugs.documentfoundation.org/attachment.cgi?id=174478=edit This is the original file in question prior to changes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144009] New: LibreOffice 7.2, Impress, Edit Styles and Formating, Notes, Filesave Doesn't not save
https://bugs.documentfoundation.org/show_bug.cgi?id=144009 Bug ID: 144009 Summary: LibreOffice 7.2, Impress, Edit Styles and Formating, Notes, Filesave Doesn't not save Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mike.pc.rear...@gmail.com Description: Hi I installed 7.2 version on Linux lite os on laptop with 4gb RAM and 128 GB SSD Received a MS PPT file. Began modifications. Upon adding notes, changed font, font size and default font from Arial 20pt to Liberation Sans 16pt. And changed indent to zero. Saved. Re-open the next day, style remains default from original MS PPT. Changed in Notes Master. Managed styles. Updated. Saved But nothing sticks when I reopen the file. Workaround is to remake the changes prior to presentation. What a pain.. Steps to Reproduce: 1.In one slide, change note style and formatting. Save. Close. Open and File save is not saved for note. 2.In impress, go to format style, notes, make changes, save. Close. Open and file is not saved for style 3 In impress, to to master notes, make changes, save. Close. Open and filesave is not saved for font (from Arial to Liberation Sans); font size (20 to 16) and indent down to zeo. 3. Actual Results: It works when in the file. Upon reopening it is not saved. Expected Results: That upon reopening changes to style and formating remain. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: This is a completely new install -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143993] FilePicker unexpectedly opens instead of FolderPicker
https://bugs.documentfoundation.org/show_bug.cgi?id=143993 Caolán McNamara changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | Ever confirmed|0 |1 --- Comment #3 from Caolán McNamara --- looks like the vista file/folder picker impl will default back to "file open" if initialization is explicitly called on the folder service -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113083] [META] New RTF import filter regressions in LO 3.5+
https://bugs.documentfoundation.org/show_bug.cgi?id=113083 Aron Budea changed: What|Removed |Added Depends on||104390 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104390 [Bug 104390] FILEOPEN RTF Courier New erroneously replaced with fallback font, when file does not contain \pard\plain -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81234] [META] RTF filter issues
https://bugs.documentfoundation.org/show_bug.cgi?id=81234 Aron Budea changed: What|Removed |Added Depends on|104390 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104390 [Bug 104390] FILEOPEN RTF Courier New erroneously replaced with fallback font, when file does not contain \pard\plain -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104390] FILEOPEN RTF Courier New erroneously replaced with fallback font, when file does not contain \pard\plain
https://bugs.documentfoundation.org/show_bug.cgi?id=104390 Aron Budea changed: What|Removed |Added Keywords||preBibisect, regression Blocks|81234 |113083 Version|5.2.3.3 release |3.5.0 release --- Comment #15 from Aron Budea --- This was fine in LO 3.4.0, and got buggy in 3.5.0, thus it is probably a regression related to the new RTF import code. Already buggy in oldest of bibisect-43all -> preBibisect. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=81234 [Bug 81234] [META] RTF filter issues https://bugs.documentfoundation.org/show_bug.cgi?id=113083 [Bug 113083] [META] New RTF import filter regressions in LO 3.5+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140152] Automatic spell check doesn't work properly in CALC (Version 7.1.0.3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140152 --- Comment #17 from Volker Strönisch --- Meanwhile version 7.1.5 became the version for "conservative users" - and the bug described by myself still remains. Am I the only one recognizing this? I used a freshly installed version, so no potential garbage from previous ones, and I can still reproduce the issue, that the automatic spellcheck shows the conten of many cells as incorrect, while in fact it is correct. After going through the spellcheck the cell is shown as correct, but with the next loading the game starts again. Very disappointing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143881] FORMULA: abs{x}^2 is formatted with unexpected operator precedence
https://bugs.documentfoundation.org/show_bug.cgi?id=143881 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #7 from Mike Kaganski --- This is definitely an inconsistent behavior, and a bug. However, fixing this is naturally a compatibility problem. There are two options: 1. Do what Dante suggests in comment 4 (the braces around the function). Somewhat ugly, but the least intrusive solution keeping backward and forward compatibility. 2. Introduce a compatibility flag, that would signal that abs priority is changed. That would allow to use new precedence in new documents, and allow to keep the formula layout in existing documents without the flag, but will break the formula in older versions of software (or AOO). Also users would face different behavior of formulas in different cases (maybe even inside the same ODT, if two formulas internally have two different flag values). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144008] LO crashes when macro tries to start a form document in Base
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 Robert Großkopf changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144008] New: LO crashes when macro tries to start a form document in Base
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 Bug ID: 144008 Summary: LO crashes when macro tries to start a form document in Base Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 174477 --> https://bugs.documentfoundation.org/attachment.cgi?id=174477=edit Open the database with macros enabled. A messagebox with content and a form should appear. For reproducing this bug you have to open the attached database with macros enabled. Open the database file. A messagebox (msgbox) appears - without content, without button OK. Close the messagebox. LO crashes immediately. Open the file in any version up to LO 7.1.5.2. The messagebox will appear with content and button OK. Pressing OK and a form will be opened. The first described buggy behavior appears with LO 7.2.0.4, not with older version up to LO 7.1.5.2 on OpenSuSE 15.2 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142952] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=142952 --- Comment #9 from Andreas Säger --- More discussion on https://ask.libreoffice.org/t/bug-id-142952-crashing-mail-merge/67215/4 I think it has something to do with the datasource widget displayed in the datasource window and in the mail merge dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144002] excel template from ms website not rendering/printing properly
https://bugs.documentfoundation.org/show_bug.cgi?id=144002 Ming Hua changed: What|Removed |Added CC||ming.v@qq.com --- Comment #9 from Ming Hua --- I got 2 pages for the Summary sheet with: Version: 7.2.0.3 (x64) / LibreOffice Community Build ID: 2a7ea282da28d665a7dc086360567b4aea27bf08 CPU threads: 2; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: threaded I also see labels going out of the chart box like attachment 174469. However it seems the whole sheet is using "Franklin Gothic Book" font, which I don't have on my system. So maybe font related? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144007] [CALC] FORMATTING Insert line above current line uses wrong format
https://bugs.documentfoundation.org/show_bug.cgi?id=144007 --- Comment #1 from crptdng...@gmx.net --- COMMENT It is worth noting that the issue affects all rows in a table, not just the first data row. Whenever you add a line ABOVE a particular line CALC will always use the Format of the line above that row instead of copying the format relatively from row you started insertion from. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144007] New: [CALC] FORMATTING Insert line above current line uses wrong format
https://bugs.documentfoundation.org/show_bug.cgi?id=144007 Bug ID: 144007 Summary: [CALC] FORMATTING Insert line above current line uses wrong format Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: crptdng...@gmx.net [CALC] FORMATTING Insert line above current line uses wrong format Steps to reproduce (1) Open Calc, (2) create some entries for a small table (e.g. 5 columns). Table has a header and some rows with data. (3) Change header line format to have yellow background of cells, increase text size of header cells. (4) Click first cell in first row of data (1st row below header). (5) Select full first row of data (the same row that you have just clicked first cell of) (6) Right click mouse to open context menu. Select "Add line above" (7) BUG: Calc will insert a new line below header, but instead assigning the same format to it as data rows have it will copy header format (i.e. yellow background, bigger text size). Expected behaviour: newly inserted line should have same format as first data row has because that is from where whole procedure started. Same happens (but less an issue, more expected) when using "insert line below" when starting from header row. When I select a row and use "insert line above/ below" I expect CALC to use the same format for newly inserted line as has the line that I have selected to start inserting above/below from. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143993] FilePicker unexpectedly opens instead of FolderPicker
https://bugs.documentfoundation.org/show_bug.cgi?id=143993 --- Comment #2 from Uwe Auer --- Repro Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 10c742afd5f04c2c3a3e1f881fd6a8c61d364c03 CPU threads: 1; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144006] New: Shortcut for Formula object insertion
https://bugs.documentfoundation.org/show_bug.cgi?id=144006 Bug ID: 144006 Summary: Shortcut for Formula object insertion Product: LibreOffice Version: 7.1.5.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jr...@hotmail.com Description: I want to be able to create/insert Formula objects via shortcut (, since I mostly deal with Math documents (homework). The current formula shortcut (F2) is for use inside tables, and not Math formulas. Steps to Reproduce: 1. Go to "Insert > Object > Formula..." or click on the "sqrt(4)" icon to open the Formula editor in LO Writer 2. Go to "Tools > Customize... > Keyboard" and search for Formula, none of the options available are the Formula editor Actual Results: The "Formula" shortcut (F2) opens a LO Calc like Formula top panel, which is for tables, and not the Formula editor. Expected Results: There should be a "Insert Formula" option available in shortcuts. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.1.5.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR Ubuntu package version: 1:7.1.5-0ubuntu0.21.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108897 Gabor Kelemen changed: What|Removed |Added Depends on||144002 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144002 [Bug 144002] excel template from ms website not rendering/printing properly -- You are receiving this mail because: You are the assignee for the bug.
