[Libreoffice-bugs] [Bug 125624] CRASH working with file with lots of hints
https://bugs.documentfoundation.org/show_bug.cgi?id=125624 --- Comment #7 from Mike Kaganski --- /me has some inexplicable feeling that tdf#125624 has something to do with mst___'s redline work :-D -- 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 125624] CRASH working with file with lots of hints
https://bugs.documentfoundation.org/show_bug.cgi?id=125624 --- Comment #6 from Mike Kaganski --- One needs to launch soffice with SW_REDLINEHIDE=1, to successfully bibisect prior to https://git.libreoffice.org/core/+/ae3150b1e1863e854224c2e41c7e50991f945dad -- 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 125729] Tab colors in Calc should show the line version when inactive and full version when active to be more intuitive
https://bugs.documentfoundation.org/show_bug.cgi?id=125729 Tim Chambers changed: What|Removed |Added Summary|Tab colors in Calc should |Tab colors in Calc should |show the line version when |show the line version when |inactive and ull version|inactive and full version |when active |when active to be more ||intuitive -- 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 125729] New: Tab colors in Calc should show the line version when inactive and ull version when active
https://bugs.documentfoundation.org/show_bug.cgi?id=125729 Bug ID: 125729 Summary: Tab colors in Calc should show the line version when inactive and ull version when active Product: LibreOffice Version: 6.2.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tim.chambers1...@gmail.com Description: In Calc, colors can be assigned to tabs. Currently the active tab is white (base colour) with the tab colour shown as a line across the bottom. Inactive tabs are shown with the tab being filled with the tab colour. If this were reversed, where the active tab had more colour than the inactive tabs, it would be more intuitive Steps to Reproduce: 1. Create multiple tabs in a spreadsheet 2.Assign colours to the tabs 3. Switch between tabs Actual Results: as described above Expected Results: as described above Reproducible: Always User Profile Reset: No Additional Info: Perhaps a UI option to switch between methods would be good? -- 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 125671] Calc stops accepting keyboard input after pasting into a cell with data
https://bugs.documentfoundation.org/show_bug.cgi?id=125671 Szymon Tomasz Stefanek changed: What|Removed |Added Resolution|--- |INVALID Status|NEEDINFO|RESOLVED --- Comment #2 from Szymon Tomasz Stefanek --- You are right, I have upgraded libreoffice to the newest ubuntu packages (6.2.3.2) and the problem went away. Sorry for the noise. Closing. -- 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 124947] Dialog theming/UX - Radio buttons are hard to use
https://bugs.documentfoundation.org/show_bug.cgi?id=124947 --- Comment #3 from Tomaz Vajngerl --- Hmm. the hit area is shifted down. Fixing that should make it easier to hit a radio button easier. -- 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 125728] New: Feature request - adding Julia language for scripting in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=125728 Bug ID: 125728 Summary: Feature request - adding Julia language for scripting in Calc Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: anton.koch...@gmail.com Julia is a multiple-paradigm (fully imperative, partially functional, and partially object-oriented) programming language designed for scientific and technical (read numerical) computing. https://julialang.org Performance gains range in the range from 10x-30x over Python (R is even slower, so we don’t include it. R was not built for speed). Industry reports in 2016 indicated that Julia was a language with high potential and possibly the chance of becoming the best option for data science if it received advocacy and adoption by the community. Well, two years on, the 1.0 version of Julia was out in August 2018 (version 1.0), and it has the advocacy of the programming community and the adoption by a number of companies (see https://www.juliacomputing.com) as the preferred language for many domains — including data science. And 1.2 version is almost ready as well: https://github.com/JuliaLang/julia/milestone/30 Advantages of Julia (compared to Python) - Performance - GPU Support - Smooth Learning Curve, and Extensive Built-in Functionality - Multiple dispatch or the multimethod functionality - Distributed and Parallel Computing Support - Interoperation with other programming languages (C, Java, Python, etc) Moreover, Julia Computing offers the JuliaInXL package - Julia integration with Microsoft Excel: - https://juliacomputing.com/blog/2017/10/24/julia-in-xl-intro.html - https://juliacomputing.com/products/juliafin.html#excel - https://www.youtube.com/watch?v=59Kr37uqtm4 See more at: - https://medium.com/@thomascherickal/will-julia-replace-python-and-r-as-a-data-science-tool-897efcf18b73 - https://www.analyticsindiamag.com/can-julia-be-the-new-python-heres-what-you-need-to-know/ -- 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 99623] Copy-paste freezes LibreOffice when CLCL is running (sysdtrans.dll!CMtaOleClipboard::getClipboard) - no steps
https://bugs.documentfoundation.org/show_bug.cgi?id=99623 --- Comment #23 from Buovjaga --- Well, we have Leo442, who was suffering from this last year. Would be interesting to hear his experience with 6.2.4. -- 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 124590] DPI of exported PNG images is never what I set it to
https://bugs.documentfoundation.org/show_bug.cgi?id=124590 QA Administrators changed: What|Removed |Added Whiteboard|QA:needsComment | -- 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 125407] Special character dialog doesn't work anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=125407 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- 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 125416] LibreOffice Impress embed video broken outside slide
https://bugs.documentfoundation.org/show_bug.cgi?id=125416 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- 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 124590] DPI of exported PNG images is never what I set it to
https://bugs.documentfoundation.org/show_bug.cgi?id=124590 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125433] Is there a shortkey to use "Always correct to"? It would saved have millions of hours.
https://bugs.documentfoundation.org/show_bug.cgi?id=125433 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- 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 125690] Sort not functional in Base Reports defined with old report designer
https://bugs.documentfoundation.org/show_bug.cgi?id=125690 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125435] LibreOffice PDF export regression -- edit file properties before saving/exporting doesn't work correctly and the PDF isn't opened automatically after export
https://bugs.documentfoundation.org/show_bug.cgi?id=125435 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- 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 124590] DPI of exported PNG images is never what I set it to
https://bugs.documentfoundation.org/show_bug.cgi?id=124590 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- 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 125699] No menu item shortcut keys shown in LO 6.2.4.2
https://bugs.documentfoundation.org/show_bug.cgi?id=125699 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- 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 125699] No menu item shortcut keys shown in LO 6.2.4.2
https://bugs.documentfoundation.org/show_bug.cgi?id=125699 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- 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 115251] LibreOffice draw hangs with 100% CPU after opening a pdf file
https://bugs.documentfoundation.org/show_bug.cgi?id=115251 --- Comment #7 from QA Administrators --- Dear Dmitry Yakimov, 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 114257] DRAW: Bad "Convert - To Curve" some arabic letters from the Text Box
https://bugs.documentfoundation.org/show_bug.cgi?id=114257 --- Comment #15 from QA Administrators --- Dear Kamil Landa, 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 108152] Diacritic positioning at beginning of paragraph not working with Graphite font
https://bugs.documentfoundation.org/show_bug.cgi?id=108152 --- Comment #11 from QA Administrators --- Dear Floater, 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 104892] Adding a bunch of very small images (jpg/png) will cause a high CPU load
https://bugs.documentfoundation.org/show_bug.cgi?id=104892 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 125690] Sort not functional in Base Reports defined with old report designer
https://bugs.documentfoundation.org/show_bug.cgi?id=125690 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113791] Slow scrolling with multiple animated gifs
https://bugs.documentfoundation.org/show_bug.cgi?id=113791 --- Comment #7 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 114813] Calc always inserts a space between v and o
https://bugs.documentfoundation.org/show_bug.cgi?id=114813 --- Comment #9 from QA Administrators --- Dear gghbonline, 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 37864] EDITING Calc Input bar error looses last character of pasted content
https://bugs.documentfoundation.org/show_bug.cgi?id=37864 --- Comment #16 from QA Administrators --- Dear Christopher M. Penalver, 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 91628] BASE: Multiselection Option in Form List Control Broken or Disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=91628 --- Comment #11 from QA Administrators --- Dear Doug, 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 117173] Search Dialog does not provide search results to Assistive Technology tools at 5.2 and later, results are recorded to GUI without accessible event as text in SetSearchL
https://bugs.documentfoundation.org/show_bug.cgi?id=117173 --- Comment #10 from QA Administrators --- Dear zahra, 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 52060] LibreOffice Calc does not validate xml and does not notify when fixing broken xml structure.
https://bugs.documentfoundation.org/show_bug.cgi?id=52060 --- Comment #7 from QA Administrators --- Dear Johnny Baloney, 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 80345] HTML Document: default table styles vertical borders not rendered visibly
https://bugs.documentfoundation.org/show_bug.cgi?id=80345 --- Comment #11 from QA Administrators --- Dear Kevin Suo, 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 98130] after upgrade from LO 4.4.7.2 to 5.0.5.2, clicking on checkboxes in a Base grid table form is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=98130 --- Comment #9 from QA Administrators --- Dear jnplg, 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 116519] FILEOPEN DOC: Word Document not correct displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=116519 --- Comment #16 from QA Administrators --- Dear Michael Velten, 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 104111] FILEOPEN RTF: Three red dots appear if a textbox is placed in a drawing canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=104111 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 38003] Calc doesn't print the content of a cell until you go out this cell
https://bugs.documentfoundation.org/show_bug.cgi?id=38003 --- Comment #17 from QA Administrators --- Dear r.aviolat, 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 104771] Graphics unit is not displayed correctly in the converted file.
https://bugs.documentfoundation.org/show_bug.cgi?id=104771 --- Comment #12 from QA Administrators --- Dear lex, 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 117148] FIREBIRD allows no edit for table with unique index, but no primary key, contrary to message
https://bugs.documentfoundation.org/show_bug.cgi?id=117148 --- Comment #4 from QA Administrators --- Dear Gerhard Weydt, 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 107168] High use of CPU when clone formatting more than once
https://bugs.documentfoundation.org/show_bug.cgi?id=107168 --- Comment #6 from QA Administrators --- Dear Martin M., 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 114769] Relative URL lost after Save as HTML (Export as HTML works)
https://bugs.documentfoundation.org/show_bug.cgi?id=114769 --- Comment #8 from QA Administrators --- Dear hans.van.buitenen, 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 95555] FILEOPEN RTF Frames overlap in document created by Oracle Reports
https://bugs.documentfoundation.org/show_bug.cgi?id=9 --- Comment #14 from QA Administrators --- Dear Dženan Zukić, 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 116361] Subscript causes additional vertical border to be added when setting borders through character formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=116361 --- Comment #6 from QA Administrators --- Dear Santi, 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 100419] Can't scroll to the last page in print preview, if in single page preview
https://bugs.documentfoundation.org/show_bug.cgi?id=100419 --- Comment #21 from QA Administrators --- Dear kolAflash, 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 117253] FIREBIRD: Migration: Migration routine does not import HSQL TEXT TABLES.
https://bugs.documentfoundation.org/show_bug.cgi?id=117253 --- Comment #6 from QA Administrators --- Dear Drew Jensen, 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 107776] Saving and opening document looses graphics positions
https://bugs.documentfoundation.org/show_bug.cgi?id=107776 --- Comment #6 from QA Administrators --- Dear Dave Nadler, 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 58440] EDITING: moving columns/rows with overwrites instead of ousting
https://bugs.documentfoundation.org/show_bug.cgi?id=58440 --- Comment #39 from QA Administrators --- Dear Martin Peter, 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 115654] EDITING: Copied column labels reference wrong cell until file is reloaded, Part 2
https://bugs.documentfoundation.org/show_bug.cgi?id=115654 --- Comment #3 from QA Administrators --- Dear Gilward Kukel, 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 105580] Redraw problems when using fonts with long underlengths (see comment 6)
https://bugs.documentfoundation.org/show_bug.cgi?id=105580 --- Comment #16 from QA Administrators --- Dear Patrick Schönbach, 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 125727] Bad line rendering of Text Box & Frame & Line
https://bugs.documentfoundation.org/show_bug.cgi?id=125727 --- Comment #1 from Menno Cornelßen --- Created attachment 151950 --> https://bugs.documentfoundation.org/attachment.cgi?id=151950=edit Text Box & Frame & Shape/Line – All with line width 1 mm -- 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 125727] New: Bad line rendering of Text Box & Frame & Line
https://bugs.documentfoundation.org/show_bug.cgi?id=125727 Bug ID: 125727 Summary: Bad line rendering of Text Box & Frame & Line Product: LibreOffice Version: 6.3.0.0.beta1+ Hardware: x86-64 (AMD64) OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: menno.cornels...@mailbox.org Description: It's impossible draw a Text Box or Frame or Line with a border or line width of eg. 1 mm. The lines are rendered by far too wide. When scrolling the shapes are often rendered incomplete. Both Writer and Draw show this fault. Steps to Reproduce: 1. Insert Text Box or Frame or Shape/Line 2. Set border/line width to 1 mm 3. The border/line will be rendered with a width of more than 1 cm Actual Results: The border/line will be rendered with a width of more than 1 cm Expected Results: The border/line should be rendered with a width of 1 mm Reproducible: Always User Profile Reset: No Additional Info: -- 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 99623] Copy-paste freezes LibreOffice when CLCL is running (sysdtrans.dll!CMtaOleClipboard::getClipboard) - no steps
https://bugs.documentfoundation.org/show_bug.cgi?id=99623 --- Comment #22 from Konstantin Vlasov --- Sorry again for having disappeared. Too many things to do, too little time to do them... :-( I installed LO version 6.2.4.2 x64 shortly after your request, and since then I was working without prior exiting CLCL (as I was normally doing since I've noticed the bug). Unfortunately, it's not that often that I need to use LO, so the statistics is not plenty. Still, I can already tell that there is, if not a complete fix, then at least significant improvement. Out of 4 or 5 work sessions I've had, only once LO did freeze, but I don't know if it was the version 6.2.4 or not. Unfortunately my head was completely filled with the task at hand, so with a curse and barely any other thought I just quickly killed both LO and CLCL, restarted LO and continued my work. It was only much later that I remembered about the incident, and banged my head for not recording the event. Now I don't even remember which LO version was installed on that computer at that moment. I did update LO to the version 6.2.4 there, but somehow I completely forgot if the freeze happened before or after this update. Sorry about that, it would be very useful information. For now, I will keep watch on this problem and not forget to take a dump if it's reproduced. Is it OK to keep the bug open for a while, while I continue experimenting? If in a few weeks I don't reproduce the freeze I'll gladly call this fixed. As for checking for regression... I'll try to find time for it, but I cannot promise. -- 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 125726] New: Firebird: Migration Assistant: Add URL on Request Dialog pointing to wiki page with information on how to perform migration
https://bugs.documentfoundation.org/show_bug.cgi?id=125726 Bug ID: 125726 Summary: Firebird: Migration Assistant: Add URL on Request Dialog pointing to wiki page with information on how to perform migration Product: LibreOffice Version: 6.3.0.0.beta1+ Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: drewjensen.in...@gmail.com This enhancement request is to add, in the dialog which pops up when an HSQL connection is created, a URLpointing to a TDF wiki page that covers: What is happening? HSQL is going away Instructions on how to migrate their data out of the HSQL sdbc Base file. The migration could be using the Migration Assistant. It could be to move their data to an external database. There should be instructions on how to migrate to an Firebird sdbc file without the migration assistant as well as with it. The wiki page should be setup for native language translations. -- 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 124590] DPI of exported PNG images is never what I set it to
https://bugs.documentfoundation.org/show_bug.cgi?id=124590 --- Comment #2 from Francis --- Created attachment 151949 --> https://bugs.documentfoundation.org/attachment.cgi?id=151949=edit Sample image I exported at 600 DPI (2.5 x 3.5 Inches) -- 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 125404] Request for new sinitic languages
https://bugs.documentfoundation.org/show_bug.cgi?id=125404 --- Comment #7 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/c4f9b1cae7e9400b9aa4bc085ee39371c3b67485%5E%21 Related: tdf#125404 alias cmn-CN to zh-CN, cmn-TW to zh-TW It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125404] Request for new sinitic languages
https://bugs.documentfoundation.org/show_bug.cgi?id=125404 Commit Notification changed: What|Removed |Added Whiteboard||target:6.4.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 125560] FILEOPEN PPTX: text transformation "Deflate" is wrongly imported as "Inflate"
https://bugs.documentfoundation.org/show_bug.cgi?id=125560 --- Comment #2 from Regina Henschel --- Created attachment 151948 --> https://bugs.documentfoundation.org/attachment.cgi?id=151948=edit shape type textInflateTop with image The transformation "textInflateTop" is wrongly mapped too. -- 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 125705] Impossible to edit any TextField (except URL) inside a spreadsheet cell by user code.
https://bugs.documentfoundation.org/show_bug.cgi?id=125705 --- Comment #1 from Wolfgang Jäger --- (Just a guess?) The DateTime TextField in a Calc cell I tried to edit claims to support the service "com.sun.star.text.textfield.DateTime". The service reference https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1text_1_1textfield_1_1DateTime.html, however, lists a Public Attribiute DataTimeValue of type "com.sun.star.util.DateTime", while the mentioned inspected textfield in Calc has not an attribute of that name, but one named DateTime which also is a structure of type "com.sun.star.util.DateTime". There is also a service "com.sun.star.presentation.textfield.DateTime" which is not marked Published, but for which the API reference refers to the same "DateTime.idl". Might there be an internal mixup? -- 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 122652] [META] Memory problems in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=122652 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||125687 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125687 [Bug 125687] Extreme memory usage opening/saving a large ODS with tracking changed enabled -- 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 125687] Extreme memory usage opening/saving a large ODS with tracking changed enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=125687 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||122652 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122652 [Bug 122652] [META] Memory problems in LibreOffice -- 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 125674] [META] Document Comparison bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=125674 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||125689 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125689 [Bug 125689] Comparing a large ODS (with an identical file) is extremely slow -- 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 125689] Comparing a large ODS (with an identical file) is extremely slow
https://bugs.documentfoundation.org/show_bug.cgi?id=125689 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||125674 Keywords||perf Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125674 [Bug 125674] [META] Document Comparison bugs and enhancements -- 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 125716] Libre Office WORD does not do Print Screen or Alt Prt any more
https://bugs.documentfoundation.org/show_bug.cgi?id=125716 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- don't repro in Version: 6.4.0.0.alpha0+ (x64) Build ID: c30ea50dd2b1c557dfbefc1a4c660fbf2402a604 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-06-05_00:23:26 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded try enable View->Image and Charts -- 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 125723] Check for updates is an empty dialog box (and all menu's are empty afterwards)
https://bugs.documentfoundation.org/show_bug.cgi?id=125723 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru Keywords||possibleRegression --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- don't repro in Version: 6.4.0.0.alpha0+ (x64) Build ID: c30ea50dd2b1c557dfbefc1a4c660fbf2402a604 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-06-05_00:23:26 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded win 7 problem? -- 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 125725] Fonctionnalité "Renvoi"
https://bugs.documentfoundation.org/show_bug.cgi?id=125725 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru, ||so...@libreoffice.org --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Sophie, please help us with translate it to English -- 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 124755] Crash - Hsqldb ODB file crashes office on opening from StartCenter
https://bugs.documentfoundation.org/show_bug.cgi?id=124755 --- Comment #16 from Scott --- (In reply to Alex Thurgood from comment #14) > @Scott : > > - which theme are you using on Mint ? > - which desktop ? Alex, I am using Mint 19.1 Cinnamon 4.0.10. My desktop theme is as follows: Window Borders: Mint-Y-Dark Icons: Mint-X-Teal Controls: Mint-Y-Dark-Teal Mouse Pointer: DMZ-Black Desktop: Mint-Y-Dark-Teal Please advise if you think I should restore the original themes/use different themes/or even just be more consistent across the board with whatever theme I choose. Thanks. Scott -- 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 125449] Changing percent gradient or color changes chart wall gradient color to black and white
https://bugs.documentfoundation.org/show_bug.cgi?id=125449 --- Comment #7 from Xisco Faulí --- OTOH, if the mentioned line is deleted the gradient is saved after RT in the chart. This is all a mystery to me... -- 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 124755] Crash - Hsqldb ODB file crashes office on opening from StartCenter
https://bugs.documentfoundation.org/show_bug.cgi?id=124755 Scott changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #15 from Scott --- (In reply to Xisco Faulí from comment #13) > Hello Scott, > LibreOffice 6.1.6 as been announced as final this week. > Could you please download it from > https://www.libreoffice.org/download/libreoffice-fresh/ and retest this bug ? > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the bug is still present in the latest version. First, I apologize for not getting back to you in a timely fashion. Second, I did install 6.1.6 as instructed and the crash continues. Lastly, last night I just installed 6.2.4, which I love, still crashes. Specifically, the crash happens in the "New Relationship" creation dialog when invoking the right drop-down box to change tables. I would love to get this resolved and I totally appreciate all of the effort being 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 125449] Changing percent gradient or color changes chart wall gradient color to black and white
https://bugs.documentfoundation.org/show_bug.cgi?id=125449 --- Comment #6 from Xisco Faulí --- If I remove the line 'aString = "gradient";' then it works, however, if we create a gradient in impress and save it, it will be gone after RT -- 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 125725] New: Fonctionnalité "Renvoi"
https://bugs.documentfoundation.org/show_bug.cgi?id=125725 Bug ID: 125725 Summary: Fonctionnalité "Renvoi" Product: LibreOffice Version: 6.1.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sonny...@hotmail.fr Description: La fonctionnalité permettant de renvoyer automatiquement à un numéro d'illustration semble ne pas fonctionner correctement. Steps to Reproduce: Pour effectuer le renvoi, j'effectue: 1. Insertion - Renvoi.. 2. Dans l'onglet "Renvois", je sélectionne le type "Illustration" 3. Dans la colonne "Sélection", je sélectionne l'illustration voulu c'est à dire l'illustration 1 Actual Results: j'obtiens le numéro 3 Expected Results: le numéro 1 est attendu Reproducible: Always User Profile Reset: No Additional Info: -- 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 125724] New: FORMATTING issue for multi-segment connectors when saving as .pptx
https://bugs.documentfoundation.org/show_bug.cgi?id=125724 Bug ID: 125724 Summary: FORMATTING issue for multi-segment connectors when saving as .pptx Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: andr...@chaeron.com Created attachment 151947 --> https://bugs.documentfoundation.org/attachment.cgi?id=151947=edit Zip file with screenshots of problem and sample Impress files. When using multi-segment connectors between boxes, saving as .odp works fine. If I save as .pptx then re-open the .pptx the lines are not drawn correctly, with the vertices of the connectors moving around from where they should be. Happening in latest stable 6.2.4.2 version of LO. Been happening for quite some time now. -- 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 105799] Undoing applied table style (aka autoformat) doesnt return table text formatting back to original
https://bugs.documentfoundation.org/show_bug.cgi?id=105799 Telesto changed: What|Removed |Added CC||rayk...@gmail.com --- Comment #10 from Telesto --- @Jim: I thought you might be interested in this issue -- 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 105799] Undoing applied table style (aka autoformat) doesnt return table text formatting back to original
https://bugs.documentfoundation.org/show_bug.cgi?id=105799 --- Comment #9 from Telesto --- I still repro Version: 6.4.0.0.alpha0+ (x86) Build ID: c30ea50dd2b1c557dfbefc1a4c660fbf2402a604 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-06-04_22:59:40 Locale: it-IT (nl_NL); UI-Language: en-US Calc: threaded -- 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 125449] Changing percent gradient or color changes chart wall gradient color to black and white
https://bugs.documentfoundation.org/show_bug.cgi?id=125449 Xisco Faulí changed: What|Removed |Added Keywords|regression | --- Comment #5 from Xisco Faulí --- Actually this is not a regression, before ff1f83dd08b7b0169301ffe0a53499a27af613b9, the values selected in the area dialog weren't saved... -- 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 125723] New: Check for updates is an empty dialog box (and all menu's are empty afterwards)
https://bugs.documentfoundation.org/show_bug.cgi?id=125723 Bug ID: 125723 Summary: Check for updates is an empty dialog box (and all menu's are empty afterwards) Product: LibreOffice Version: 6.4.0.0.alpha0+ Master Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Check for updates is an empty dialog box (and all menu's are empty afterwards) Steps to Reproduce: 1. Launch LibreOffice 2. Help -> Check for updates -> Empty box 3. Close it & expand a menu like file -> empty list Actual Results: Check for updates is an empty dialog Expected Results: Some text & and not affecting everything else Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.0.0.alpha0+ (x86) Build ID: c30ea50dd2b1c557dfbefc1a4c660fbf2402a604 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-06-04_22:59:40 Locale: it-IT (nl_NL); UI-Language: en-US Calc: threaded -- 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 125383] Dialog theming/UX - scaling of tunneled dialog may lead to missing application menu
https://bugs.documentfoundation.org/show_bug.cgi?id=125383
--- Comment #8 from Tor Lillqvist ---
I suspect it might be the call
> $('#' + strId).parent().css({display: 'none'});
in loleaflet/src/control/Control.LokDialog.js that causes the menubar and
toolbar to be hidden, because I think that when I had commented out that, they
did not seem to disappear whatever I did. But playing with this code is not
100% repeatable all the time, so it might be just luck, and it is just a guess.
Anyway, I don't understand the code at all, so it would be much better if
somebody who actually understands it could give some input...
--
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 70234] FILESAVE: DOC/DOCX - Track change of fields not saved correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=70234 --- Comment #28 from Commit Notification --- László Németh committed a patch related to this issue. It has been pushed to "libreoffice-6-3": https://git.libreoffice.org/core/+/7dc4f5d686f7834702ff133b4e75f29ffa6b5ec3%5E%21 tdf#70234 DOCX export: fix only expanded fields It will be available in 6.3.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125062] Export as PNG with transparency changes shape of objects radically
https://bugs.documentfoundation.org/show_bug.cgi?id=125062 --- Comment #11 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "libreoffice-6-3": https://git.libreoffice.org/core/+/95ffc97e9dc1c7ba2f13f6b46e495608f70bbe96%5E%21 tdf#125062: distort hairline borders only if selection is used It will be available in 6.3.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125062] Export as PNG with transparency changes shape of objects radically
https://bugs.documentfoundation.org/show_bug.cgi?id=125062 Commit Notification changed: What|Removed |Added Whiteboard|target:6.4.0|target:6.4.0 target:6.3.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 125711] Comments (permanently) deleted, with record track changes enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=125711 --- Comment #6 from Dieter Praas --- (In reply to Telesto from comment #5) > Where can I see the number of comments Navigator => Tooltip if you click on "comments" -- 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 125722] Some form items will disappear after cut, but won't be pasted
https://bugs.documentfoundation.org/show_bug.cgi?id=125722 --- Comment #1 from Telesto --- Created attachment 151946 --> https://bugs.documentfoundation.org/attachment.cgi?id=151946=edit Example file -- 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 125722] New: Some form items will disappear after cut, but won't be pasted
https://bugs.documentfoundation.org/show_bug.cgi?id=125722 Bug ID: 125722 Summary: Some form items will disappear after cut, but won't be pasted Product: LibreOffice Version: 6.4.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Some form items will disappear after cut, but won't be pasted Steps to Reproduce: 1. Open the attached file 2. Press CTRL+A & CTRL+X 3. CTRL+N & CTRL+V Actual Results: Label field & Option button gone Expected Results: Label field & option button should be pasted too Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.0.0.alpha0+ (x86) Build ID: 93477d1a963e38e3319013e43835a8ffef200972 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-06-02_10:16:52 Locale: it-IT (nl_NL); UI-Language: en-US Calc: threaded -- 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 125711] Comments (permanently) deleted, with record track changes enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=125711 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression --- Comment #5 from Telesto --- No repro with Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL @Dieter Where can I see the number of comments -- 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 125609] radiobutton receives item status changed event after listbox value selection
https://bugs.documentfoundation.org/show_bug.cgi?id=125609 Justin L changed: What|Removed |Added Whiteboard||Request:WindowsTester -- 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 125721] New: With Flatpak version of LibreOffice, opening the Options window takes a long time
https://bugs.documentfoundation.org/show_bug.cgi?id=125721 Bug ID: 125721 Summary: With Flatpak version of LibreOffice, opening the Options window takes a long time Product: LibreOffice Version: 6.2.4.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: anti-str...@laposte.net Hi, I'm using the LibreOffice flatpak version (6.2.4.2) from flathub Opening the Options window (Tools > Options) takes a long time : much more than the deb package (version 6.1.5) I used to have Thanks -- 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 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Dieter Praas changed: What|Removed |Added Depends on||125711 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125711 [Bug 125711] Comments (permanently) deleted, with record track changes enabled -- 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 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Dieter Praas changed: What|Removed |Added Depends on||125711 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125711 [Bug 125711] Comments (permanently) deleted, with record track changes enabled -- 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 125711] Comments (permanently) deleted, with record track changes enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=125711 Dieter Praas changed: What|Removed |Added Version|6.4.0.0.alpha0+ Master |6.3.0.0.beta1+ Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Blocks||106179, 83946 CC||dgp-m...@gmx.de --- Comment #4 from Dieter Praas --- I confirm it with Version: 6.3.0.0.beta1 (x64) Build ID: a187af327633f5f00363be5131bd21a13e0f1a7b CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (de_DE); UI-Language: en-GB Calc: threaded number of comments in original document: 1465 number of comments affected by track changes after delete all: 370 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83946 [Bug 83946] [META] Tracking changes issues https://bugs.documentfoundation.org/show_bug.cgi?id=106179 [Bug 106179] [META] Writer comment bugs and enhancements -- 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 125677] Radio button selection changed when tabbing into the group.
https://bugs.documentfoundation.org/show_bug.cgi?id=125677 Justin L changed: What|Removed |Added Whiteboard||Request:WindowsTester -- 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 125720] Calc: current cell indicator is not following the focused cell (in a particular Form configuration document)
https://bugs.documentfoundation.org/show_bug.cgi?id=125720 Justin L changed: What|Removed |Added Whiteboard||Request:WindowsTester -- 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 114229] Basic -timeserial function minutes outside the range 0-59
https://bugs.documentfoundation.org/show_bug.cgi?id=114229 --- Comment #11 from Eike Rathke --- Seems the implementation is the linked VBA reference "each TimeSerial argument should be in the normal range for the unit; that is, 0–23 for hours and 0–59 for minutes and seconds" part, not considering the following any 16-bit integer is possible for each argument. The "if the time specified by the three arguments causes the date to fall outside the acceptable range of dates, an error occurs." sounds as if more than 24 hours are possible; Excel doesn't handle negative dates so a resulting value of <0 would not be possible, but how about VBA? And what about values >=0 24 hours? @Mike, can you check? Our own help says the individual arguments can have any numeric value, but also restricts the result to be between 0 and 0.99 (which in this case is between 00:00:00 and 23:59:59). This actually make most sense to me and IMHO implementation should follow that. -- 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 125715] Crash in: ld-2.22.so while starting with SAL_USE_VCLPLUGIN=gtk3_kde5 soffice
https://bugs.documentfoundation.org/show_bug.cgi?id=125715 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #7 from Michael Weghorn --- (In reply to opensuse.lietuviu.kalba from comment #0) > I use openSUSE Leap 42.3 Linux, KDE 5.8.7, KF 5.32, Qt 5.6.2. Hm, that's a very old Qt version and according to [1], openSUSE Leap 42.3 is close to it EOL. Can you try with a newer version of openSUSE Leap? [1] https://en.wikipedia.org/wiki/OpenSUSE#Releases -- 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 125720] Calc: current cell indicator is not following the focused cell (in a particular Form configuration document)
https://bugs.documentfoundation.org/show_bug.cgi?id=125720 Justin L changed: What|Removed |Added CC||armin.le.gr...@me.com, ||jl...@mail.com 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 125720] New: Calc: current cell indicator is not following the focused cell (in a particular Form configuration document)
https://bugs.documentfoundation.org/show_bug.cgi?id=125720 Bug ID: 125720 Summary: Calc: current cell indicator is not following the focused cell (in a particular Form configuration document) Product: LibreOffice Version: 6.3.0.0.alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com Starting in LO 6.3, the current cell indicator is not following the selected cell in this particular document. I was able to create a clean-room copy of this (once). Using radio buttons MIGHT be a common theme. I first created some other kind of form control (a checkbox for example), and then I created TWO radio buttons. After that, the cell selection seems to disappear. (For form design, see View->Toolbars->Form Controls). Unfortunately I can't reproduce this on demand, but the example document always shows the problem at least. Expanding a selection by dragging on the selection point also yields interesting results... Row 4 seems to be special somehow - notice A4, B4, and C4. Bisected to this change in LO 6.3: author Armin Le Grand 2018-11-27 11:33:10 +0100 commit d464d505fbf6e53a38afdd3661d320fac8c760d6 Refactor calc non-linear ViewToDevice transform Steps to reproduce using attachment 151805 [details] (from bug 125609) 1.) Notice that E5 seems to be the selected cell. 2.) Select a different cell. The highlighting on E5 remains, and very little indicates which cell actually has the focus. Note: macros can remain disabled. There is no need to allow the macros to run in order to reproduce the problem. -- 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 125719] RTF: bold text property mismatch
https://bugs.documentfoundation.org/show_bug.cgi?id=125719 Serge Krot (CIB) changed: What|Removed |Added Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |serge.k...@cib.de |desktop.org | Status|UNCONFIRMED |ASSIGNED -- 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 125719] RTF: bold text property mismatch
https://bugs.documentfoundation.org/show_bug.cgi?id=125719 --- Comment #1 from Serge Krot (CIB) --- Created attachment 151945 --> https://bugs.documentfoundation.org/attachment.cgi?id=151945=edit Second test case -- 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 125719] New: RTF: bold text property mismatch
https://bugs.documentfoundation.org/show_bug.cgi?id=125719 Bug ID: 125719 Summary: RTF: bold text property mismatch Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: serge.k...@cib.de Created attachment 151944 --> https://bugs.documentfoundation.org/attachment.cgi?id=151944=edit First test case Attached documents are loaded and exported with wrong bold properties. -- 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 125715] Crash in: ld-2.22.so while starting with SAL_USE_VCLPLUGIN=gtk3_kde5 soffice
https://bugs.documentfoundation.org/show_bug.cgi?id=125715 --- Comment #6 from opensuse.lietuviu.ka...@gmail.com --- In comment you could see: "I can reproduce with <...> VCL: gtk3; " , but actually it is pasted from case with > SAL_USE_VCLPLUGIN=gtk3 /opt/libreofficedev6.3/program/soffice that is only working way (to start and to grab version information). -- 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 125690] Sort not functional in Base Reports defined with old report designer
https://bugs.documentfoundation.org/show_bug.cgi?id=125690 --- Comment #4 from pebro --- Yes, this Report was made in the old OpenOffice program. I checked, the report has been done correctly again (sorts). It is a pity that LO is not 100% compatible with OO. -- 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 125715] Crash in: ld-2.22.so while starting with SAL_USE_VCLPLUGIN=gtk3_kde5 soffice
https://bugs.documentfoundation.org/show_bug.cgi?id=125715 --- Comment #5 from opensuse.lietuviu.ka...@gmail.com --- I can reproduce with Version: 6.3.0.0.alpha1+ Build ID: 77ae0abe21f672cf4b7d2e069f1d40d20edc49a7 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-31_15:33:33 Locale: lt-LT (lt_LT.UTF-8); UI-Language: en-US Calc: threaded Indeed, all these commands fails in master build: > SAL_USE_VCLPLUGIN=gtk3_kde5 /opt/libreofficedev6.3/program/soffice > SAL_USE_VCLPLUGIN=kde5 /opt/libreofficedev6.3/program/soffice > SAL_USE_VCLPLUGIN=qt5 /opt/libreofficedev6.3/program/soffice > SAL_USE_VCLPLUGIN=kde4 /opt/libreofficedev6.3/program/soffice The only way to start LibreOffice is: > SAL_USE_VCLPLUGIN=gtk3 /opt/libreofficedev6.3/program/soffice http://crashreport.libreoffice.org/stats/crash_details/e42da55d-8dde-4a9c-8a96-75a39d655724 (it indicates that this is for 6.2.4.2 version, but actually is from master version – I manually edited ~/.config/libreofficedev/4/crash/dump.ini to be able to submit crash raport – otherwise it don't show link/crash ID) -- 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 125717] Scrolling up stuck with cursor position during two-fingers scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=125717 --- Comment #1 from Daniel T. --- Screencast: http://versiforma.net/screencast20190605174233.mp4 -- 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 114263] [LOCALHELP] More BASIC functions to document in Help pages
https://bugs.documentfoundation.org/show_bug.cgi?id=114263 --- Comment #16 from LibreOfficiant --- Print statement help page is unclear, its related Spc statement in unprecise while its related Tab Statement is missing. MS-VBA Print, Spc, Tab help pages aren't clearer either as for 'how to use Print statement' variations. IBM LotusScript online help pages for these 3 statements are prettier. Some adaptation is needed in order to improve LO respective pages. Links: Online help at https://www.ibm.com/support/knowledgecenter/en/SSVRGU_9.0.1/basic/LSAZ_CHAPTER_7_STATEMENTS_BUILTIN_FUNCTIONS_SUBS_DATA_TYPES_AND_DIRECTIVES.html Acrobat copy at http://www-12.lotus.com/ldd/doc/uafiles.nsf/docs/ls70/$file/lscript.pdf May be worth mentioning in the wiki as available in japanese language too -- 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 125676] Cosinus wrong value
https://bugs.documentfoundation.org/show_bug.cgi?id=125676 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- 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
