[Libreoffice-bugs] [Bug 84238] EDITING: Tables - Updating the line height is saved, but isn't read out of content.xml in the *.odb-file
https://bugs.documentfoundation.org/show_bug.cgi?id=84238 --- Comment #12 from Robert Großkopf --- Bug is still the same in LO 7.4.1.2 on OpenSUSE 15.3 64bit rpm Linux. Row height has been saved, but won't be read while opening the database file again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151114] Wrong font used for rendering in Style Preview
https://bugs.documentfoundation.org/show_bug.cgi?id=151114 --- Comment #1 from Kevin Suo --- Created attachment 182609 --> https://bugs.documentfoundation.org/attachment.cgi?id=182609=edit screenshots.pdf This is the screenshots shown the current bad behaviour on master and the good behaviour in 7.4.3+. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151114] New: Wrong font used for rendering in Style Preview
https://bugs.documentfoundation.org/show_bug.cgi?id=151114 Bug ID: 151114 Summary: Wrong font used for rendering in Style Preview Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Created attachment 182608 --> https://bugs.documentfoundation.org/attachment.cgi?id=182608=edit test.odt Steps to Reproduce: 1. Switch to English UI. 2. Open the attached test.odt. 3. Observe the font used for Style Preview (in Styles sidebar) for the style named "Title". Compare it with the contents shown in the document. Current Result: It seems that the font used for rendering the style preview is not the one used in the style (i.e. Liberation Sans). Expected Result: The font used for style preview should be the same as the ones set in the style (for this test document, it is Liberation Sans for western and Noto Sans CJK SC for Asian). Broken in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 18f4fc547a8c055afdaec4aad69c9fea387696c3 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: en-US Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.4-CN Calc: threaded But works OK in: Version: 7.4.3.0.0+ / LibreOffice Community Build ID: afdc5430770825cbbb3389a0897e7afbdaa772e2 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: en-US Calc: threaded Fedora 36 Wayland. -- You are receiving this mail because: You are the assignee for the bug.
New Defects reported by Coverity Scan for LibreOffice
Hi,
Please find the latest report on new defect(s) introduced to LibreOffice found
with Coverity Scan.
1 new defect(s) introduced to LibreOffice found with Coverity Scan.
4 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent
build analyzed by Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 1515531: Memory - corruptions (OVERRUN)
*** CID 1515531: Memory - corruptions (OVERRUN)
/unotools/source/config/configpaths.cxx: 110 in
utl::splitLastFromConfigurationPath(std::basic_string_view>, rtl::OUString &, rtl::OUString &)()
104 nEnd = nPos + 1;
105 nPos = _sInPath.rfind('[',nEnd);
106 nStart = nPos + 1;
107 }
108
109 OSL_ENSURE(nPos != std::u16string_view::npos && _sInPath[nPos]
== '[', "Invalid config path: unmatched quotes or brackets");
>>> CID 1515531: Memory - corruptions (OVERRUN)
>>> Calling "operator []" with "_sInPath._M_str" and "nPos" is suspicious
>>> because of the very large index, 18446744073709551614. The index may be due
>>> to a negative parameter being interpreted as unsigned.
110 if (nPos != std::u16string_view::npos && _sInPath[nPos] == '[')
111 {
112 nPos = _sInPath.rfind('/',nPos);
113 }
114 else // defined behavior for invalid paths
115 {
To view the defects in Coverity Scan visit,
https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P0qcxCbhZ31OYv50ypSs1kiFPuCn2xFdlMIFBirii0zZ9j2-2F9F2XPBcBm2BNgi9duPy3v-2FzgFDd2LJ-2BDKI-3DBQlx_OTq2XUZbbipYjyLSo6GRo-2FpVxQ9OzkDINu9UTS-2FQhSdO0F0jQniitrGlNxDIzPJi77qd4kU6xvIhaXKiFLs4f8lXr7J91rf1LyZYjyq7N601F2wIHfKLGV7FUL5-2Fgm3LO3B9sy2mp75eeY00pLXOwkVgV-2FPXtyLPNdEkHbKHiEy-2BdEdpZRwKjeJKQVccGtZEM2RFYnLg5flC8NK1FRPqmoZ5ck4MKGgV1-2BKFpoJIV9w-3D
[Libreoffice-bugs] [Bug 98769] Editing: Search for all instances of a paragraph style does not respect paragraph ends
https://bugs.documentfoundation.org/show_bug.cgi?id=98769 --- Comment #5 from Paul --- Bug still exists in LO 7.3.3.1 on Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150848] Tab with filling by character is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 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 150886] Text in Exported Writer Forms is Hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150886 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 150886] Text in Exported Writer Forms is Hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150886 --- Comment #13 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147588] skinny DIFFICULT TO LOCATE typing cursor in .odt Word software ... Can I widen or thicken it?
https://bugs.documentfoundation.org/show_bug.cgi?id=147588 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 147588] skinny DIFFICULT TO LOCATE typing cursor in .odt Word software ... Can I widen or thicken it?
https://bugs.documentfoundation.org/show_bug.cgi?id=147588 --- Comment #3 from QA Administrators --- Dear Rod T, 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 147492] Missing print orientation on macOS v12.1
https://bugs.documentfoundation.org/show_bug.cgi?id=147492 --- Comment #3 from QA Administrators --- Dear Emrah Dulan, 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 147492] Missing print orientation on macOS v12.1
https://bugs.documentfoundation.org/show_bug.cgi?id=147492 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 147885] Crash if properties resize bar is dragged vertically
https://bugs.documentfoundation.org/show_bug.cgi?id=147885 --- Comment #2 from QA Administrators --- Dear jon0x0, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99770] Open Remote File for LotusLive does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=99770 --- Comment #8 from QA Administrators --- Dear Shauns, 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 98769] Editing: Search for all instances of a paragraph style does not respect paragraph ends
https://bugs.documentfoundation.org/show_bug.cgi?id=98769 --- Comment #4 from QA Administrators --- Dear Paul, 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 93875] Searching after selecting a shape returns a strange text-selection result
https://bugs.documentfoundation.org/show_bug.cgi?id=93875 --- Comment #5 from QA Administrators --- Dear Mihai Varga, 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 87390] Additional master slides in a 16:9 document use the default 4:3 styles
https://bugs.documentfoundation.org/show_bug.cgi?id=87390 --- Comment #8 from QA Administrators --- Dear nodatalog, 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 84580] does not to the top of the document in certain instances
https://bugs.documentfoundation.org/show_bug.cgi?id=84580 --- Comment #17 from QA Administrators --- Dear Todd, 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 84238] EDITING: Tables - Updating the line height is saved, but isn't read out of content.xml in the *.odb-file
https://bugs.documentfoundation.org/show_bug.cgi?id=84238 --- Comment #11 from QA Administrators --- Dear pierre-yves samyn, 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 83927] EDITING: Pasted object position still differs from the original one
https://bugs.documentfoundation.org/show_bug.cgi?id=83927 --- Comment #9 from QA Administrators --- Dear pafal, 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 83768] LO BASE / soffice.bin *32 fails to close properly on Windows systems after editing objects
https://bugs.documentfoundation.org/show_bug.cgi?id=83768 --- Comment #7 from QA Administrators --- Dear Doug, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 83561] Language variants should function when variant files are not there
https://bugs.documentfoundation.org/show_bug.cgi?id=83561 --- Comment #10 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 136905] NB Layout tab 'Page Size' drop list UX is poor
https://bugs.documentfoundation.org/show_bug.cgi?id=136905 --- Comment #3 from QA Administrators --- Dear medmedin2014, 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 128660] Empty pop-up at the end of the search bar at some window widths
https://bugs.documentfoundation.org/show_bug.cgi?id=128660 --- Comment #5 from QA Administrators --- Dear B.J. Herbison, 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 128458] mailmerge: Fields "File name" and "Last printed" not filled
https://bugs.documentfoundation.org/show_bug.cgi?id=128458 --- Comment #5 from QA Administrators --- Dear Christian, 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 128419] In Find and Replace, 'Replace backwards' gets toggled back off or back on by the buttons 'Find All', 'Find Previous', etc.
https://bugs.documentfoundation.org/show_bug.cgi?id=128419 --- Comment #2 from QA Administrators --- Dear Alex, 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 122816] Empty search content is saved on the quick find text list
https://bugs.documentfoundation.org/show_bug.cgi?id=122816 --- Comment #3 from QA Administrators --- Dear Joao Farias, 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 117454] EDITING Writer crashes when manipulating variables in Compress window
https://bugs.documentfoundation.org/show_bug.cgi?id=117454 --- Comment #11 from QA Administrators --- Dear Emil Tanev, 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 115845] CPU usage increases randomly while writer is minimized after it has been open for several hours
https://bugs.documentfoundation.org/show_bug.cgi?id=115845 --- Comment #19 from QA Administrators --- Dear Alexandre Bibeau, 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 115174] Find "Whole words only" does not function properly
https://bugs.documentfoundation.org/show_bug.cgi?id=115174 --- Comment #4 from QA Administrators --- Dear Daniel Grigoras, 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 78164] FORMATTING: Writer does not respect the specified bottom margin of paragraphs in HTML files
https://bugs.documentfoundation.org/show_bug.cgi?id=78164 --- Comment #8 from David Melik --- This is much wider than HTML; Writer doesn't respect spacing below paragraph setting in *any* file type; same problem in prose (.TXT before you even format as .ODT) forcing 0.08 even when reset to historically-standard zero. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47295] Default paragraph style should be "Text body" and not "Default"
https://bugs.documentfoundation.org/show_bug.cgi?id=47295 --- Comment #38 from David Melik --- I don't believe you nor agree, because not everyone is necessarily even writing a paragraph rather than writing as a text editor just with nice formatting, which might be anything, like unorganized note(s), to-do & shopping & reading lists with no paragraphs nor list formatting, all in plain or formatted text or informal HTML... just let people use it like a text editor, without assuming what type of document they're making (nor forcing any other sort of setting/style, especially post-Internet). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151113] New: PRINTING "selection" ignores selected items and prints the whole page
https://bugs.documentfoundation.org/show_bug.cgi?id=151113 Bug ID: 151113 Summary: PRINTING "selection" ignores selected items and prints the whole page Product: LibreOffice Version: 7.0 all versions Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: allottni...@gmail.com In earlier versions - specifically up to 6.3.6.2 (which I still use because of this problem), I could select an item in Draw and then proceed to the first printer dialog screen, push the "selection" button and only the selected item would preview and print. This does not work with more recent versions - all items, both selected and unselected show in the preview and print on the page. (May be related to Bug 40163?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151112] New: Calc: Navigator does not retain focus after user presses F5
https://bugs.documentfoundation.org/show_bug.cgi?id=151112 Bug ID: 151112 Summary: Calc: Navigator does not retain focus after user presses F5 Product: LibreOffice Version: 7.3.5.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: martin.thornh...@gmail.com Description: In Calc 7.3.5.2 LibreOffice Community, press F5 to launch the Navigator. Any subsequent navigational key tab, shift+tab, left, right - goes to the spreadsheet instead of the Navigator. Steps to Reproduce: 1. See description. Actual Results: See description. Expected Results: Press F5, keyboard input should go to the Navigator, not the spreadsheet. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue
https://bugs.documentfoundation.org/show_bug.cgi?id=151095 --- Comment #5 from PeterSergej --- (In reply to V Stuart Foote from comment #2) > The text runs "render". > > But, whatever font gets selected by the font manager for fallback does not > have coverage of the glyph--that is what the placeholder/missing glyphs (the > X-boxes) on the "wrong" lines of bold text indicate. Thank you for the clarification. In my Libre Writer settings no font fallback has been configured; does the program itself look for a fallback when encountering a problem? I assume that the 'rendering' of the font either did not find the bold OTF file, or looked at the wrong glyphs. I logged this as a bug because both GIMP and Scribus, running on the same Linux system as the 'bug' in Libre Writer, did render the font as bold, and the problem does not exist for Libre Office in Windows 10. Have I erred? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151111] New: Paste special mechanism significantly deficient in options
https://bugs.documentfoundation.org/show_bug.cgi?id=15 Bug ID: 15 Summary: Paste special mechanism significantly deficient in options Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com When Pasting tabular content in Calc, we now get the following options: Unformatted Text; Text / Number / Formula; Transpose Paste as HTML/Unformatted Text/Text Import Dialog There's redundancy here; plus, it's not immediately clear how the text import dialog is not what you get when you paste as unformatted text. But - that's not why I'm filing this bug... In actuality, most of these are _orthogonal_ options. A more complete set of options would be: * Transpose the pasted range(s)? Y/N * Interpretations, if a source document is defined: * Does keeping cell style means using the same-name style in the target document, or "pasting" an additional cell style into the target document? * Will reference be interpreted as referring to the source document, or as though the same reference definition has been made in the target document? * Pre-transformations: * Realize pasted range(s)' cell styles into Direct Formatting (DF)? Y/N * Replace formulae with their computed values (incl. references)? Y/N * Kinds of content: * Clear out formulas? Y/N * Clear out numbers? Y/N * Clear out non-number strings? Y/N * Clear out anchored objects? Y/N * Direct Formatting (DF) of the cell: * Apply existing DF to the pasted content? Y/N * Apply the input range(s)' DF TO the pasted content? Y/N * Which DF takes precedence? Pasted or Existing? * Cell style: * Which cell style to have after paste? Existing/Pasted/None * (If multiple cell styles are implemented - see bug 149271 - we would also have the option of keeping both styles) I'd say _any_ combination of answers to these questions should be supported (almost; e.g. if formulae are cleared, it doesn't matter how they're interpreted). That's nearly 2^12 * 3 ~= 6000 combinations, not 4. Plus the possible interpretation as other formats besides tabular ranges. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90546] Should shortcut keys be translated to a localized UI
https://bugs.documentfoundation.org/show_bug.cgi?id=90546 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1106 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 V Stuart Foote changed: What|Removed |Added Depends on||151106 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151106 [Bug 151106] Unify localized shortcuts -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123768] Make shortcuts extensionizable
https://bugs.documentfoundation.org/show_bug.cgi?id=123768 V Stuart Foote changed: What|Removed |Added Blocks||151106 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151106 [Bug 151106] Unify localized shortcuts -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151106] Unify localized shortcuts
https://bugs.documentfoundation.org/show_bug.cgi?id=151106 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval Depends on||123768 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=90 ||546 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Blocks||98259 --- Comment #1 from V Stuart Foote --- Sure, and the Framework is in place already to be done via extension, see bug 123768 Contributions welcome. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=123768 [Bug 123768] Make shortcuts extensionizable -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151106] Unify localized shortcuts
https://bugs.documentfoundation.org/show_bug.cgi?id=151106 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval Depends on||123768 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=90 ||546 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Blocks||98259 --- Comment #1 from V Stuart Foote --- Sure, and the Framework is in place already to be done via extension, see bug 123768 Contributions welcome. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=123768 [Bug 123768] Make shortcuts extensionizable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: icon-themes/sifr icon-themes/sifr_dark icon-themes/sifr_dark_svg icon-themes/sifr_svg
dev/null |binary icon-themes/sifr/cmd/32/controlproperties.png |binary icon-themes/sifr/cmd/32/customanimation.png |binary icon-themes/sifr/cmd/32/downsearch.png |binary icon-themes/sifr/cmd/32/editcurindex.png |binary icon-themes/sifr/cmd/32/firstpage.png |binary icon-themes/sifr/cmd/32/firstrecord.png |binary icon-themes/sifr/cmd/32/insertindexentry.png |binary icon-themes/sifr/cmd/32/lastpage.png |binary icon-themes/sifr/cmd/32/lastrecord.png |binary icon-themes/sifr/cmd/32/modifylayer.png |binary icon-themes/sifr/cmd/32/movepagefirst.png |binary icon-themes/sifr/cmd/32/movepagelast.png |binary icon-themes/sifr/cmd/32/nextrecord.png |binary icon-themes/sifr/cmd/32/prevrecord.png |binary icon-themes/sifr/cmd/32/renamepage.png |binary icon-themes/sifr/cmd/32/scaletext.png |binary icon-themes/sifr/cmd/32/showtoolbar.png |binary icon-themes/sifr/cmd/32/slidechangewindow.png |binary icon-themes/sifr/cmd/32/statusbarvisible.png |binary icon-themes/sifr/cmd/32/tabdialog.png |binary icon-themes/sifr/cmd/32/text_marquee.png |binary icon-themes/sifr/cmd/32/textattributes.png |binary icon-themes/sifr/cmd/32/toolbarmode.png |binary icon-themes/sifr/cmd/32/updatecurindex.png |binary icon-themes/sifr/cmd/32/upsearch.png |binary icon-themes/sifr/cmd/32/verticaltextfittosizetool.png |binary icon-themes/sifr/cmd/lc_controlproperties.png |binary icon-themes/sifr/cmd/lc_customanimation.png |binary icon-themes/sifr/cmd/lc_downsearch.png |binary icon-themes/sifr/cmd/lc_editcurindex.png |binary icon-themes/sifr/cmd/lc_firstpage.png |binary icon-themes/sifr/cmd/lc_firstrecord.png |binary icon-themes/sifr/cmd/lc_lastpage.png |binary icon-themes/sifr/cmd/lc_lastrecord.png |binary icon-themes/sifr/cmd/lc_modifylayer.png |binary icon-themes/sifr/cmd/lc_movepagefirst.png |binary icon-themes/sifr/cmd/lc_movepagelast.png |binary icon-themes/sifr/cmd/lc_nextrecord.png |binary icon-themes/sifr/cmd/lc_prevrecord.png |binary icon-themes/sifr/cmd/lc_radiobutton.png |binary icon-themes/sifr/cmd/lc_renamepage.png |binary icon-themes/sifr/cmd/lc_scaletext.png |binary icon-themes/sifr/cmd/lc_showtoolbar.png |binary icon-themes/sifr/cmd/lc_slidechangewindow.png |binary icon-themes/sifr/cmd/lc_statusbarvisible.png |binary icon-themes/sifr/cmd/lc_tabdialog.png |binary icon-themes/sifr/cmd/lc_text_marquee.png |binary icon-themes/sifr/cmd/lc_textattributes.png |binary icon-themes/sifr/cmd/lc_toolbarmode.png |binary icon-themes/sifr/cmd/lc_updatecurindex.png |binary icon-themes/sifr/cmd/lc_upsearch.png |binary icon-themes/sifr/cmd/lc_verticaltextfittosizetool.png |binary icon-themes/sifr/cmd/sc_controlproperties.png |binary icon-themes/sifr/cmd/sc_customanimation.png |binary icon-themes/sifr/cmd/sc_downsearch.png |binary icon-themes/sifr/cmd/sc_editcurindex.png |binary icon-themes/sifr/cmd/sc_firstpage.png |binary icon-themes/sifr/cmd/sc_firstrecord.png |binary icon-themes/sifr/cmd/sc_lastpage.png |binary
[Libreoffice-bugs] [Bug 147967] Libreoffice Writer crashes after trying to insert a formula via the formula editor (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=147967 --- Comment #35 from Alex Thurgood --- (In reply to Noel Grandin from comment #33) > Alex, if you can do a debug build and get a better stacktrace for me, I can > probably fix this. Noel, unfortunately I haven't built LO on macOS since I switched to Arm silicon, let alone a debug-enabled build. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149717] Systematic crash on resize of Firebird database table creation window
https://bugs.documentfoundation.org/show_bug.cgi?id=149717 --- Comment #16 from Julien Nabet --- Badfully even with gen rendering with master sources updated today and trying to stick to the screencast, I don't reproduce this (pc Debian x86-64). I'm afraid it's really specific to macOS (or even macOS with specific version + arm) :-( -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151107] Print Preview: page orientation depends on moving forward or backwards through print preview
https://bugs.documentfoundation.org/show_bug.cgi?id=151107 Julien Nabet changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | Status|NEW |ASSIGNED --- Comment #3 from Julien Nabet --- I gave a try with this: https://gerrit.libreoffice.org/c/core/+/140358 but I must recognize I'm not sure it's the right thing to do, printing part is quite tricky. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150886] Text in Exported Writer Forms is Hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150886 --- Comment #12 from Marc Schreiber --- And I must apologize. My project did not initialize the LO backend so that it is reproducible because I wasn't aware that the LO API picks up the settings of my LO profile. The commit https://gitlab.com/schrieveslaach/nextcloud-open-document-forms/-/commit/46b0f2974d1044719a14bc764f52591bb19dce51 starts the backend now in the same way as in my screencast. So if you checkout the project and if you follow the instruction, test PDF should be generated in the same way. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 --- Comment #11 from Caolán McNamara --- this is "call_attention_to()" of include/vcl/weld.hxx, the gtk impl is in vcl/unx/gtk3/gtkinst.cxx (and the css for it in gtkdata.cxx as call_attention_to_1/call_attention_to_2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: download.lst external/libpng
download.lst |4 ++-- external/libpng/libpng-osx.patch.1 |2 +- 2 files changed, 3 insertions(+), 3 deletions(-) New commits: commit 18f4fc547a8c055afdaec4aad69c9fea387696c3 Author: Taichi Haradaguchi <20001...@ymail.ne.jp> AuthorDate: Wed Sep 21 17:17:35 2022 +0900 Commit: Caolán McNamara CommitDate: Wed Sep 21 22:20:04 2022 +0200 libpng: update to release 1.6.38 Change-Id: Ife594699cc8736ffdfc8f68e462d11416d7930e9 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140311 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/download.lst b/download.lst index 759af2d03bd5..d81256d3afc0 100644 --- a/download.lst +++ b/download.lst @@ -206,8 +206,8 @@ export PDFIUM_SHA256SUM := ecb9c2a0d777196949994946e3f24ed251ae5d3db8a9fa1e2827e export PDFIUM_TARBALL := pdfium-5298.tar.bz2 export PIXMAN_SHA256SUM := 6d200dec3740d9ec4ec8d1180e25779c00bc749f94278c8b9021f5534db223fc export PIXMAN_TARBALL := pixman-0.40.0.tar.gz -export LIBPNG_SHA256SUM := 505e70834d35383537b6491e7ae8641f1a4bed1876dbfe361201fc80868d88ca -export LIBPNG_TARBALL := libpng-1.6.37.tar.xz +export LIBPNG_SHA256SUM := b3683e8b8111ebf6f1ac004ebb6b0c975cd310ec469d98364388e9cedbfa68be +export LIBPNG_TARBALL := libpng-1.6.38.tar.xz export LIBTIFF_SHA256SUM := 49307b510048ccc7bc40f2cba6e8439182fe6e654057c1a1683139bf2ecb1dc1 export LIBTIFF_TARBALL := tiff-4.4.0.tar.xz export POPPLER_SHA256SUM := d7a8f748211359cadb774ba3e18ecda6464b34027045c0648eb30d5852a41e2e diff --git a/external/libpng/libpng-osx.patch.1 b/external/libpng/libpng-osx.patch.1 index 0e9d7336a762..387b3a8cc613 100644 --- a/external/libpng/libpng-osx.patch.1 +++ b/external/libpng/libpng-osx.patch.1 @@ -4,7 +4,7 @@ Avoid warning: 'inflateValidate' is only available on macOS 10.13 or newer [-Wun --- a/pngrutil.c +++ b/pngrutil.c -@@ -419,7 +419,8 @@ +@@ -422,7 +422,8 @@ } #if ZLIB_VERNUM >= 0x1290 && \
[Libreoffice-bugs] [Bug 151060] PDF Printing showing random black lines on my document.
https://bugs.documentfoundation.org/show_bug.cgi?id=151060 Telesto changed: What|Removed |Added Version|7.4.1.2 release |7.0.0.3 release Keywords||bibisectRequest, regression --- Comment #5 from Telesto --- Still OK with Versie: 6.4.0.2 (x86) Build ID: 08d19fecdc7a2298d051e19cfdb7c35544855fc3 CPU-threads: 4; Besturingssysteem: Windows 6.3 Build 9600; UI-render: GL; VCL: win; Locale: nl-NL (nl_NL); UI-taal: nl-NL Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151060] PDF Printing showing random black lines on my document.
https://bugs.documentfoundation.org/show_bug.cgi?id=151060 Telesto changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from Telesto --- Confirm Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 349e3af0c5dd5ed495ed61aab526f63c16f0e215 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 1. Open the attached file 2. Export to PDF 3. Open the PDF .. page 3 and 4 containing an unexpected line Same issue is also visible in Print Preview. Press CTRL+P and press arrow right button navigating to page 3/4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8349 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 --- Comment #10 from Eyal Rozenberg --- Calling attention is good, and I think I even brought this up at some point, but the animation is totally overboard... :-P -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 --- Comment #9 from Buovjaga --- I searched for a way to disable all animations and I wonder if this still works: gsettings set org.gnome.desktop.interface enable-animations false I don't seem to get the search box animation under gtk3 no matter if the setting is true or false. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 --- Comment #8 from Rafael Lima --- (In reply to Buovjaga from comment #7) > According to the blog post it was deliberately added: > https://caolanm.blogspot.com/2022/04/gtk-calling-attention-to-widget-in.html I had no idea about that. I thought it was some upstream change in Gtk. TBH I like the idea of adding some animations to the UI to make it smoother and more modern. So kudos for Caolan for this initiative. In this case specifically I think the animation feels a bit too long. It could be something shorter, similar to when you try to log in and the password fails, then the entry shakes very briefly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32950] FILEOPEN XLS: Cell height may be wrong because 'Optimal height" of rows is not re-calculated at load time.
https://bugs.documentfoundation.org/show_bug.cgi?id=32950 --- Comment #34 from Justin L --- (In reply to Justin L from comment #33) > I haven't found the code for that yet. sc/source/filter/excel/xistyle.cxx's XclImpXF::CreatePattern // Excel's cell margins are different from Calc's default margins. SvxMarginItem aItem(40, 40, 40, 40, ATTR_MARGIN); [Excel here meaning binary excel. oox matches Calc's default margins and so doesn't need to do anything different.] -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130149] Text using the Cantarell variable font is not printed or PDF exported in some Linux (comment 8 and comment 26)
https://bugs.documentfoundation.org/show_bug.cgi?id=130149 --- Comment #33 from خالد حسني --- I see, sorry for the noise (it looked scary in the bug list with the crossed out text). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #7 from Buovjaga --- (In reply to Rafael Lima from comment #6) > I am setting this to NEW because I believe this animation effect is derived > from gtk3 and was not intended to be added to LO Calc. > > BTW this animation also happens in Writer under gtk3. According to the blog post it was deliberately added: https://caolanm.blogspot.com/2022/04/gtk-calling-attention-to-widget-in.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150886] Text in Exported Writer Forms is Hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150886 --- Comment #11 from Marc Schreiber --- Created attachment 182607 --> https://bugs.documentfoundation.org/attachment.cgi?id=182607=edit A screencast that shows how to reproduce I made a screencast that show how I can reproduce the bug. The screencast also shows that I'm using a fresh profile folder (see soffice -env:UserInstallation=file:///tmp/test) and I opened the ODT from here (https://gitlab.com/schrieveslaach/nextcloud-open-document-forms/-/blob/main/example-docs/firstname.odt). Copying the text from the exported PDF into a text editor shows that the text is there but invisible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130149] Text using the Cantarell variable font is not printed or PDF exported in some Linux (comment 8 and comment 26)
https://bugs.documentfoundation.org/show_bug.cgi?id=130149 Buovjaga changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #32 from Buovjaga --- Khaled: let's keep as closed because this has attracted spam and we have automated measures in place targeting closed statuses. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149221] [LOCALHELP] Bad Help page for database connection wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=149221 --- Comment #2 from Rafael Lima --- FTR if you open Base then the Database Wizard will show with the "Select database" page selected. Pressing F1 now will work because the widget that is selected is "Create a new database", which is in the "generalpagewizard.ui". Now if you click "Save and Proceed" and then click back "Select database" and press F1, you'll be redirected to the Mail Merge help page. Notice now that the "Create a new database" is no longer selected. The problem here is that when you click "Save and Proceed" you fall back to the general wizard widget in LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151060] PDF Printing showing random black lines on my document.
https://bugs.documentfoundation.org/show_bug.cgi?id=151060 --- Comment #3 from Gabriel Scheller --- (In reply to Telesto from comment #1) > Could you please add an example file exhibiting the problem. > > See also: > https://wiki.documentfoundation.org/QA/Bugzilla/ > Sanitizing_Files_Before_Submission added, thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151060] PDF Printing showing random black lines on my document.
https://bugs.documentfoundation.org/show_bug.cgi?id=151060 --- Comment #2 from Gabriel Scheller --- Created attachment 182606 --> https://bugs.documentfoundation.org/attachment.cgi?id=182606=edit evidence file (docx) When you print this file as .pdf on LibreOffice, it shows the random line on the page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svgio/inc svgio/qa svgio/source
svgio/inc/svgcharacternode.hxx|1
svgio/qa/cppunit/SvgImportTest.cxx| 20 +++
svgio/qa/cppunit/data/tdf103888.svg | 11 ++
svgio/source/svgreader/svgcharacternode.cxx |5 --
svgio/source/svgreader/svgdocumenthandler.cxx | 44 ++
5 files changed, 34 insertions(+), 47 deletions(-)
New commits:
commit a42f5faac7c6d4590e632cf40e3ba9eb618e6f56
Author: Xisco Fauli
AuthorDate: Wed Sep 21 17:25:17 2022 +0200
Commit: Xisco Fauli
CommitDate: Wed Sep 21 21:04:40 2022 +0200
tdf#103888: Do not add a gap at the end of each text portion
I can't think of any situation where it's needed
Change-Id: I1c2c6ec3d22eb9263f3c3c20793d9fe3926b8d78
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140351
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/svgio/inc/svgcharacternode.hxx b/svgio/inc/svgcharacternode.hxx
index b7a0a9a254c9..9558e7b752b9 100644
--- a/svgio/inc/svgcharacternode.hxx
+++ b/svgio/inc/svgcharacternode.hxx
@@ -141,7 +141,6 @@ namespace svgio::svgreader
virtual const SvgStyleAttributes* getSvgStyleAttributes() const
override;
void
decomposeText(drawinglayer::primitive2d::Primitive2DContainer& rTarget,
SvgTextPosition& rSvgTextPosition) const;
void whiteSpaceHandling();
-void addGap();
void concatenate(std::u16string_view rText);
/// Text content
diff --git a/svgio/qa/cppunit/SvgImportTest.cxx
b/svgio/qa/cppunit/SvgImportTest.cxx
index 7db9c8335b1f..07a98f4a5a2f 100644
--- a/svgio/qa/cppunit/SvgImportTest.cxx
+++ b/svgio/qa/cppunit/SvgImportTest.cxx
@@ -73,6 +73,7 @@ class Test : public test::BootstrapFixture, public
XmlTestTools
void test123926();
void test47446();
void test47446b();
+void testTdf103888();
void testMaskText();
void testTdf4();
void testTdf99115();
@@ -121,6 +122,7 @@ public:
CPPUNIT_TEST(test123926);
CPPUNIT_TEST(test47446);
CPPUNIT_TEST(test47446b);
+CPPUNIT_TEST(testTdf103888);
CPPUNIT_TEST(testMaskText);
CPPUNIT_TEST(testTdf4);
CPPUNIT_TEST(testTdf99115);
@@ -479,7 +481,7 @@ void Test::testTdf85770()
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]",
"height", "11");
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]",
"familyname", "Times New Roman");
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]",
"fontcolor", "#00");
-assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]",
"text", "Start ");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]",
"text", "Start");
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]",
"height", "11");
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]",
"familyname", "Times New Roman");
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[3]",
"fontcolor", "#00");
@@ -846,6 +848,22 @@ void Test::test47446b()
}
+void Test::testTdf103888()
+{
+Primitive2DSequence aSequenceMaskText =
parseSvg(u"/svgio/qa/cppunit/data/tdf103888.svg");
+CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequenceMaskText.getLength()));
+
+drawinglayer::Primitive2dXmlDump dumper;
+xmlDocUniquePtr pDocument =
dumper.dumpAndParse(Primitive2DContainer(aSequenceMaskText));
+
+CPPUNIT_ASSERT (pDocument);
+
+// Without the fix in place, this test would have failed here with number
of nodes is incorrect
+assertXPath(pDocument,
"/primitive2D/transform/transform/textsimpleportion[1]", "text", "Her");
+assertXPath(pDocument,
"/primitive2D/transform/transform/textsimpleportion[2]", "text", "vor");
+assertXPath(pDocument,
"/primitive2D/transform/transform/textsimpleportion[3]", "text", "hebung");
+}
+
void Test::testMaskText()
{
//Check that mask is applied on text
diff --git a/svgio/qa/cppunit/data/tdf103888.svg
b/svgio/qa/cppunit/data/tdf103888.svg
new file mode 100644
index ..1663fa395e40
--- /dev/null
+++ b/svgio/qa/cppunit/data/tdf103888.svg
@@ -0,0 +1,11 @@
+
+
+http://www.w3.org/2000/svg; version="1.1"
+ width="75mm"
+ height="15mm"
+ viewBox="0 0 250 50">
+ Hervorhebung
+
diff --git a/svgio/source/svgreader/svgcharacternode.cxx
b/svgio/source/svgreader/svgcharacternode.cxx
index 0a4731b200d5..31376ee179a8 100644
--- a/svgio/source/svgreader/svgcharacternode.cxx
+++ b/svgio/source/svgreader/svgcharacternode.cxx
@@ -549,11 +549,6 @@ namespace svgio::svgreader
}
}
-void SvgCharacterNode::addGap()
-{
-maText += " ";
-}
-
void SvgCharacterNode::concatenate(std::u16string_view rText)
{
maText += rText;
diff --git a/svgio/source/svgreader/svgdocumenthandler.cxx
b/svgio/source/svgreader/svgdocumenthandler.cxx
index 288b0205397d..dc2dd6fa7c6b 100644
---
[Libreoffice-bugs] [Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Bug 88278 depends on bug 103888, which changed state. Bug 103888 Summary: SVG: tspan element gets an additional horizontal spacing before and after https://bugs.documentfoundation.org/show_bug.cgi?id=103888 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Rafael Lima changed: What|Removed |Added Depends on||151110 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151110 [Bug 151110] Search box in bottom bar has silly animation effect -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129523] Color Emojis are not exported to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=129523 خالد حسني changed: What|Removed |Added Version|6.3.3.2 release |Inherited From OOo Summary|FILESAVE Emojis not |Color Emojis are not |exported to PDF |exported to PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 Rafael Lima changed: What|Removed |Added Blocks||103182 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #6 from Rafael Lima --- I am setting this to NEW because I believe this animation effect is derived from gtk3 and was not intended to be added to LO Calc. BTW this animation also happens in Writer under gtk3. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103182 [Bug 103182] [META] GTK3-specific bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149221] [LOCALHELP] Bad Help page for database connection wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=149221 Rafael Lima changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130149] Text using the Cantarell variable font is not printed or PDF exported in some Linux (comment 8 and comment 26)
https://bugs.documentfoundation.org/show_bug.cgi?id=130149 خالد حسني changed: What|Removed |Added Status|CLOSED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149224] [LOCALHELP] Bad Help page for database properties wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=149224 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9221 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149221] [LOCALHELP] Bad Help page for database connection wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=149221 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9224 CC||rafael.palma.l...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Rafael Lima --- Confirmed with Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.4.1~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded This seems to be a generic reference used by all "wizards" -> vcl/ui/wizard/Wizard Actually, using this as HID for Mail Merge is also a mistake. This is possibly the same explanation for bug 149224. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 Eyal Rozenberg changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #5 from Eyal Rozenberg --- Thank you, Rafael, for taking the time to make the GIF :-) I believe the NEEDINFO can be removed now - can we mark this as NEW? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 Bug 71732 depends on bug 148900, which changed state. Bug 148900 Summary: Faux Bold and Italic on Unifont https://bugs.documentfoundation.org/show_bug.cgi?id=148900 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148900] Faux Bold and Italic on Unifont
https://bugs.documentfoundation.org/show_bug.cgi?id=148900 خالد حسني changed: What|Removed |Added Resolution|--- |INVALID CC||kha...@aliftype.com Status|UNCONFIRMED |RESOLVED --- Comment #8 from خالد حسني --- Unifont comes only in a regular style, whatever you are seeing in other applications are also synthetic (faux) styles. There is no standard that defines how much to slant or embolden a font, so different applications might give different results. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151107] Print Preview: page orientation depends on moving forward or backwards through print preview
https://bugs.documentfoundation.org/show_bug.cgi?id=151107 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||serval2...@yahoo.fr Ever confirmed|0 |1 --- Comment #2 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I got the exact opposite pb. At step 3 when I reach page 4, I got landscape orientation. But if I click right arrow button the left arrow button, it becomes portrait orientation. Anyway, let's put this one as New since there's indeed a pb here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 --- Comment #4 from Rafael Lima --- Created attachment 182605 --> https://bugs.documentfoundation.org/attachment.cgi?id=182605=edit Find animation in Calc (gtk3) Here's a short gif showing the animation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 --- Comment #3 from Rafael Lima --- This only happens in Calc using gtk3 backend. It is a horizontal shrinking animation. I agree it looks a bit silly. Actually we have very few animations in the UI, so this one seems too much to me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151086] Writer crashes when insert SVG image with default anchor set to As Character (STR: comment 4 + comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=151086 Julien Nabet changed: What|Removed |Added CC||michael.st...@allotropia.de Keywords|wantBacktrace |haveBacktrace --- Comment #13 from Julien Nabet --- Assertion has been added with 0ed73a0817ad0ff0107cb297208252c0afe3b4a9 fdo#59437: SwFmtAnchor::SetAnchor: Anchors may be on StartNodes Assertion added in 90a0116ccb48388d91b21128fcac2e4609838581 wasn't quite right. (in 2013). Michael: thought you might be interested in this one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/gdi/impglyphitem.cxx |4
1 file changed, 4 insertions(+)
New commits:
commit 5468a58c3244cf98341945c17db040b067c825f7
Author: Caolán McNamara
AuthorDate: Wed Sep 21 15:31:45 2022 +0100
Commit: Caolán McNamara
CommitDate: Wed Sep 21 20:37:07 2022 +0200
crashtesting: disable glyph caching for "XB Roya" font
as seen in tdf119074-1.odt. harfbuzz upstream bug of
https://github.com/harfbuzz/harfbuzz/issues/3824 filed to look for
guidance.
Change-Id: I792f86334c2a2958b175a0e14334a0a7a6ba81d8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140345
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/vcl/source/gdi/impglyphitem.cxx b/vcl/source/gdi/impglyphitem.cxx
index 7bed1391c0d5..a8eed4a02020 100644
--- a/vcl/source/gdi/impglyphitem.cxx
+++ b/vcl/source/gdi/impglyphitem.cxx
@@ -327,6 +327,10 @@ SalLayoutGlyphsCache::GetLayoutGlyphs(VclPtr outputDevice, c
if (nLen == 0)
return nullptr;
const CachedGlyphsKey key(outputDevice, text, nIndex, nLen, nLogicWidth);
+// for now disable if the font is the one seen in tdf#119074
+// https://github.com/harfbuzz/harfbuzz/issues/3824
+if (key.fontMetric.GetFamilyName() == "XB Roya")
+return nullptr;
GlyphsCache::const_iterator it = mCachedGlyphs.find(key);
if (it != mCachedGlyphs.end())
{
[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108897 Justin L changed: What|Removed |Added Depends on|140185 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140185 [Bug 140185] XLSX file doesn't save border padding for styles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88173] [META] DOCX (OOXML) format limitations
https://bugs.documentfoundation.org/show_bug.cgi?id=88173 Justin L changed: What|Removed |Added Depends on||140185 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140185 [Bug 140185] XLSX file doesn't save border padding for styles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88173] [META] DOCX (OOXML) format limitations
https://bugs.documentfoundation.org/show_bug.cgi?id=88173 Bug 88173 depends on bug 140185, which changed state. Bug 140185 Summary: XLSX file doesn't save border padding for styles https://bugs.documentfoundation.org/show_bug.cgi?id=140185 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140185] XLSX file doesn't save border padding for styles
https://bugs.documentfoundation.org/show_bug.cgi?id=140185 Justin L changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED Blocks|108897 |88173 --- Comment #17 from Justin L --- Internet searches indicate this is can only be done for columns, via "indent" options for left/right/distributed (up to 15pt). [This doesn't seem to be mapping to anything in LO, but there are lots of bug reports and the indenting amount is very in-exact.] Apparently nothing exists for height (except centring and specifying a row height). https://www.addintools.com/documents/excel/where-is-cell-padding/where-is-cell-padding.html Marking as INVALID - request is for something not possible in MSO formats. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=88173 [Bug 88173] [META] DOCX (OOXML) format limitations https://bugs.documentfoundation.org/show_bug.cgi?id=108897 [Bug 108897] [META] XLSX (OOXML) bug tracker -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151060] PDF Printing showing random black lines on my document.
https://bugs.documentfoundation.org/show_bug.cgi?id=151060 --- Comment #1 from Telesto --- Could you please add an example file exhibiting the problem. See also: https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151086] Writer crashes when insert SVG image with default anchor set to As Character (STR: comment 4 + comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=151086 --- Comment #12 from Julien Nabet --- Created attachment 182604 --> https://bugs.documentfoundation.org/attachment.cgi?id=182604=edit bt with debug symbols On pc Debian x86-64 with master sources updated today, I got an assertion. I had to run: Tool -> Options -> LibreOffice Writer -> Formatting Aids -> Image = As Character. then I tried https://bugs.documentfoundation.org/show_bug.cgi?id=151086#c4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 Eyal Rozenberg changed: What|Removed |Added Component|Writer |Calc --- Comment #2 from Eyal Rozenberg --- Sorry, I forgot to add the build info, and got the app wrong. Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 6c81a09e3ef239a2d7a991d00fe3620a67298b99 CPU threads: 4; OS: Linux 5.18; 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.
[Libreoffice-bugs] [Bug 149998] Libre Office Writer crashes with Save As PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=149998 --- Comment #4 from Telesto --- (In reply to Mike Kaganski from comment #2) 1. Open Writer 2. Type something: say AAA 3. CTRL+A & CTRL+C 4. CTRL+P 5. Select, in my case: Microsoft XPS printer 6. Press OK -> Save as Dialog opens 7. Paste inside the file name field with CTRL+V-> Freeze Also in 4.4.7.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- It does not happen to me. At least in Linux (kf5) the search bar does not have such animation. I press Ctrl+F in Writer and if I keep trying to search terms that do not match anything, no animation happens. What OS / backend are you using? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149501] [DOCX] Text in white color and glow effect imported as black text
https://bugs.documentfoundation.org/show_bug.cgi?id=149501 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4061 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144061] Effects: Allow GLOW to apply to Text (as we have for shapes)
https://bugs.documentfoundation.org/show_bug.cgi?id=144061 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9501 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144061] Effects: Allow GLOW to apply to Text (as we have for shapes)
https://bugs.documentfoundation.org/show_bug.cgi?id=144061 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140529] Enhancement: Glow Effect needs to work on more than base shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=140529 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4061 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107657] [META] Font effects bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107657 Rafael Lima changed: What|Removed |Added Depends on||144061 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144061 [Bug 144061] Effects: Allow GLOW to apply to Text (as we have for shapes) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144061] Effects: Allow GLOW to apply to Text (as we have for shapes)
https://bugs.documentfoundation.org/show_bug.cgi?id=144061 Rafael Lima changed: What|Removed |Added Summary|Effects: Allow GLOW to |Effects: Allow GLOW to |apply to Text (as well as |apply to Text (as we have |shapes) |for shapes) CC||rafael.palma.l...@gmail.com Blocks||107657 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0529 --- Comment #2 from Rafael Lima --- Still an issue in LO 7.5. I am setting this one to new. As mentioned in bugs 123941 and 136772 there are some effects still missing in LO, glow being one of them. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107657 [Bug 107657] [META] Font effects bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151110] New: Search box in bottom bar has silly animation effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151110 Bug ID: 151110 Summary: Search box in bottom bar has silly animation effect Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com When you repeatedly search and fail, using the search bar in the bottom panel in Writer, it seems the text box contracts and expands back and forth. This is silly, distracting and weird, please don't do that. There are other ways to gain attention (and I think the red color is enough to attract attention). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151104] Shadow and image fill does not work together in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151104 Rafael Lima changed: What|Removed |Added Keywords||bibisectRequest, ||possibleRegression Status|UNCONFIRMED |NEW CC||rafael.palma.l...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Rafael Lima --- Repro with: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 35702fd6781542f5eefbd3710304ab9a25ac61fe CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded I see the following issues: Slide 1: The shadow is a copy of the colored text (should be white) Slide 2: all ok Slide 3: all ok Slide 4: all ok Slide 5: same problem as slide 1 I'm setting this to NEW. However this seems to be a regression. It is NOT REPRO with: Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.4.1~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109362] [META] Custom/object animation bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109362 Rafael Lima changed: What|Removed |Added Depends on||151096 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151096 [Bug 151096] Impress Animation: The smiley face incorrectly dims/disappears after the appearance event occurs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151096] Impress Animation: The smiley face incorrectly dims/disappears after the appearance event occurs
https://bugs.documentfoundation.org/show_bug.cgi?id=151096 Rafael Lima changed: What|Removed |Added Blocks||109362 CC||rafael.palma.l...@gmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109362 [Bug 109362] [META] Custom/object animation bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109362] [META] Custom/object animation bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109362 Rafael Lima changed: What|Removed |Added Depends on||151097 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151097 [Bug 151097] Impress Animation: The smiley face does not dim to the desired color after the appearance event occurs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151097] Impress Animation: The smiley face does not dim to the desired color after the appearance event occurs
https://bugs.documentfoundation.org/show_bug.cgi?id=151097 Rafael Lima changed: What|Removed |Added Blocks||109362 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109362 [Bug 109362] [META] Custom/object animation bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
