[Libreoffice-bugs] [Bug 118253] Roku tech support number
https://bugs.documentfoundation.org/show_bug.cgi?id=118253 raal changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118259] Updated ToC in DOC(X) loses tabulator between numbering and heading
https://bugs.documentfoundation.org/show_bug.cgi?id=118259 --- Comment #1 from Aron Budea --- Created attachment 142947 --> https://bugs.documentfoundation.org/attachment.cgi?id=142947=edit Sample in DOC -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118259] Updated ToC in DOC(X) loses tabulator between numbering and heading
https://bugs.documentfoundation.org/show_bug.cgi?id=118259 --- Comment #2 from Aron Budea --- Created attachment 142948 --> https://bugs.documentfoundation.org/attachment.cgi?id=142948=edit Comparison screenshot (Word - Writer) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118259] New: Updated ToC in DOC(X) loses tabulator between numbering and heading
https://bugs.documentfoundation.org/show_bug.cgi?id=118259 Bug ID: 118259 Summary: Updated ToC in DOC(X) loses tabulator between numbering and heading Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Keywords: filter:doc, filter:docx Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ba...@caesar.elte.hu Blocks: 104524 Created attachment 142946 --> https://bugs.documentfoundation.org/attachment.cgi?id=142946=edit Sample in DOCX Open the attached DOC/DOCX files with a ToC having a couple of entries. Update ToC. => The tabulators between the numbering and heading entries are removed. Attaching screenshot comparing DOCX's ToC in Word and in Writer after update (before update the tabulators are there). Observed using LO 6.1 beta2 & 4.4.0.3 / Windows 7. In 4.0.0.3 even the import is incorrect (the import was likely fixed with bug 79547's fix). In 3.3.0 no ToC is imported at all. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104524 [Bug 104524] [META] DOCX (OOXML) Table of Contents (ToC) and Index related issues -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104524] [META] DOCX (OOXML) Table of Contents (ToC) and Index related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104524 Aron Budea changed: What|Removed |Added Depends on||118259 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=118259 [Bug 118259] Updated ToC in DOC(X) loses tabulator between numbering and heading -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117049] Severe bug in LibreOffice (Calc Speadsheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=117049 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117049] Severe bug in LibreOffice (Calc Speadsheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=117049 --- Comment #14 from Mike Kaganski --- I will ask one more time, trying to rephrase my question, since the rude behaviour of OP shows not only that s/he is not well-mannered person, but also that s/he cannot understand the idea behind the prior questions, in the hope that OP would choose to return to a constructive dialogue. Your idea is based on assumption that the initial value of B1 in the iterative calculation must be zero. Only then the single iteration of formula "=B1+A1" might bring the 100. But the actual value in the B1 at the moment of the first calculation is not 0, but (a formula) "=B1+A1", which is simply *uncertainty* initially, since it's a self-referencing formula. There's *no* number in the universe that may represent that uncertainty; and any initial number that we might choose to use as its initial value is just a guess, which will be improved iteratively. If we happen to blindly guess a value that would happen to be the limit of the iterative calculations, then the very first iteration would give a delta that is less than our minimum change, and thus, the iterative calculation will have the minimal length. Just to make things clear: the value in the B2 in the course of iterative calculations is not a single static value, but a series of values, which are expected to converge to prescribed maximum error in the given number of iterations. Let's put the series in a hypothetical B1 here in some abstract series for some unspecified formulas: > i0 i1 i2i3 i4 ... > 0 -10 -100 -1000 -1 ... > 1 1.1 1.11 1.111 1. ... Here you may see that some formula might give a diverging results if the initial guess is 0, but converging result when the initial guess is 1. And if the initial guess would magically happen to be 1.111... from the very beginning, then the following iterations would not change the value in that B1, i.e., the initial guess would be the final value. Of course, it's unrealistic to expect that we would be able to guess the correct final value in that cell each time; but *generally*, the initial guess does affect the number of iterations before the delta becomes small enough; and in some cases, it even affects the very possibility to come to a converging iterations. And I repeat once more: the very idea of the iterative calculations is to make sure we come to a converging result series, not to misuse the feature in obscure ways. And again: the initial value in the cell with iterative calculations is not something that necessarily must be decided once for all; it's just an initial guess of the final result, and the quality of the guess affects the quality (time to get, and ability to get close enough to, the theoretical limit of the infinite calculation series)! There exist different approaches to guessing the initial value that starts the series; of course, *one of them* (the dumbest one) is just to take it to be zero. But this dumbest initial guess is by no means the best out there in existence. === That is why I question the validity of your assumption that it must be like that. And that is why I ask you to provide an evidence in form of documentation that states that *in the beginning of the series of iterative self-referencing calculations, the initial guess of the value in that cell must be equal to zero*! === I set the status to NEEDINFO once again. The status here is not for you, Carlo Sarti; it's for us, who decide what to do next with the issue: if we need to proceed and declare it confirmed (and thus a candidate to be fixed eventually), or if we need more details on this; or if an issue should be closed. We ask you the necessary information, because it's you who is interested in "fixing" this, so it's in your interests to provide as much information as it's required. Doing this does not mean any hostile behaviour towards you; if someone wanted, one could just close this, and not ask you in the hope that you could make the issue clear (and so, we tell you that we hope that you can convince us!). Please only change the status back to UNCONFIRMED when you have provided the requested evidence in form of references to documentation. Thank you. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118257] when zooming bar is moved on Open GL , percent does not change
https://bugs.documentfoundation.org/show_bug.cgi?id=118257 Aron Budea changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ba...@caesar.elte.hu Status|UNCONFIRMED |RESOLVED See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |6208| --- Comment #2 from Aron Budea --- Thanks for the bug report, this is the same issue as bug 116208, closing as duplicate. *** This bug has been marked as a duplicate of bug 116208 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116208] Zoom factor, word counter etc. do not update in status bar (with OpenGL)
https://bugs.documentfoundation.org/show_bug.cgi?id=116208 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |8257| CC||a...@kagaku.xii.jp --- Comment #30 from Aron Budea --- *** Bug 118257 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108613] UI: colour bars for text became huge
https://bugs.documentfoundation.org/show_bug.cgi?id=108613 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91332] Saving XLSX File Removes textbox Linked to Other Tabs
https://bugs.documentfoundation.org/show_bug.cgi?id=91332 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 48965] FORMATTING: Incorrect alignment of characters from Catalog
https://bugs.documentfoundation.org/show_bug.cgi?id=48965 --- Comment #12 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 90175] Deactivating Bullets Removes Set Ruler Margins
https://bugs.documentfoundation.org/show_bug.cgi?id=90175 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104377] Handles on the ruler doesn't change according to the list indentation
https://bugs.documentfoundation.org/show_bug.cgi?id=104377 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 67774] FILEOPEN: XLS/XLSX: Alignment shift is incorrect - should use font's space size
https://bugs.documentfoundation.org/show_bug.cgi?id=67774 --- Comment #17 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 53004] Black squares is missing after import WMF files created by LTspice
https://bugs.documentfoundation.org/show_bug.cgi?id=53004 --- Comment #18 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68282] FILESAVE: Pasted Cells Format (Numbers) to blank cells for a whole row not preserved in .xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=68282 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86617] Ruler’s numbers and tick marks have low contrast when using dark KDE themes
https://bugs.documentfoundation.org/show_bug.cgi?id=86617 --- Comment #14 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 93242] Ruler numbers have 14 decimal places after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=93242 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 62812] writer_pdf_Export Font GDI handle leaks
https://bugs.documentfoundation.org/show_bug.cgi?id=62812 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 44400] UI: Ruler is not Left-aligned back, when the Enhanced Language Support is Disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=44400 --- Comment #12 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103987] FILESAVE: DOCX File corrupted after roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=103987 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108630] FILEOPEN: DOCX file numbered list sporadically bolding numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=108630 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 95231] Colors are not displayed in cells only after save as XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=95231 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107614] Chinese characters are wrongly aligned if 'vpal' feature enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=107614 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 43959] Horizontal ruler updates bad when changing zoom level
https://bugs.documentfoundation.org/show_bug.cgi?id=43959 --- Comment #13 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 92315] Writer incorrectly renders EMF file with text in it
https://bugs.documentfoundation.org/show_bug.cgi?id=92315 --- Comment #13 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118257] when zooming bar is moved on Open GL , percent does not change
https://bugs.documentfoundation.org/show_bug.cgi?id=118257 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||6208 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116208] Zoom factor, word counter etc. do not update in status bar (with OpenGL)
https://bugs.documentfoundation.org/show_bug.cgi?id=116208 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||8257 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118258] When LibreLogo run on Writer on Open GL , the character got broken.
https://bugs.documentfoundation.org/show_bug.cgi?id=118258 --- Comment #1 from Junichi Matsukawa --- Created attachment 142945 --> https://bugs.documentfoundation.org/attachment.cgi?id=142945=edit When LibreLogo run on Writer on Open GL ,the character got broken. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118258] New: When LibreLogo run on Writer on Open GL , the character got broken.
https://bugs.documentfoundation.org/show_bug.cgi?id=118258 Bug ID: 118258 Summary: When LibreLogo run on Writer on Open GL ,the character got broken. Product: LibreOffice Version: 6.1.0.0.beta2+ Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: graphics stack Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: a...@kagaku.xii.jp Description: When LibreLogo run on Writer on Open GL ,the character got broken. Steps to Reproduce: 1.options - view - graphics output 2.Use OpenGL for all rendering -- ON 3.Start 'Logo program button' on Writer 4.Change enlargement ratio 5.The character of LibreLogo gets broken. Actual Results: The character of LibreLogo gets broken. Expected Results: To repair Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: バージョン: 6.1.0.0.beta2 (x64) Build ID: 0f4d2060bc90b4008fbc8e6d9a49ec7eeea60b78 CPU threads: 4; OS:Windows 10.0; UI render: GL; ロケール: ja-JP (ja_JP); Calc: CL Using Separate Install GUI Use OpenGL for all rendering -- ON -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118257] when zooming bar is moved on Open GL , percent does not change
https://bugs.documentfoundation.org/show_bug.cgi?id=118257 --- Comment #1 from Junichi Matsukawa --- Created attachment 142944 --> https://bugs.documentfoundation.org/attachment.cgi?id=142944=edit when zooming bar is moved on Open GL ,percent does not change -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118257] New: when zooming bar is moved on Open GL , percent does not change
https://bugs.documentfoundation.org/show_bug.cgi?id=118257 Bug ID: 118257 Summary: when zooming bar is moved on Open GL ,percent does not change Product: LibreOffice Version: 6.1.0.0.beta2+ Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: graphics stack Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: a...@kagaku.xii.jp Description: when zooming bar is moved on Open GL ,percent does not change Steps to Reproduce: 1.options - view - graphics output 2.Use OpenGL for all rendering -- ON 2.Start Writer or Calc or Impress or Draw 3.zooming bar is moved 4.Percent does not change Actual Results: Percent does not change Expected Results: To repair Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: バージョン: 6.1.0.0.beta2 (x64) Build ID: 0f4d2060bc90b4008fbc8e6d9a49ec7eeea60b78 CPU threads: 4; OS:Windows 10.0; UI render: GL; ロケール: ja-JP (ja_JP); Calc: CL Using Separate Install GUI Use OpenGL for all rendering -- ON -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118249] LibreOffice can't handle umlauts in file-path
https://bugs.documentfoundation.org/show_bug.cgi?id=118249 Susan Gessing changed: What|Removed |Added CC||susanjea...@yahoo.com --- Comment #1 from Susan Gessing --- Could not reproduce on Windows 8.1: in Version: 6.0.5.1 (x64) Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 CPU threads: 4; OS: Windows 6.3; UI render: GL; Locale: en-US (en_US); Calc: CL and Version: 6.2.0.0.alpha0+ Build ID: b1740fba0d1e6e3d69c3781734509317f42a0e4f CPU threads: 4; OS: Windows 6.3; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-15_08:49:04 Locale: en-US (en_US); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 112926] FREEZE with some images images
https://bugs.documentfoundation.org/show_bug.cgi?id=112926 Susan Gessing changed: What|Removed |Added CC||susanjea...@yahoo.com --- Comment #7 from Susan Gessing --- Could not reproduce on Windows 8.1: Version: 6.0.5.1 (x64) Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 CPU threads: 4; OS: Windows 6.3; UI render: GL; Locale: en-US (en_US); Calc: CL and Version: 6.2.0.0.alpha0+ Build ID: b1740fba0d1e6e3d69c3781734509317f42a0e4f CPU threads: 4; OS: Windows 6.3; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-15_08:49:04 Locale: en-US (en_US); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 88277] [META] SVG fileOpen filter (Draw)
https://bugs.documentfoundation.org/show_bug.cgi?id=88277 Bug 88277 depends on bug 48066, which changed state. Bug 48066 Summary: SVG: stroke-linecap="round" and stroke-miterlimit="1" are ignored https://bugs.documentfoundation.org/show_bug.cgi?id=48066 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 48066] SVG: stroke-linecap="round" and stroke-miterlimit="1" are ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=48066 Regina Henschel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #20 from Regina Henschel --- Follow-up bug for rendering errors in presentation mode is bug 118255, errors in PDF export is bug 118256. The file first attached, renders now correctly in edit mode if inserted as image, and opening the file renders fine too after LO has switched to svgio for file open recently. Tested with Version: 6.2.0.0.alpha0+ (x64) Build ID: 2c85607101e2e04e870e3b87362f39f9a9148e6c CPU threads: 8; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-06-16_00:12:37 Locale: de-DE (de_DE); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 53276] draw:style="round" under draw:stroke-dash is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=53276 Bug 53276 depends on bug 48066, which changed state. Bug 48066 Summary: SVG: stroke-linecap="round" and stroke-miterlimit="1" are ignored https://bugs.documentfoundation.org/show_bug.cgi?id=48066 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118256] New: PDF export of presentation with svg image with stroke-miterlimit is wrong.
https://bugs.documentfoundation.org/show_bug.cgi?id=118256 Bug ID: 118256 Summary: PDF export of presentation with svg image with stroke-miterlimit is wrong. Product: LibreOffice Version: 6.2.0.0.alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de This is a follow-up report for bug 48066. After the fix for bug 48066, rendering of stroke-miterlimit is correct in edit mode. But export to PDF shows errors. To reproduce it us attachment https://bugs.documentfoundation.org/attachment.cgi?id=124241 "Presentation with linked svg and screenshots" from bug 48066. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118255] New: SVG: stroke-miterlimit is wrongly rendered in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118255 Bug ID: 118255 Summary: SVG: stroke-miterlimit is wrongly rendered in presentation mode Product: LibreOffice Version: 6.2.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de This is a follow-up report for bug 48066. After the fix for bug 48066, rendering of stroke-miterlimit is correct in edit mode. But in a running presentation it is still wrong. To reproduce it us attachment https://bugs.documentfoundation.org/attachment.cgi?id=124241 "Presentation with linked svg and screenshots" from bug 48066. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83675] embedded fonts are double and also non-used fonts are embedded - the used font is not embedded
https://bugs.documentfoundation.org/show_bug.cgi?id=83675 --- Comment #13 from Robert --- Confirmed problem exists in LibreOffice Writer 5.4.4 and 5.4.7.2 (both x64). See attachment "Demo of problem". I added two lines, then manually (not with styles) changed the font of one line to Merriweather Light and the other line to Montserrat ExtraBold. Both fonts were downloaded from FontSquirrel, both under the SIL Open Font License v1.10. I checked the embedding permissions on both fonts, and they are both installable. If I open the saved file with 7-zip and look at the font folder, neither font is in there. They are not being embedded even though the embed fonts checkbox is checked. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83675] embedded fonts are double and also non-used fonts are embedded - the used font is not embedded
https://bugs.documentfoundation.org/show_bug.cgi?id=83675 --- Comment #12 from Robert --- Created attachment 142943 --> https://bugs.documentfoundation.org/attachment.cgi?id=142943=edit Demo of problem This demonstrates the problem. Fonts are set to be embedded, and the two fonts have installable for the embedding permission. Yet neither is in the font folder. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 65353] FILESAVE: LibreOffice embeds fonts defined in styles (e.g. CJK and CTL fonts) but arent used in the document
https://bugs.documentfoundation.org/show_bug.cgi?id=65353 --- Comment #30 from Robert --- The problem is still present in LibreOffice Writer 5.4.7.2 (x64). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118233] ReportBuilder: filter setting function inconsistent in use of aliases when report based on nested query
https://bugs.documentfoundation.org/show_bug.cgi?id=118233 Drew Jensen changed: What|Removed |Added Summary|ReportBuilder: Firebird:|ReportBuilder: filter |filter setting function |setting function |inconsistent in use of |inconsistent in use of |aliases when report based |aliases when report based |on nested query |on nested query -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118233] ReportBuilder: Firebird: filter setting function inconsistent in use of aliases when report based on nested query
https://bugs.documentfoundation.org/show_bug.cgi?id=118233 --- Comment #6 from Drew Jensen --- Created attachment 142942 --> https://bugs.documentfoundation.org/attachment.cgi?id=142942=edit hsql version of file Very same behavior with hsql based file (had to change the queries just a tad but otherwise identical DBs) So, not just firebird, will update summary again. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118254] New: Extension TexMaths (0.46) broken in LibO 6.1 beta
https://bugs.documentfoundation.org/show_bug.cgi?id=118254 Bug ID: 118254 Summary: Extension TexMaths (0.46) broken in LibO 6.1 beta Product: LibreOffice Version: 6.1.0.0.beta2+ Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sergio.calleg...@gmail.com Description: It is unclear to me if the issue is on the TexMaths side or on the LibO one. However, the quite useful TexMaths extension appears to be broken on 6.1 beta 1 and 2. Trying to edit equations with texmaths and LibO 6.1 beta 2 results in an "Object variable not set." error on line 574 of TexMathsTools oDrawDocCtrl = oDrawDoc.getCurrentController() I have opened an issue on the TexMaths tracker as well: https://sourceforge.net/p/texmaths/bugs/98/ Steps to Reproduce: 1. Open a document with a TexMaths equation in it (tested with a draw document) 2. Select the equation and click the button to open the TexMaths editior 3. Press the "LaTeX" button to reprocess the equation into its svg version. Actual Results: An error dialog is reported. The macro editor opens. Expected Results: The equation svg image is regenerated. Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104753] Missing option to have a symbol with a subscript and a prime symbol in LibO Math
https://bugs.documentfoundation.org/show_bug.cgi?id=104753 --- Comment #9 from sergio.calleg...@gmail.com --- Sorry, you are right, I missed that. I think that the "normal_padded_prime" example looks like a significant improvement with respect to the current situation. I would definitely go for it! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104134] Wishlist - Add insert content file from git repository
https://bugs.documentfoundation.org/show_bug.cgi?id=104134 Javi Barroso changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #5 from Javi Barroso --- Hello, (In reply to Jean-Baptiste Faure from comment #4) > (In reply to Javi Barroso from comment #3) > > Our git repository is not available via http / https, but if libreoffice > > could have this feature, we would add http support to git > > I do not understand what you mean. If you add http support to your git > repository, there is no need to have git support in LibreOffice. > > Please explain why you prefer a change in LibreOffice instead of a change in > your git repository configuration. When I document, at our job, is needed to include scripts on the document, because maybe people without (full) access to the source. Currently we create annexes and copy-paste the code, but when we modify the code at the server, the document is difficult to have updated (you will forgot that the script is in the document) > > Status set to NEEDINFO, please set it back to UNCONFIRMED once requested > informations are provided. > > Best regards. JBF Hello, Imagine, I want to have the updated content of a file inside a doc. Libreoffice could add an option to load a section from an URI. For example I could write: "See the source code of vibreoffice:" and then insert a section with the next URL: https://github.com/seanyeh/vibreoffice/blob/master/src/vibreoffice.vbs Then libreoffice download the file and mark the section as updated at 2018/06/20 00:08 (and show you the new session with the content of the file) Next time that I will open the document, it should be configurable to tell what to do about every section: - update on startup - update on demand - update when visualize the section - show cached file when there is not network connection The same can be applied with git://xxx, scheme or other URIs Thank you! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118253] New: Roku tech support number
https://bugs.documentfoundation.org/show_bug.cgi?id=118253 Bug ID: 118253 Summary: Roku tech support number Product: LibreOffice Version: 3.3.0 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: roku4h...@gmail.com Description: With a group of specialists, we are to a great degree near accomplishing every one of the accomplishments by making surety of consumer loyalty. Steps to Reproduce: 1.Roku customer care phone number 2.Roku customer care 3.Roku support phone number Actual Results: https://www.techistra.com/roku-customer-care/ Expected Results: https://www.techistra.com/roku-customer-care/ Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: https://www.techistra.com/roku-customer-care/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118233] ReportBuilder: Firebird: filter setting function inconsistent in use of aliases when report based on nested query
https://bugs.documentfoundation.org/show_bug.cgi?id=118233 Drew Jensen changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Summary|ReportBuilder does not know |ReportBuilder: Firebird: |aliases for Firebird views |filter setting function ||inconsistent in use of ||aliases when report based ||on nested query --- Comment #5 from Drew Jensen --- Changing summary to more closely match error -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118233] ReportBuilder does not know aliases for Firebird views
https://bugs.documentfoundation.org/show_bug.cgi?id=118233 Drew Jensen changed: What|Removed |Added CC||drewjensen.in...@gmail.com --- Comment #4 from Drew Jensen --- Created attachment 142941 --> https://bugs.documentfoundation.org/attachment.cgi?id=142941=edit screen shot showing issue Got it: Two QueryDefinitions; MitgliederVerbandExcelvorlage and Abfrage1. MitgliederVerbandExcelvorlage uses table MitgliederVerband Abfrage1 uses MitgliederVerbandExcelvorlage and creates one alias, VereinID Report is based on Abfrage1 and in the set filter dialog references Abfrage1.VereinID But the filter SQL snippet references "MitgliederVerbandExcelvorlage"."Verien" instead of ( "Abfrage1"."VereinID" = '0' ) As far as I can tell it doesn't change the result set (didn't after I added some records and ran the report with both variations), but it seems it should the later and the not the former. Put it all in pictures(why not? ;) see attachment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105257] Wayland: Popup menus are misplaced when two monitors are not combined exactly side by side
https://bugs.documentfoundation.org/show_bug.cgi?id=105257 --- Comment #13 from Maxim Monastirsky --- (In reply to Dima Ryazanov from comment #12) And in the meantime I converted master to use gtk_menu_popup_at_rect, so likely we're not affected by this anymore: https://cgit.freedesktop.org/libreoffice/core/commit/?id=c3e552ac25be001a623469c549ee8d0719b98133 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114736] Crash with CJK characters in status bar (OpenGL)
https://bugs.documentfoundation.org/show_bug.cgi?id=114736 --- Comment #24 from Commit Notification --- Tamas Bunth committed a patch related to this issue. It has been pushed to "libreoffice-6-0-5": http://cgit.freedesktop.org/libreoffice/core/commit/?id=bdeb53b8dfee78ea312110563d1e80b969436cbc=libreoffice-6-0-5 tdf#114736 no need to call AdjustLayout here It will be available in 6.0.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114736] Crash with CJK characters in status bar (OpenGL)
https://bugs.documentfoundation.org/show_bug.cgi?id=114736 Commit Notification changed: What|Removed |Added Whiteboard|target:6.1.0 target:6.0.6 |target:6.1.0 target:6.0.6 ||target:6.0.5 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105257] Wayland: Popup menus are misplaced when two monitors are not combined exactly side by side
https://bugs.documentfoundation.org/show_bug.cgi?id=105257 --- Comment #12 from Dima Ryazanov --- This is actually a Gtk+ bug. I have a fix for it here: https://gitlab.gnome.org/GNOME/gtk/issues/1154 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108270] Reloading presentation created with Focus template leaks memory leaks more memory every time (see comment 1)
https://bugs.documentfoundation.org/show_bug.cgi?id=108270 --- Comment #7 from Telesto --- Created attachment 142940 --> https://bugs.documentfoundation.org/attachment.cgi?id=142940=edit DrMemory (In reply to Caolán McNamara from comment #6) > drmemory didn't report any leaks from reloading a few times and exiting, so > hard to see what's accumulating I did a drmemory run. Results attached. I get quite a lot of errors. Mostly python35.dll. An example: Error #271: UNADDRESSABLE ACCESS beyond heap bounds: reading 0x1067d010-0x1067d014 4 byte(s) # 0 python35.dll!Py_GetAllocatedBlocks +0x3fe(0x533395ee ) # 1 python35.dll!PyObject_Free +0x11 (0x533391e2 ) # 2 python35.dll!PyEval_EvalFrameEx+0x792(0x53392323 ) # 3 python35.dll!PyEval_GetFuncDesc+0x4d3(0x53396e64 ) # 4 python35.dll!PyEval_GetFuncDesc+0x3d2(0x53396d63 ) # 5 python35.dll!PyEval_EvalFrameEx+0x2264 (0x53393df5 ) # 6 python35.dll!PyEval_EvalFrameEx+0x410e (0x53395c9f ) # 7 python35.dll!PyEval_GetFuncDesc+0x53b(0x53396ecc ) # 8 python35.dll!PyEval_GetFuncDesc+0x3d2(0x53396d63 ) # 9 python35.dll!PyEval_EvalFrameEx+0x2264 (0x53393df5 ) #10 python35.dll!PyEval_GetFuncDesc+0x4d3(0x53396e64 ) #11 python35.dll!PyEval_GetFuncDesc+0x3d2(0x53396d63 ) #12 python35.dll!PyEval_EvalFrameEx+0x2264 (0x53393df5 ) #13 python35.dll!PyEval_GetFuncDesc+0x4d3(0x53396e64 ) #14 python35.dll!PyEval_GetFuncDesc+0x3d2(0x53396d63 ) #15 python35.dll!PyEval_EvalFrameEx+0x2264 (0x53393df5 ) #16 python35.dll!PyEval_GetFuncDesc+0x4d3(0x53396e64 ) #17 python35.dll!PyEval_GetFuncDesc+0x3d2(0x53396d63 ) #18 python35.dll!PyEval_EvalFrameEx+0x2264 (0x53393df5 ) #19 python35.dll!PyEval_GetFuncDesc+0x4d3(0x53396e64 ) Note: @0:00:38.872 in thread 2632 Note: next higher malloc: 0x1067d020-0x1067d060 Note: prev lower malloc: 0x1067c470-0x1067ca80 Note: instruction: mov0x10(%edx) -> %esi Version: 6.2.0.0.alpha0+ Build ID: 66effc66abb1356af0aa54a79a83b1aae53520e4 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-19_05:01:54 Locale: nl-NL (nl_NL); Calc: CL Removing: bibisected, bisected; probably wrong -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108270] Reloading presentation created with Focus template leaks memory leaks more memory every time (see comment 1)
https://bugs.documentfoundation.org/show_bug.cgi?id=108270 Telesto changed: What|Removed |Added Keywords|bibisected, bisected, | |regression | -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118252] New: Focus not properly restored to the document after using submenu items of a context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=118252 Bug ID: 118252 Summary: Focus not properly restored to the document after using submenu items of a context menu Product: LibreOffice Version: 6.0.0.0.alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: graphics stack Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: momonas...@gmail.com Steps to reproduce: 1. Open Writer with vclplug which doesn't use native context menus (i.e. not gtk3 or macOS). 2. Write something and copy it. 3. Right click > Paste Special > Unformatted Text. Actual results: At this stage there is no longer blinking cursor inside the document, although typing is still possible. Running a debug build emits this warning while typing: warn:vcl:25661:25661:vcl/source/window/winproc.cxx:840: ImplHandleKey: Keyboard-Input is sent to a frame without focus It works correctly when using commands from the first level of the context menu (e.g. "Paste"). Expected Results: Text cursor should be visible after using the context menu. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118120] EDITING: Selecting the ALL button on the message box displayed when user starts DELETE of multiple items in Base Tables window goes to help file instead of deleting all
https://bugs.documentfoundation.org/show_bug.cgi?id=118120 Julien Nabet changed: What|Removed |Added Keywords||regression Severity|normal |major --- Comment #3 from Julien Nabet --- On pc Debian x86-64 with LO Debian package 6.0.5.1, I don't reproduce this => regression -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118251] Crash when closing the color picker dialog if it was opened from the overflow toolbar popup
https://bugs.documentfoundation.org/show_bug.cgi?id=118251 Xisco Faulí changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected Severity|major |critical Status|UNCONFIRMED |NEW Version|6.2.0.0.alpha0+ Master |6.1.0.0.alpha1+ CC||caol...@redhat.com, ||xiscofa...@libreoffice.org Ever confirmed|0 |1 Priority|medium |highest --- Comment #1 from Xisco Faulí --- Regression introduced by: author Caolán McNamara 2018-05-08 12:35:19 +0100 committer Caolán McNamara 2018-05-08 16:05:41 +0200 commit bfcf57de81ddd5ed8544ff2ede23bd8428f0c0ce (patch) treea6d3a528b2ec1e5f41764984d16675df3d352621 parent b68daa69739e83095c023b683234d344d0fa02c8 (diff) Resolves: tdf#117470 reuse parent window of colorwindow... as parent of color selector window Bisected with: bibisect-linux64-6.1 Adding Cc: to Caolán McNamara -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117049] Severe bug in LibreOffice (Calc Speadsheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=117049 --- Comment #13 from Eike Rathke --- (In reply to sarti_ca...@yahoo.com from comment #11) > Eike Rathke, are you an Calc expert? have you done anything? > If you are not sure if the described behavior is a bug, you mast change > work. The agricolture offers many opportunities. Do you want to effing annoy me? Go on, goal reached. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118250] CSV Datei aus Google Sheets als Datenbankquelle
https://bugs.documentfoundation.org/show_bug.cgi?id=118250 --- Comment #1 from Drew Jensen --- (In reply to fra2uth from comment #0) > Description: > Habe eine .csv Datei aus Google Sheets als Datenquelle angelegt, in den > erstellten Berichten werden die Umlaute aber nicht korrekt als Unicode > angezeigt, wenn ich die selbe Datei nach CALC importiere und UTF-8 wähle ist > die Darstellung korrekt > > Steps to Reproduce: > 1.Google Sheets als .csv mit ÄäöÖüÜ in Spalten auf Google drive erstellen > 2.Google Sync einrichten > 3.Bei Base -> Neue Datenbankc-> aus vorhandener erstellen -> Tabellendokument If instead you created selected 'aus vorhandener erstellen -> Text' and supplied a directory where the .csv is stored, then you have the option to set the character set for the files, UTF-8 or otherwise, as needed. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97653] INSERT: woman's body not rendered in SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=97653 --- Comment #3 from kompilainenn <79045_79...@mail.ru> --- still repro in 6.1 beta 2 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97651] INSERT: SVG tag not supported
https://bugs.documentfoundation.org/show_bug.cgi?id=97651 --- Comment #6 from kompilainenn <79045_79...@mail.ru> --- still repro in 6.1 beta 1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97585] INSERT: SVG background not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=97585 --- Comment #5 from kompilainenn <79045_79...@mail.ru> --- still repro in 6.1 beta 2 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118221] Calc fails to render kerning=off (default setting) for single-line cells, only works during cell edit mode [F2] (affects screen, paper and PDF) [Comment 15]
https://bugs.documentfoundation.org/show_bug.cgi?id=118221 --- Comment #27 from Eike Rathke --- (In reply to OfficeUser from comment #25) > @Stuart: > > "Suspect flushing all cell content through edit engine just to provide > > layout kerning is going to impose considerable performance drag. > > Are there any values for a performance degrade available if using EditEngine > always? I did a short stress testing right now, =1 formulas in narrow (optimal width) columns to have as many columns as possible to paint filling a screen width, 5000 rows, jump to end, hold PageUp to scroll to row 1: takes 5 seconds; compiled to force EditEngine takes 30 seconds. > > What might be possible is for non-EditEngine cells tell OutputDevice to > > force kerning off via SalLayoutFlags::DisableKerning (I didn't track how > > exactly we call OutputDevice draws there). > > Is this possible to change per character? We need to keep in mind that we > are talking of a character attribute (like bold, underlined, ...). As said in my previous comment, for inline formatted content (i.e. per character attribution) already EditEngine text is used. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118120] EDITING: Selecting the ALL button on the message box displayed when user starts DELETE of multiple items in Base Tables window goes to help file instead of deleting all
https://bugs.documentfoundation.org/show_bug.cgi?id=118120 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105207] Crash while calling MRI when it is not loaded.
https://bugs.documentfoundation.org/show_bug.cgi?id=105207 Jean-Baptiste Faure changed: What|Removed |Added Ever confirmed|0 |1 CC||jbfa...@libreoffice.org Status|UNCONFIRMED |NEEDINFO --- Comment #6 from Jean-Baptiste Faure --- What is MRI library ? Is it cross-platform or Windows only? Status set to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97583] INSERT: SVG doesnt support blur
https://bugs.documentfoundation.org/show_bug.cgi?id=97583 --- Comment #6 from kompilainenn <79045_79...@mail.ru> --- still repro in 6.1 beta 2 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97576] INSERT: SVG font glyphs ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=97576 --- Comment #2 from kompilainenn <79045_79...@mail.ru> --- still repro in 6.1 beta 2 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97566] INSERT: SVG redraw at different zoom/resize levels crops content
https://bugs.documentfoundation.org/show_bug.cgi?id=97566 kompilainenn <79045_79...@mail.ru> changed: What|Removed |Added Status|NEW |RESOLVED CC||79045_79...@mail.ru Resolution|--- |WORKSFORME --- Comment #3 from kompilainenn <79045_79...@mail.ru> --- don't repro in 6.1 beta 2 but bottom text "SVG Open 2009" shows not correctly -> this will be a new bug, imho Status -> WFM -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 88278] [META] insert SVG image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Bug 88278 depends on bug 97566, which changed state. Bug 97566 Summary: INSERT: SVG redraw at different zoom/resize levels crops content https://bugs.documentfoundation.org/show_bug.cgi?id=97566 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97539] INSERT: SVG clippath not fully supported
https://bugs.documentfoundation.org/show_bug.cgi?id=97539 --- Comment #14 from kompilainenn <79045_79...@mail.ru> --- still repro in LO 6.1 beta 2 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118251] New: Crash when closing the color picker dialog if it was opened from the overflow toolbar popup
https://bugs.documentfoundation.org/show_bug.cgi?id=118251 Bug ID: 118251 Summary: Crash when closing the color picker dialog if it was opened from the overflow toolbar popup Product: LibreOffice Version: 6.2.0.0.alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Keywords: bibisectRequest, regression Severity: major Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: momonas...@gmail.com Steps to reproduce: 1. Open Writer. 2. Resize the window horizontally, so that at least one of the toolbar color buttons won't be visible anymore. 3. Click the toolbar overflow indicator to show the hidden items. 4. Click the dropdown arrow of the color button, and choose "Custom Color..." 5. Close the dialog -> Crash. Regression, as it used to work in 6.0. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97537] INSERT: SVG text color and style incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=97537 kompilainenn <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #4 from kompilainenn <79045_79...@mail.ru> --- Created attachment 142939 --> https://bugs.documentfoundation.org/attachment.cgi?id=142939=edit bloglines in LO Draw 6.1 beta 2 still repro in LO Draw 6.1 beta 2, but rendering became worse -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118250] New: CSV Datei aus Google Sheets als Datenbankquelle
https://bugs.documentfoundation.org/show_bug.cgi?id=118250 Bug ID: 118250 Summary: CSV Datei aus Google Sheets als Datenbankquelle Product: LibreOffice Version: 6.0.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: fra2...@gmail.com Description: Habe eine .csv Datei aus Google Sheets als Datenquelle angelegt, in den erstellten Berichten werden die Umlaute aber nicht korrekt als Unicode angezeigt, wenn ich die selbe Datei nach CALC importiere und UTF-8 wähle ist die Darstellung korrekt Steps to Reproduce: 1.Google Sheets als .csv mit ÄäöÖüÜ in Spalten auf Google drive erstellen 2.Google Sync einrichten 3.Bei Base -> Neue Datenbankc-> aus vorhandener erstellen -> Tabellendokument 4.Pfad zu Tabellendokument in lokalem Google Drive Ordner angeben 5.Bericht erstellen 6. im Bericht werden die Umlaute falsch dargestellt und es gibt keine Möglichkeit dass zu ändern Actual Results: Rücklauf Expected Results: Rücklauf Reproducible: Always User Profile Reset: No Additional Info: Version: 6.0.4.2 (x64) Build-ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: group -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104804] TOC entries are not exported as Named Destinations in PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=104804 Jean-Baptiste Faure changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||jbfa...@libreoffice.org --- Comment #19 from Jean-Baptiste Faure --- (In reply to crun from comment #18) > I will make a pdf example showing what I have done, and explaining it, and > upload soon. Hi crun, Do you still plan to do that pdf example? Status set to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117830] Wrong header/footer shown for intermittent section in DOC(X)
https://bugs.documentfoundation.org/show_bug.cgi?id=117830 Buovjaga changed: What|Removed |Added CC||todven...@suomi24.fi Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #6 from Buovjaga --- Confirmed. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: dc9ee533dc707cc10b99d537eaccc3ee5aa555fe CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on June 16th 2018 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118217] Menubar: writer menubar update
https://bugs.documentfoundation.org/show_bug.cgi?id=118217 --- Comment #10 from andreas_k --- I start first with a convergence between ALL LibO APPS cause now "only" swriter, scalc, sdraw and simpress are done. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118183] FILEOPEN: bad text position rendering in table
https://bugs.documentfoundation.org/show_bug.cgi?id=118183 --- Comment #6 from Regina Henschel --- Version: 6.1.0.0.beta1 (x64) Build ID: 8c76dfe1284e211954c30f219b3a38dcdd82f8a0 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: CL I see the table borders on the margin edge. That is wrong, because fo:margin-left="-0.125cm". The paragraph seems to take the table margin in account and therefore the paragraph start is left from the table start. The error is not the paragraph start but the table start. Version: 6.2.0.0.alpha0+ (x64) Build ID: c3e552ac25be001a623469c549ee8d0719b98133 CPU threads: 8; OS: Windows 10.0; UI render: GL; Locale: de-DE (de_DE); Calc: CL I see a correct position of table and paragraph, both -0.13cm left from the margin edge. But I get a glitch in the table property dialog. The option "from left" is active, but fields Width and Left are disabled. The behavior was correct in Version: Version: 6.0.0.0.alpha1+ (x64) Build ID: a5af0fd9f27af42cf2e8571f659cdad6e606215b CPU threads: 8; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-07_00:30:02 Locale: de-DE (de_DE); Calc: CL The error needs to be fixed for the version 6.1.beta, because such negative left table alignment value is needed for import of .docx files, which were produced by older Word versions or saved in Word compatibility mode. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118239] Short cuts – allow for actions in reverse ways.
https://bugs.documentfoundation.org/show_bug.cgi?id=118239 --- Comment #2 from ricky.t...@gmail.com --- Indeed in the case of 'Ctrl+H' that is the use of key Esc that was adopted to act as the Close command, not the reverse way. So it seems that there was then no object for enhancement in the present report. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118212] Launching Character dialog from any module crashes ( with CJK and CTL disabled )
https://bugs.documentfoundation.org/show_bug.cgi?id=118212 Julien Nabet changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | Status|NEW |ASSIGNED --- Comment #15 from Julien Nabet --- Patch submitted on gerrit here: https://gerrit.libreoffice.org/#/c/56124/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118212] Launching Character dialog from any module crashes ( with CJK and CTL disabled )
https://bugs.documentfoundation.org/show_bug.cgi?id=118212 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #14 from Julien Nabet --- Created attachment 142938 --> https://bugs.documentfoundation.org/attachment.cgi?id=142938=edit bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117814] PIVOTTABLE: date format from registered data source lost (FORMATTING)
https://bugs.documentfoundation.org/show_bug.cgi?id=117814 Buovjaga changed: What|Removed |Added Keywords||bibisectRequest, regression Status|NEEDINFO|NEW --- Comment #3 from Buovjaga --- Thanks! I could repro, but not in 3.6.7 -> regression. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: dc9ee533dc707cc10b99d537eaccc3ee5aa555fe CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on June 16th 2018 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118242] DOCX EXPORT: anchor of text frame is wrong + MSO can't open the file
https://bugs.documentfoundation.org/show_bug.cgi?id=118242 Xisco Faulí changed: What|Removed |Added CC||vmik...@collabora.co.uk, ||xiscofa...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||7805 Status|UNCONFIRMED |NEW Keywords||bibisected, bisected, ||filter:docx, regression Ever confirmed|0 |1 --- Comment #3 from Xisco Faulí --- Wow, that was a fast catch! Regression introduced by: author Miklos Vajna 2018-06-18 21:06:30 +0200 committer Miklos Vajna 2018-06-19 09:02:59 +0200 commit 853350787df9a8d92c269ef1b6e764863e74ec2a (patch) treee6a25de0428e94b7ea4fa46d7c202d65e947b92f parent 3a8375eb974eb8ba36ac616478acd881b70f8e19 (diff) tdf#117805 DOCX export: fix lost header with at-page anchored frames The bug has two parts: on one hand, the header was not completely lost, just was written inside a shape. This is not valid, but at least our own import understood that. This commit restores that old behavior, focusing on just the regression part of the bugreport. On the other hand the exported header is still referenced at an incorrect location: the correct location would be the end of the document. But that is follow-up work, it seems that never worked. Bisected with: bibisect-linux64-6.2 Adding Cc: to Miklos Vajna -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 101736] standard keyboard shortcut to increase / decrease indent on macOS (macOS only)
https://bugs.documentfoundation.org/show_bug.cgi?id=101736 --- Comment #5 from Thomas Lendo --- If a shortcut will be added it should follow the main and similar other products of the OS so that's better memorizable by users. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118217] Menubar: writer menubar update
https://bugs.documentfoundation.org/show_bug.cgi?id=118217 --- Comment #9 from Thomas Lendo --- Personally I'm not afraid of or against changes per se. But I would really like to hear the reasons for every change. Maybe it's a good idea that others also like and we can do that. Step by step could help too instead of a mass change for that you can't convince others. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94792] Fileopen: performance regression for xlsx with chart with >1.000 data labels; also dump (svllo!SfxBroadcaster::RemoveListener+16)
https://bugs.documentfoundation.org/show_bug.cgi?id=94792 --- Comment #17 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=378f15a48bcb9fc9676644c20541a943efcd5565=libreoffice-6-1 tdf#94792 performance regression for xlsx with chart with >1000 data labels It will be available in 6.1.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94792] Fileopen: performance regression for xlsx with chart with >1.000 data labels; also dump (svllo!SfxBroadcaster::RemoveListener+16)
https://bugs.documentfoundation.org/show_bug.cgi?id=94792 Commit Notification changed: What|Removed |Added Whiteboard|target:6.2.0|target:6.2.0 target:6.1.0.1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118220] LO Base : Tools -> Table Filter crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=118220 Noel Grandin changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118220] LO Base : Tools -> Table Filter crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=118220 --- Comment #7 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=b28464abc71c28450784f15ce8344da8b316da86 tdf#118220 Base : Tools -> Table Filter crashes It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118220] LO Base : Tools -> Table Filter crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=118220 Commit Notification changed: What|Removed |Added Whiteboard||target:6.2.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 110736] SAVING : Calc freezes during saving a remote file on Google Drive
https://bugs.documentfoundation.org/show_bug.cgi?id=110736 malboarg changed: What|Removed |Added Ever confirmed|0 |1 CC||malbo...@gmail.com Status|UNCONFIRMED |NEW --- Comment #4 from malboarg --- The bug is present in: Version: 6.1.0.0.beta1 Build ID: 8c76dfe1284e211954c30f219b3a38dcdd82f8a0 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; When I click on "File" (step 4bis) it takes average 6 or 7 seconds to respond. The file tested is small (27kb) ,and my connection is slow (6Mb). After that, during navigation, sometimes there are some small freezes of 3 or 4 seconds (for instance when I change a cell content). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117049] Severe bug in LibreOffice (Calc Speadsheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=117049 --- Comment #12 from sarti_ca...@yahoo.com --- I my comment #7, I added an attached: Conto.xls. Do you see it? If you don't, I can add again. Best regards Carlo Sarti -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117813] *.csv database: changing character set needs a disconnect
https://bugs.documentfoundation.org/show_bug.cgi?id=117813 --- Comment #6 from Drew Jensen --- Created attachment 142937 --> https://bugs.documentfoundation.org/attachment.cgi?id=142937=edit screen shot after character set change (In reply to Oliver Brinzing from comment #4) > please have a look at attached picture "db_properties", tab "Additional > Settings" it seems to be working for me here. Ubuntu 18.04 and Libo 6.1Beta2 Downloaded the data files, registered the database, opened a new calc file and the data source window there. Selected the datasource and opened it for editing, changed the character support from system to UTF-8. Saved and close the odb file. Back in the beamer window I opened the table and the data displayed all appears as I would expect with UTF-8 as the character set. OK, so I went and opened the odb for editing, again from the context menu in the datasource window and changed the character set to (something else which I was pretty sure would not display the characters properly; cryllic), saved the file, refreshed the tables via the ODB interface and closed the ODB file. Back in the Calc file, the data in the beamer grid has not changed, and I would not expect it to, Base has always IIRC used dirty reads for the table grid control. However, I then grad the table item in the tree view and drag it to the calc sheet, and sure enough the data generates some rather odd looking characters. Screen shot attached. So, it looks to me like it is updating to the change -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117049] Severe bug in LibreOffice (Calc Speadsheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=117049 sarti_ca...@yahoo.com changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #11 from sarti_ca...@yahoo.com --- I don't understand the status change done by jbfa...@libreoffice.org and miguelange...@liber.org. Your comment #9 is following to mine (#7 and 8). mikekagan...@hotmail.com wrote, in comment #1, "I do reproduce the described behavior". m.a.riosv, you made a "crap" to change my bug as "RESOLVED DUPLICATE of bug 114482". Please, stop to do other changes. Mike Kaganski wrote , in comment #1, "but I can't confirm the bug because I don't know if it's actually a bug … Calc experts may have a different opinion here, and correct me. For that reason, I add Eike Rathke to the CC". Eike Rathke, are you an Calc expert? have you done anything? If you are not sure if the described behavior is a bug, you mast change work. The agricolture offers many opportunities. In any case, all you must read my comments #7 and 8. I explain because it is a bug. I explain, mathematically speaking, what means to do B1=B1+A1 (one time), starting from B1=0 and A1=100. Furthermore, I add the use for piggy bank, as use of circular references with Steps (first parameter in Iterations) set to 1. Excuse me, if I, at the end of comment #8, joked writing "Have I invented a new technique? Must I patent it? I don't think", for the use as continued addition. After having added new info (comments #7 and 8), I changed the status from NEEDINFO to UNCONFIRMED, as suggested by the system. I will change again the Status to UNCONFIRMED. Who has to make a decision to solve this stupid bug? I thing that UBUNTU must replace Libre with SoftMaker. In these days, this society released "free office 2018". Best regards Carlo Sarti -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117814] PIVOTTABLE: date format from registered data source lost (FORMATTING)
https://bugs.documentfoundation.org/show_bug.cgi?id=117814 Oliver Brinzing changed: What|Removed |Added CC||oliver.brinz...@gmx.de --- Comment #2 from Oliver Brinzing --- - download data.odb and data.csv from https://bugs.documentfoundation.org/show_bug.cgi?id=117813 - Tools/Options.../LibreOffice Base/Databases [New...], [Browse...], select "data.odb" [OK] - calc menu Data/Pivot Table/Create... (*) Data Source registered in LibreOffice [OK] - Database [data ] Type [Table] Data Souce [data ] [OK] - add [Datum] to "Column Fields" [OK] -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117813] *.csv database: changing character set needs a disconnect
https://bugs.documentfoundation.org/show_bug.cgi?id=117813 --- Comment #5 from Buovjaga --- (In reply to Oliver Brinzing from comment #4) > please have a look at attached picture "db_properties", tab "Additional > Settings" Yeah, I am missing the tab. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117792] Maximised windows for forms or reports in Base are reopened bigger than the actual window (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=117792 Buovjaga changed: What|Removed |Added Ever confirmed|0 |1 Summary|Maximised windows for forms |Maximised windows for forms |in Base are reopened bigger |or reports in Base are |than the actual window |reopened bigger than the ||actual window ||(Windows-only) Status|UNCONFIRMED |NEW CC||todven...@suomi24.fi Keywords||notBibisectable, regression --- Comment #3 from Buovjaga --- I confirm it was bigger than the screen size. Not yet seen in 5.4.2.2. Tried to bibisect with Win 6.0 repo, but unfortunately got stuck in a skipping nightmare because there were commits where the program hung upon opening a form. Not seen on Linux. Version: 6.2.0.0.alpha0+ (x64) Build ID: 2c85607101e2e04e870e3b87362f39f9a9148e6c CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-06-16_00:12:37 Locale: fi-FI (fi_FI); Calc: group threaded Version: 6.0.4.2 (x64) Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: dc9ee533dc707cc10b99d537eaccc3ee5aa555fe CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on June 16th 2018 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117813] *.csv database: changing character set needs a disconnect
https://bugs.documentfoundation.org/show_bug.cgi?id=117813 --- Comment #4 from Oliver Brinzing --- please have a look at attached picture "db_properties", tab "Additional Settings" -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
