[Bug 161368] Text wraps before page margins when page width exceeds 119 cm
https://bugs.documentfoundation.org/show_bug.cgi?id=161368 Mike Kaganski changed: What|Removed |Added See Also||https://bz.apache.org/ooo/s ||how_bug.cgi?id=34348 --- Comment #2 from Mike Kaganski --- i#34348 already changed *some* fields in SwTextFormatInfo from sal_uInt16, so putting that to See Also. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160740] cell styles in protected sheets lose background colours
https://bugs.documentfoundation.org/show_bug.cgi?id=160740 Aron Budea changed: What|Removed |Added Hardware|x86-64 (AMD64) |All CC||aron.bu...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer"
https://bugs.documentfoundation.org/show_bug.cgi?id=161381 Aron Budea changed: What|Removed |Added Alias|Regressions-ooxml-handle-fi |Regressions-ooxml-handle-fi |rst-hderfter|rst-hdr-ftr -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161139] FILEOPEN DOCX SaxException when opening specific file
https://bugs.documentfoundation.org/show_bug.cgi?id=161139 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |6472| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160139] Header and footer gets removed in Writer and cannot be restored after pasting some text from a shape (steps in comment 2)
https://bugs.documentfoundation.org/show_bug.cgi?id=160139 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |6472| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160976] FILESAVE RTF Footer content lost after saving from DOCX to RTF
https://bugs.documentfoundation.org/show_bug.cgi?id=160976 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |6472| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159385] Crash at undo of RTF Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=159385 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |6472| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158977] FILEOPEN: DOCX: footer has text when it shouldn't
https://bugs.documentfoundation.org/show_bug.cgi?id=158977 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |6472| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer"
https://bugs.documentfoundation.org/show_bug.cgi?id=161381 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||6472 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159013] FILEOPEN: DOCX: first page is duplicated on page 2
https://bugs.documentfoundation.org/show_bug.cgi?id=159013 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |6472| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136472] FILEOPEN DOCX: be like DOC - import bTitlePage into Default Page Style (as separate first header), not First Page style
https://bugs.documentfoundation.org/show_bug.cgi?id=136472 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com See Also|https://bugs.documentfounda |https://bugs.documentfounda |tion.org/show_bug.cgi?id=15 |tion.org/show_bug.cgi?id=16 |8977, |1381, |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |9013, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |9385, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=16 | |0139, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=16 | |0976, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=16 | |1139| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160139] Header and footer gets removed in Writer and cannot be restored after pasting some text from a shape (steps in comment 2)
https://bugs.documentfoundation.org/show_bug.cgi?id=160139 Aron Budea changed: What|Removed |Added Blocks||161381 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161381 [Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer"
https://bugs.documentfoundation.org/show_bug.cgi?id=161381 Aron Budea changed: What|Removed |Added Depends on||160139 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160139 [Bug 160139] Header and footer gets removed in Writer and cannot be restored after pasting some text from a shape (steps in comment 2) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161139] FILEOPEN DOCX SaxException when opening specific file
https://bugs.documentfoundation.org/show_bug.cgi?id=161139 Aron Budea changed: What|Removed |Added Blocks||161381 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161381 [Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159385] Crash at undo of RTF Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=159385 Aron Budea changed: What|Removed |Added Blocks||161381 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161381 [Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer"
https://bugs.documentfoundation.org/show_bug.cgi?id=161381 Aron Budea changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158977] FILEOPEN: DOCX: footer has text when it shouldn't
https://bugs.documentfoundation.org/show_bug.cgi?id=158977 Aron Budea changed: What|Removed |Added Blocks||161381 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161381 [Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160976] FILESAVE RTF Footer content lost after saving from DOCX to RTF
https://bugs.documentfoundation.org/show_bug.cgi?id=160976 Aron Budea changed: What|Removed |Added Blocks||161381 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161381 [Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159013] FILEOPEN: DOCX: first page is duplicated on page 2
https://bugs.documentfoundation.org/show_bug.cgi?id=159013 Aron Budea changed: What|Removed |Added Blocks||161381 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161381 [Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161381] New: [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer"
https://bugs.documentfoundation.org/show_bug.cgi?id=161381 Bug ID: 161381 Summary: [META] Regressions from "tdf#136472 adjust ooxml import to handle first header/footer" Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aron.bu...@gmail.com Depends on: 158977, 159013, 159385, 160976, 161139 Collective bug report for tracking issues that started with the following commit: http://cgit.freedesktop.org/libreoffice/core/commit/?id=4b0fa253a4540f5461397815d290586f9ddabe61 author Tomaž Vajngerl 2023-11-28 13:46:21 +0900 committer Tomaž Vajngerl2023-12-01 08:26:38 +0100 tdf#136472 adjust ooxml import to handle first header/footer Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158977 [Bug 158977] FILEOPEN: DOCX: footer has text when it shouldn't https://bugs.documentfoundation.org/show_bug.cgi?id=159013 [Bug 159013] FILEOPEN: DOCX: first page is duplicated on page 2 https://bugs.documentfoundation.org/show_bug.cgi?id=159385 [Bug 159385] Crash at undo of RTF Paste https://bugs.documentfoundation.org/show_bug.cgi?id=160976 [Bug 160976] FILESAVE RTF Footer content lost after saving from DOCX to RTF https://bugs.documentfoundation.org/show_bug.cgi?id=161139 [Bug 161139] FILEOPEN DOCX SaxException when opening specific file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160786] Weird formatting in Calc 24.2
https://bugs.documentfoundation.org/show_bug.cgi?id=160786 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #7 from Aron Budea --- This only occurs at 100% display scaling for me with the bugdoc. A bit of debugging showed that there are several calls to GenericSalLayout::LayoutText(...), but in some cases GetSubpixelPositioning() ends up being true, messing up the calculations here (previously the values were always rounded): https://opengrok.libreoffice.org/xref/core/vcl/source/gdi/CommonSalLayout.cxx?r=0b6a07f0#715 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49787] Formatting: Allow different slide / page styles (orientation, size) in a single Drawing document
https://bugs.documentfoundation.org/show_bug.cgi?id=49787 --- Comment #37 from ardv --- i hope that the developing team fix this issue -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161161] Incorrect positioning of unprintable characters with different style
https://bugs.documentfoundation.org/show_bug.cgi?id=161161 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161158] Scrolling in the navigator window for an .odm file does not go to te end
https://bugs.documentfoundation.org/show_bug.cgi?id=161158 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161375] When loading a DOCX, LibreOffice writer crashes with Abort trap: 6
https://bugs.documentfoundation.org/show_bug.cgi?id=161375 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158059] saving a spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=158059 --- Comment #3 from QA Administrators --- Dear Greg Smith, 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.
[Bug 161147] Remove hyphenation from a paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=161147 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158059] saving a spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=158059 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 111450] [META] SVG fileSave filter (Draw/Impress)
https://bugs.documentfoundation.org/show_bug.cgi?id=111450 Bug 111450 depends on bug 124620, which changed state. Bug 124620 Summary: SVG Export: Only one bullet point is exported https://bugs.documentfoundation.org/show_bug.cgi?id=124620 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161337] Delete Comment Thread only deletes one comment
https://bugs.documentfoundation.org/show_bug.cgi?id=161337 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155692] Resizing RTL table cells is almost impossible (very tricky)
https://bugs.documentfoundation.org/show_bug.cgi?id=155692 --- Comment #3 from QA Administrators --- Dear Hossein, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124620] SVG Export: Only one bullet point is exported
https://bugs.documentfoundation.org/show_bug.cgi?id=124620 --- Comment #7 from QA Administrators --- Dear Samuel Mehrbrodt (allotropia), 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.
[Bug 87012] REPORT-BUILDER: Charts without content if chart contain date or time
https://bugs.documentfoundation.org/show_bug.cgi?id=87012 --- Comment #19 from QA Administrators --- Dear Robert Großkopf, 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.
[Bug 139165] View Relationships: MSSQL via ODBC: Crash in: rtl_uString2String
https://bugs.documentfoundation.org/show_bug.cgi?id=139165 --- Comment #12 from QA Administrators --- Dear Jay Fude, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146945] Chart in writer doesn't update axis labels if its data is in Writer table
https://bugs.documentfoundation.org/show_bug.cgi?id=146945 --- Comment #4 from QA Administrators --- Dear Roman Kuznetsov, 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.
[Bug 133119] Chart layout resized on edit changes after file reload (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=133119 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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.
[Bug 131862] ODF: Remove deprecated attribute table:cell-range-address from element
https://bugs.documentfoundation.org/show_bug.cgi?id=131862 --- Comment #4 from QA Administrators --- Dear Regina Henschel, 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.
[Bug 141017] Error Printing Landscape (windows only)
https://bugs.documentfoundation.org/show_bug.cgi?id=141017 --- Comment #14 from QA Administrators --- Dear Dimitri Junker, 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.
[Bug 131868] Presentation with existing "mouse as pen" shapes is marked modified after presenting it
https://bugs.documentfoundation.org/show_bug.cgi?id=131868 --- Comment #3 from QA Administrators --- Dear Jan-Marek Glogowski, 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.
[Bug 128975] WORK: EDIT: issues left in fixing shared-formula / autocalculate problems? - edge case ( steps in comment 4 )
https://bugs.documentfoundation.org/show_bug.cgi?id=128975 --- Comment #11 from QA Administrators --- Dear b., 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.
[Bug 125986] [FILEOPEN] After pasting Excel table as EMF into right aligned paragraph, some parts of text become invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=125986 --- Comment #19 from QA Administrators --- Dear Erez W, 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.
[Bug 124495] Outline view: slides are not deleted after undo
https://bugs.documentfoundation.org/show_bug.cgi?id=124495 --- Comment #6 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.
[Bug 116832] Process remains in background after closing LibreOffice if an extension prompts an error trying to be installed
https://bugs.documentfoundation.org/show_bug.cgi?id=116832 --- Comment #5 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.
[Bug 100905] Splitting Table Breaks Spacing, Fonts, etc.
https://bugs.documentfoundation.org/show_bug.cgi?id=100905 --- Comment #7 from QA Administrators --- Dear MarjaE, 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.
[Bug 161376] Print Command File Pathing, (Can't Print!)
https://bugs.documentfoundation.org/show_bug.cgi?id=161376 --- Comment #2 from Alex --- Thank you so much for making commentary on this. Is the change you suggest an update or are you saying to uninstall and download a different version of Office Libre all over again? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159222] Low performance with comments
https://bugs.documentfoundation.org/show_bug.cgi?id=159222 --- Comment #10 from nobu --- > Comment 8 > Also, this does not repro with an existing file with comments. You need to go > through the steps from scratch. Certainly, i did not reproduce it in the existing documentation. --- --- --- --- Most of the posted glitches are reproducible, but oddly enough, when the mouse cursor is off the sheet, it moves briskly. For example, if the mouse cursor is over a sheet label (ex. [A] [1]), it moves briskly. I hope you find it useful. (by TexTra) Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fbe57382eef1138999f63e01b6152d4d05749807 CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 10240); UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161380] New: "reputationally" is marked as a misspelled work
https://bugs.documentfoundation.org/show_bug.cgi?id=161380 Bug ID: 161380 Summary: "reputationally" is marked as a misspelled work Product: LibreOffice Version: 24.2.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: drakesoba...@protonmail.com Description: Typing the word "reputationally" into LibreOffice Writer version 24.2.3.2(X86_64) on Windows 10 (22H2) results in the word being marked as misspelled. Steps to Reproduce: 1. Open LibreOffice Writer 2. Type the word "reputationally" Actual Results: A red squiggly line appears under the word Expected Results: A red squiggly line should not appear under the word Reproducible: Always User Profile Reset: No Additional Info: None -- You are receiving this mail because: You are the assignee for the bug.
[Bug 41777] Window size reopening a document not like size when saved
https://bugs.documentfoundation.org/show_bug.cgi?id=41777 wildgugu2...@gmail.com changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |wildgugu2...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161379] New: closes unexpectedly
https://bugs.documentfoundation.org/show_bug.cgi?id=161379 Bug ID: 161379 Summary: closes unexpectedly Product: LibreOffice Version: unspecified Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: chuck0...@gmail.com I installed the latest version of libre office 24.2.3.2 on a new Lenovo ideapad 1i. When I open an existing spreadsheet I can enter data into 1 cell, but when I try to advance to the next cell, the program freezes and after a few seconds the software closes. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161372] Spreadsheets with comments are unreasonably slow
https://bugs.documentfoundation.org/show_bug.cgi?id=161372 --- Comment #4 from Telesto --- Bug 113112 bug 133267 (and duplicates bug 125666 bug 126092) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161372] Spreadsheets with comments are unreasonably slow
https://bugs.documentfoundation.org/show_bug.cgi?id=161372 Telesto changed: What|Removed |Added CC||tele...@surfxs.nl Keywords||bibisectRequest, perf OS|Linux (All) |All --- Comment #3 from Telesto --- (In reply to Buovjaga from comment #2) > Probably this could be closed as a duplicate of bug 123419. The point is not > about having a large file. See even bug 159222 comment 8. You can have very > minimal repro steps. The bugs mentioned don't fit, IMHO. This bug remind me quite a number of bugs I reported/bisected in the past regarding slow deletion of columns/rows. The bug likely introduced by likely Kohei. A number (all?) got fixed by Luboš Luňák. The might contain some clues how to fix this one too.. 1. Open the attached file 2. Go to Comments tab 3. Select column A+B, right click -> delete columns Found in Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: e3bd3c7e3178dc091fd002628f052666b4db3be6 CPU threads: 4; OS: Windows 8.1 X86_64 (6.3 build 9600); UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded and in Version: 7.0.7.0.0+ (x64) Build ID: 626ea4e62a3e5005fe9825923a1c0c5bdb61cc08 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL and in Version: 5.1.0.0.alpha1+ Build ID: 49c2b9808df8a6b197dec666dfc0cda6321a4306 Threads 4; Ver: Windows 6.29; Render: GL and in 4.4.7.2 and in Versie: 4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba7 fine with Versie: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108827] [META] Calc functions bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108827 Bug 108827 depends on bug 158789, which changed state. Bug 158789 Summary: Allow SUMIF and SUBTOTAL to apply to arrays https://bugs.documentfoundation.org/show_bug.cgi?id=158789 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback list is not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||1378 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103342] [META] Font substitution bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103342 Eyal Rozenberg changed: What|Removed |Added Depends on||161378 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161378 [Bug 161378] Improve/create visibility for font fallback lists in the UI -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161378] Improve/create visibility for font fallback lists in the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=161378 Eyal Rozenberg changed: What|Removed |Added Blocks||103342 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||1373 Summary|Improve/create visibility |Improve/create visibility |for font lists in the UI|for font fallback lists in ||the UI CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103342 [Bug 103342] [META] Font substitution bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161378] New: Improve/create visibility for font lists in the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=161378 Bug ID: 161378 Summary: Improve/create visibility for font lists in the UI Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com The ODF format supports [1] setting not not just single fonts, but lists of fallback font families, so that if some of the families are not available with the appropriate features on the system, the next list item would be chose. This is intended to make font choices more robust for display on systems which don't have the same installed fonts as the author's. In fact, the list notation can be used for all aspects of a font, so that it's not just a fallback among families, but among complete font descriptions. Now, here's the UI situation, as I see it: * The UI does not represent the nature of the font info as a list of (tuples of) items - even when the current selection actually has non-degenerate list (i.e. more than 1 item). * One can type in multiple font families, separated by a semicolon - but not all (and perhaps not any) other aspects of the font. For example, if one types "12;11" as the font size, this is replaced with the maximum value, 999.9 pt, for some reason. * The font family combo-box always (AFAICT) shows lists of font-families as missing or existing based on the first item on the list. * There is no mechanism for collapsing and uncollapsing the list in the family combo-box, to show only the first item, or only the first available item. * There is no mechanism for scrolling the list in the family combo-box. I am not suggesting any specific action be taken, but I am suggesting that _some_ action be taken to make it possible for users who need it actually to work with font fallback lists. [1] https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part3-schema.html#attribute-svg_font-family ; and that directs you to: https://www.w3.org/TR/2008/REC-CSS2-20080411/fonts.html#font-family -- You are receiving this mail because: You are the assignee for the bug.
[Bug 97569] Filesave as docx saves lists with bulgarian or serbian character numbering as simple digit numbering (see comment 12)
https://bugs.documentfoundation.org/show_bug.cgi?id=97569 Edward changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |outlay-curfew...@icloud.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161376] Print Command File Pathing, (Can't Print!)
https://bugs.documentfoundation.org/show_bug.cgi?id=161376 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- 7.4 branch is a bit old. Please use a more recent LO version. Since you use Debian, you can use LO package from Debian testing instead of stable. BTW, "stable" is more for production servers, not for desktop. "testing" is a good compromise between stability and updated version. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback list is not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 Eyal Rozenberg changed: What|Removed |Added OS|All |Linux (All) --- Comment #11 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #10) Just tested on a Windows 10 machine, and it worked for me. So, it is indeed a VCL/platform issue. Let's mark it as Linux, and perhaps someone can check on a Mac. There's another point, which one notices when reading the specs: The fallback list should actually involve not just the family, but all font aspects. So, for example, we should be able to say the family is "Aptos;Carlito;serif" and the size is "12;11;11" - which means: "Use Aptos 12pt if available, otherwise Carlito 11pt; otherwise any serif font at 11pt". Useful for when the metrics for the different fallbacks are different. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159222] Low performance with comments
https://bugs.documentfoundation.org/show_bug.cgi?id=159222 --- Comment #9 from Telesto --- (In reply to Buovjaga from comment #8) > I'm wondering about Telesto's result with 7.0 vs. 7.1 in comment 6. 1. Open Calc 2. Insert a comment in a A1 3. Copy A1 4. Paste it in A1:A40 5. Select A1 6. Press CTRL+Arrow Down -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101522] [META] Media playback bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101522 --- Comment #33 from umair abdullah --- Thank for sharing wonderful info, also for Message D’anniversaire Sympa i found this website amazing https://messagedanniversairesympa.site/; target="_blank" rel="noopener">Message D’anniversaire Sympa -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101522] [META] Media playback bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101522 --- Comment #32 from umair abdullah --- Thank for sharing wonderful info, also for utorrent apk version i found this website amazing https://utorrentapk.pro/; target="_blank" rel="noopener">uTorrent Apk Pro -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101522] [META] Media playback bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101522 --- Comment #31 from umair abdullah --- Thank for sharing wonderful info, also for remini apk version i found this website amazing https://reminimodapk.pro/; target="_blank" rel="noopener">Remini Mod Apk Pro -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161356] Undo puts previous text to a wrong position
https://bugs.documentfoundation.org/show_bug.cgi?id=161356 Telesto changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161356] Undo puts previous text to a wrong position
https://bugs.documentfoundation.org/show_bug.cgi?id=161356 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression --- Comment #3 from Telesto --- Confirm with Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: e3bd3c7e3178dc091fd002628f052666b4db3be6 CPU threads: 4; OS: Windows 8.1 X86_64 (6.3 build 9600); UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded fine with Version: 7.6.3.0.0+ (X86_64) / LibreOffice Community Build ID: 35f19e5cb93ce218787904e99c2bedfd40e725cc CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 121539] Laggy scrolling & zooming in/out
https://bugs.documentfoundation.org/show_bug.cgi?id=121539 --- Comment #8 from Telesto --- Scrolling is still bit laggy. Heavily formatted file, though Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: e3bd3c7e3178dc091fd002628f052666b4db3be6 CPU threads: 4; OS: Windows 8.1 X86_64 (6.3 build 9600); UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161147] Remove hyphenation from a paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=161147 --- Comment #2 from Orwel --- Hi, thank you for the response. I often do not use automatic hyphenation in documents. But sometimes I only need to hyphenate one word (e.g. if it has 20 or more letters), so I want to be able to do manual hyphenation as well.(In reply to Stéphane Guillou (stragu) from comment #1) > (Side note: that manual, word-by-word hyphenation feature makes me feel like > it should not even exist when we have automatic hyphenate through Format > > Paragraph > Text Flow > Hyphenation, or in the equivalent Style dialogue. > Any reason why you would stick to the manual method, Orwel?) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140443] FILEOPEN DOCX Opening file with many tracked changes is slow
https://bugs.documentfoundation.org/show_bug.cgi?id=140443 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #5 from Buovjaga --- With the first three patches toward bug 144208 on Linux, time with OOO_EXIT_POST_STARTUP=1 is real0m3,320s user0m2,904s sys 0m0,408s With 24.2 the time is real0m8,476s user0m8,303s sys 0m0,236s -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148013] Larger ODT with ~500 pages and comments an record changes very slow to load, worse than before
https://bugs.documentfoundation.org/show_bug.cgi?id=148013 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #9 from Buovjaga --- With the first three patches toward bug 144208 on Linux, time with OOO_EXIT_POST_STARTUP=1 is real0m23,352s user0m22,909s sys 0m0,400s With 24.2 the time is real2m5,035s user2m4,135s sys 0m0,864s -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144208] Slow File OPEN of 477 pages ODT with 282 comments and track changes
https://bugs.documentfoundation.org/show_bug.cgi?id=144208 --- Comment #9 from Buovjaga --- I built with the three patches on Linux. Time with OOO_EXIT_POST_STARTUP=1 real0m26,429s user0m26,304s sys 0m0,392s With 24.2 the time is real2m59,777s user2m58,274s sys 0m0,910s Time to document/UI responsiveness is greater in reality. Close to 2 minutes even with the patches. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158641] Inconsistent 'point edit mode' for comments in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158641 BogdanB changed: What|Removed |Added Summary|inconsistent 'point edit|Inconsistent 'point edit |mode' for comments in Calc |mode' for comments in Calc Blocks||101216 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101216 [Bug 101216] [META] Calc comment bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 BogdanB changed: What|Removed |Added Depends on||158641 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158641 [Bug 158641] Inconsistent 'point edit mode' for comments in Calc -- You are receiving this mail because: You are the assignee for the bug.
[Bug 112873] [META] Impress/Draw comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112873 BogdanB changed: What|Removed |Added Depends on||160681 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160681 [Bug 160681] White background comment box drop down button in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160681] White background comment box drop down button in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=160681 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||112873 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112873 [Bug 112873] [META] Impress/Draw comment bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 BogdanB changed: What|Removed |Added Depends on||161372 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161372 [Bug 161372] Spreadsheets with comments are unreasonably slow -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161372] Spreadsheets with comments are unreasonably slow
https://bugs.documentfoundation.org/show_bug.cgi?id=161372 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||101216 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101216 [Bug 101216] [META] Calc comment bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158989] FILEOPEN: Incorrect text color in textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=158989 --- Comment #14 from Eyal Rozenberg --- (In reply to Eyal Rozenberg from comment #13) ... but also note that our current behavior is wrong also in the absolute sense, as pointed out in my dupe bug 160719. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158989] FILEOPEN: Incorrect text color in textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=158989 --- Comment #13 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #12) > When opening MS Office documents, it is *definitely* a valid assumption that > we must show the same as MSO. We need a very good reason to deliberately > decide to differ. Well, suppose there's a bug in MSO, which causes a calculated color to be black rather than white... But I do agree that, when it's not too much trouble, we should by default aim for "bug-to-bug compatibility" with MSO when opening DOCX files. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 72662] Use Different Measurement Units for Line vs Page Properties (e.g. point vs inch)
https://bugs.documentfoundation.org/show_bug.cgi?id=72662 --- Comment #39 from Luke --- This could be solved in 2 stages. First, create the 2 classes: * Typographical Unit – default point for line spacing, font size, and line width * Ruler Units – margin, page ruler, shape size dimensions etc. This is how MS Office works now. If enough people wanted it, we could later add the option to have both configurable like WordPerfect. The two classes could be changed in Option > General Measurement Unit. This should make most people happy while avoiding a complex UI. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161377] New: Create an option to set ISO 8601 as the default date format for any locale.
https://bugs.documentfoundation.org/show_bug.cgi?id=161377 Bug ID: 161377 Summary: Create an option to set ISO 8601 as the default date format for any locale. Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Localization Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@psilosoph.de The subject should tell everything. Currently each locale comes with its specific "default". This creates confusion again and again, aggravates community help, causes time-wasting there, and ecourages the perpetuatiuon of outdated stubborn formats. There will soon be more and more cases where the century becomes unclear even for dates that were "current" once when data keeping was already done with computers. Does nobody remember the "y2k" confusion? A special case is the ambiguity created by the US "standard". Counter-standard date formatting can cause very serious problems if it afflicts data exchange via csv-styled files. Of course, we can't assume people will drop bad habits as soon as the requested feature is available. However, people who want to get it better would be supported and encouraged. BTW: An extremely absurd way to show date and time related information is how the sofware and the settings(?) used by the ask.libreoffice site does it. People may even be mislead to believe that's also a "standard". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161056] Show bullets used in current document in bullets dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=161056 raal changed: What|Removed |Added Status|RESOLVED|VERIFIED CC||r...@post.cz --- Comment #4 from raal --- Verified in Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c497cd602d543b4212f79ba1ecf378e415fc CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback list is not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 --- Comment #10 from Mike Kaganski --- Created attachment 194510 --> https://bugs.documentfoundation.org/attachment.cgi?id=194510=edit Screenshot of working fallback This screenshot is made using Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: en-GB (ru_RU); UI: en-GB Calc: CL threaded Indeed, given that font management is platform-specific (VCL-specific), the comment 6 may be correct. It would be useful to check using gen plugin on Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108252] [META] Cell-related bugs and enhancements (including formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=108252 Bug 108252 depends on bug 161288, which changed state. Bug 161288 Summary: Wrong Chinese upper number negative sign https://bugs.documentfoundation.org/show_bug.cgi?id=161288 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161363] Backward compatibility issue in Impress: not visible texts (white texts) and formatting issues
https://bugs.documentfoundation.org/show_bug.cgi?id=161363 raal changed: What|Removed |Added CC||heiko.tietze@documentfounda ||tion.org, r...@post.cz Keywords|bibisectRequest |bibisected, bisected Regression By||Heiko Tietze --- Comment #6 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-24.2. Adding Cc: to Heiko Tietze ; Could you possibly take a look at this one? Thanks c360bb4042d85a453b2cf898bf815aafb6afd4ad is the first bad commit commit c360bb4042d85a453b2cf898bf815aafb6afd4ad Author: Jenkins Build User Date: Sat Jul 15 09:22:37 2023 +0200 source sha:ddb483509113e469b771320fea52f1b089574021 154352: Resolves tdf#156182 - Automatic text color unreadable with darker cells | https://gerrit.libreoffice.org/c/core/+/154352 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback list is not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 --- Comment #9 from Mike Kaganski --- Note that the ODF documentation of font-family attribute [1] references SVG, so the respective SVG documentation [2] applies. The SVG (and by extension, ODF) syntax uses comma. But the UI uses semicolon. [1] https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part3-schema.html#attribute-svg_font-family [2] https://www.w3.org/TR/2008/REC-CSS2-20080411/fonts.html#font-family -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161376] Print Command File Pathing, (Can't Print!)
https://bugs.documentfoundation.org/show_bug.cgi?id=161376 Alex changed: What|Removed |Added Version|4.2.7.2 release |7.4.7.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback list is not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 --- Comment #8 from Mike Kaganski --- Created attachment 194509 --> https://bugs.documentfoundation.org/attachment.cgi?id=194509=edit A document with two paragraphs using fallback lists The second paragraph uses Foo;Liberation Mono; the third uses Bar;DejaVu Serif. Just to exclude possibilities mentioned in comment 6. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161376] New: Print Command File Pathing, (Can't Print!)
https://bugs.documentfoundation.org/show_bug.cgi?id=161376 Bug ID: 161376 Summary: Print Command File Pathing, (Can't Print!) Product: LibreOffice Version: 4.2.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alexboa...@gmail.com Description: On a Chrome Book after partitioning some of the hardware to run Linux it is clear that the Libre Office, version 7.4.7.2, I installed does not have the correct file path to execute a print Command. I saw some articles calling to adjust options in the screen found by following the: Tools=> Options => Libre Office => Print No solution there File => Print Settings => Properties Also no solution Does anyone know what to do? I have checked my printer connection, I can print off the chrome web browser with no problem. Steps to Reproduce: 1.This happened right after installation, I never could print with 4.2.7.2 2. 3. Actual Results: Print Command returns, yellow exclamation error, "Could not start printer, Please check your printer configuration" Expected Results: printing .docx file Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.7.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 2; OS: Linux 6.6; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Debian package version: 4:7.4.7-1+deb12u2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback list is not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 Eyal Rozenberg changed: What|Removed |Added Summary|Font-family fallback lists |Font-family fallback list |not respected/not working |is not respected/not ||working -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback lists not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 --- Comment #7 from Eyal Rozenberg --- Bug also manifests with Western text and build: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161373] Font-family fallback lists not respected/not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161373 Eyal Rozenberg changed: What|Removed |Added Summary|Support font-family |Font-family fallback lists |fallback lists |not respected/not working Severity|enhancement |normal --- Comment #6 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #4) > Of course I am :-) I tested that before answering. > However, I only tested with a Western text. It is possible, that this is not > implemented / broken with other groups? Maybe, but - I tried now with the Western language font, and it again did not work for me. Build info: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 92815f3a464b447898ecf52492247335228e4a72 CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US Could it be that... * It's VCL-dependent? * It's OS-dependent? * It's somehow a recent regression, or alternatively fixed by a more recent build than mine? * You used a second font (FF2) that is the same as your default/global fallback font? Anyway, we seem to have two issues. One, why does it not work at all in some cases / on some systems, and two, having some UI visibility. Let's focus this bug on the "baseline" of it actually working consistently and split off the UI aspect of this to another bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161368] Text wraps before page margins when page width exceeds 119 cm
https://bugs.documentfoundation.org/show_bug.cgi?id=161368 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Version|unspecified |Inherited From OOo --- Comment #1 from Mike Kaganski --- Almost definitely an integer overflow. 65536 twip is 115.6 cm; add 2 x 2 cm margins, and you get 119.6 cm (and then, 120 cm - 119.6 cm gives the 4 mm). A tentative code pointer: sal_uInt16 SwTextFormatInfo::Width() in sw/source/core/text/inftxt.hxx (and many other cases of use of sal_uInt16 e.g. in sw/source/core/text/itrform2.cxx). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161152] LibreOffice doesn't set printer option "sides" leading to duplex not working on printers relying on this option
https://bugs.documentfoundation.org/show_bug.cgi?id=161152 --- Comment #1 from qez33...@fosiq.com --- In order for the PPD file to appear under /var/spool/cups you have to wait 1-2 min. The file starts with a "c". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161375] When loading a DOCX, LibreOffice writer crashes with Abort trap: 6
https://bugs.documentfoundation.org/show_bug.cgi?id=161375 --- Comment #2 from Jens Troeger --- > Please attach the docx file, that produces the problem. It’s a copyrighted file, which I am unable to share publicly. > Do you have access to a Windows or Linux PC and can test, whether the file > crashes there too? I could set up a VM and run on both platforms, yes. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161375] When loading a DOCX, LibreOffice writer crashes with Abort trap: 6
https://bugs.documentfoundation.org/show_bug.cgi?id=161375 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 CC||rb.hensc...@t-online.de Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Regina Henschel --- Please attach the docx file, that produces the problem. Do you have access to a Windows or Linux PC and can test, whether the file crashes there too? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160719] Automatic text color for table cell bg of RGB=(0, 255, 0) is White, should be Black
https://bugs.documentfoundation.org/show_bug.cgi?id=160719 Mike Kaganski changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |6182| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159983] FILEOPEN ODS: Wrong text and cell background color
https://bugs.documentfoundation.org/show_bug.cgi?id=159983 Mike Kaganski changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |6182| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158989] FILEOPEN: Incorrect text color in textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=158989 --- Comment #12 from Mike Kaganski --- To comment 8: When opening MS Office documents, it is *definitely* a valid assumption that we must show the same as MSO. We need a very good reason to deliberately decide to differ. When opening *own* existing files, we may want to consider the fact, that such changes are in fact *breaking* changes, i.e. they break someone's existing document. So one option is a compat flag, even if the changed algorithm will break less existing documents. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161372] Spreadsheets with comments are unreasonably slow
https://bugs.documentfoundation.org/show_bug.cgi?id=161372 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #2 from Buovjaga --- Probably this could be closed as a duplicate of bug 123419. The point is not about having a large file. See even bug 159222 comment 8. You can have very minimal repro steps. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159222] Low performance with comments
https://bugs.documentfoundation.org/show_bug.cgi?id=159222 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #8 from Buovjaga --- Jumping to the end is instant, but Calc hangs after that when I click on a different cell. Same on Windows. Bibisected that behaviour with linux-64-6.3 to d464d505fbf6e53a38afdd3661d320fac8c760d6, which is also blamed for bug 125619 (and two others which are not perf issues). Also, this does not repro with an existing file with comments. You need to go through the steps from scratch. I'm wondering about Telesto's result with 7.0 vs. 7.1 in comment 6. Heiko, Xisco and Michael are invited to check with bibisect repos. -- You are receiving this mail because: You are the assignee for the bug.
