[Libreoffice-bugs] [Bug 101179] Writer/Web: View > HTML Source mode toggles are awkward
https://bugs.documentfoundation.org/show_bug.cgi?id=101179 Heiko Tietze changed: What|Removed |Added CC||skyh...@shaw.ca --- Comment #7 from Heiko Tietze --- *** Bug 145264 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145264] menu “View - HTML Source” radio button control inappropriately applied as a toggle switch
https://bugs.documentfoundation.org/show_bug.cgi?id=145264 Heiko Tietze changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Heiko Tietze --- Absolutely true, and reported a few times. But I wonder why anyone would edit HTML with LibreOffice. Isn't it better to remove all this functionality? But better discuss this at the duplicate. *** This bug has been marked as a duplicate of bug 101179 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101179] Writer/Web: View > HTML Source mode toggles are awkward
https://bugs.documentfoundation.org/show_bug.cgi?id=101179 Heiko Tietze changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #6 from Heiko Tietze --- *** Bug 133204 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133204] UI: View > HTML-source works as a toggle function, but looks as an option button
https://bugs.documentfoundation.org/show_bug.cgi?id=133204 Heiko Tietze changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #3 from Heiko Tietze --- *** This bug has been marked as a duplicate of bug 101179 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60953] REPORTBUILDER: missing header and footer on first page when section "Detail" is set to Page-Break after Section
https://bugs.documentfoundation.org/show_bug.cgi?id=60953 --- Comment #24 from Robert Großkopf --- Created attachment 175870 --> https://bugs.documentfoundation.org/attachment.cgi?id=175870&action=edit It should look all the same: Pagebreak should have nothing to do with header and footer, Hi Julien, Changing the page break in Detail shouldn't change anything of the header and footer. So the bug is: On first page has to appear Page-Header on the top and Page-Footer on the button. And this won't happen if Detail is set to "page break after section". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141845] LibreOffice Vanilla / Collabora Productivity fails to open postgres connected ODB file using the postgres native connector
https://bugs.documentfoundation.org/show_bug.cgi?id=141845 --- Comment #9 from Alex Thurgood --- How can this be bibisected against Collabora's codebase/release ? With TDF Version: 7.2.1.2 / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded it still works just fine, the postgres SDBC connector is still there. So, the problem appears to lie specifically with the way Collabora builds their own release and the LO Vanilla release. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133200] ODF 1.3: in not displayed by Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=133200 --- Comment #3 from Lemke --- Nothing is better than tutoring that is the explanation instructors and gatekeepers stress their youngsters to be refined. You can click here https://bestwritingsclues.com/reviews/essayedge-review/ for more info as guidance is reasonable the best wealth that we can't see anyway it will help us in future when we will really need to get perpetual money inferable from our educational limits. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 Alex Thurgood changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #10 from Alex Thurgood --- Per comment 9, NOTOURBUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 55058] EMF+ List of EMF import bugs with examples
https://bugs.documentfoundation.org/show_bug.cgi?id=55058 --- Comment #64 from Buovjaga --- (In reply to Timur from comment #63) > Wrap-up would be useful, to know what's left here. Well, several open reports are still in "Depends on" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145268] how to remove QuickBooks Error 3371
https://bugs.documentfoundation.org/show_bug.cgi?id=145268 Acer nancy changed: What|Removed |Added URL||https://takeactionnyc.com/q ||uickbooks-error-3371/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145268] New: how to remove QuickBooks Error 3371
https://bugs.documentfoundation.org/show_bug.cgi?id=145268 Bug ID: 145268 Summary: how to remove QuickBooks Error 3371 Product: Impress Remote Version: 1.0.2 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: acernancy1...@gmail.com Description: 've worked in the accounting field for over a decade. I've also faced many QuickBooks issues in my job, and now that I've accumulated enough experience, I can assist you in overcoming difficulties like QuickBooks Error 15241. Steps to Reproduce: 1.CLOSE ALL THE RUNNING FILE 2.GO TO CONTROL PANEL, AND UNINSTALL THE SOFTWARE 3.RESTART THE SYSTEM & DOWNLOAD THE SOFTWARE AGAIN Actual Results: IT DOES WORK Expected Results: YES Reproducible: Always User Profile Reset: No Additional Info: https://takeactionnyc.com/quickbooks-error-3371/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35092] Inking functionality: Ink drawings / annotations with Stylus, Pen or Finger on Touchscreen or Tablet
https://bugs.documentfoundation.org/show_bug.cgi?id=35092 Jon Bright changed: What|Removed |Added URL||https://www.bookunitedairli ||nes.com/united-airlines-can ||cellation-policy/ --- Comment #128 from Jon Bright --- You can cancel your tickets inside 24 hours of the booking yet before 7 days of the planned takeoff. If it's not too much trouble, note that it does exclude the tickets booked through e-endorsement and gathering tickets. To know more about cancellation fee Visit us at united airlines cancellation fee. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108681] [META] Cell formatting/style dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108681 Bug 108681 depends on bug 60127, which changed state. Bug 60127 Summary: Allow Empty Rotation-Degrees-Pane https://bugs.documentfoundation.org/show_bug.cgi?id=60127 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60127] Allow Empty Rotation-Degrees-Pane
https://bugs.documentfoundation.org/show_bug.cgi?id=60127 Rainer Bielefeld Retired changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #9 from Rainer Bielefeld Retired --- I remember the problem. An it has gone, in step 5 from original report I now get an empty angle input line after some . WFM with Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded Might have been resolved in an more early version, I did not test. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141845] LibreOffice Vanilla / Collabora Productivity fails to open postgres connected ODB file using the postgres native connector
https://bugs.documentfoundation.org/show_bug.cgi?id=141845 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144972] very slow LibreOffice writer start
https://bugs.documentfoundation.org/show_bug.cgi?id=144972 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144985] Chart custom colors are not used in the legend
https://bugs.documentfoundation.org/show_bug.cgi?id=144985 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144983] Wrong umlaut behaviour in linux
https://bugs.documentfoundation.org/show_bug.cgi?id=144983 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144982] Export unicode in pdf-file using Ubuntu (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=144982 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144979] Function XSystemChildFactory::createSystemChild() hangs
https://bugs.documentfoundation.org/show_bug.cgi?id=144979 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144978] Decimal point - Should not be dependent of language
https://bugs.documentfoundation.org/show_bug.cgi?id=144978 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145179] The scope of auto-filter (Ctrl+Shift+L) is not limited to the rows which were selected
https://bugs.documentfoundation.org/show_bug.cgi?id=145179 --- 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] [Bug 145179] The scope of auto-filter (Ctrl+Shift+L) is not limited to the rows which were selected
https://bugs.documentfoundation.org/show_bug.cgi?id=145179 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141122] Firebird Field AUTOINCREMENT in a Base Table is not settable via the GUI nor via SQL
https://bugs.documentfoundation.org/show_bug.cgi?id=141122 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141122] Firebird Field AUTOINCREMENT in a Base Table is not settable via the GUI nor via SQL
https://bugs.documentfoundation.org/show_bug.cgi?id=141122 --- Comment #4 from QA Administrators --- Dear ramon6419, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136009] UI : toolbar float opens with wrong size
https://bugs.documentfoundation.org/show_bug.cgi?id=136009 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136009] UI : toolbar float opens with wrong size
https://bugs.documentfoundation.org/show_bug.cgi?id=136009 --- Comment #6 from QA Administrators --- Dear netjiro, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135877] Libreoffice Math PDF Export Problem(Windows and Linux version)
https://bugs.documentfoundation.org/show_bug.cgi?id=135877 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135877] Libreoffice Math PDF Export Problem(Windows and Linux version)
https://bugs.documentfoundation.org/show_bug.cgi?id=135877 --- Comment #7 from QA Administrators --- Dear Angelo81523, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135599] Table cell in impress doesn't grow with content at redo
https://bugs.documentfoundation.org/show_bug.cgi?id=135599 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135599] Table cell in impress doesn't grow with content at redo
https://bugs.documentfoundation.org/show_bug.cgi?id=135599 --- Comment #4 from QA Administrators --- Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135592] LO release 7.0.0.3 freezes after first call, on Windows 7 pro with "extended security updates"
https://bugs.documentfoundation.org/show_bug.cgi?id=135592 --- Comment #3 from QA Administrators --- Dear Olaf Langmack, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135592] LO release 7.0.0.3 freezes after first call, on Windows 7 pro with "extended security updates"
https://bugs.documentfoundation.org/show_bug.cgi?id=135592 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135123] LibreOffice 6.4.5 eliminated use of keyboard arrows to move around in Libreoffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=135123 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135123] LibreOffice 6.4.5 eliminated use of keyboard arrows to move around in Libreoffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=135123 --- Comment #9 from QA Administrators --- Dear Old Heart, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99752] FILEOPEN: Impress/Draw ODF open; style's parent style is lost for grandsons
https://bugs.documentfoundation.org/show_bug.cgi?id=99752 --- Comment #3 from QA Administrators --- Dear DaniM, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98561] Cannot handle elements pasted from a website
https://bugs.documentfoundation.org/show_bug.cgi?id=98561 --- Comment #3 from QA Administrators --- Dear bugcatcher1, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98053] Print preview closes the read-only infobar
https://bugs.documentfoundation.org/show_bug.cgi?id=98053 --- Comment #7 from QA Administrators --- Dear pavelz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94312] UI: Page pane renders hidden layers
https://bugs.documentfoundation.org/show_bug.cgi?id=94312 --- Comment #8 from QA Administrators --- Dear tmacalp, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83387] FORMATTING: Adjusting line color does not adjust icon color in preview
https://bugs.documentfoundation.org/show_bug.cgi?id=83387 --- Comment #7 from QA Administrators --- Dear Sebastian Werk, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81913] Navigating with arrow keys disables cell highlighting (in text and in spreadsheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=81913 --- Comment #6 from QA Administrators --- Dear fuer_kommentare, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68055] VIEWING: Selection frame is not destroyed when using paintbrush on frame
https://bugs.documentfoundation.org/show_bug.cgi?id=68055 --- Comment #7 from QA Administrators --- Dear freddi34, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64465] auto scrolling does not work in impress and Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=64465 --- Comment #7 from QA Administrators --- Dear ilikebigbugs, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62902] 'Show references in color' doesn't work across sheets, when the sheet name contains a space
https://bugs.documentfoundation.org/show_bug.cgi?id=62902 --- Comment #7 from QA Administrators --- Dear Jos, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60127] Allow Empty Rotation-Degrees-Pane
https://bugs.documentfoundation.org/show_bug.cgi?id=60127 --- Comment #8 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50301] RTL: DOC - Shapes, images and textboxes not positioned correctly in two column page
https://bugs.documentfoundation.org/show_bug.cgi?id=50301 --- Comment #15 from QA Administrators --- Dear A Sh, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47352] Unacceptable kerning of subscripts in Math formulas for italic style
https://bugs.documentfoundation.org/show_bug.cgi?id=47352 --- Comment #13 from QA Administrators --- Dear bellgardt, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 44954] delegate search to the database
https://bugs.documentfoundation.org/show_bug.cgi?id=44954 --- Comment #15 from QA Administrators --- Dear Lionel Elie Mamane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43848] selecting whole table with merged cells at certain position not possible with draging the mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=43848 --- Comment #18 from QA Administrators --- Dear dE, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113262] FILESAVE: PPTX: Link changed colour after RT
https://bugs.documentfoundation.org/show_bug.cgi?id=113262 --- Comment #7 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108720] Do not render previews of symbol fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=108720 --- Comment #11 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101142] Print preview picks the color from the document background option
https://bugs.documentfoundation.org/show_bug.cgi?id=101142 --- Comment #6 from QA Administrators --- Dear RGB, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145179] The scope of auto-filter (Ctrl+Shift+L) is not limited to the rows which were selected
https://bugs.documentfoundation.org/show_bug.cgi?id=145179 --- Comment #2 from 123dev...@gmail.com --- Created attachment 175869 --> https://bugs.documentfoundation.org/attachment.cgi?id=175869&action=edit Screenshot Please check the attached screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145267] New: Writer crashes when docking or undocking sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=145267 Bug ID: 145267 Summary: Writer crashes when docking or undocking sidebar Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: benr...@gmail.com Writer crashes instantly when docking or undocking the Sidebar or the Navigator by drag and drop. In the case of navigator only docking can be tested because docking is never successful due to crash. Undocking the sidebar by pressing Ctrl+Shift+F10 doesn't work. OS used: Win 10 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 panosmoisia...@pm.me changed: What|Removed |Added Summary|Writer crashes when |Writer crashes when |inserting equation |inserting formula object -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] New: Writer crashes when inserting equation
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 Bug ID: 145266 Summary: Writer crashes when inserting equation Product: LibreOffice Version: 7.2.1.2 release Hardware: x86-64 (AMD64) OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: panosmoisia...@pm.me Description: When in Writer, inserting an equation causes LibreOffice to crash (including other documents such as an impress presentation). This bug does not occur when inserting an equation into an impress presentation or drawing. I am also able to create formulas in Math with no problem. I tested and found this bug in 7.2.1.2 and 7.2.2.2 Steps to Reproduce: 1. In a Writer document, click Insert > Object > Formula Object. 2. Edit the formula in any way. 3. Click off the formula. Actual Results: LibreOffice will crash, closing all open documents. Expected Results: A formula should be inserted into the Writer document with no issue. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136770] QR code generator does not work correctly if the properties (URL/Text) are set using a macro
https://bugs.documentfoundation.org/show_bug.cgi?id=136770 Aron Budea changed: What|Removed |Added Status|RESOLVED|CLOSED CC||ba...@caesar.elte.hu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145265] New: add BIDI support to import pdf in Draw.
https://bugs.documentfoundation.org/show_bug.cgi?id=145265 Bug ID: 145265 Summary: add BIDI support to import pdf in Draw. Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: helpmep...@gmail.com Description: text in imported pdf to draw in hebrew is reversed. there is a thing called visual hebrew and logical Hebrew . a bidi library has a conversion for it. FILEOPEN PDF Steps to Reproduce: 1. open pdf file in draw with hebrew for example this one: http://bagrutbesafrut.co.il/59.pdf see text reversed 2. view it with something. and see text is ok Actual Results: the imported text is reversed. Expected Results: the text imported in logical order. Reproducible: Always User Profile Reset: No Additional Info: the export pdf is also visible reversed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145231] URL Recognition option not working
https://bugs.documentfoundation.org/show_bug.cgi?id=145231 --- Comment #5 from Ken C --- Response to Michael Warner 2021-10-21 12:57:01 UTC Sorry for the typo. I tried this with the same result: no linkification. https://a.co -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 --- Comment #9 from Herbert --- (In reply to Robert Großkopf from comment #8) > Have tested this on OpenSuSE 15.2 64bit rpm Linux. > Could execute the report of every database in the attachment with > > Version: 7.1.4.2 / LibreOffice Community > Build ID: 10(Build:2) > CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 > Locale: de-DE (de_DE.UTF-8); UI: de-DE > Calc: threaded > > and also with > Version: 7.2.2.2 / LibreOffice Community > Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 > CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) > Locale: de-DE (de_DE.UTF-8); UI: de-DE > Calc: threaded > > You have installed the version SuSE Tumblweed has created. Please test it > with a version directly from LO. I have installed many versions parallel as > a normal user - not as root - to test the behavior for bugs. > > File the bug to SuSE, because it seems to be a special behavior of the > version SuSE has build. Thanks Robert, I will file the bug to SuSE. This Version works fine: Version: 7.1.2.2 / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded and Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded works fine as well. I did installation with several version in /opt . All are usable - only the one from SuSErepo http://download.opensuse.org/tumbleweed or http://download.opensuse.org/update/tumbleweed/ has this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145264] menu “View - HTML Source” radio button control inappropriately applied as a toggle switch
https://bugs.documentfoundation.org/show_bug.cgi?id=145264 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Component|Writer |Writer Web OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139471] UI: LibreOffice main icon revamp
https://bugs.documentfoundation.org/show_bug.cgi?id=139471 V Stuart Foote changed: What|Removed |Added CC||varady.m...@gmail.com --- Comment #13 from V Stuart Foote --- *** Bug 145257 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145257] Add macOS Big Sur themed app icon
https://bugs.documentfoundation.org/show_bug.cgi?id=145257 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||vstuart.fo...@utsa.edu --- Comment #1 from V Stuart Foote --- *** This bug has been marked as a duplicate of bug 139471 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145049] copy / paste of numbered style numbers everything
https://bugs.documentfoundation.org/show_bug.cgi?id=145049 --- Comment #2 from goodgu...@zoho.com --- Created attachment 175868 --> https://bugs.documentfoundation.org/attachment.cgi?id=175868&action=edit test document this is an new, empty document, where i added 4 lines. header has a standard list behind it. 1. crtl-a, ctrl-x 2. ctrl-v -> i see all lines being numbered after the paste. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145245] A relative position other than zero of extrusion of custom shapes is wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=145245 Regina Henschel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145245] A relative position other than zero of extrusion of custom shapes is wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=145245 --- Comment #1 from Commit Notification --- Regina Henschel committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5ab21caf603ba0a1c95bbc94a29eebe3483d1599 tdf#145245 correct relative position of extrusion It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145245] A relative position other than zero of extrusion of custom shapes is wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=145245 Commit Notification changed: What|Removed |Added Whiteboard||target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141634] Allow entering a new subhead below a subhead that has content hidden beneath it.
https://bugs.documentfoundation.org/show_bug.cgi?id=141634 --- Comment #4 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/827c0f9766f148520aed7fe3abe2b138a157a6d3 tdf#141634 Special end of para split for folded outline node It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141634] Allow entering a new subhead below a subhead that has content hidden beneath it.
https://bugs.documentfoundation.org/show_bug.cgi?id=141634 Commit Notification changed: What|Removed |Added Whiteboard||target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145264] menu “View - HTML Source” radio button control inappropriately applied as a toggle switch
https://bugs.documentfoundation.org/show_bug.cgi?id=145264 skyh...@shaw.ca changed: What|Removed |Added Summary|menu “View - HTML Source” |menu “View - HTML Source” |control switch behaving as |radio button control |radio button; |inappropriately applied as |inappropriately applied |a toggle switch -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145264] New: menu “View - HTML Source” control switch behaving as radio button; inappropriately applied
https://bugs.documentfoundation.org/show_bug.cgi?id=145264 Bug ID: 145264 Summary: menu “View - HTML Source” control switch behaving as radio button; inappropriately applied Product: LibreOffice Version: 7.0.0.3 release Hardware: x86 (IA32) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: skyh...@shaw.ca Description: The “View - HTML Source” menu item is presented as a radio button when it actually toggles like a checkbox, while still exclusive. When selected it greys alternative radio buttons and but can be toggled to re-enable them. Toggling swaps function between editing and WYSIWIG. I believe this implementation is needlessly confusing and the concept should be handled as three radio buttons, pick one, options always present even if disabled. It isn't intuitive to toggle a radio button like a checkbox, and if modality is the goal all buttons should all be active while exclusive options. The view toggling effect behaves like a radio button with other radio buttons actually still in play, but only after toggling, the current means to the same end. The help file below should be considered part of a repair. Specifically, “or opening an existing one” doesn’t appear possible where “one” is referring to an HTML file. When opened, an existing file of any extension hides the “View - HTML Source” radio button. I believe any menu item should be present while disabled if not selectable, not hidden modality: https://help.libreoffice.org/7.0/en-US/text/shared/02/1909.html?&DbPAR=WRITER&System=UNIX To compare, note that the style menu works, while not how I wish it was handled, because radio buttons remain evident and give the user a visual affordance to understand what's happening, combining inputs with annunciators. Steps to Reproduce: 1. Select menu "File>New>HTML Document" 2. Select menu "View>HTML Source"; option missing without step #1 3. Save dialogue appears, new document returns to editing with !DOCTYPE boilerplate Actual Results: Selecting menu "View>HTML Source" will now toggle between code and HTML code and WYSIWIG views. Expected Results: Actual results notwithstanding, this maneuver should be implemented as three radio buttons for HTML/Web/Normal where HTML should remain but disabled if not available. I would never expect to toggle a radio button as the very nature of that control is to be mutually exclusive amongst alternative buttons. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Explanation condensed from my exasperated version, with more background, at: https://ask.libreoffice.org/t/is-a-view-menu-control-applied-inappropriately/69474 I took a very long time to figure out what was actually happening, combining the given interface with the the incorrect help file, before I accidentally toggled the radio button and all became clear. Also noted were the large percentage of help requests from users struggling to understand HTML formats within Writer. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145043] Footnotes & endnotes category in navigator causes exponential lag
https://bugs.documentfoundation.org/show_bug.cgi?id=145043 --- Comment #11 from Jim Raykowski --- Here is a patch that should help reduce lag: https://gerrit.libreoffice.org/c/core/+/124036 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60953] REPORTBUILDER: missing header and footer on first page when section "Detail" is set to Page-Break after Section
https://bugs.documentfoundation.org/show_bug.cgi?id=60953
Julien Nabet changed:
What|Removed |Added
CC||serval2...@yahoo.fr
--- Comment #23 from Julien Nabet ---
Created attachment 175867
--> https://bugs.documentfoundation.org/attachment.cgi?id=175867&action=edit
Result of a test
Robert:
I tried this patch:
diff --git
a/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java
b/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java
index d8e50d2d4991..6888da1d204b 100644
---
a/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java
+++
b/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java
@@ -979,6 +979,12 @@ public class TextRawReportTarget extends
OfficeDocumentReportTarget
performStyleProcessing(attrs);
}
+if (isSectionPagebreakAfter(attrs))
+{
+// force a pagebreak ..
+setPagebreakDefinition(new
PageBreakDefinition(isResetPageNumber()));
+}
+
final String namespace =
ReportTargetUtil.getNamespaceFromAttribute(attrs);
final String elementType =
ReportTargetUtil.getElemenTypeFromAttribute(attrs);
final AttributeList attrList = buildAttributeList(attrs);
I'm not sure what should be the result of After, could you tell me if the pdf
is ok or not?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145188] New line when typing á é í ó ú characters
https://bugs.documentfoundation.org/show_bug.cgi?id=145188 --- Comment #6 from Artur Correia --- Hello again Just installed LibreOffice 2.2.2 The problem persists After further testing I found out that the character inserting a new line is the ´ character, instead of the usual behaviour which would be waiting for a character (a, e i o u) to be inserted. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145263] File size randomly increases Dramatically
https://bugs.documentfoundation.org/show_bug.cgi?id=145263 Kurt changed: What|Removed |Added Version|7.2.2.2 release |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145263] New: File size randomly increases Dramatically
https://bugs.documentfoundation.org/show_bug.cgi?id=145263 Bug ID: 145263 Summary: File size randomly increases Dramatically Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: k...@revanchellc.com Description: When editing a form sometimes the file size of a form will jump from a few KB to a few MB. Something hidden is being embedded in the form. Tested with both Linux Mint UMA 20.2 and a completely separate Win 10 Pro 21H1 system. Started from scratch in both systems observed the same behavior in both. The file size of the Database can sometimes jump over 20 times by a simple edit of a form. Also form size will just increase in size over time when repeated editing/ saving of a form. Steps to Reproduce: 1.Repeatedly editing a Form and testing of a form before saving a form. 2. 3. Actual Results: File size dramatically increases Expected Results: little or none file size increase Reproducible: Sometimes User Profile Reset: Yes Additional Info: Links to two base files Both Files contain the same data, same forms one is 47 KB the other is 5 MB. Over a 100 times bigger for the same database. The added garbage/data is somehow contained in the form "frm_add_parts" in the larger DB file. https://drive.google.com/file/d/1sJxJSr2-bF7f8Eh8Vit0ithE6Zpf6d5n/view?usp=sharing https://drive.google.com/file/d/1ouEGfqz3Q2DudmqHYzQizhXXJUxyA3Oj/view?usp=sharing Someone reported this problem several years ago. Seems people didn't understand the error being described. I observed the same thing with and without crashes. https://ask.libreoffice.org/t/base-file-size-randomly-increases-dramatically/47543 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57308] Basic IDE: watching of variable not working if variable is returning value of function
https://bugs.documentfoundation.org/show_bug.cgi?id=57308 Andreas Heinisch changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |andreas.heini...@yahoo.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145262] New: UI: Context menu for table content with Index / Bibliography entry is missing commands
https://bugs.documentfoundation.org/show_bug.cgi?id=145262 Bug ID: 145262 Summary: UI: Context menu for table content with Index / Bibliography entry is missing commands Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoffice@phv.email Description: By default, the commands "Index Entry..." and "Bibliography Entry..." are missing from the context menu when right-clicking an item written inside a table. Steps to Reproduce: 1. Create a table in Writer. 2. Insert a text inside the table as "Index Entry" or "Bibliography Entry". 3. Do a right-click on the previous text to display the context menu. Actual Results: The context menu has no "Index Entry..." or "Bibliography Entry..." commands. Expected Results: The context menu should propose "Index Entry..." and "Bibliography Entry..." commands. Reproducible: Always User Profile Reset: Yes Additional Info: An easy workaround is, for the user, to customize the Table context menu, but I think that these commands may have been forgotten because the behaviour is inconsistent. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144065] add RTF \page control as an option for inserting page breaks in RTF documents
https://bugs.documentfoundation.org/show_bug.cgi?id=144065 --- Comment #2 from Tracey --- When I add a page break before or after a paragraph, LO puts a \pagebb(page break before paragraph) in both instances. Can LO be fixed to insert a \page(page break) after a paragraph? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 Robert Großkopf changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #8 from Robert Großkopf --- Have tested this on OpenSuSE 15.2 64bit rpm Linux. Could execute the report of every database in the attachment with Version: 7.1.4.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded and also with Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded You have installed the version SuSE Tumblweed has created. Please test it with a version directly from LO. I have installed many versions parallel as a normal user - not as root - to test the behavior for bugs. File the bug to SuSE, because it seems to be a special behavior of the version SuSE has build. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142891] FILEOPEN, EDITING, Chart or Range fails to update using Undo:delete for OpenCL when a cell with operator == is present
https://bugs.documentfoundation.org/show_bug.cgi?id=142891 Julien Nabet changed: What|Removed |Added Keywords||wantBacktrace CC||serval2...@yahoo.fr --- Comment #8 from Julien Nabet --- Could you give a try to 7.2.2 and, if you still reproduce the pb, could you attach /cache/opencl_devices.log and opencl_profile.xml (see https://wiki.documentfoundation.org/QA/FirstSteps#Computation-related_issues_in_Calc_.28OpenCL.29) ? Perhaps a backtrace may be useful too (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97391] [META] OpenCL and "Software Interpreter" issues in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=97391 Julien Nabet changed: What|Removed |Added Depends on||142891 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142891 [Bug 142891] FILEOPEN, EDITING, Chart or Range fails to update using Undo:delete for OpenCL when a cell with operator == is present -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142891] FILEOPEN, EDITING, Chart or Range fails to update using Undo:delete for OpenCL when a cell with operator == is present
https://bugs.documentfoundation.org/show_bug.cgi?id=142891 Julien Nabet changed: What|Removed |Added Blocks||97391 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=97391 [Bug 97391] [META] OpenCL and "Software Interpreter" issues in Calc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131025] Writer document with tables lost data in cells (apparently) replacing with 0
https://bugs.documentfoundation.org/show_bug.cgi?id=131025 --- Comment #49 from Justin L --- I have an attempted patch at https://gerrit.libreoffice.org/c/core/+/123904, but it might be a bit heavy handed. I thought it might be an export problem (?since it only seems to affect certain locales using the Standard numbering format and not the General format?), but in both cases it wrote out what we see in comment 12 etc. An easier workaround to fix it (and a clue that this might actually be an import bug) is to edit styles.xml and remove the language/country number:language="ru" number:country="RU" from -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142539] table corrupt after insert row above
https://bugs.documentfoundation.org/show_bug.cgi?id=142539 --- Comment #5 from Justin L --- There seems to be some kind of import discrepancy. If I unzip the ODT and edit styles.xml's number:number-style and comment out then the file loads as expected. Similarly, if I add that to my English locale example (in which I couldn't reproduce the problem from scratch), then its text turns into zeros as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92015] wrong language detection in style:rfc-language-tag when country is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=92015
Eike Rathke changed:
What|Removed |Added
Assignee|libreoffice-b...@lists.free |er...@redhat.com
|desktop.org |
--- Comment #15 from Eike Rathke ---
As the USER in LANGUAGE_USER_ANCIENT_GREEK denotes it is a user defined LCID
hence 0x0649 from the set reserved for user defined LCIDs. The 0x0249 is an
on-the-fly generated LCID for a language tag {grc} that is not present in our
mappings. The value decomposes into primary 0x249 and sub 0x00, whereas the
{grc-GR} 0x649 value decomposes into primary 0x249 and sub 0x01, because
on-the-fly LCIDs for a language-only tag try to derive from a known
language-country LCID. Changing the value in lang.h would be wrong.
There's also nothing wrong with generating an on-the-fly LCID for {grc} if
there is no predefined 1:1 mapping. The resulting language listbox entry "qlt
(Greece) {grc}" looks odd though, the qlt would be our reserved internal use
code for an extended language tag when expressed in a lang::Locale, but {grc}
wouldn't need any..
The question is rather why the document hast stored
style:rfc-language-tag="grc" at all, because the also present fo:language="grc"
fo:country="GR" would be sufficient (and actually result in the known {grc-GR}
0x0469 mapping) and the style:rfc-language-tag not needed at all, and we
probably create an extended tag if it is present, on purpose because the
fo:language and fo:country would only be a subset, but in this case the
style:rfc-language-tag is a subset. Which even is a violation of ODF 19.516
style:rfc-language-tag "It shall only be used if its value cannot be expressed
as a valid combination of the fo:language 19.871, fo:script 19.242 and
fo:country 19.234 attributes".
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#__RefHeading__1418006_253892949
Seeing the document was stored using LibreOfficeDev/5.0.0.0.beta1 I really
don't care.. but I'll take a look what actually happens when loading.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 Julien Nabet changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #7 from Julien Nabet --- On pc Debian x86-64 with LO Debian testing package 7.2.2, I don't reproduce this. I mean, I could open biblio2HSQLDB.odb for example and execute the report. I don't know at all how Zypper works and never used Suse or OpenSuse. Did you check Java was installed and it corresponded 32/64 bits (I mean LO 32 bits needs Java 32 bits, LO 64 bits needs Java 64 bits)? What Java do you use, what's its version and 32/64 bits? Also, on Debian there's a package: libreoffice-java-common I don't know if it's the case for OpenSuse. Robert: I don't remember what distrib you use but thought you may have some opinion here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50879] form exported as pdf does not embed all required fonts (fix per Comment 43)
https://bugs.documentfoundation.org/show_bug.cgi?id=50879 --- Comment #72 from Lionel Elie Mamane --- (In reply to Daniel James from comment #71) > Hi Mikos, I'm not sure you're correct that this bug is only about special > characters. Indeed, it was about *all* characters, not only "special" ones. > The bug I found was the same as in comment 1 by Christian > Schlittchen dated 2012-06-08. You found it in versions 6.1.5 and 6.4.5. This bug is fixed in 7.1.0 only. > PDF forms created in LibreOffice don't work cross-platform, apparently > because the 'standard' Type 1 fonts originally selected by Adobe in the PDF > specification are no longer supported in LibreOffice. Please try again with LibreOffice 7.1.0 or later. There, the form fonts are forced to be one of the standard Type 1 fonts on PDF export. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 --- Comment #6 from Herbert --- (In reply to Julien Nabet from comment #1) > On which Linux distrib are you? > How did you install 7.2.2? installed via ftp.gwdg.de/pub/opensuse/. by command: zypper dup -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 --- Comment #5 from Herbert --- (In reply to Julien Nabet from comment #1) > On which Linux distrib are you? > How did you install 7.2.2? this comes from opensuse updated system by #/: zypper dup via ftp.gwdg.de/pob/opensuse -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 --- Comment #4 from Herbert --- Comment on attachment 175866 --> https://bugs.documentfoundation.org/attachment.cgi?id=175866 Database Testfiles Hello Julien Nabet very simply I use from my configuration files: ../.config/libreoffice/4/user/database/ which was automatically set with first opening of libreoffice. This is a dbase database as example. Result is same as with other formats mysql, tablefiles, mariadb or other dbase. The .odb is hereattached format table, dbase and HSQLDB. With Mariadb it is the same bad result. I just set a little report for arbitrary fields: Author and identifier . No report is printed or executed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145260] Database-Report is not executable
https://bugs.documentfoundation.org/show_bug.cgi?id=145260 --- Comment #3 from Herbert --- Created attachment 175866 --> https://bugs.documentfoundation.org/attachment.cgi?id=175866&action=edit Database Testfiles Hello Julien Nabet The .odb is hereattached format as table, dbase and HSQLDB. With Mariadb it is the same bad result. Within each odb file I just created a little report for some fields: Author and identifier . No report is printed or executed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50879] form exported as pdf does not embed all required fonts (fix per Comment 43)
https://bugs.documentfoundation.org/show_bug.cgi?id=50879 --- Comment #71 from Daniel James --- (In reply to Miklos Vajna from comment #70) > Discussed in today's ESC call: the original problem was that special > characters may be missing when filling in PDF forms: restricting the font to > builtin names fixes that problem. > > If you still want to embed a full custom font (all glyphs) for fill form > purposes, please file a separate bug for that. Thanks! Hi Mikos, I'm not sure you're correct that this bug is only about special characters. The bug I found was the same as in comment 1 by Christian Schlittchen dated 2012-06-08. PDF forms created in LibreOffice don't work cross-platform, apparently because the 'standard' Type 1 fonts originally selected by Adobe in the PDF specification are no longer supported in LibreOffice. Substitute form fonts are not embedded in the form fields, causing a 'missing fonts' error. Placeholder characters are shown instead, particularly in Adobe Reader. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92015] wrong language detection in style:rfc-language-tag when country is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=92015 Julien Nabet changed: What|Removed |Added CC||er...@redhat.com --- Comment #14 from Julien Nabet --- Eike: I noticed this line: include/i18nlangtag/lang.h:630:#define LANGUAGE_USER_ANCIENT_GREEK LanguageType(0x0649) But I found no ref confirming that ancient Greek corresponded with 0x0649. In decimal so debug in gdb gives 585 so 0x0249 I wanted to try this patch: diff --git a/include/i18nlangtag/lang.h b/include/i18nlangtag/lang.h index ae434fd0c06a..c6a69e59fb68 100644 --- a/include/i18nlangtag/lang.h +++ b/include/i18nlangtag/lang.h @@ -627,7 +627,7 @@ namespace o3tl #define LANGUAGE_USER_ARABIC_PALESTINE LanguageType(0x9801) /* makeLangID( 0x26, getPrimaryLanguage( LANGUAGE_ARABIC_SAUDI_ARABIA)) */ #define LANGUAGE_USER_ARABIC_SOMALIALanguageType(0x9C01) /* makeLangID( 0x27, getPrimaryLanguage( LANGUAGE_ARABIC_SAUDI_ARABIA)) */ #define LANGUAGE_USER_ARABIC_SUDAN LanguageType(0xA001) /* makeLangID( 0x28, getPrimaryLanguage( LANGUAGE_ARABIC_SAUDI_ARABIA)) */ -#define LANGUAGE_USER_ANCIENT_GREEK LanguageType(0x0649) +#define LANGUAGE_USER_ANCIENT_GREEK LanguageType(0x0249) #define LANGUAGE_USER_ASTURIAN LanguageType(0x064A) #define LANGUAGE_USER_LATGALIAN LanguageType(0x064B) #define LANGUAGE_USER_MAORE LanguageType(0x064C) but it rebuilds a lot of things Or perhaps should we declare LANGUAGE_USER_ANCIENT_GREEK_2? Also, just wonder if "649" would be just a typo instead of "249" and so wonder if there exist some real documents using 649 as ancient Greek. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136296] Bullet points are displayed in wrong order
https://bugs.documentfoundation.org/show_bug.cgi?id=136296 --- Comment #3 from niina-ma...@outlook.com --- Thank you for reporting the bug. I can not reproduce the bug in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ec76fff198323122bedc63ffdfd896c2543102c6 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: fi-FI Calc: CL or Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: fi-FI Calc: CL but it did give me A>A and B and C>A and B and C and D in both of them occasionally when i used a mouse but not with the keys, so it might just have something to do with my mouse instead. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92015] wrong language detection in style:rfc-language-tag when country is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=92015
--- Comment #13 from Julien Nabet ---
part of bt from the first console log quoted in my previous comment:
#0 (anonymous
namespace)::SvtLanguageTableImpl::GetString(o3tl::strong_int) const
(this=0x7f702b279d40 ::get()::instance>, eType=...) at
svtools/source/misc/langtab.cxx:236
#1 0x7f702af36d95 in
SvtLanguageTable::GetLanguageString(o3tl::strong_int) (eType=...) at svtools/source/misc/langtab.cxx:251
#2 0x7f7014472760 in SwTextShell::GetState(SfxItemSet&) (this=0x701de20,
rSet=SfxItemSet of pool 0x76706b0 with parent 0x0 and Which ranges: [(11209,
11209)] = {...})
at sw/source/uibase/shells/textsh1.cxx:1663
#3 0x7f7014460340 in SfxStubSwTextShellGetState(SfxShell*, SfxItemSet&)
(pShell=0x701de20, rSet=SfxItemSet of pool 0x76706b0 with parent 0x0 and Which
ranges: [(11209, 11209)] = {...})
at workdir/SdiTarget/sw/sdi/swslots.hxx:3086
#4 0x7f702d98d12a in SfxShell::GetSlotState(unsigned short, SfxInterface
const*, SfxItemSet*) (this=0x701de20, nSlotId=11209, pIF=0x3c3ae10,
pStateSet=0x0) at sfx2/source/control/shell.cxx:493
#5 0x7f702d92ce53 in SfxDispatcher::QueryState(unsigned short,
com::sun::star::uno::Any&) (this=0x926adb0, nSID=11209, rAny=uno::Any(void)) at
sfx2/source/control/dispatch.cxx:1862
#6 0x7f702da176d6 in
SfxDispatchController_Impl::addStatusListener(com::sun::star::uno::Reference
const&, com::sun::star::util::URL const&) (this=
0x8d90300, aListener=uno::Reference to
(framework::LanguageSelectionMenuController *) 0x7857758, aURL=...) at
sfx2/source/control/unoctitm.cxx:760
#7 0x7f702da17561 in
SfxOfficeDispatch::addStatusListener(com::sun::star::uno::Reference
const&, com::sun::star::util::URL const&)
(this=0x8d90260, aListener=uno::Reference to
(framework::LanguageSelectionMenuController *) 0x7857758, aURL=...) at
sfx2/source/control/unoctitm.cxx:279
#8 0x7f702eea1766 in
framework::LanguageSelectionMenuController::updatePopupMenu() (this=0x78576f0)
at framework/source/uielement/langselectionmenucontroller.cxx:254
#9 0x7f702aff5333 in
svt::PopupMenuControllerBase::setPopupMenu(com::sun::star::uno::Reference
const&) (this=0x78576f0, xPopupMenu=
uno::Reference to (VCLXPopupMenu *) 0x85e64f8) at
svtools/source/uno/popupmenucontrollerbase.cxx:356
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109238] [META] CSV bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109238 Bug 109238 depends on bug 109073, which changed state. Bug 109073 Summary: Being able to open and convert .json to .csv https://bugs.documentfoundation.org/show_bug.cgi?id=109073 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113974] Ability to parse/filter JSON data and extract fields
https://bugs.documentfoundation.org/show_bug.cgi?id=113974 Kevin Suo changed: What|Removed |Added CC||rob...@orzanna.de --- Comment #4 from Kevin Suo --- *** Bug 109073 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109073] Being able to open and convert .json to .csv
https://bugs.documentfoundation.org/show_bug.cgi?id=109073 Kevin Suo changed: What|Removed |Added CC||suokunl...@126.com Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #3 from Kevin Suo --- *** This bug has been marked as a duplicate of bug 113974 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92015] wrong language detection in style:rfc-language-tag when country is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=92015
--- Comment #12 from Julien Nabet ---
On pc Debian x86-64 with master sources updated today, I could reproduce this.
I noticed this log several times on console:
warn:svtools.misc:1258302:1258302:svtools/source/misc/langtab.cxx:239:
Language: 0x249 with unknown name, so returning lang-tag of: qlt (Greece) {grc}
--
You are receiving this mail because:
You are the assignee for the bug.
