[Bug 62032] Cannot specify a Paragraph Style to use a numbering level (over 1) for a chosen Numbering (List) style (See comment 35)
https://bugs.documentfoundation.org/show_bug.cgi?id=62032 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||1172 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161172] New: UNDO incomplete: list level is not restored in a specific document
https://bugs.documentfoundation.org/show_bug.cgi?id=161172 Bug ID: 161172 Summary: UNDO incomplete: list level is not restored in a specific document Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Keywords: implementationError Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com CC: vmik...@collabora.com Created attachment 194188 --> https://bugs.documentfoundation.org/attachment.cgi?id=194188&action=edit A manual list item 1. Open the attachment. See that the single paragraph there (with the text "foo") has the paragraph style "No_list", the numbering style "Num_1", the list level 1 (shown in the status bar), and the numbering label "Num1_lvl1_1". 2. Double-click paragraph style "Num_1_lvl2" in the Stylist (F11) to apply it to the paragraph. See that the list level in the status bar changes to level 2, and that the numbering label becomes "Num1_lvl2_1". 3. Undo (Ctrl+Z). See that the paragraph style restores to the "No_list". The problem is: the list level is not restored to level 1 (it is still level 2), and the numbering label is still "Num1_lvl2_1", instead of the expected "Num1_lvl1_1". The change of the list level in step 2 was implemented in commit c1cfe85f8bba10d367ef9ef1d6d569f53969dd34 (tdf#62032 use style list level when changing style, 2023-07-10). The correct Undo needs to be implemented. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160634] Alternate substitution feature does not work when AAT tables are present in font
https://bugs.documentfoundation.org/show_bug.cgi?id=160634 Y. Kawara changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOTABUG |--- --- Comment #10 from Y. Kawara --- Sorry, but it is a bug. The feature is available in the UI (shows there are 4 alternates) but does nothing. "So if the font has a morx table but the alternate substitution feature is in GSUB table then the alternate substitution feature will be considered missing and will not be applied since the GSUB table is not consulted at all." I think this is a good description of the bug, from where things can be worked on. It is not impossible to take a different approach. Again, it works fine in Inkscape. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161171] New: incorrect password error
https://bugs.documentfoundation.org/show_bug.cgi?id=161171 Bug ID: 161171 Summary: incorrect password error Product: Impress Remote Version: 1.0.6 Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: smamiri...@gmail.com Description: test description. Steps to Reproduce: 1.open browser 2.type your password 3.it will show you incorrect password error Actual Results: login without showing error message Expected Results: show direct on our page. Reproducible: Sometimes User Profile Reset: No Additional Info: test -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161169] New: Login Screen shown incorrect error message
https://bugs.documentfoundation.org/show_bug.cgi?id=161169 Bug ID: 161169 Summary: Login Screen shown incorrect error message Product: Impress Remote Version: 1.0.0 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: smamiri...@gmail.com Description: Spelling mistake Actual Results: Incorrect error message Expected Results: correct message Reproducible: Always User Profile Reset: No Additional Info: test -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161170] New: Login Screen shown incorrect error message
https://bugs.documentfoundation.org/show_bug.cgi?id=161170 Bug ID: 161170 Summary: Login Screen shown incorrect error message Product: Impress Remote Version: 1.0.0 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: smamiri...@gmail.com Description: Spelling mistake Actual Results: Incorrect error message Expected Results: correct message Reproducible: Always User Profile Reset: No Additional Info: test -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161088] Page numbers in status bar forgotten to translate (in Japanese UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=161088 --- Comment #1 from Saburo --- Thank you for the report. It's not a bug, it's just that "weblate" hasn't finished translating it. Proposed it, so I think it will be adopted in the next release. https://translations.documentfoundation.org/translate/libo_ui-master/swmessages/ja/?checksum=ea223f8fe19c72ed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161141] Build fails: ma_client_plugin.c: error: initialization of ‘struct st_mysql_client_plugin *’ from incompatible pointer type ‘struct st_mysql_client_plugin_AUTHENTICATION *’ [-Wincompatibl
https://bugs.documentfoundation.org/show_bug.cgi?id=161141 --- Comment #4 from Commit Notification --- Printf Debugging committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/cc389f64a500fde75a632173cba9b9e1ee5abb86 tdf#150082 tdf#161141 fix typecasting error in Makefile It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161141] Build fails: ma_client_plugin.c: error: initialization of ‘struct st_mysql_client_plugin *’ from incompatible pointer type ‘struct st_mysql_client_plugin_AUTHENTICATION *’ [-Wincompatibl
https://bugs.documentfoundation.org/show_bug.cgi?id=161141 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150082] LO Base MySQL connector don't accept auth via gssapi (missing auth_gssapi_client.dll?)
https://bugs.documentfoundation.org/show_bug.cgi?id=150082 --- Comment #13 from Commit Notification --- Printf Debugging committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/cc389f64a500fde75a632173cba9b9e1ee5abb86 tdf#150082 tdf#161141 fix typecasting error in Makefile It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160933] Writer does not follow the link to open document
https://bugs.documentfoundation.org/show_bug.cgi?id=160933 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160929] Per-document spelling dictionary/ignore list
https://bugs.documentfoundation.org/show_bug.cgi?id=160929 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down
https://bugs.documentfoundation.org/show_bug.cgi?id=135739 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157538] LibreOffice Calc crashes on exit
https://bugs.documentfoundation.org/show_bug.cgi?id=157538 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down
https://bugs.documentfoundation.org/show_bug.cgi?id=135739 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.
[Bug 160919] UI: Release notes button is black on dark blue background if macOS's "increase contrast" setting is on
https://bugs.documentfoundation.org/show_bug.cgi?id=160919 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158285] Formatting. Extremely large page number literals have appeared through my spreadsheet eg PAGE 20019
https://bugs.documentfoundation.org/show_bug.cgi?id=158285 --- Comment #2 from QA Administrators --- Dear Steve, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108670] Active color in the Area tab looks like set to black when active color not defined
https://bugs.documentfoundation.org/show_bug.cgi?id=108670 --- Comment #23 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157538] LibreOffice Calc crashes on exit
https://bugs.documentfoundation.org/show_bug.cgi?id=157538 --- Comment #3 from QA Administrators --- Dear bughunter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158045] mail merge: data sources not updated when opening the file
https://bugs.documentfoundation.org/show_bug.cgi?id=158045 --- Comment #5 from QA Administrators --- Dear walter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98462] EDITING: cross-reference to heading gets lost when inserted by a section file link with a link region
https://bugs.documentfoundation.org/show_bug.cgi?id=98462 --- Comment #5 from QA Administrators --- Dear Xaver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 84571] headless libreoffice renders progress bar ...
https://bugs.documentfoundation.org/show_bug.cgi?id=84571 --- Comment #11 from QA Administrators --- Dear Michael Meeks, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 45028] label of connector, ordinary lines and arrow gets written through line
https://bugs.documentfoundation.org/show_bug.cgi?id=45028 --- Comment #48 from QA Administrators --- Dear hdv.jadev, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147702] Fileopen DOC: Text jumbled together on a page
https://bugs.documentfoundation.org/show_bug.cgi?id=147702 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147539] Assertion fails in debug build in changing size of the thumbnail placeholder in handout master
https://bugs.documentfoundation.org/show_bug.cgi?id=147539 --- Comment #6 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 138629] No Smooth Scrolling in Writer (clicking and holding in the empty space around scrollbar) (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=138629 --- Comment #10 from QA Administrators --- Dear Noah Li, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145116] assert fails in debug build when touch a style dialog second time
https://bugs.documentfoundation.org/show_bug.cgi?id=145116 --- Comment #6 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107439] librelogo does not work with language set to Finnish
https://bugs.documentfoundation.org/show_bug.cgi?id=107439 --- Comment #12 from QA Administrators --- Dear Ari Latvala, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161159] Add GROUPBY, PIVOTBY, PERCENTOF functions to Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=161159 --- Comment #3 from m_a_riosv --- I can, but would be fine having more opinions. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161166] show column and row totals option not saved to .xlsx format file
https://bugs.documentfoundation.org/show_bug.cgi?id=161166 --- Comment #4 from m_a_riosv --- I think no, there is a sample file on tdf@122469. But if you want, add there your comment and your sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down
https://bugs.documentfoundation.org/show_bug.cgi?id=135739 --- Comment #6 from Jim Raykowski --- (In reply to Julien Nabet from comment #5) > On pc Debian x86-64 with master sources updated today, I don't reproduce > this anymore. > > Could someone else give a new try? Hi Julien, I also don't repro any longer with current master build. The accelerator bindings have changed since the report was made. Looking at the code history I think they were: .uno:PageDownSel for Shift+PgDn .uno:JumpToNextTableSel for Ctrl+Shift+PgDn Ctrl+Shift+PgDn is now assigned to .uno:ZoomMinus -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108540] [META] Page watermark bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108540 Stéphane Guillou (stragu) changed: What|Removed |Added Version|unspecified |5.4.0.3 release --- Comment #1 from Stéphane Guillou (stragu) --- Introduced in 5.4 by Szymon Kłos: http://blog.eszkadev.com/2017/06/watermark-for-libreoffice-writer.html -- You are receiving this mail because: You are the assignee for the bug.
[Bug 122567] Inserting watermark (menu Format > Watermark) can't be undone
https://bugs.documentfoundation.org/show_bug.cgi?id=122567 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #7 from Stéphane Guillou (stragu) --- Still the case in recent daily build: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 1b45ca1aa7d7cb8e7adcc07f8c60e26a413eca8c CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108540] [META] Page watermark bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108540 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|159413 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159413 [Bug 159413] Adding a watermark in Writer makes Undo unavailable even for old events -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|159413 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159413 [Bug 159413] Adding a watermark in Writer makes Undo unavailable even for old events -- You are receiving this mail because: You are the assignee for the bug.
[Bug 122567] Inserting watermark (menu Format > Watermark) can't be undone
https://bugs.documentfoundation.org/show_bug.cgi?id=122567 Stéphane Guillou (stragu) changed: What|Removed |Added CC||kaktebyaviru...@gmail.com --- Comment #6 from Stéphane Guillou (stragu) --- *** Bug 159413 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159413] Adding a watermark in Writer makes Undo unavailable even for old events
https://bugs.documentfoundation.org/show_bug.cgi?id=159413 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Resolution|--- |DUPLICATE Status|NEW |RESOLVED Blocks|105948, 108540 | --- Comment #4 from Stéphane Guillou (stragu) --- *** This bug has been marked as a duplicate of bug 122567 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105948 [Bug 105948] [META] Undo/Redo bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108540 [Bug 108540] [META] Page watermark bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158914] Calc leaks RAM when using macOS accessibility
https://bugs.documentfoundation.org/show_bug.cgi?id=158914 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5376 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 48741] [META] Writer's page header and footer issues
https://bugs.documentfoundation.org/show_bug.cgi?id=48741 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||111325 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=111325 [Bug 111325] Adding a watermark automatically adds a page header -- You are receiving this mail because: You are the assignee for the bug.
[Bug 111325] Adding a watermark automatically adds a page header
https://bugs.documentfoundation.org/show_bug.cgi?id=111325 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Blocks||48741 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=48741 [Bug 48741] [META] Writer's page header and footer issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160923] Inserting a watermark to a word document also adds a blank header.
https://bugs.documentfoundation.org/show_bug.cgi?id=160923 Stéphane Guillou (stragu) changed: What|Removed |Added Version|24.8.0.0 alpha0+ Master |7.6.7.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160923] Inserting a watermark to a word document also adds a blank header.
https://bugs.documentfoundation.org/show_bug.cgi?id=160923 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Stéphane Guillou (stragu) --- Thanks for the report, Vena Cava. Reproduced in: Version: 7.6.7.2 (X86_64) / LibreOffice Community Build ID: dd47e4b30cb7dab30588d6c79c651f218165e3c5 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But as m_a_riosv said, this is considered "not a bug", as explained by Szymon in bug 111325 comment 6: > Watermark is inserted to the page header and that is the root cause. This is > done for a compatibility with other suites (MS Office also does Watermark this > way, and adds page header). I am closing as a duplicate so we keep track of how many users think this is an issues. If you want, feel free to comment in bug 111325. *** This bug has been marked as a duplicate of bug 111325 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 111325] Adding a watermark automatically adds a page header
https://bugs.documentfoundation.org/show_bug.cgi?id=111325 Stéphane Guillou (stragu) changed: What|Removed |Added CC||vena.c...@virgin.net --- Comment #11 from Stéphane Guillou (stragu) --- *** Bug 160923 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 Hossein changed: What|Removed |Added Depends on||161021 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161021 [Bug 161021] Writer hangs when footnote is on the wrong page -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107396] [META] Repagination issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107396 Hossein changed: What|Removed |Added Depends on||161021 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161021 [Bug 161021] Writer hangs when footnote is on the wrong page -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161021] Writer hangs when footnote is on the wrong page
https://bugs.documentfoundation.org/show_bug.cgi?id=161021 Hossein changed: What|Removed |Added Blocks||136524, 107396 Summary|Writer hangs (endless loop) |Writer hangs when footnote |when footnote is on the |is on the wrong page |wrong page | --- Comment #9 from Hossein --- (In reply to Markus Grob from comment #8) > I now have tested it on my Win10. New Laptop with 28 cores. Export with > DEv-version from 18th of Mai needed 2 minutes and 4 seconds to build the pdf. > WHen I start the build with the document as argument, it needs the same > time. First it seems to stuck with the message "repagening", but after 1 > minute it changed to "export" and from the start until it's on the > directory, it's the same time. > For me, the time to read and analyze the document is the point where the > problem needs to be searched. Now I try to get the "bad" parts of the > document, as I now have found I way to display the nodenumber in the warning > window. In LibreOffice Bugzilla, there is even a dedicated meta bug for re-pagination, which is an important issue: tdf#107396. You can see a tree of these issues here: https://bugs.documentfoundation.org/showdependencytree.cgi?id=107396&hide_resolved=1 I add this issue to the Performance meta bug, and also remove "(endless loop)" from the title to describe the fact that this does not always lead to a complete hang. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107396 [Bug 107396] [META] Repagination issues https://bugs.documentfoundation.org/show_bug.cgi?id=136524 [Bug 136524] [META] Performance/hang/lag/high CPU issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=35538 --- Comment #92 from João Paulo --- Is this the same bug as reported or a new bug? * Use Merriweather Sans in Light and Bold styles in your document; * Save the document and close all instances of LibreOffice; * Reopen the document in LibreOffice Writer; * LibreOffice uses a fake bold style derived from the Light style instead of the real Bold style installed in your system; * Extra: If you first open a document which was formatted Merriweather Sans Regular and Bold before opening the (second) document which was formatted with Light and Bold, when you open the second document LibreOffice Writer shows correctly the Light and Bold styles; however, when printing or exporting to PDF it again shows a fake bold style derived from the Light style. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135645] LO corrupts bitmaps and crashes in X11 with 16 bit color (TrueColor)
https://bugs.documentfoundation.org/show_bug.cgi?id=135645 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||bibisectRequest, regression CC||stephane.guillou@libreoffic ||e.org Crash report or||["libmergedlo.so"] crash signature|| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150946] Random crashes while working on large documents, forcing me to restart my PC
https://bugs.documentfoundation.org/show_bug.cgi?id=150946 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #4 from Stéphane Guillou (stragu) --- (In reply to mvk1234321 from comment #0) > the issue may be caused by something I am doing > that most users don't do frequently like: > 1. Cut-and-pasting lots of text > 2. Scrolling back and forth frequently That sounds like bug 149527, fixed in recent versions > 3. Opening multiple windows for the same document for reference > 4. Using extremely small font sizes > 5. Leaving LibreOffice open in the background for a while without saving Other reports mention an issue after sleep, like bug 153665 or bug 153665. I tested with your sample document on Windows 11, did the actions you listed, let Windows go to sleep, and then used LO again. No crash. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Given that quite a few crashes have been resolved since you reported this, including bug 149527, please try the following: - make sure Windows is up to date - install the latest LO version (24.2.3 or above) - test and see if the issue persists - if you still get crashes, try using a new user profile (and backup the old one): https://wiki.documentfoundation.org/UserProfile - if you still get crashes after that, please provide updated details, including the full information from Help > About LibreOffice Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161159] Add GROUPBY, PIVOTBY, PERCENTOF functions to Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=161159 --- Comment #2 from Óvári --- (In reply to m_a_riosv from comment #1) > +1 Can you please update the Status from UNCONFIRMED to NEW? Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161159] Add GROUPBY, PIVOTBY, PERCENTOF functions to Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=161159 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- +1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161165] Crash in: SvListView::SelectListEntry(SvTreeListEntry *,bool)
https://bugs.documentfoundation.org/show_bug.cgi?id=161165 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 CC||serval2...@yahoo.fr Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Julien Nabet --- On pc Debian x86-64 with master sources updated today + gen rendering, I don't reproduce this. Could you apply https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile and give a new try? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161160] Indent increase multiple cells not formatting correctly when Aligned right in box
https://bugs.documentfoundation.org/show_bug.cgi?id=161160 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- Maybe in relation with tdf#107213 and tdf#126829 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161165] Crash in: SvListView::SelectListEntry(SvTreeListEntry *,bool)
https://bugs.documentfoundation.org/show_bug.cgi?id=161165 Julien Nabet changed: What|Removed |Added Hardware|All |x86-64 (AMD64) OS|All |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161167] LibreOffice Version: 24.2.3.2 (X86_64) - Writer - Footnotes not displayed.
https://bugs.documentfoundation.org/show_bug.cgi?id=161167 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161021] Writer hangs (endless loop) when footnote is on the wrong page
https://bugs.documentfoundation.org/show_bug.cgi?id=161021 --- Comment #8 from Markus Grob --- I now have tested it on my Win10. New Laptop with 28 cores. Export with DEv-version from 18th of Mai needed 2 minutes and 4 seconds to build the pdf. WHen I start the build with the document as argument, it needs the same time. First it seems to stuck with the message "repagening", but after 1 minute it changed to "export" and from the start until it's on the directory, it's the same time. For me, the time to read and analyze the document is the point where the problem needs to be searched. Now I try to get the "bad" parts of the document, as I now have found I way to display the nodenumber in the warning window. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161168] WebDav UCP - has (fairly) busy-loop in a thread refreshing locks
https://bugs.documentfoundation.org/show_bug.cgi?id=161168 Michael Meeks changed: What|Removed |Added Keywords||difficultyInteresting, ||easyHack, skillCpp, ||topicCleanup Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||michael.st...@allotropia.de --- Comment #1 from Michael Meeks --- Hi Michael; not sure if you're interested in this one =) but was a curio I stumbled over in some code reading there. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161168] New: WebDav UCP - has (fairly) busy-loop in a thread refreshing locks
https://bugs.documentfoundation.org/show_bug.cgi?id=161168 Bug ID: 161168 Summary: WebDav UCP - has (fairly) busy-loop in a thread refreshing locks Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: framework Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michael.me...@collabora.com It appears that: ucb/source/ucp/webdav-curl/SerfLockStore.cxx Hasa thread that wakes up 25 times per second: std::this_thread::sleep_for( std::chrono::milliseconds(1000/25) ); to see if some timeouts have expired. However - the method 'refreshLocks' could easily tell us how long it will be until we need to refresh another lock; and if we wait/sleep on a condition we can signal that if new ones are added. This would make scheduling far more relaxed. Suggest adding a shortest deadline in milliseconds to wake up again as a return value from 'refreshLocks()' there and sleeping that long. =) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161021] Writer hangs (endless loop) when footnote is on the wrong page
https://bugs.documentfoundation.org/show_bug.cgi?id=161021 Hossein changed: What|Removed |Added Summary|LO hangs (endless loop) |Writer hangs (endless loop) |when footnote is on the |when footnote is on the |wrong page |wrong page -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157453] ListBox in Table Control does not follow the property "line count"
https://bugs.documentfoundation.org/show_bug.cgi?id=157453 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caolan.mcnamara@collabora.c |desktop.org |om --- Comment #9 from Caolán McNamara --- I'm not sure why we have a feature like this, it seems an odd thing to support. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157844] [META] Automatic color bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=157844 Bug 157844 depends on bug 161057, which changed state. Bug 161057 Summary: [24.8] Changing dark/light application colour scheme in Draw and Impress does not switch text colour anymore in text boxes https://bugs.documentfoundation.org/show_bug.cgi?id=161057 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153293] [META] Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=153293 Bug 153293 depends on bug 161057, which changed state. Bug 161057 Summary: [24.8] Changing dark/light application colour scheme in Draw and Impress does not switch text colour anymore in text boxes https://bugs.documentfoundation.org/show_bug.cgi?id=161057 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161021] LO hangs (endless loop) when footnote is on the wrong page
https://bugs.documentfoundation.org/show_bug.cgi?id=161021 Hossein changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #7 from Hossein --- (In reply to Markus Grob from comment #0) > In my document, a footnote is somewhere wrong. As the documend has nearby > 500 pages, it's not easy to find the stucking one. Very slow loading, UI interaction and/or converting the files is in itself a problem, which falls into the category of "Performance", categorized as meta bug tdf#136524. You can measure the time needed to convert the file using command line, even without building LibreOffice: $ time libreoffice24.2 --convert-to pdf input.odt Or with the LibreOffice built from sources: $ time instdir/program/soffice --convert-to pdf input.odt The amount of time needed to convert your 500 pages PDF files should be a few seconds. If it takes more than a minute, it means that this is actually a bug around performance. Converting using LibreOffice 24.2 was also possible, withing a few seconds. I could also convert the file using the latest LO dev master (debug build is slower) in 2m38s. On the other hand, when opening the file, and immediately trying to export the file to PDF via "File > Export as > Export as PDF", waiting a few seconds lead to LibreOffice hang. This happens in LibreOffice 24.2, but not 24.8 dev master: Reproducible with: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Not reproducible with: (it warns me about missing hyphenation data for de-CH) Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 9422879a5cf74120c1057b0f8150529e304f7c95 CPU threads: 20; OS: Windows 11 (10.0 build 22631); UI render: default; VCL: win Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded One thing to mention is that some hanging shapes and formulas are displayed on the top of the first page for a small amount of time, but they disappear very fast. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108440] [META] Database form bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108440 Bug 108440 depends on bug 161133, which changed state. Bug 161133 Summary: Date field in Table Control's read-only column can be edited with date picker https://bugs.documentfoundation.org/show_bug.cgi?id=161133 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161164] Overline is incorrectly shown for paragraph mark
https://bugs.documentfoundation.org/show_bug.cgi?id=161164 --- Comment #3 from Hossein --- (In reply to V Stuart Foote from comment #2) > Also, why does the New Line (+ line break with downwards arrow > leftwards, looks like U+21B5) *not* get the font size at its position in the > paragraph text run? Nor does it get any of the character font effects. > What's different for that NPC? This is another bug, that I will file. And thanks for confirming. Also, one thing to mention is that any solution for this bug should not just copy the way underline is rendered, because in most cases, overline is better (and correctly) rendered, and underline is not. See tdf#17 comment 10. Paragraph mark is an exception. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161167] New: LibreOffice Version: 24.2.3.2 (X86_64) - Writer - Footnotes not displayed.
https://bugs.documentfoundation.org/show_bug.cgi?id=161167 Bug ID: 161167 Summary: LibreOffice Version: 24.2.3.2 (X86_64) - Writer - Footnotes not displayed. Product: LibreOffice Version: 24.2.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gil.ba...@gmail.com Description: My footnotes are not displayed anymore. Only the line that precede them is visible above the footer. This happen for any document I typed before If I insert a new foot note, its number is given, but I must type it blindly without seeint it. Footnotes still exist and are visible with F5, but not visible anymore, even in print preview. To modify my blind typing error, I had to open the document with OpenOffice, where all footnotes are visibles. Steps to Reproduce: 1.open a document containing foot notes or insert a new foot note, you can't see what you type 2. 3. Actual Results: No footnotes visible. Impossible to see what you type in a new one, impossible do modify them, impossible to see them in print preview. Expected Results: Footnotes available like before :) Reproducible: Always User Profile Reset: No Additional Info: https://ask.libreoffice.org/t/notes-de-bas-de-page-disparues-mes-notes-de-bas-de-page-ne-sont-plus-visibles/105941 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161164] Overline is incorrectly shown for paragraph mark
https://bugs.documentfoundation.org/show_bug.cgi?id=161164 --- Comment #2 from V Stuart Foote --- Also, why does the New Line (+ line break with downwards arrow leftwards, looks like U+21B5) *not* get the font size at its position in the paragraph text run? Nor does it get any of the character font effects. What's different for that NPC? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161166] show column and row totals option not saved to .xlsx format file
https://bugs.documentfoundation.org/show_bug.cgi?id=161166 --- Comment #3 from Paul Cluse --- You are correct its the same scenario as described in 122469. Do you still need a sample file? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161164] Overline is incorrectly shown for paragraph mark
https://bugs.documentfoundation.org/show_bug.cgi?id=161164 Hossein changed: What|Removed |Added Summary|Overline is incorrectly |Overline is incorrectly |shown for end of line |shown for paragraph mark |character | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161164] Overline is incorrectly shown for end of line character
https://bugs.documentfoundation.org/show_bug.cgi?id=161164 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Ever confirmed|0 |1 Keywords||bibisectRequest Status|UNCONFIRMED |NEW --- Comment #1 from V Stuart Foote --- Confirmed. Weird in that while the Para mark has always followed the font of the paragraph, the other 'Font Effects' overline, strikethrough, and underline have changed. >From LO 3.3.0 all font effects were applied to paragraph end mark. Through at least the 6.4.7 release. But by the 7.3.6 release the strikethrough and underline were removed and the overline remained. Don't have 7.0, 7.1 or 7.2 build handy to test. But a change in there somewhere that didn't get applied to the overline. Needs a reverse bibisect to find that change, then see if the same handling can be applied to the overline effect. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 149758] void SwAutoFormat::DelEmptyLine(bool): Assertion `!m_aDelPam.HasMark()' failed.
https://bugs.documentfoundation.org/show_bug.cgi?id=149758 Hossein changed: What|Removed |Added Assignee|hoss...@libreoffice.org |libreoffice-b...@lists.free ||desktop.org Status|ASSIGNED|NEW -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Bug 105537 depends on bug 148304, which changed state. Bug 148304 Summary: Using toolbar in Calc to set object line, style, width or colour triggers Assertion `(typeid(*this) == typeid(SfxItemSet)) && "cannot call this on a subclass of SfxItemSet"' failed. https://bugs.documentfoundation.org/show_bug.cgi?id=148304 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148304] Using toolbar in Calc to set object line, style, width or colour triggers Assertion `(typeid(*this) == typeid(SfxItemSet)) && "cannot call this on a subclass of SfxItemSet"' failed.
https://bugs.documentfoundation.org/show_bug.cgi?id=148304 Buovjaga changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Buovjaga --- Yep, gone in a debug build. Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 98142886f21e40d0f7052f18108d9586f4b2fbc5 CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: kf6 (cairo+wayland) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 88454] EDITING: Erroneous Behaviour of Selection Modes “Extended” and “Block” in Documents with tables
https://bugs.documentfoundation.org/show_bug.cgi?id=88454 Julien Nabet changed: What|Removed |Added CC||michael.st...@allotropia.de ||, serval2...@yahoo.fr --- Comment #14 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. After some debugging, I found that in SwBaseShell::InsertTable we go to the first if block when using "extending select" and in the else block when using "standard select". (see https://opengrok.libreoffice.org/xref/core/sw/source/uibase/shells/basesh.cxx?r=1a91641f#3070). If I force the use of the else block when using "extending select", the result is almost perfect, the only remaining pb is in [6], when undoing, it removes the table AND puts back "standard select". Michael: any thoughts here? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 122469] FILESAVE XLSX, A total result line appears in pivot table after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=122469 m_a_riosv changed: What|Removed |Added CC||paul.cl...@gmx.co.uk --- Comment #14 from m_a_riosv --- *** Bug 161166 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161166] show column and row totals option not saved to .xlsx format file
https://bugs.documentfoundation.org/show_bug.cgi?id=161166 m_a_riosv changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEEDINFO|RESOLVED --- Comment #2 from m_a_riosv --- *** This bug has been marked as a duplicate of bug 122469 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161166] show column and row totals option not saved to .xlsx format file
https://bugs.documentfoundation.org/show_bug.cgi?id=161166 m_a_riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161166] show column and row totals option not saved to .xlsx format file
https://bugs.documentfoundation.org/show_bug.cgi?id=161166 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please attach a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161166] New: show column and row totals option not saved to .xlsx format file
https://bugs.documentfoundation.org/show_bug.cgi?id=161166 Bug ID: 161166 Summary: show column and row totals option not saved to .xlsx format file Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: paul.cl...@gmx.co.uk Version Info from Calc Help about: Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.4 Calc: threaded Change to turn off pivot table column and row totals lost when saved as .xlsx and then reopened. Works correctly if saved as .ods format. To Reproduce: Using spreadsheet with pivot table saved in .xlsx format. Turn off column and row totals. Total turned off by: right click on pivot table. select properties.. select options. uncheck Total Columns and/or Total Rows. and hit OK. Totals are correctly removed. Save (as .xlsx). Close. Reopen .xlsx format sheet and the pivot table row and column totals are shown again. My first bug posting so hope it ok! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161165] New: Crash in: SvListView::SelectListEntry(SvTreeListEntry *,bool)
https://bugs.documentfoundation.org/show_bug.cgi?id=161165 Bug ID: 161165 Summary: Crash in: SvListView::SelectListEntry(SvTreeListEntry *,bool) Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ellen.sann...@alumni.stanford.edu Created attachment 194187 --> https://bugs.documentfoundation.org/attachment.cgi?id=194187&action=edit Base odb file This bug was filed from the crash reporting server and is br-1748aca4-dd91-4dfd-a5b6-f1eeb2272089. = Deleted two forms in small database. It asked permission for the first and I clicked yes. It asked for permission for the second. I clicked yes. The forms didn't show on the list and then the program closed abruptly. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 59447] Allow users to view word-breaks created by ICU Breakiterator
https://bugs.documentfoundation.org/show_bug.cgi?id=59447 Hossein changed: What|Removed |Added Summary|: Allow users to view |Allow users to view |word-breaks created by ICU |word-breaks created by ICU |Breakiterator |Breakiterator -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141705] assertion in BigPtrArray::operator[]: `idx < m_nSize'
https://bugs.documentfoundation.org/show_bug.cgi?id=141705 Julien Nabet changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #3 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I don't reproduce this anymore. Terrence: could you give a try with a recent build from master sources? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102345 Hossein changed: What|Removed |Added Depends on||161164 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161164 [Bug 161164] Overline is incorrectly shown for end of line character -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161164] Overline is incorrectly shown for end of line character
https://bugs.documentfoundation.org/show_bug.cgi?id=161164 Hossein changed: What|Removed |Added Blocks||102345 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102345 [Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107838] [META] Character-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107838 Hossein changed: What|Removed |Added Depends on||161161 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161161 [Bug 161161] Incorrect positioning of unprintable characters with different style -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102345 Hossein changed: What|Removed |Added Depends on||161161 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161161 [Bug 161161] Incorrect positioning of unprintable characters with different style -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161161] Incorrect positioning of unprintable characters with different style
https://bugs.documentfoundation.org/show_bug.cgi?id=161161 Hossein changed: What|Removed |Added Blocks||107838, 102345 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102345 [Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=107838 [Bug 107838] [META] Character-level bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107838] [META] Character-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107838 Hossein changed: What|Removed |Added Depends on||161164 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161164 [Bug 161164] Overline is incorrectly shown for end of line character -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161164] Overline is incorrectly shown for end of line character
https://bugs.documentfoundation.org/show_bug.cgi?id=161164 Hossein changed: What|Removed |Added Blocks||71732, 107838 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=71732 [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO https://bugs.documentfoundation.org/show_bug.cgi?id=107838 [Bug 107838] [META] Character-level bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 Hossein changed: What|Removed |Added Depends on||161164 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161164 [Bug 161164] Overline is incorrectly shown for end of line character -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161164] New: Overline is incorrectly shown for end of line character
https://bugs.documentfoundation.org/show_bug.cgi?id=161164 Bug ID: 161164 Summary: Overline is incorrectly shown for end of line character Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 194186 --> https://bugs.documentfoundation.org/attachment.cgi?id=194186&action=edit Text with overline and underline (odt) Description: If you enable overline for a line of text, overline is also shown (incorrectly) for end of line character. This only happens when you enable showing the formatting marks. Steps to Reproduce: 2. Open attachment, which is an ODT document 3. Enable unprintable characters with: "Toggle Formatting Marks (Ctrl+F10)" button. Actual Results: End of line character, which is a formatting mark is incorrectly overlined in blue. If you disable formatting marks with "Toggle Formatting Marks (Ctrl+F10)", it goes away. This is also true for line break, which is displayed in incorrectly small size. Expected Results: End of line character should not be overlined. User Profile Reset: No Additional Info: Reproducible with LO 24.2: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Also reproducible with the latest LO 24.8 dev master: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 551c8230b495e8c0e0502b73445f6edd1510633e CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161160] Indent increase multiple cells not formatting correctly when Aligned right in box
https://bugs.documentfoundation.org/show_bug.cgi?id=161160 --- Comment #2 from ady --- (In reply to ady from comment #1) > In the same way, the workaround for this case is: > 1. Set alignment to "left" (for LTR languages). > 2. Increase indent. > 3. Set alignment to "right". Hmm, no. Even when following the original workaround, the indent is applied only to the first cell of the range; the rest is not taking the indent value. > > This is a long-standing bug, so there is probably already some report about > it somewhere. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161160] Indent increase multiple cells not formatting correctly when Aligned right in box
https://bugs.documentfoundation.org/show_bug.cgi?id=161160 ady changed: What|Removed |Added CC||heiko.tietze@documentfounda ||tion.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from ady --- The real problem starts with selecting an alignment that is different than "left" (for LTR languages), and only then trying to set the indentation value. In order to set an indent value, Calc (incorrectly) "requires" to first set the alignment to left, then the indent value, and then modify the alignment to something else (other than "left"). If you attempt to set the indent value while the alignment is not "left" (for LTR languages), the indent field is grayed out. STR: 1. New Calc. 2. [CTRL]+[1] 3. Alignment 4. The indent field is grayed out, unless the horizontal alignment field is set to "left" (for LTR languages). If you want an indentation value for a right-aligned cell (for LTR languages): 1. First change the alignment to "left". 2. Set the indent value. 3. Change the alignment (back) to right. I am not saying this is correct. I am just saying that this is the workaround that is working. So, the fact that the procedure described on comment 0 fails (i.e. to apply the indentation to the whole range at once, as expected) is only an extension of the problem I just described. In the same way, the workaround for this case is: 1. Set alignment to "left" (for LTR languages). 2. Increase indent. 3. Set alignment to "right". This is a long-standing bug, so there is probably already some report about it somewhere. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down
https://bugs.documentfoundation.org/show_bug.cgi?id=135739 Julien Nabet changed: What|Removed |Added Keywords|haveBacktrace | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down
https://bugs.documentfoundation.org/show_bug.cgi?id=135739 Julien Nabet changed: What|Removed |Added Attachment #164305|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down
https://bugs.documentfoundation.org/show_bug.cgi?id=135739 Julien Nabet changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I don't reproduce this anymore. Could someone else give a new try? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161163] Crash when opening/creating a brand new file on Base (gtk3 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=161163 Julien Nabet changed: What|Removed |Added CC||caolan.mcnamara@collabora.c ||om, m.wegh...@posteo.de --- Comment #2 from Julien Nabet --- Caolán : you might be interested in this one since it's specific to gtk3 Michael: just in case it could be related to accessibility work since I don't reproduce this with gen rendering. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161163] Crash when opening/creating a brand new file on Base (gtk3 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=161163 --- Comment #1 from Julien Nabet --- Created attachment 194185 --> https://bugs.documentfoundation.org/attachment.cgi?id=194185&action=edit bt with debug symbols Behaviour is quite recent (I'd say less than 1 month) since I regularly open Base for some tests. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161163] New: Crash when opening/creating a brand new file on Base (gtk3 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=161163 Bug ID: 161163 Summary: Crash when opening/creating a brand new file on Base (gtk3 only) Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: serval2...@yahoo.fr Description: On pc Debian x86-64 with master sources updated today, LO quits brutally when opening a odb file or when trying to create one. (only with gtk3 rendering, no pb with gen rendering for example). Steps to Reproduce: 1. Launch Base 2. Try to open an existing odb file and just create a brand new one (with HSQL DB for example) Actual Results: LO quits/crashes Expected Results: No crash Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 2f4103da5625a9b90eb41d5c767a248a8d0b4255 CPU threads: 12; OS: Linux 6.7; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160884] Noto Color Emojis vertically misaligned in exported PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=160884 خالد حسني changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |kha...@libreoffice.org |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
