[Libreoffice-bugs] [Bug 143948] Clone formatting tool doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=143948 Evgenija Chumachenko changed: What|Removed |Added CC||evgenija...@gmail.com --- Comment #1 from Evgenija Chumachenko --- No repo in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 3c0c1b79b689775f09b3bff75bb01118b380f41f CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (ru_RU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96852] Calc: Add option in "Move/Copy Sheet..." to another workbook for copying page format
https://bugs.documentfoundation.org/show_bug.cgi?id=96852 Timur changed: What|Removed |Added Severity|normal |enhancement Summary|FORMATTING: "Move/Copy |Calc: Add option in |Sheet..." not copying page |"Move/Copy Sheet..." to |format |another workbook for ||copying page format --- Comment #9 from Timur --- This can only be an enhancement to have an option, not the change that would force it. So I retitle, in accordance with comment 1. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37511] copy-paste from Draw to Writer results appearing unexpected styles
https://bugs.documentfoundation.org/show_bug.cgi?id=37511 --- Comment #18 from Rainer Bielefeld Retired --- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53961] OLE attachment of .doc file doesn't appear in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=53961 --- Comment #12 from vga...@gmail.com --- The problem still present. Version: 7.2.0.3 (x64) / LibreOffice Community Build ID: 2a7ea282da28d665a7dc086360567b4aea27bf08 CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75057] [META] OOXML Chart object issues
https://bugs.documentfoundation.org/show_bug.cgi?id=75057 Bug 75057 depends on bug 142264, which changed state. Bug 142264 Summary: charts lost by calc export to xlsx https://bugs.documentfoundation.org/show_bug.cgi?id=142264 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143947] Function DATE yields wrong year if input is only "year"
https://bugs.documentfoundation.org/show_bug.cgi?id=143947 --- Comment #2 from Henrik Palomäki --- It seems a value in DATE function defaults to 0 if no number is given. It seems MS Excel acts in the same way. Should the default value be 1 instead of 0? In that case the expected result for the all given examples should be 2006-01-01. Currently, the value 0 in DATE function gives the previous value of 1 that is 12 for the case of month and in the case of day it is the last day of previous month. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #10 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143599] Help Buttons for Save Remote Screens are confusing for non technical users
https://bugs.documentfoundation.org/show_bug.cgi?id=143599 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 143725] Unable to register/login to ask.libreoffice
https://bugs.documentfoundation.org/show_bug.cgi?id=143725 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 141810] Impress table doesn't adapt in size after redo (under circumstances)
https://bugs.documentfoundation.org/show_bug.cgi?id=141810 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 143927] : Auto filter - Quick filter does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=143927 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143927] : Auto filter - Quick filter does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=143927 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 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142633] UI: Disabled Textfield flickers
https://bugs.documentfoundation.org/show_bug.cgi?id=142633 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 143730] Spell Checker giving wrong spelling
https://bugs.documentfoundation.org/show_bug.cgi?id=143730 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 141909] Calc: Switching to Read only leaves the lock files in place
https://bugs.documentfoundation.org/show_bug.cgi?id=141909 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 142634] Animation-Object gets unselected upon change.
https://bugs.documentfoundation.org/show_bug.cgi?id=142634 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 135698] Existing user data gets ignored at install
https://bugs.documentfoundation.org/show_bug.cgi?id=135698 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71414] take NUM_PREC_RADIX into account
https://bugs.documentfoundation.org/show_bug.cgi?id=71414 --- Comment #8 from QA Administrators --- Dear Lionel Elie Mamane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#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 135698] Existing user data gets ignored at install
https://bugs.documentfoundation.org/show_bug.cgi?id=135698 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 91330] MSO2013 Template - Fitness Tracker - Incorrect data points type in chart (filled instead of no-fill)
https://bugs.documentfoundation.org/show_bug.cgi?id=91330 --- Comment #7 from QA Administrators --- Dear Jorendc, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 140530] Upon updating to 7.0.4.2 (64) I loaded up one of my previous documents in Draw and half the pictures had been changed to other pictures in the documents, and the format
https://bugs.documentfoundation.org/show_bug.cgi?id=140530 --- Comment #2 from QA Administrators --- Dear hadeslorster, 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 60217] error message limited to a dot when mysql native connector is used
https://bugs.documentfoundation.org/show_bug.cgi?id=60217 --- Comment #16 from QA Administrators --- Dear t.bazin, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 71452] Print area for bottom margin can not be resized as other margins
https://bugs.documentfoundation.org/show_bug.cgi?id=71452 --- Comment #6 from QA Administrators --- Dear gorbot, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 96852] FORMATTING: "Move/Copy Sheet..." not copying page format
https://bugs.documentfoundation.org/show_bug.cgi?id=96852 --- Comment #8 from QA Administrators --- Dear baril_mathieu, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 140536] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=140536 --- Comment #2 from QA Administrators --- Dear Matthias Ronge, 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 53961] OLE attachment of .doc file doesn't appear in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=53961 --- Comment #11 from QA Administrators --- Dear vgango, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 143947] Function DATE yields wrong year if input is only "year"
https://bugs.documentfoundation.org/show_bug.cgi?id=143947 Henrik Palomäki changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Henrik Palomäki --- Reproduced on version 7.3+. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96124] Chart's Text Flow:break doesn't work with Date or Time formatted Cell
https://bugs.documentfoundation.org/show_bug.cgi?id=96124 --- Comment #7 from QA Administrators --- Dear Luke, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 143599] Help Buttons for Save Remote Screens are confusing for non technical users
https://bugs.documentfoundation.org/show_bug.cgi?id=143599 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37511] copy-paste from Draw to Writer results appearing unexpected styles
https://bugs.documentfoundation.org/show_bug.cgi?id=37511 --- Comment #17 from QA Administrators --- Dear sasha.libreoffice, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 126332] "sujet." does not find synonyms because of period
https://bugs.documentfoundation.org/show_bug.cgi?id=126332 --- Comment #3 from QA Administrators --- Dear waynekendall, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 115733] "Open with" dialog menu items have no icons next the name "Libreoffice"
https://bugs.documentfoundation.org/show_bug.cgi?id=115733 --- Comment #7 from QA Administrators --- Dear Al M., 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://kiwiirc.com/nextclient/irc.freenode.net/#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 114498] EDITING: Slow down when editing text in document with content.xml text styles non-existent in styles.xml
https://bugs.documentfoundation.org/show_bug.cgi?id=114498 --- Comment #13 from QA Administrators --- Dear LotusDev, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 127007] Editable field "Data range:" associated with the context menu of any Chart wall treats its list separator badly: Confusion.
https://bugs.documentfoundation.org/show_bug.cgi?id=127007 --- Comment #5 from QA Administrators --- Dear Wolfgang Jäger, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 126941] Date format with frontslashes (15/08/2019) will be changed to format with points (15.08.2019) when input data in a date-field of a tablecontrol of a form.
https://bugs.documentfoundation.org/show_bug.cgi?id=126941 --- Comment #2 from QA Administrators --- Dear Dmitry Mikhailov, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 115292] FILEOPEN open PDF - picture shifted
https://bugs.documentfoundation.org/show_bug.cgi?id=115292 --- Comment #6 from QA Administrators --- Dear solar020, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 111746] Rotation applied on title shape is not removed by resetting the layout
https://bugs.documentfoundation.org/show_bug.cgi?id=111746 --- Comment #10 from QA Administrators --- Dear Tamás Zolnai, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 111403] Text and various lines are shown inconsistently in different scales
https://bugs.documentfoundation.org/show_bug.cgi?id=111403 --- Comment #6 from QA Administrators --- Dear Ruslan Kabatsayev, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 125924] Exporting xls/rhbz499466-2.xls to PDF triggers undefined conversion from NaN to int
https://bugs.documentfoundation.org/show_bug.cgi?id=125924 --- Comment #2 from QA Administrators --- Dear Stephan Bergmann, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 118476] Korean Hanja to Hangul Conversion can't show multiple Korean Hangul Characters
https://bugs.documentfoundation.org/show_bug.cgi?id=118476 --- Comment #11 from QA Administrators --- Dear DaeHyun Sung, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 111796] Tableview doesn't save when scrolled down more than 46rows without saving directly
https://bugs.documentfoundation.org/show_bug.cgi?id=111796 --- Comment #12 from QA Administrators --- Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#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 111508] Text to number conversion on concatenation with direct references ends with number as text.
https://bugs.documentfoundation.org/show_bug.cgi?id=111508 --- Comment #6 from QA Administrators --- Dear m.a.riosv, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 110443] View settings not preserved saving a calc file loaded in hidden mode.
https://bugs.documentfoundation.org/show_bug.cgi?id=110443 --- Comment #6 from QA Administrators --- Dear Luis, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 108756] Alignment and spacing in format options for search and replace does not recognise non incremental numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=108756 --- Comment #11 from QA Administrators --- Dear Antonio CASADO, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 107879] Draw should not prepend a decimal , xx value with zero without leaving the input field
https://bugs.documentfoundation.org/show_bug.cgi?id=107879 --- Comment #9 from QA Administrators --- Dear Roland Illig, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 107614] Chinese characters are wrongly aligned if 'vpal' feature enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=107614 --- Comment #12 from QA Administrators --- Dear Volga, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 143599] Help Buttons for Save Remote Screens are confusing for non technical users
https://bugs.documentfoundation.org/show_bug.cgi?id=143599 --- Comment #2 from Colin --- (In reply to Eleonora Govallo from comment #1) > Hello! > As i understand, if you want to save remote you need to open remote file, > could you clarify did you open the file that you want to save remote, from > the remote server? > First advice in the instruction is how to open remote file that you will > save remote. Remote file save to Google drive isn't working yet - at present, it's just in the testing phase and release to later versions. Therefore, no I didn't open anything as it's not currently possible. This report is merely to define that the help definitions seem to create a circular path and in general, are not easy for a new user - that would be the type of user who most needs clear concise help functions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143599] Help Buttons for Save Remote Screens are confusing for non technical users
https://bugs.documentfoundation.org/show_bug.cgi?id=143599 Colin 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 143930] Amend Help for Remove personal information
https://bugs.documentfoundation.org/show_bug.cgi?id=143930 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | --- Comment #1 from Rafael Lima --- Hi Timur, thanks for reporting. Relevant file is: text/shared/optionen/securityoptionsdialog.xhp I'm taking this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143949] New: Crash in: cppu::OInterfaceContainerHelper::disposeAndClear(com::sun::star::lang::EventObject const &)
https://bugs.documentfoundation.org/show_bug.cgi?id=143949 Bug ID: 143949 Summary: Crash in: cppu::OInterfaceContainerHelper::disposeAndClear(com:: sun::star::lang::EventObject const &) Product: LibreOffice Version: 7.0.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sushee...@gmail.com This bug was filed from the crash reporting server and is br-9cf96505-08af-4291-bbb4-ae4cd2af1a40. = Software crashed while trying to open a print preview -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143948] New: Clone formatting tool doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=143948 Bug ID: 143948 Summary: Clone formatting tool doesn't work Product: LibreOffice Version: 7.1.1.2 release Hardware: All OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: b...@bobswriting.com Description: I downloaded Libre Office for Mac yesterday. Clone formatting tool doesn't work at all. I have checked all instructions and nothing works. Steps to Reproduce: 1. click on paintbrush icon or select format clone from format menu 2.click in paragraph to be changed 3.or use command, or command+shift keys Actual Results: no change in target location Expected Results: change format in target location to that of source location Reproducible: Always User Profile Reset: No Additional Info: I think I have said it all -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141810] Impress table doesn't adapt in size after redo (under circumstances)
https://bugs.documentfoundation.org/show_bug.cgi?id=141810 Eleonora Govallo changed: What|Removed |Added CC||elya.gova...@gmail.com --- Comment #2 from Eleonora Govallo --- No repro in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: adf65471e889676a600a9c6d0454c75cbd549ad3 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-13_04:44:18 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141909] Calc: Switching to Read only leaves the lock files in place
https://bugs.documentfoundation.org/show_bug.cgi?id=141909 Eleonora Govallo changed: What|Removed |Added CC||elya.gova...@gmail.com Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Eleonora Govallo --- Repro in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: adf65471e889676a600a9c6d0454c75cbd549ad3 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-13_04:44:18 Calc: threaded Calc offered me to save changes before closing, but i could editr file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142264] charts lost by calc export to xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=142264 Mike Kaganski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | --- Comment #12 from Mike Kaganski --- https://gerrit.libreoffice.org/c/core/+/120688 This is not actually a true regression, just a pre-existing bug that was only masked by a side effect of charts being incorrectly marked modified on open. This is all about export filter not loading properly the OLE objects that may get unloaded by the memory management in LO. The export reused the obsoleted references to unloaded objects, which couldn't be exported correctly; and I even suspect that existing "IsValidObject" testing chart objects validity in sc/source/filter/xcl97/xcl97rec.cxx might be a hack to "workaround" this actual filter bug. I am thankful to paulystefan for this bug and the nice reproducers, that eventually allowed me to notice the fixed number of object kept in the result. I am suspecting now that there might be a similar problem elsewhere in our code, that could be responsible for many "I lost images in a document" complaints that were impossible to investigate, because there were never a reliable reproducer. Now I suppose that adding a substantial number of different images, while reducing GraphicMemoryLimit (or TotalCacheSize) might allow to find a good reproducing scenario. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142634] Animation-Object gets unselected upon change.
https://bugs.documentfoundation.org/show_bug.cgi?id=142634 Eleonora Govallo changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eleonora Govallo --- *** This bug has been marked as a duplicate of bug 142633 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142633] UI: Disabled Textfield flickers
https://bugs.documentfoundation.org/show_bug.cgi?id=142633 --- Comment #3 from Eleonora Govallo --- *** Bug 142634 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142633] UI: Disabled Textfield flickers
https://bugs.documentfoundation.org/show_bug.cgi?id=142633 --- Comment #2 from Eleonora Govallo --- No repro in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: adf65471e889676a600a9c6d0454c75cbd549ad3 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-13_04:44:18 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143947] New: Function DATE yields wrong year if input is only "year"
https://bugs.documentfoundation.org/show_bug.cgi?id=143947 Bug ID: 143947 Summary: Function DATE yields wrong year if input is only "year" Product: LibreOffice Version: 7.1.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: flavius.chir...@gmail.com When using the DATE function which requires inputs (Year;Month;Day), omitting one or two inputs (i.e. Month/Day or both) yields incorrect output. Is this by design? Explanation would help, otherwise it's a bug, no? Examples: =DATE(2006;;) -> 2005-11-30 incorrect / bug?! =DATE(2006;1;) -> 2005-12-31 incorrect / bug?! =DATE(2006;;1) -> 2005-12-01 incorrect / bug?! =DATE(2006;1;1) -> 2006-01-01 correct Reproducable: new document As usual, please link to duplicates or solutions etc., online search did however not easily find something. Thanks, Greets -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143946] New: Add klingon as a supported language
https://bugs.documentfoundation.org/show_bug.cgi?id=143946 Bug ID: 143946 Summary: Add klingon as a supported language Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Localization Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ferg...@kaivos.org Description: Klingon is one of the most popular constructed languages. I'm currently working on a spell checker for it and would like to make a LibreOffice extension. For this, Klingon needs to be added as a supported language. The ISO 639-3 language code of Klingon is "tlh". It is written from left to right with latin alphabet or its own alphabet. Steps to Reproduce: Change the language of the document. Actual Results: Klingon is not available in the language drop-down menu when choosing the document's language. Expected Results: Klingon is available as a language. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.3.2 Build ID: 10(Build:2) CPU threads: 4; OS: Linux 5.12; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: fi-FI Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143268] Slow response in document with many tables
https://bugs.documentfoundation.org/show_bug.cgi?id=143268 --- Comment #23 from David --- Created attachment 174399 --> https://bugs.documentfoundation.org/attachment.cgi?id=174399=edit perf data Perf data has been attached. Is this the information needed? The data has been recorded while pressing a key twice while within a table. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143945] New: A spreadsheet wants to open up to its maximum size
https://bugs.documentfoundation.org/show_bug.cgi?id=143945 Bug ID: 143945 Summary: A spreadsheet wants to open up to its maximum size Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ahovi@gmail.com Description: A spreadsheet I have used before now wants to open up all the columns and rows! Actual Results: When I open the spreadsheet, I expect it to display about 10 columns and 20 rows, but the rows and columns just keep growing! Incidentally, the dropdown menus are not working. I see the list but when I move my mouse to make a selection, the list disappears! Expected Results: a display of a few columns and rows Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143944] New: A spreadsheet wants to open up to its maximum size
https://bugs.documentfoundation.org/show_bug.cgi?id=143944 Bug ID: 143944 Summary: A spreadsheet wants to open up to its maximum size Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ahovi@gmail.com Description: A spreadsheet I have used before now wants to open up all the columns and rows! Actual Results: When I open the spreadsheet, I expect it to display about 10 columns and 20 rows, but the rows and columns just keep growing! Incidentally, the dropdown menus are not working. I see the list but when I move my mouse to make a selection, the list disappears! Expected Results: a display of a few columns and rows Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143567] Area Style/Filling from Image toolbar doesn't match with sidebar info for Area
https://bugs.documentfoundation.org/show_bug.cgi?id=143567 Katarina Behrens changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |bu...@bubli.org |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143927] : Auto filter - Quick filter does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=143927 --- Comment #2 from wolf seiboth --- Linux Distro: KUBUNTU 18.04 LO About Dialog: Version: 7.0.5.2 Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kf5 Locale: de-DE (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143599] Help Buttons for Save Remote Screens are confusing for non technical users
https://bugs.documentfoundation.org/show_bug.cgi?id=143599 Eleonora Govallo changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Eleonora Govallo --- Hello! As i understand, if you want to save remote you need to open remote file, could you clarify did you open the file that you want to save remote, from the remote server? First advice in the instruction is how to open remote file that you will save remote. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #9 from Heather Ellsworth --- I did not test with Windows and unfortunately I don't have a Windows environment for testing, but the issue is present in Ubuntu 20.04 and newer. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Bug 103182 depends on bug 143353, which changed state. Bug 143353 Summary: [GTK3] Tip of the Day dialogue is focused but does not respond to clicks until Template dialogue is closed https://bugs.documentfoundation.org/show_bug.cgi?id=143353 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70668] FILEOPEN: Display does not fit to a page format from a Calligra Words document.
https://bugs.documentfoundation.org/show_bug.cgi?id=70668 Markus Elfring changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #18 from Markus Elfring --- (In reply to Jean-Baptiste Faure from comment #17) > With my LO 7.2.1.0+ the file opens in portrait Letter format. Is this software behaviour questionable? > In order to decide if the problem is on the LibreOffice side or on the > Calligra side, it would be interesting to test this file in the latest > version of Calligra. I find that my test document is displayed in the expected way (including page orientation and size) also by the software version “Calligra Words 3.2.1-9”. Under which circumstances will the desired clarification be achieved for further applications finally? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105575] Slow rendering when using a Logo command
https://bugs.documentfoundation.org/show_bug.cgi?id=105575 --- Comment #27 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2e74c1107bc8422ee7a819722f3f0a366127330f use visitor callback to avoid container construction (tdf#105575) It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143943] New: [FILEOPEN] XLSB booleans interpreted as numeric formulae
https://bugs.documentfoundation.org/show_bug.cgi?id=143943 Bug ID: 143943 Summary: [FILEOPEN] XLSB booleans interpreted as numeric formulae Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d...@sheetjs.com Description: LibreOffice translates both `BrtCellBool` (record type 4) as well as `BrtShortBool` (record type 15) to numeric expressions. Steps to Reproduce: download and open https://github.com/SheetJS/notes/raw/main/xlsb_short_records/brt_sst.xlsb Actual Results: cell A4 is 1 (formula expression `=TRUE()`) cell B4 is 0 (formula expression `=FALSE()`) Expected Results: Cell A4 is `TRUE` (the value TRUE) Cell A4 is `FALSE` (the value FALSE) Reproducible: Always User Profile Reset: Yes Additional Info: XLSB differentiates the literal true (record type 4 `BrtCellBool`) from the formula =TRUE() (record type 10 `BrtFmlaBool`) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143893] wiki publisher gives server connection error
https://bugs.documentfoundation.org/show_bug.cgi?id=143893 Julien Nabet changed: What|Removed |Added CC||michael.st...@allotropia.de ||, serval2...@yahoo.fr --- Comment #3 from Julien Nabet --- Just for the record, I could save a website for Mediawiki when I put no login/password. Michael: do you succeed in declaring a website for mediawiki with a user account? I took a look at swext/mediawiki/src/com/sun/star/wiki/Helper.java and don't know what's wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134569] FILEOPEN DOCX Paragraph after nested table gets unexpected spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=134569 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #8 from BogdanB --- Justin, please mark this as resolved. I just verified and it is ok in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5b025285b3528910a4360899abb2bbbaadc72c97 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143942] FILEOPEN XLSX Label taking value from cells not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=143942 --- Comment #1 from Aron Budea --- Created attachment 174398 --> https://bugs.documentfoundation.org/attachment.cgi?id=174398=edit Screenshot in Excel -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133402] Undo of deleting a large comment or copy pasting text with large comment doesn't recreate the original size of the comment box instantly only after scroll
https://bugs.documentfoundation.org/show_bug.cgi?id=133402 --- Comment #6 from Telesto --- Confirm being gone Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 18771471f75685a6d3838a22d16dcff5c398e652 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75057] [META] OOXML Chart object issues
https://bugs.documentfoundation.org/show_bug.cgi?id=75057 Aron Budea changed: What|Removed |Added Depends on||143942 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143942 [Bug 143942] FILEOPEN XLSX Label taking value from cells not imported -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103863] Enhancement request: Chart title/label from spreadsheet cell (i.e., dynamic instead of fixed value)
https://bugs.documentfoundation.org/show_bug.cgi?id=103863 Aron Budea changed: What|Removed |Added Blocks||143942 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143942 [Bug 143942] FILEOPEN XLSX Label taking value from cells not imported -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143942] New: FILEOPEN XLSX Label taking value from cells not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=143942 Bug ID: 143942 Summary: FILEOPEN XLSX Label taking value from cells not imported Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Keywords: filter:xlsx Severity: normal Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ba...@caesar.elte.hu Depends on: 103863 Blocks: 75057 Created attachment 174397 --> https://bugs.documentfoundation.org/attachment.cgi?id=174397=edit Sample XLSX with scatter chart In Excel one can set the label option "Value From Cells", and select a cell range. This isn't supported in Calc, and thus isn't imported: the individual points have no label in Calc. This bug report is about the XLSX import part, bug 103863 is open on the general feature. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=75057 [Bug 75057] [META] OOXML Chart object issues https://bugs.documentfoundation.org/show_bug.cgi?id=103863 [Bug 103863] Enhancement request: Chart title/label from spreadsheet cell (i.e., dynamic instead of fixed value) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143893] wiki publisher gives server connection error
https://bugs.documentfoundation.org/show_bug.cgi?id=143893 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I tried with my account on Wikipedia, whereas login/password is ok, I got: "User name or password is incorrect. Please try again, or leave the fields blank for an anonymous connection." I had fixed some bugs about Mediawiki but I don't remember if I used this or not. Anyway, looking at the code, I don't understand why it doesn't work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143847] Setting a DOCX to multi-page view; affecting other DOCX documents on file open
https://bugs.documentfoundation.org/show_bug.cgi?id=143847 --- Comment #12 from Telesto --- (In reply to Heiko Tietze from comment #11) > The last state should be restored. If DOCX doesn't store this option, the > default should be single page. +1 for NAB I'm really confused right now :-) I created the bug report because there is no single page by default. It simply inherits the view of previously opened DOCX/DOC file. Which results in kind of erratic behaviour. If you open a DOCX and set it to multipage view. Close it.. Open a different DOCX, it will go to multipage view.. simply because that was the last state.. So doesn't do what you say it should do (if I'm reading it correctly), but it's NAB at the same time? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143941] New: LibreCalc freezes machine when shutting down [1]
https://bugs.documentfoundation.org/show_bug.cgi?id=143941 Bug ID: 143941 Summary: LibreCalc freezes machine when shutting down [1] Product: LibreOffice Version: 7.1.5.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dpkesl...@gmail.com Description: When I use ExitLibreOffice command on pulldown, the user interface window closes properly, but continuing background processes consume all available memory... as observed using Microsoft Resource Monitor. Sometimes, after a couple minutes, the machine will eventually succeed in closing down all Libre processes... other times the machine hard freezes, not accepting any input. Steps to Reproduce: 1.Calc session w/ 8 column x 8000 row table. 2 hour session occasionally deleting single row at a time. 2.Use pulldown to ExitLibreOffice command. 3. (Look at software environment described below) Actual Results: Interface window closes promptly without issue. Problem is in post-processing stage. As observed on Resource Monitor graphs, memory usage spikes about 7GB indicated before machine freezes. Neither CPU nor Disk usage are particularly heavy. It's memory contention/exhaustion. Expected Results: Postclose processing does not consume all available memory, freezing the machine. Reproducible: Always User Profile Reset: Yes Additional Info: Running on an HP 8530 with 8GB installed memory, 740 GB available disk space. Applications open for my typical work session. LibreCalc. GIMP 2.10 Firefox browser with Fireshot screengrab accessory frequently used while visiting web pages. McAfee AV LiveSafe Win 10 all software at latest release level -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140992] Direct input through copy and paste to table is lost
https://bugs.documentfoundation.org/show_bug.cgi?id=140992 Robert Großkopf changed: What|Removed |Added CC||twars...@gmx.de --- Comment #5 from Robert Großkopf --- *** Bug 143936 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143936] Shortcuts Strg c and Strg v don't work any more in the table view
https://bugs.documentfoundation.org/show_bug.cgi?id=143936 Robert Großkopf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Robert Großkopf --- Seems to be a duplicate of Bug 140992. I will mark this one as duplicate. Feel free to reopen if you think it's another bug. *** This bug has been marked as a duplicate of bug 140992 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140057] Paragraphs in Writer do not behave according to their format specifications, either default or when overridden on a per paragraph basis
https://bugs.documentfoundation.org/show_bug.cgi?id=140057 --- Comment #4 from irrevdj...@gmx.co.uk --- Further to my previous comment, I have come to the tentative conclusion that there may have been a problem in the template file, since other weird formatting errors occurred in documents based on it, e.g. a text format applied ad hoc to an entire paragraph of a built-in style would be applied across the board to all other paragraphs of that type. Paragraphs that used custom styles could have Format > Text > (style) applied with no knock-on effects. Today I have re-built the template from scratch, and so far have had no further formatting problems. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143643] The size of comment box isn't restored at undo (so plenty of space, but showing scrollbar)
https://bugs.documentfoundation.org/show_bug.cgi?id=143643 psidiumcode changed: What|Removed |Added Version|7.3.0.0 alpha0+ Master |6.3 all versions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #8 from m.a.riosv --- I cannot repro with Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133402] Undo of deleting a large comment or copy pasting text with large comment doesn't recreate the original size of the comment box instantly only after scroll
https://bugs.documentfoundation.org/show_bug.cgi?id=133402 psidiumcode changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from psidiumcode --- I could reproduce it in version: Version: 7.0.6.2 Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded But I could not reproduce it in version: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5aac78e5fb241050a86714687e9ff8804588ae3c CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 127957, which changed state. Bug 127957 Summary: calc using scenarios crash after 5 minutes away https://bugs.documentfoundation.org/show_bug.cgi?id=127957 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127957] calc using scenarios crash after 5 minutes away
https://bugs.documentfoundation.org/show_bug.cgi?id=127957 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from Justin L --- 1.) open Untitled 2.ods 2.) select A2 - B5 3.) Tools - Scenarios. Display borders (no), prevent changes (no) 4.) tools - scenarios. Set name to num2. No borders, No prevent change 5.) make some random changes in the data. 6.) Delete Num2 scenario and select earlier scenario 7.) tools - scenarios. Set name to num2. No borders, No prevent change 8.) View - Navigator - Scenarios - Switched to earlier scenario 9.) 11:19 - documented these steps in firefox and checked my email. 10.) 11:25 - select cell A1 and hit save. Crash seen in bibisect 6.4. No crash in bibisect 6.2 or 7.3 master. It SEEMS to have been fixed in 7.0. I tried bibisecting it, but it is hard to be confident that these steps have been followed accurately. Plus, the brain doesn't handle the fact that in this "fixed" case, a crash is marked as bisect good, and a successful save is marked as bisect bad. Sometimes it took 3 attempts to get a crash. In any case, I tried 4 times on master and didn't get a crash. So I'll mark as WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143931] CALC Conditional Formatting - Simplified single background colour fill
https://bugs.documentfoundation.org/show_bug.cgi?id=143931 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #5 from m.a.riosv --- Don't worry, nobody is borne knowing. And this is the typical, no easy, to find how. In any case, when you have doubts, better begin asking on our forum. https://ask.libreoffice.org/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143931] CALC Conditional Formatting - Simplified single background colour fill
https://bugs.documentfoundation.org/show_bug.cgi?id=143931 --- Comment #4 from Colin --- (In reply to m.a.riosv from comment #3) > Created attachment 174388 [details] > Sample conditional format background 2 > > Attached the sample file with a more explicit use of the styles. > > Only one style, it's needed to modify the background of cells with different > styles. > > Seems you want a direct format from the CF, what it's achieved, I think, > with the sample file, without any search. I think I've found your page now. I was always working from the "styles selection and maintenance" within the conditional formatting management facility - a nightmare for the uninitiated. Now I've "found" the "manage styles" sidebar it becomes a lot clearer. Some experimentation is called for. Perhaps a status change to idiot user is appropriate. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 Heather Ellsworth changed: What|Removed |Added Attachment #174389|0 |1 is obsolete|| --- Comment #7 from Heather Ellsworth --- Created attachment 174396 --> https://bugs.documentfoundation.org/attachment.cgi?id=174396=edit faulty-spreadsheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #6 from Heather Ellsworth --- Created attachment 174395 --> https://bugs.documentfoundation.org/attachment.cgi?id=174395=edit proc maps -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #5 from Heather Ellsworth --- Created attachment 174394 --> https://bugs.documentfoundation.org/attachment.cgi?id=174394=edit proc status -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #4 from Heather Ellsworth --- Created attachment 174393 --> https://bugs.documentfoundation.org/attachment.cgi?id=174393=edit registers -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #3 from Heather Ellsworth --- Created attachment 174392 --> https://bugs.documentfoundation.org/attachment.cgi?id=174392=edit segv analysis -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #2 from Heather Ellsworth --- Created attachment 174391 --> https://bugs.documentfoundation.org/attachment.cgi?id=174391=edit top of stacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 --- Comment #1 from Heather Ellsworth --- Created attachment 174390 --> https://bugs.documentfoundation.org/attachment.cgi?id=174390=edit stacktrace signature -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143940] New: FILESAVE: add a new line in a large spreadsheet and save causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=143940 Bug ID: 143940 Summary: FILESAVE: add a new line in a large spreadsheet and save causes crash Product: LibreOffice Version: 7.2.0.1 rc Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: heather.ellswo...@canonical.com Created attachment 174389 --> https://bugs.documentfoundation.org/attachment.cgi?id=174389=edit faulty-spreadsheet Here is a spreadsheet that is 897 rows and 9 columns that is really nothing fancy. If you add a line anywhere in the middle of the existing lines (insert above or below) and then try to save the change, the spreadsheet crashes. There is no crash after adding columns or sheets... just lines. And you can add a line at the end of the text and save just fine. The crash only occurs when you add a line in the middle of the sheet and try to save. I've tried creating a new spreadsheet of equal size and cannot reproduce the issue so I'm not sure what is special about this spreadsheet that causes the crash. The issue was reported in launchpad based off of Ubuntu 20.04 and Libreoffice 6.4.7 but it happens easily on 7.1.5 and 7.2.0 rc3. The corresponding launchpad bug: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1938735 I'll attach the faulty spreadsheet as well as the user's system state information (remember this is relative to 6.4.7, but the same thing happens on 7.2.0) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Bug 106179 depends on bug 119064, which changed state. Bug 119064 Summary: The size of comment box size isn't adjust on paste (only after scrolling) https://bugs.documentfoundation.org/show_bug.cgi?id=119064 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
