[Libreoffice-bugs] [Bug 93689] EDITING: Paste Special DDE link: Pastes selected AND ALL PREVIOUS text from source file
https://bugs.documentfoundation.org/show_bug.cgi?id=93689 --- Comment #15 from Mike Kaganski --- Testing using 7.4.2.1, I could repro what is described in comment 11. However, I also wanted to see what happens when the DDE source changes - and I couldn't make the text update in the target document. So: does DDE (with Writer source document) actually work, or is it just some broken feature? (Calc source document definitely works.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93689] EDITING: Paste Special DDE link: Pastes selected AND ALL PREVIOUS text from source file
https://bugs.documentfoundation.org/show_bug.cgi?id=93689 Mike Kaganski changed: What|Removed |Added Attachment #128110|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150664] Formula bar in Calc is moved to down
https://bugs.documentfoundation.org/show_bug.cgi?id=150664 sebalis changed: What|Removed |Added CC||lis...@math.uni-bielefeld.d ||e --- Comment #12 from sebalis --- Confirming this bug. I am using Arch Linux and have seen this in all the 7.4 versions of libreoffice-fresh that I have tried, including the one current at the time of writing (7.4.1-3). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130796] FILESAVE: Font changes when saving ODS file to XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=130796 --- Comment #4 from Kevin Suo --- (In reply to QA Administrators from comment #3) Still reproducible on Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 09c076c3f29c28497f162d3a5b7baab040725d56 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75349] [UI] No animations/transitions shown in remote control app
https://bugs.documentfoundation.org/show_bug.cgi?id=75349 YoWhatsappAPK changed: What|Removed |Added URL||https://yowhatsapp.org --- Comment #25 from YoWhatsappAPK --- Thank you for sharing such a wonderful and informative article with us. It was very interesting. Although the topic is usually interesting, your interesting writing makes it even more interesting. Thank you again for all you do! Also Fouad WhatsApp APK is a modified version of WhatsApp Messenger https://yowhatsapp.org;>YOWhatsapp latste versie downloaden https://fouadwhatsapp.in;>Fouad WhatsApp APK download (Official) https://fouadwhatsapp.id;>Fouad WhatsApp APK (Anti-Ban) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148717] Calc - Form Control - URL link BUTTONs "lost" when column inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=148717 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 151167] All potentially very long operations should be cancellable.
https://bugs.documentfoundation.org/show_bug.cgi?id=151167 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 148563] Cannot embed a zip file using OLE
https://bugs.documentfoundation.org/show_bug.cgi?id=148563 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 147279] DDE link from Pivot Table to Writer loses CR and LF control characters
https://bugs.documentfoundation.org/show_bug.cgi?id=147279 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 151412] window opening problems
https://bugs.documentfoundation.org/show_bug.cgi?id=151412 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151157] When odf saved to network location Read Error. Format error discovered in the file in sub-document styles.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=151157 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 151162] Inserting a Word Joiner Unicode character doesn't always prevent a line break from occurring
https://bugs.documentfoundation.org/show_bug.cgi?id=151162 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 151412] window opening problems
https://bugs.documentfoundation.org/show_bug.cgi?id=151412 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147917] Scatter graph values are wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=147917 --- Comment #6 from QA Administrators --- Dear Kuba Orlik, 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 147917] Scatter graph values are wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=147917 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148204] Indenting Wrong for Ordered List
https://bugs.documentfoundation.org/show_bug.cgi?id=148204 --- Comment #7 from QA Administrators --- Dear Jens-D Doll, 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 98947] PIVOTTABLE: Drilling after sorting returns unsorted "drill" results
https://bugs.documentfoundation.org/show_bug.cgi?id=98947 --- Comment #4 from QA Administrators --- Dear datakid, 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 93992] Typos in Calc function names and error codes, test documents for different releases, load to check localized versions.
https://bugs.documentfoundation.org/show_bug.cgi?id=93992 --- Comment #27 from QA Administrators --- Dear Daniel Rentz, 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 93611] Spell checker does not treat many characters normally not part of words in the language being verified as separators
https://bugs.documentfoundation.org/show_bug.cgi?id=93611 --- Comment #13 from QA Administrators --- Dear andréb, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90142] Recovery gets to the point of "successful". After "Finish" is pressed, Writer aborts.
https://bugs.documentfoundation.org/show_bug.cgi?id=90142 --- Comment #8 from QA Administrators --- Dear Paul Roos, 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 58452] FILEOPEN: docx embedded image object does not show up
https://bugs.documentfoundation.org/show_bug.cgi?id=58452 --- Comment #13 from QA Administrators --- Dear A.S., 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 48610] FILEOPEN: tables content shown as text from .doc and not shown from .docx if created in Text Box inside Drawing Canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=48610 --- Comment #20 from QA Administrators --- Dear Sergey, 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 51127] FILEOPEN: .DOC file leaves blank page in middle (page 2) of four page document - per Comment 7 (also if resaved in MSO as DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=51127 --- Comment #13 from QA Administrators --- Dear Jerry Heyman, 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 44195] First row of data added to XYDiagram is interpretted as Y-Values rather than X-Values
https://bugs.documentfoundation.org/show_bug.cgi?id=44195 --- Comment #8 from QA Administrators --- Dear Toby, 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 133173] Calc creates a wrong result when I use "Drill to details" option in Pivot table
https://bugs.documentfoundation.org/show_bug.cgi?id=133173 --- Comment #4 from QA Administrators --- Dear Roman Kuznetsov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36999] DOCX import: For hidden ActiveX control, the replacement wmf is always shown
https://bugs.documentfoundation.org/show_bug.cgi?id=36999 --- Comment #21 from QA Administrators --- Dear Tobias Burnus, 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 131166] if Excel .xlsx spreadsheet FILESAVE to .ods file some FORMATTING is changed rendering spreadsheet unusable
https://bugs.documentfoundation.org/show_bug.cgi?id=131166 --- Comment #5 from QA Administrators --- Dear Juha Ahtiainen, 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 130796] FILESAVE: Font changes when saving ODS file to XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=130796 --- Comment #3 from QA Administrators --- Dear Kevin Suo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 127684] FILESAVE: XLSX: Date field lost on save (calc)
https://bugs.documentfoundation.org/show_bug.cgi?id=127684 --- Comment #6 from QA Administrators --- Dear Michael Nattinger, 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 127589] Filesave XLSX: Missing data in two graphs that were shown before
https://bugs.documentfoundation.org/show_bug.cgi?id=127589 --- Comment #14 from QA Administrators --- Dear Timur, 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 126815] Calc-diagonal cell border xlsx file
https://bugs.documentfoundation.org/show_bug.cgi?id=126815 --- Comment #21 from QA Administrators --- Dear Andrzej, 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 126702] XLSX FILEOPEN Issues with partially grouped pivot table fields in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=126702 --- Comment #5 from QA Administrators --- Dear Aron Budea, 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 116992] Libreoffice on macOS update dialog starts download, enables install button and crashes on button press
https://bugs.documentfoundation.org/show_bug.cgi?id=116992 --- Comment #7 from QA Administrators --- Dear steve -_-, 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 125860] FILEOPEN XLSX: separate options for display/print Zero values | Set print-zero as in XLSX during import
https://bugs.documentfoundation.org/show_bug.cgi?id=125860 --- Comment #5 from QA Administrators --- Dear Tobias Burnus, 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 98067] Menu bar and right tool bar are invisible, but functional in high-contrast-mode/theme
https://bugs.documentfoundation.org/show_bug.cgi?id=98067 --- Comment #33 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-3": https://git.libreoffice.org/core/commit/49f5b1a2750ec8f20d983c91ee99cb056a536901 tdf#98067 get menu readable in windows high contrast mode It will be available in 7.3.7. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98067] Menu bar and right tool bar are invisible, but functional in high-contrast-mode/theme
https://bugs.documentfoundation.org/show_bug.cgi?id=98067 Commit Notification changed: What|Removed |Added Whiteboard|target:7.5.0 target:7.4.3 |target:7.5.0 target:7.4.3 ||target:7.3.7 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98067] Menu bar and right tool bar are invisible, but functional in high-contrast-mode/theme
https://bugs.documentfoundation.org/show_bug.cgi?id=98067 --- Comment #32 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/75fd9e5a6947bc370cf230afe32bbf755a91e2ea Related: tdf#98067 get high contrast hover/default button text color right It will be available in 7.4.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151430] Groupedbar Compact UI : missing "columns..." entry of the "format" menu of the menu bar
https://bugs.documentfoundation.org/show_bug.cgi?id=151430 V Stuart Foote changed: What|Removed |Added CC||kain...@gmail.com, ||vstuart.fo...@utsa.edu --- Comment #1 from V Stuart Foote --- Confirm that the .uno:FormatColumns command is not available in the Notebookbar's 'Groupedbar Compact' MUFFIN assemblage. But not clear the dialog is really needed, Table Properties dialog (.uno:TableDialog) provides comparable function. @Andreas? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151431] CONFIGURATION Emoji toolbar button doesn't appear when activated
https://bugs.documentfoundation.org/show_bug.cgi?id=151431 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from V Stuart Foote --- The Emoji picker widget is an experimental feature so requires the Tools -> Options -> Advanced 'Enable experimental features (may be unstable' check box be set active. However, the emoji.json feature has been removed for the 7.5 branch of current master as unsupported and unnecessary as the os/DE provide suitable Emoji selection, see bug 151197 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135543] Writer auto spellcheck works intermittently
https://bugs.documentfoundation.org/show_bug.cgi?id=135543 Rajasekaran Karunanithi changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #13 from Rajasekaran Karunanithi --- I opened a document in writer and tried some misspelled words and sentences when Automatic Spell checking was ON. It showed those red underlines every time I tried some misspelled words. I tested in the latest LO 7.4.1.2 (x64) version with build :3c58a8f3a960df8bc8fd77b461821e42c061c5f0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96000] [META] Spelling and grammar checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=96000 Bug 96000 depends on bug 135543, which changed state. Bug 135543 Summary: Writer auto spellcheck works intermittently https://bugs.documentfoundation.org/show_bug.cgi?id=135543 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable
https://bugs.documentfoundation.org/show_bug.cgi?id=141586 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1427 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151427] Writer is not opening at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=151427 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||1586 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151407] Pressing and holding ctrl+o opens multiple file open dialogs
https://bugs.documentfoundation.org/show_bug.cgi?id=151407 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #5 from raal --- No repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: a0bc0cc81b597aa81189355a8125753d6b873cce CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Xorg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125543] unmaximizing the window reduces to minimal width and height, making window barely visible (Linux-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=125543 --- Comment #35 from stragu --- The only way I consistently reproduce this bug is by following steps similar to comment 10, when opening a LibreOffice component involves getting through a dialog first. For example: 1. open Calc 2. maximise the window 3. close Calc 4. Open a CSV file with Calc 5. Once passed the import dialog, unmaximise (aka "restore down") the Calc window But also: 1. open Base 2. maximise the window 3. close Base 4. Open Base again 5. Once passed the database creation dialog, unmaximise (aka "restore down") the Base window Result: the windows is tiny. However, it is possible to resize the window to an extremely small size in any LO component. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Bug 80430 depends on bug 133156, which changed state. Bug 133156 Summary: Improved help information needed for Calc Solvers https://bugs.documentfoundation.org/show_bug.cgi?id=133156 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133156] Improved help information needed for Calc Solvers
https://bugs.documentfoundation.org/show_bug.cgi?id=133156 Olivier Hallot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151417] Editing with Draw, activating Form controls, selecting one, LO crash without code number.
https://bugs.documentfoundation.org/show_bug.cgi?id=151417 raal changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected CC||noelgran...@gmail.com, ||r...@post.cz Regression By||Noel Grandin --- Comment #4 from raal --- This seems to have begun at the below commit. Adding Cc: to Noel Grandin ; Could you possibly take a look at this one? Thanks 6f10bfc3f53a7d88037a32deadcc7f3be94c061e is the first bad commit commit 6f10bfc3f53a7d88037a32deadcc7f3be94c061e Author: Jenkins Build User Date: Mon Aug 29 14:09:10 2022 +0200 source sha:8611f6e259b807b4f19c8dc0eab86ca648891ce3 https://git.libreoffice.org/core/+/8611f6e259b807b4f19c8dc0eab86ca648891ce3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151424] Spider web chart drawing error since LO Calc version 7.4.1.2
https://bugs.documentfoundation.org/show_bug.cgi?id=151424 raal changed: What|Removed |Added Keywords||bibisected, bisected Regression By||Noel Grandin CC||noelgran...@gmail.com, ||r...@post.cz --- Comment #4 from raal --- This seems to have begun at the below commit. Adding Cc: to Noel Grandin ; Could you possibly take a look at this one? Thanks 81c08fbea6b2e21217f88b82428b4aa07e8d8671 is the first bad commit commit 81c08fbea6b2e21217f88b82428b4aa07e8d8671 Author: Jenkins Build User Date: Sat Feb 5 22:08:06 2022 +0100 source sha:333ccb081b4ab62adce50ca4c93162b9baf984d0 https://git.libreoffice.org/core/+/333ccb081b4ab62adce50ca4c93162b9baf984d0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151119] Font (family) selection UI elements should allow searching by substring
https://bugs.documentfoundation.org/show_bug.cgi?id=151119 --- Comment #5 from Cor Nouws --- (In reply to Heiko Tietze from comment #4) > We discussed the topic in the design meeting. > > There is agreement to change the behavior in the dialog and filter the list > of font when text is being entered (would start with three letters minimum). > > Doing the same for dropdown controls is desirable but means to change the > behavior completely since we currently just autocomplete. Similar request in > bug 139099 was rejected as the effort bears no relation to the benefit. Good to see the investigation done here :)! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103537] [META] High contrast mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103537 Bug 103537 depends on bug 124672, which changed state. Bug 124672 Summary: Hi-Contrast mode should use Sifr dark icons, not Sifr https://bugs.documentfoundation.org/show_bug.cgi?id=124672 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47295] Paragraph style used for the single paragraph in a new Writer file, should be "Text body" and not "Default"
https://bugs.documentfoundation.org/show_bug.cgi?id=47295 --- Comment #45 from Cor Nouws --- (In reply to Miklos Vajna from comment #44) > I agree that Writer's default vs text body choice is inconsistent; Word just > uses Normal for both initial para style and after heading. How ugly :) > Improving > consistency in this area sounds useful. If this is just a UI change for new > documents, I expect no problems. Thanks Miklos! Any code hints? Possibly easyHack? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69724] There is no ability to set/configure the default number/bullet styles
https://bugs.documentfoundation.org/show_bug.cgi?id=69724 --- Comment #18 from Cor Nouws --- (In reply to Heiko Tietze from comment #17) > Please add the keyword needsUXEval along with CC ux-advice@ - I need to remind that - apologies. >and a question > for the UX people. Don't see an open question here. Please cast your votes ;) > +1 for the hierarchy in list styles, +1 to a new topic. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151429] DDE link drops Unicode characters not representable in Windows system encoding
https://bugs.documentfoundation.org/show_bug.cgi?id=151429 Mike Kaganski changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED OS|All |Windows (All) --- Comment #1 from Mike Kaganski --- https://gerrit.libreoffice.org/c/core/+/141125 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151431] New: CONFIGURATION Emoji toolbar button doesn't appear when activated
https://bugs.documentfoundation.org/show_bug.cgi?id=151431 Bug ID: 151431 Summary: CONFIGURATION Emoji toolbar button doesn't appear when activated Product: LibreOffice Version: 7.4.1.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: s...@riseup.net Description: "Emoji" toolbar button available in 'Assigned Commands' but, when activated, does not appear in toolbar. Steps to Reproduce: 1. Right-click on the toolbar and select 'Customize Toolbar'. Customize window opens on Toolbars tab. On the right side of the window, under "Assigned Commands" is an option to enable "Emoji" button. 2. Select (put checkmark in) "Emoji" option. 3. Push OK button. Actual Results: Emoji button does not appear in toolbar. Expected Results: Emoji button appears (after Symbol button, for example). Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Also if I happen to remove Emoji button from the "Assigned Commands" by clicking the Left Arrow button, the command is lost and doesn't even appear in the list of "Available Commands". Can get it to reappear in the Assigned Commands by Defaults or Reset button. Workaround is to use the Symbol button then click More Characters button and pick the Noto Color Emoji (or other) font. Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Debian package version: 1:7.4.1-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151430] Groupedbar Compact UI : missing "columns..." entry of the "format" menu of the menu bar
https://bugs.documentfoundation.org/show_bug.cgi?id=151430 Jérôme changed: What|Removed |Added Blocks||107158 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107158 [Bug 107158] [META] Notebookbar Groupedbar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107158] [META] Notebookbar Groupedbar
https://bugs.documentfoundation.org/show_bug.cgi?id=107158 Jérôme changed: What|Removed |Added Depends on||151430 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151430 [Bug 151430] Groupedbar Compact UI : missing "columns..." entry of the "format" menu of the menu bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151430] New: Groupedbar Compact UI : missing "columns..." entry of the "format" menu of the menu bar
https://bugs.documentfoundation.org/show_bug.cgi?id=151430 Bug ID: 151430 Summary: Groupedbar Compact UI : missing "columns..." entry of the "format" menu of the menu bar Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jerome.bo...@laposte.net -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151413] Unable to create a DDE link to a file with special characters in name on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=151413 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1429 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151429] New: DDE link drops Unicode characters not representable in Windows system encoding
https://bugs.documentfoundation.org/show_bug.cgi?id=151429 Bug ID: 151429 Summary: DDE link drops Unicode characters not representable in Windows system encoding Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com 1. Create a Calc document, and put some text into A1, including some Cyrillic and Japanese: e.g., "テストabcабв" 2. Save it as ODS 3. Select A1, and copy to clipboard 4. Create a Writer document, and Paste Special -> as DDE Link. The pasted data turns all the characters not representable in current system encoding into question marks. This means that on most Linux systems, having Unicode as system encoding, everything would arrive OK; but on Windows, the text will arrive with the question marks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151414] libre office is not opening
https://bugs.documentfoundation.org/show_bug.cgi?id=151414 --- Comment #7 from elias estatistics --- Trying to set the 4 last values to different values than 0, a new line present inside the file. Trying to change the same 4-last values other than 0, but, now this line does not keep these new values. In exit, override them with zeroes. 0,0,1,1;5;3,3,3,3; 0,0,1,1;5;0,0,0,0; -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151414] libre office is not opening
https://bugs.documentfoundation.org/show_bug.cgi?id=151414 --- Comment #6 from elias estatistics --- Yes this was the bug! How i can stop from populate each time in user profile? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151414] libre office is not opening
https://bugs.documentfoundation.org/show_bug.cgi?id=151414 --- Comment #5 from elias estatistics --- I found the culprit i think! inside user profile, the file "registrymodifications.xcu" contains a line that says: 0,0,1,1;5;0,0,0,0; So this line is creating the bug in KDE. I was deleting lines from "xcu" until i found the culprit. If this line is present, LO is not appearing, if not, appearing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151414] libre office is not opening
https://bugs.documentfoundation.org/show_bug.cgi?id=151414 --- Comment #4 from elias estatistics --- NO no no! after deleting user profile, it runs. closing it, and then not running again. Same bug! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151414] libre office is not opening
https://bugs.documentfoundation.org/show_bug.cgi?id=151414 --- Comment #3 from elias estatistics --- Created attachment 182919 --> https://bugs.documentfoundation.org/attachment.cgi?id=182919=edit user profile bug Removing user profile fixed that bug. I debugged further the behaviour. I copied back my profile, same behaviour (hanging) I played with removing elements inside user folder. One time i remove all things except registrymodifications.xcu Same bug behaviour. So i upload to check what is going wrong, cause i like my user profile! And maybe help to improve libreoffice profile bugs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150743] [Editing] Horizontal line will disappear while setting position and height through sidebar if "Keep ratio" is set.
https://bugs.documentfoundation.org/show_bug.cgi?id=150743 --- Comment #16 from Jean-Baptiste Faure --- I see the same behavior with LO 6.4.7. What you are highlighting is that the notion of a rectangle surrounding a drawing object, defined by its width and height, is not adapted to the case of a horizontal or vertical line. In the case where "Keep ratio" is checked, we just have a special case here that involves a division by zero. Best regards. JBF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147279] DDE link from Pivot Table to Writer loses CR and LF control characters
https://bugs.documentfoundation.org/show_bug.cgi?id=147279 Mike Kaganski changed: What|Removed |Added CC||er...@redhat.com --- Comment #1 from Mike Kaganski --- Code pointer: This is done explicitly in ScServerObject::GetData [1]: > aObj.SetExportTextOptions( ScExportTextOptions( ScExportTextOptions::ToSpace, > ' ', false ) ); No idea what could break - looks like there may be opposite expectations in some people, who prefer the current way, or maybe it's simply the code that is used in very different scenarios? Eike, do you have an idea? [1] https://opengrok.libreoffice.org/xref/core/sc/source/ui/docshell/servobj.cxx?r=8930b1f6#195 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151428] New: when pressing enter to move 10-12 tables downwards, it lags ~20-30secs vs ~1sec.
https://bugs.documentfoundation.org/show_bug.cgi?id=151428 Bug ID: 151428 Summary: when pressing enter to move 10-12 tables downwards, it lags ~20-30secs vs ~1sec. Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: elias__0...@yahoo.com Created attachment 182918 --> https://bugs.documentfoundation.org/attachment.cgi?id=182918=edit bug_lag_enter_tables when pressing enter to move 10-12 tables downwards, it lags ~20-30secs vs ~1sec. Go to page 4 under table. Press 10 times ENTER. You will see that it will be a lagged. You cannot do anything for the next 15-30sec. Version: 7.4.1.2 / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Distributor ID: Debian Description:Debian GNU/Linux 11 (bullseye) Release:11 Codename: bullseye -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151414] libre office is not opening
https://bugs.documentfoundation.org/show_bug.cgi?id=151414 --- Comment #2 from elias estatistics --- I dont know when it is hunging. possibly, profile may play a role. But as a user, i cant explain why it can be run while running a much older version of it. This means that some subprocesses are confused between libreoffice versions? or something remain in the ram? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151407] Pressing and holding ctrl+o opens multiple file open dialogs
https://bugs.documentfoundation.org/show_bug.cgi?id=151407 --- Comment #4 from Jean-Baptiste Faure --- (In reply to Hossein from comment #3) > Can you test and see if the problem is reproducible when > selecting/deselecting this option? > > Tools > Options > General > Open/Save Dialogs > Use LibreOffice dialogs That doesn't make any difference. Do you use Xorg or Wayland session ? Best regards. JBF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148717] Calc - Form Control - URL link BUTTONs "lost" when column inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=148717 raal changed: What|Removed |Added Version|7.2.6.2 release |4.1.0.4 release --- Comment #4 from raal --- Repro with Version 4.1.0.0.alpha0+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148717] Calc - Form Control - URL link BUTTONs "lost" when column inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=148717 raal changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from raal --- reproducible with X11 Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: a0bc0cc81b597aa81189355a8125753d6b873cce CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: x11 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148717] Calc - Form Control - URL link BUTTONs "lost" when column inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=148717 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #2 from raal --- No repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: a0bc0cc81b597aa81189355a8125753d6b873cce CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51868] "Find Record": search through all subforms
https://bugs.documentfoundation.org/show_bug.cgi?id=51868 --- Comment #3 from Michael --- I confirm the issue for version 6.4.7.2 and Version: 7.3.6.2 / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded Without an improvement, e.g speed up the searches, BASE is almost useless for normal users. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 44954] delegate search to the database
https://bugs.documentfoundation.org/show_bug.cgi?id=44954 Michael changed: What|Removed |Added CC||mailinglis...@kmhessler.de --- Comment #17 from Michael --- I confirm the issue for version 6.4.7.2 and Version: 7.3.6.2 / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded May be, it's related to [51868](https://bugs.documentfoundation.org/show_bug.cgi?id=51868), nevertheless it's very important to get fixed. Without an improvement, e.g speed up the searches, BASE is almost useless for normal users. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151427] New: Writer is not opening at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=151427 Bug ID: 151427 Summary: Writer is not opening at last cursor position Product: LibreOffice Version: 7.3.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gddel...@gmail.com This is an on-going, off-going problem. It gets fixed, and then re-appears in some subsequent release. I mean, how many times must we see the same basic problem? I have all the user data completed, it has been like that for years. Returning the cursor to the position it was at when closed has been working in the past. Please don't ask me to do backward re-installs to determine what the last 'working' version was, not gonna happen. I'm on 7.3.2.2 Windows 64bit, and I 'think' the problem re-appeared within the last 2-3 releases. I ignored it for a while assuming it was an 'oops' type error and would quickly be repaired. It's an annoying little bug, but reflects poorly on LibreOffice that it keeps re-appearing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151424] Spider web chart drawing error since LO Calc version 7.4.1.2
https://bugs.documentfoundation.org/show_bug.cgi?id=151424 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||regression CC||miguelangelrv@libreoffice.o ||rg OS|Linux (All) |All --- Comment #3 from m.a.riosv --- Reproducible Version: 7.4.2.1 (x64) / LibreOffice Community Build ID: 681d65acd9ede00dd724d6716f21cabfdcc95bd2 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL and masster Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 6834fda784f3066a89838cd6cda4fe945f4c7904 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Regression form Version: 7.3.6.2 (x64) / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142783] SELECTING Date Field dropdown causes 'When losing focus' event.
https://bugs.documentfoundation.org/show_bug.cgi?id=142783 raal changed: What|Removed |Added CC||r...@post.cz Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Keywords||regression --- Comment #7 from raal --- Please make test file and provide steps to reproduce. Date dropdown is probably some content control, but I don't know which one. For easy reproduction add some trivial macro (msgbox for example) to When losing Focus event. Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148563] Cannot embed a zip file using OLE
https://bugs.documentfoundation.org/show_bug.cgi?id=148563 raal changed: What|Removed |Added Status|UNCONFIRMED |NEW OS|Windows (All) |All Blocks||107810 Ever confirmed|0 |1 CC||r...@post.cz --- Comment #1 from raal --- Reproducible with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: a0bc0cc81b597aa81189355a8125753d6b873cce CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Tested in Version 4.1.0.0.alpha0+ and the problem is the same, only LO offers Filter selection dialog. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107810 [Bug 107810] [META] OLE/Embedded object bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107810] [META] OLE/Embedded object bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107810 raal changed: What|Removed |Added Depends on||148563 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148563 [Bug 148563] Cannot embed a zip file using OLE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151426] New: Feature request: extend IFERROR/IFNA to other predicates
https://bugs.documentfoundation.org/show_bug.cgi?id=151426 Bug ID: 151426 Summary: Feature request: extend IFERROR/IFNA to other predicates Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: obscur...@gmail.com Description: One great feature of LibreOffice over OpenOffice is the existence of IFERROR and ISNA. The documentation notes: `=IFERROR(X; Y)` is semantically equivalent to `=IF(ISERROR(X); Y; X)`, except that the former case is more efficient because `X` is only computed once. This is an extremely common use pattern that is not limited to errors - it's providing a default value when the result doesn't fit an expected type. I have personal use cases for the equivalent of IFBLANK, IFNONTEXT, IFNONNUMBER, and these shouldn't be too difficult to implement, giving a real performance (and readability) benefit. In a different direction, the complete generalization is validate-or-default, which takes three arguments: `VALIDATE(PRED, X, Y) === IF(PRED(X),X,Y)` which guarantees X is evaluated once. This would subsume all of the above and then some, provided function references exist. Actual Results: Expected Results: Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151425] New: LIBRE OFFICE WRITER Crashes when scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=151425 Bug ID: 151425 Summary: LIBRE OFFICE WRITER Crashes when scrolling Product: LibreOffice Version: 7.4.1.2 release Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: studiowh...@hotmail.com Description: I have two WRITER documents open one. The main one which is 52 pages is the one I'm using to scroll through to read a script. Twice it's crashed upon scrolling and I have to keep saving every change to make sure the "saved" version is up-to-date when I restart. =shane= Steps to Reproduce: 1. Open 2 documents 2. Scroll...add comments (I guess...as that's why I was doing) 3. Continue scrolling Actual Results: LibreOffice Writer freezes and then shuts down. Expected Results: It should just scroll and let me keep working. Reproducible: Always User Profile Reset: Yes Additional Info: Restarting in SAFEMODE makes scrolling very choppy. The window delays in catching up with the scrolling. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151424] Spider web chart drawing error since LO Calc version 7.4.1.2
https://bugs.documentfoundation.org/show_bug.cgi?id=151424 --- Comment #2 from H077e --- Created attachment 182917 --> https://bugs.documentfoundation.org/attachment.cgi?id=182917=edit sample Calc file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151424] Spider web chart drawing error since LO Calc version 7.4.1.2
https://bugs.documentfoundation.org/show_bug.cgi?id=151424 --- Comment #1 from H077e --- Created attachment 182916 --> https://bugs.documentfoundation.org/attachment.cgi?id=182916=edit correctly labeled chart - version 6.1.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151424] Spider web chart drawing error since LO Calc version 7.4.1.2
https://bugs.documentfoundation.org/show_bug.cgi?id=151424 H077e changed: What|Removed |Added Attachment #182915|incorrectly labeled chat|incorrectly labeled chart description|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151424] New: Spider web chart drawing error since LO Calc version 7.4.1.2
https://bugs.documentfoundation.org/show_bug.cgi?id=151424 Bug ID: 151424 Summary: Spider web chart drawing error since LO Calc version 7.4.1.2 Product: LibreOffice Version: 7.4.1.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: web...@minimalmail.de Created attachment 182915 --> https://bugs.documentfoundation.org/attachment.cgi?id=182915=edit incorrectly labeled chat After the upgate to version 7.4.1.2, spider web charts are labeled incorrectly. Source is the same Calc file. Before version 7.4.1.2 is the chart correctly labeled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151414] libre office is not opening
https://bugs.documentfoundation.org/show_bug.cgi?id=151414 Rainer Bielefeld Retired changed: What|Removed |Added OS|All |Linux (All) CC||LibreOffice@bielefeldundbus ||s.de --- Comment #1 from Rainer Bielefeld Retired --- @Reporter: Please try again after having renamed your LibO User Profile (So that LibO creates a new one). And tell your results. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143750] Missing or extra parentheses and/or quotation marks function no longer works in version 7.2.0.2.
https://bugs.documentfoundation.org/show_bug.cgi?id=143750 --- Comment #7 from Marco A.G.Pinto --- Sorry, too stressed to think. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143754] No Help page for Tools > Options… > Language settings > English Sentence Checking in 7.2.0.2.
https://bugs.documentfoundation.org/show_bug.cgi?id=143754 --- Comment #7 from Marco A.G.Pinto --- Right now, I am stressed and can't think properly… sorry. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151174] sidebar transparency slider isn't hidden when it does not apply
https://bugs.documentfoundation.org/show_bug.cgi?id=151174 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8150 Regression By||Samuel Mehrbrodt Hardware|x86-64 (AMD64) |All Keywords|bibisectRequest |bibisected, bisected OS|Linux (All) |All --- Comment #2 from Aron Budea --- This is a regression from the following commit, bibisected using repo bibisect-linux-64-7.5. Adding CC: to Samuel Mehrbrodt. https://cgit.freedesktop.org/libreoffice/core/commit/?id=adc536e9efc77690df62177aa722f9252bdbf96b author Samuel Mehrbrodt 2022-06-23 10:10:11 +0200 committer Samuel Mehrbrodt 2022-06-24 08:12:25 +0200 tdf#128150 Properly show/hide widgets when "use slide background" is selected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151423] New: Unintended zoom in or out on command key press if Calc is still scrolling.
https://bugs.documentfoundation.org/show_bug.cgi?id=151423 Bug ID: 151423 Summary: Unintended zoom in or out on command key press if Calc is still scrolling. Product: LibreOffice Version: 7.3.6.2 release Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: t.lue...@nets.de Description: see steps to Reproduce As the command key is used on mac to switch apps it is very annoying when you com back to calc it is totally zoomed in or out. Steps to Reproduce: 1. start scrolling via touchpad by two finger gesture 2. press command key while calc is still scrolling, but you have stopped touching the touchpad 3. Calc start zooming in or out depending on which way it is still scrolling. Actual Results: Calc zoom in or out Expected Results: Calc should only start zooming in or out if the command key was presst before the scrolling was started. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.3.6.2 / LibreOffice Community Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e CPU threads: 10; OS: Mac OS X 12.6; UI render: default; VCL: osx Locale: de-DE (en_DE.UTF-8); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127250] [META] Text formatting issues when inserting or overwriting
https://bugs.documentfoundation.org/show_bug.cgi?id=127250 Bug 127250 depends on bug 71481, which changed state. Bug 71481 Summary: Clone formatting appends copied formatting rather than overwriting applied formatting https://bugs.documentfoundation.org/show_bug.cgi?id=71481 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114912] [META] Clone formatting (aka Format Paintbrush) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114912 Bug 114912 depends on bug 71481, which changed state. Bug 71481 Summary: Clone formatting appends copied formatting rather than overwriting applied formatting https://bugs.documentfoundation.org/show_bug.cgi?id=71481 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71481] Clone formatting appends copied formatting rather than overwriting applied formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=71481 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #24 from Buovjaga --- Good news: this is fixed by https://git.libreoffice.org/core/commit/259ed2e3a135a5650fd321f408382d6b1b86bcad sw: fix format brush to override old format Thanks, Szymon! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151422] New: LibreOffice hangs on MacOs when working woith more than one document
https://bugs.documentfoundation.org/show_bug.cgi?id=151422 Bug ID: 151422 Summary: LibreOffice hangs on MacOs when working woith more than one document Product: LibreOffice Version: 7.0 all versions Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: i...@knowhow-la.de Description: On MacOS when working with more than one open Document - in my case a database document and one or two Writer- or Draw- documents after a while, which can be 2 minutes or 15 minutes LibreOffice, the spinning waterball appears an LibreOffice hangs. Nothing, but quitting LO helps. The behaviour is the same since MacOs BigSur and LibreOffice 7.0. Steps to Reproduce: 1.Open a Base document and a Writer or Draw document 2.Change between both or all ducuments for some time 3. Actual Results: The spinning waterball appears and LibreOffice won't recover from it. Expected Results: LibreOffice will hang after some time - the duration until hanging ranges from just a few seconds to 15 minutes Reproducible: Always User Profile Reset: Yes Additional Info: Not hang -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149840] FILEOPEN DOCX SmartArt background shape has wrong size
https://bugs.documentfoundation.org/show_bug.cgi?id=149840 --- Comment #5 from Regina Henschel --- I have tried to set the size by setting the logicRect of the background shape around line#974 in writerfilter/source/dmapper/GraphicImport.cxx. That gives indeed a correct size of the background shape, but the size if the SmartArt shapes are still wrong. So this is likely the wrong place for a fix. For testing use a SmartArt with non default shape width or height in the SmartArt components. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151421] Installer can't delete Desktop Shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=151421 bugzil...@cb-computerservice.at changed: What|Removed |Added CC||bugzilla2@cb-computerservic ||e.at --- Comment #1 from bugzil...@cb-computerservice.at --- Created attachment 182914 --> https://bugs.documentfoundation.org/attachment.cgi?id=182914=edit The whole uninstall logfile (zipped) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151412] window opening problems
https://bugs.documentfoundation.org/show_bug.cgi?id=151412 --- Comment #5 from Paolo --- Libreoffice è installato su una versione pulita di Kubuntu. Il test in modalità provvisoria non presenta il problema. Ma appena si riapre lo stesso file per la seconda volta il problema si poresenta. Solo libre presenta il problema. Nessuna altra applicazione ha questo problema Libreoffice is installed on a clean version of Kubuntu. Testing in safe mode does not present the problem. But as soon as you reopen the same file for the second time, the problem occurs. Only libre presents the problem. No other application has this problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150995] Error during Installation – Installers says no access to file “*.rbf”
https://bugs.documentfoundation.org/show_bug.cgi?id=150995 bugzil...@cb-computerservice.at changed: What|Removed |Added Resolution|NOTOURBUG |MOVED Depends on||151421 --- Comment #6 from bugzil...@cb-computerservice.at --- Since this is clearly an uninstall issue and no install-issue, I made a new bug to not start into the process that confusing :D -> Bug 151421 - Installer can't delete Desktop Shortcut (edit) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151421 [Bug 151421] Installer can't delete Desktop Shortcut -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151421] Installer can't delete Desktop Shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=151421 bugzil...@cb-computerservice.at changed: What|Removed |Added Blocks||150995 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150995 [Bug 150995] Error during Installation – Installers says no access to file “*.rbf” -- You are receiving this mail because: You are the assignee for the bug.
