[Libreoffice-bugs] [Bug 41915] named cells not highlighted when editing formulae
https://bugs.documentfoundation.org/show_bug.cgi?id=41915 Rainer Bielefeld Retired changed: What|Removed |Added CC|LibreOffice@bielefeldundbus | |s.de| --- Comment #27 from Rainer Bielefeld Retired --- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101646] UI option "Scaling" was removed
https://bugs.documentfoundation.org/show_bug.cgi?id=101646 Charles C changed: What|Removed |Added CC||charlesc-documentfoundation ||.o...@pyropus.ca --- Comment #62 from Charles C --- This issue affects me significantly. I just let my system update to Bullseye/Debian 11 and the zoom-interface functionality went away with the switch to LibreOffice 7. I had always had to use this function in LibreOffice apps because the menu bar text (and various other UI bits) was too small. All other applications are fine for me, whether they're GTK or Qt or whatever. Just LibreOffice is too small. See this for comparison: https://bugs.documentfoundation.org/attachment.cgi?id=175110 On my system, other applications' menu bar text is 7 pixels high. LibreOffice's is 5 pixels and too small to read comfortably. I've set the icon sizes bigger, which takes care of that, but the text in the menu bar and controls is too small. I'm not sure if my system DPI has anything to do with this. I have older large LCD monitors with pixels that are much denser than an old traditional 72dpi, but not nearly as high as modern 4k monitors that are >>200dpi. My monitors are about 135dpi. However, as I said, all other applications are fine. It's just LibreOffice that's a problem for me. So bumping up the whole desktop is not really a solution, as that makes other applications too big. Any resolution of this issue would be greatly appreciated. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101646] UI option "Scaling" was removed
https://bugs.documentfoundation.org/show_bug.cgi?id=101646 --- Comment #61 from Charles C --- Created attachment 175110 --> https://bugs.documentfoundation.org/attachment.cgi?id=175110=edit Font-size comparison between LibreOffice and other applications All other applications show menu bar text approx 7 pixels high in my configuration. Libreoffice menu bar text is 5 pixels and much harder to read. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144518] CALC exceeding perceived limits for pasting doesn't elicit any warning
https://bugs.documentfoundation.org/show_bug.cgi?id=144518 --- Comment #3 from Colin --- Further experiments have identified that a Microsoft product - "Mouse without Borders" - which has the capacity to permit clipboard pasting across computers, will "reserve" the same amount of memory that is being allocated by LO to the clipboard during LO's "copy-paste" process. This allocation occurs despite the fact that the "allow pasting across computers" parameter is disabled AND due to a key change, the product has not even recently been "paired" with the other three PCs. The memory hog is indeed MwB which simply replicated the ever-increasing memory requirements of LO with the re-doubling of the clipboard to increase the speed of "copy-paste". Yes, MwB has subsequently been reassigned to the RatBin Presumably, that means SOLVED NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125286] FIREBIRD - Base not usable under Windows account with Chinese user name (UTF character support)
https://bugs.documentfoundation.org/show_bug.cgi?id=125286 --- Comment #12 from Ming Hua --- (In reply to Mike Kaganski from comment #10) > I believe https://gerrit.libreoffice.org/c/core/+/121886 would *improve* > this a bit. I.e., *if* the path only uses characters representable in > current Windows codepage, then it should be possible to use such paths with > Firebird DB. Indeed, I've installed a daily build including this commit, and it fixed both issues described in comment #0 for me. Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: a9cc066a86c6bd3423c5802c5a4eded55a50c754 CPU threads: 2; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: threaded As the simplified Chinese Windows code page 936 is rather large and covers many scripts, and I only have problem with Chinese characters in account names, I myself consider this issue FIXED. If the developers want to leave this open for further efforts supporting more Unicode characters not representable in Windows code page, that's fine by me, but I probably won't be able to help with any further testing. Thanks Mike for look into this, and everyone for helping! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144298] Permission errors when saving mis-diagnosed (not caught?)
https://bugs.documentfoundation.org/show_bug.cgi?id=144298 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 144299] SheetCellRanges service cant FindAll or ReplaceAll if .Count=1 / simple SheetCellRange also can't.
https://bugs.documentfoundation.org/show_bug.cgi?id=144299 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 144295] Shaded box covers menu and icons
https://bugs.documentfoundation.org/show_bug.cgi?id=144295 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 144260] 7.2.0: installation stops with error 1304
https://bugs.documentfoundation.org/show_bug.cgi?id=144260 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 144282] Crash when changing protection options on document
https://bugs.documentfoundation.org/show_bug.cgi?id=144282 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 144248] System freezes within 10 seconds because OOM (8GB) when closing LibreOffice with a sheet on the clipboard (
https://bugs.documentfoundation.org/show_bug.cgi?id=144248 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 144246] TABLE STYLE: Table style isn't applied correct in a table copied from Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=144246 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 144204] Javascript macro not saved to XLS and XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=144204 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 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 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 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 #3 from QA Administrators --- Dear hadeslorster, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60030] Russian dictionary improvement
https://bugs.documentfoundation.org/show_bug.cgi?id=60030 --- Comment #6 from QA Administrators --- Dear Urmas, 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 141152] A basic SUM function doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=141152 --- Comment #7 from QA Administrators --- Dear John Hallesy, 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 141149] Table column width changes randomly from save to save at doc format
https://bugs.documentfoundation.org/show_bug.cgi?id=141149 --- Comment #2 from QA Administrators --- Dear Army_bloodcore, 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 140834] Crash in Draw 7.1.0.3(64) when export graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=140834 --- Comment #13 from QA Administrators --- Dear Kenneth Tingey, 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 140704] Crash on call Paste Special
https://bugs.documentfoundation.org/show_bug.cgi?id=140704 --- Comment #5 from QA Administrators --- Dear m.a.riosv, 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 97657] INSERT: SVG clippath mask not supported
https://bugs.documentfoundation.org/show_bug.cgi?id=97657 --- Comment #11 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 90600] Working StarBasic macro fails after reloading the document
https://bugs.documentfoundation.org/show_bug.cgi?id=90600 --- Comment #7 from QA Administrators --- Dear Andreas Sä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 89863] Calc: Long captions in chart are out of background - option should choose just the beginning or break text
https://bugs.documentfoundation.org/show_bug.cgi?id=89863 --- Comment #12 from QA Administrators --- Dear Andy, 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 88388] CALC is not exporting ODS graphs to XLS, XLT and UOS correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=88388 --- Comment #13 from QA Administrators --- Dear Carlos Roberto, 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 87843] text-strings in CALC limited to 255 characters per cell
https://bugs.documentfoundation.org/show_bug.cgi?id=87843 --- Comment #12 from QA Administrators --- Dear maik, 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 68459] EDITING: frames are jumping and impossible to position correctly with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=68459 --- Comment #25 from QA Administrators --- Dear mango wodzak, 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 67116] Macros: RemoveByName with IDE Code Window open cause program flow termination
https://bugs.documentfoundation.org/show_bug.cgi?id=67116 --- Comment #10 from QA Administrators --- Dear irs, 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 51925] [BASIC] Writer Table getColumns().getByIndex(i) returns null, where it should not
https://bugs.documentfoundation.org/show_bug.cgi?id=51925 --- Comment #13 from QA Administrators --- Dear Olivier Hallot, 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 49994] TABLES : jumps on selecting text in table in big cell on neighboring pages
https://bugs.documentfoundation.org/show_bug.cgi?id=49994 --- Comment #9 from QA Administrators --- Dear Palagichev, 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 47876] Macro error when loading spreadsheet (works in MSoffice)
https://bugs.documentfoundation.org/show_bug.cgi?id=47876 --- Comment #10 from QA Administrators --- Dear Chris Martin, 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 47214] LINE INPUT is not recognized after a colon
https://bugs.documentfoundation.org/show_bug.cgi?id=47214 --- Comment #15 from QA Administrators --- Dear rifford, 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 42796] Macro assigned to dataform Before Unload or While Unloading events are not called when form container is closed
https://bugs.documentfoundation.org/show_bug.cgi?id=42796 --- Comment #7 from QA Administrators --- Dear Jurgen, 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 41915] named cells not highlighted when editing formulae
https://bugs.documentfoundation.org/show_bug.cgi?id=41915 --- Comment #26 from QA Administrators --- Dear john, 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 38450] XMouseClickHandler Fails To Fire Event When a Sheet Has been "Frozen"
https://bugs.documentfoundation.org/show_bug.cgi?id=38450 --- Comment #10 from QA Administrators --- Dear gn_phelps, 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 38443] Printer properties ignored from macros
https://bugs.documentfoundation.org/show_bug.cgi?id=38443 --- Comment #18 from QA Administrators --- Dear Oliver Brinzing, 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 36210] disable "Insert" command impossible through dispatch framework
https://bugs.documentfoundation.org/show_bug.cgi?id=36210 --- Comment #16 from QA Administrators --- Dear Laurent Godard, 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 127639] Fileopen: Writer won't show any content of generated simple DOCX that has word and _rels folders but no docProps
https://bugs.documentfoundation.org/show_bug.cgi?id=127639 --- Comment #5 from QA Administrators --- Dear Mikeyy - L10n HR, 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 119460] copy hidden child section at beginning of document via transferable will fail
https://bugs.documentfoundation.org/show_bug.cgi?id=119460 --- Comment #4 from QA Administrators --- Dear Oliver Brinzing, 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 119446] Form controls Design Mode impacts speed
https://bugs.documentfoundation.org/show_bug.cgi?id=119446 --- Comment #3 from QA Administrators --- Dear matti.jaatinen, 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 119175] Laggy behavior pressing paste (CTRL+V) repeatedly in a document containing a large amount of comments
https://bugs.documentfoundation.org/show_bug.cgi?id=119175 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 117941] slashing and X-"striking" of text removed from RTL text when exporting to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=117941 --- Comment #12 from QA Administrators --- Dear Eyal Rozenberg, 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 114911] Setting vertical orientation for first cell in table row shifts rendering of row on save & reopen
https://bugs.documentfoundation.org/show_bug.cgi?id=114911 --- Comment #12 from QA Administrators --- Dear Eyal Rozenberg, 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 112038] when importing docx, formula are created at default font size
https://bugs.documentfoundation.org/show_bug.cgi?id=112038 --- Comment #5 from QA Administrators --- Dear john, 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 112023] Copying data from Base truncates precision to the shown format
https://bugs.documentfoundation.org/show_bug.cgi?id=112023 --- Comment #11 from QA Administrators --- Dear Lars Jødal, 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 103113] IDE: JavaScript macros is not removed purely from Spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=103113 --- Comment #16 from QA Administrators --- Dear nvyush, 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 144599] Page count before an endnote marker shows wrong number of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144599 John changed: What|Removed |Added Summary|Page count before an|Page count before an |endnote marker |endnote marker shows wrong ||number of pages -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144599] New: Page count before an endnote marker
https://bugs.documentfoundation.org/show_bug.cgi?id=144599 Bug ID: 144599 Summary: Page count before an endnote marker Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: Start Writer and create a new document from the default template. Insert a page count field (Insert > Field > Page Count). Notice the field shows 1. Below this field, type "foo" followed by an endnote (Insert > Footnote and Endnote > Endnote). Type some text for the endnote itself (for example, "bar"). Return to your "foo". Notice that you have 2 pages now, but the page count field above "foo" still shows 1. Below "foo", insert another page count field. Notice it shows 2. So in other words here is what you will end up ``` 1 foo 2 ``` This is bad. Both counters should update automatically. Press F9 to update all fields. Now you have ``` 2 foo 2 ``` You may think pressing F9 resolves the issue partly, but actually it doesn't. For example, save this document and close it. Then open it again. Bam! You have ``` 1 foo 2 ``` again. The real life case: I have a template for technical writing with the following protected section in the very beginning of the first page: ``` document title: page count: aggigned template: ``` Each time I open a document with endnotes, the page count field shows me the wrong number of pages. Steps to Reproduce: see above Actual Results: see above Expected Results: see above Reproducible: Always User Profile Reset: No Additional Info: see above -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] New: Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 Bug ID: 144598 Summary: Crash in: SkRect::round() Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: argh_squa...@hotmail.com This bug was filed from the crash reporting server and is br-2520800e-6840-4482-8a82-b0944a0ad962. = searched / tried several "start LibreOffice in Safe Mode" solutions/procedures to the MANY other-previously reported variations of 'LO problem-s/does not work/open in Windows 10' - mostly ones about un/re-install/booting, selecting "Disable hardware acceleration" option, archiving profile, resetting factory settings/entire user profile suggestions...getting worn-out, & often times just frustrated & LOST, trying so many different things. DOES work in SafeMode but not believing this should be an on-going issue, somethings not right and i don't think this is a long-term solution for me. FWIW: i've tried OpenOffice, it works, but i prefer the stable LO Suite on my mixture of Linux & W10 machines over the Apache Oo.o option. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144508] Detached side menu off-screen can't be returned to visible area
https://bugs.documentfoundation.org/show_bug.cgi?id=144508 --- Comment #6 from no...@noses.com --- (In reply to Mike Kaganski from comment #3) > I can't easily repro. (Sort of.) I just redid it by detaching my 3rd display and attaching another one (which showed up to the right of display #2, launched writer on #2, detached the templates drawer and moved it to #3. Closed writer, attached original #3 (which was put into its recorded position by windows) and launched Writer. Detached the templates again... and gone they were. I can reattach them by keyboard commands but detaching them (with the mouse) is moving them into the original position. What I forgot to mention (but I did not think about it: I'm running PowerToys (Fancy Zones) but disabled it now and nothing changed. > I used WinKey+P to create a fake second "display" in "Extend" mode. [I don't even know how to do that 8-)] My additional displays are "real". Even if the bug can't be reproduced: How expensive would checking "is the windows we are opening (at least partially, making window controls reachable) inside the visible desktop area" every time a window is opened. Or a function (that can be triggered by keyboard) to move all windows to (0, 0) on the first desktop and resizing them to fit it)? Should I put that somewhere as feature request (actually not for Writer but for the basic infrastructure)?. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144508] Detached side menu off-screen can't be returned to visible area
https://bugs.documentfoundation.org/show_bug.cgi?id=144508 --- Comment #5 from no...@noses.com --- (In reply to V Stuart Foote from comment #2) > Interesting, so presume similar would happen on a multi-headed Windows > system (not needing 8K) dragging the pop-up window out onto a 3rd monitor. > > Disconnecting the monitor would leave that screen address in limbo. That's actually how I did it originally... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144597] New: Changes to fonts will not save
https://bugs.documentfoundation.org/show_bug.cgi?id=144597 Bug ID: 144597 Summary: Changes to fonts will not save Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bdk...@icloud.com Description: I have a number of .csv files. They all open with an unreadable font size. Changing the font and font size will not save. Have tried "save" from 3 locations. Always revert to original font. Steps to Reproduce: 1. Start csv file 2. change fonts to larger and other font 3. Save Actual Results: No change to fonts or font size Expected Results: new font 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 144594] hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144594 --- Comment #1 from steve --- Created attachment 175109 --> https://bugs.documentfoundation.org/attachment.cgi?id=175109=edit macOS 11.6 LO 7.2.1.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144596] hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144596 steve changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from steve --- after running into `504 Gateway Time-out` a few times, BZ finally decided to create the report and it created three so closing the dupes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144595] hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144595 steve changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from steve --- after running into `504 Gateway Time-out` a few times, BZ finally decided to create the report and it created three so closing the dupes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144596] New: hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144596 Bug ID: 144596 Summary: hangs right after opening file Product: LibreOffice Version: 7.2.1.1 rc Hardware: All OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@disr.it Description: This hang / crash happened right after opening a file on macOS 11.6 LO 7.2.1.2. Steps to Reproduce: Not sure, this happened right after opening a file without any user interaction. Filing and hoping the crash log is helpful in understanding what happened. Reopening the same file again did not result in a crash. If there is nothing actionable in the crash log, feel free to close this as wontfix. Actual Results: Crash Expected Results: No crash Reproducible: Sometimes User Profile Reset: No Additional Info: crash log attached -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144595] New: hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144595 Bug ID: 144595 Summary: hangs right after opening file Product: LibreOffice Version: 7.2.1.1 rc Hardware: All OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@disr.it Description: This hang / crash happened right after opening a file on macOS 11.6 LO 7.2.1.2. Steps to Reproduce: Not sure, this happened right after opening a file without any user interaction. Filing and hoping the crash log is helpful in understanding what happened. Reopening the same file again did not result in a crash. If there is nothing actionable in the crash log, feel free to close this as wontfix. Actual Results: Crash Expected Results: No crash Reproducible: Sometimes User Profile Reset: No Additional Info: crash log attached -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144594] New: hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144594 Bug ID: 144594 Summary: hangs right after opening file Product: LibreOffice Version: 7.2.1.1 rc Hardware: All OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@disr.it Description: This hang / crash happened right after opening a file on macOS 11.6 LO 7.2.1.2. Steps to Reproduce: Not sure, this happened right after opening a file without any user interaction. Filing and hoping the crash log is helpful in understanding what happened. Reopening the same file again did not result in a crash. If there is nothing actionable in the crash log, feel free to close this as wontfix. Actual Results: Crash Expected Results: No crash Reproducible: Sometimes User Profile Reset: No Additional Info: crash log attached -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144583] Blurry icon on HiDPI
https://bugs.documentfoundation.org/show_bug.cgi?id=144583 V Stuart Foote changed: What|Removed |Added OS|All |Linux (All) CC||vstuart.fo...@utsa.edu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 84575] COLOR PICKER: Custom color dialog not functioning correctly when color is white or black
https://bugs.documentfoundation.org/show_bug.cgi?id=84575 S.Zosgornik changed: What|Removed |Added CC||s.zosgor...@libreoffice.org --- Comment #7 from S.Zosgornik --- Bug is still present on LO 7.1.2.1 on both GNU/Linux and Windows. Steps to reproduce: 1. open "Custom color.." dialog e.g. from the toolbar or under Format -> Paragraph -> Area -> Pick 2. choose HSB:Hue on the right side of the dialog and place the selection cursor on the right side of the color window 3. hold-click inside the vertical color slider and and move the selection up and down -> color window change automatically with the selection 4. place the selection cursor on the most left side of the color window and hold-click inside the vertical slider to move the selection up and down -> color window doesn't change automatically with the selection 5. choose HSB:Saturation on the left side of the dialog window 6. place the color selection cursor towards the center of the color window and move the selection inside the vertical slider up and down -> color window change again with the selection automatically 7. place the selection cursor to the very bottom of the color window and move the selection inside the vertical slider again up and down -> color window doesn't change according to the vertical slider It seems to me that the color window change on the given RGB or CMYC values while it actually should change corresponding to the selected HSB value. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144590] Insert an image on Calc, click on image, a new toolbar appears making the whole sheet to "down move"
https://bugs.documentfoundation.org/show_bug.cgi?id=144590 --- Comment #2 from elias estatistics --- Thanks resolved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144576] Copy a table in Writer is not the same as Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=144576 --- Comment #2 from Israel Enriquez --- It is not a problem of copy from Calc to Writer, is a problem of copy from Writer to text. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144593] New: Other cell selected when column is marked
https://bugs.documentfoundation.org/show_bug.cgi?id=144593 Bug ID: 144593 Summary: Other cell selected when column is marked Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: al...@gmx.de Description: The situation is: - I'm editing a sheet; the selected cell is somewhere in the middle of the screen - Now I mark some columns by moving the mouse over the columns headers and draggin it. At this moment, the cell selection jumps to the top most visible cell in the last marked column. This is a little bit pity since I lose the editing context. Could we retain the current cell in this situation? As a side note: The border around the marked columns is not thick. The other major spread sheet draws a think border around the selection. Is it the intention in Calc? Steps to Reproduce: 1. Edit a sheet, place cursor to A4 2. Mark columns A and B by dragging the mouse over their headers Actual Results: Cursor is now at B1 Expected Results: Cursor remains at A4 Reproducible: Always User Profile Reset: No Additional Info: Editing context is lost. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144586] The ruler doesn't show numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=144586 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- 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 144590] Insert an image on Calc, click on image, a new toolbar appears making the whole sheet to "down move"
https://bugs.documentfoundation.org/show_bug.cgi?id=144590 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from V Stuart Foote --- Expected behavior with context sensitive toolbars. You can Unlock toolbar position, and move the Image toolbar. Docking it to the bottom or side, or even allow it to "float". Alternatively, shift to use one of the Notebook Bar modes from main menu: View -> User Interface... dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144592] New: CALC performance degradation comparing “Hide rows” versus “Group rows” followed by conceal
https://bugs.documentfoundation.org/show_bug.cgi?id=144592 Bug ID: 144592 Summary: CALC performance degradation comparing “Hide rows” versus “Group rows” followed by conceal Product: LibreOffice Version: 7.2.0.4 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: that.man.co...@gmail.com Description: There is a noticeable difference between the process of selecting & hiding rows utilising the context menu when compared with selecting & “concealing” them utilising the toolbar’s Data menu to group the same rows. When a large number of rows are simply hidden via the context menu “hide rows” it can take minutes to successfully hide them, whereas selecting the same rows and then grouping them via the menu Data>Group and Outline>Group (F12) will permit their instantaneous concealment. Importantly, when the context menu “hide rows” is “undone” with the tool button it informs that it is undoing a “row height” formatting command whereas the same undo via tool button for the “group & conceal” action informs that it is undoing “Hide details”. Clearly a contradiction and probably indicative of an inferior routine being utilised for the context menu “Hide” which is really a metric adjustment and the data menu “group” which proclaims itself to be a hide function. My experiments have demonstrated that even filling as much of the sheet as possible in 12GB of RAM with a single character in hundreds of millions of cells, has little or no impact upon the timing of either the hide or group functionality. Hiding still sucks whilst grouping and concealing is still virtually instantaneous. I am defining the speed of operation of the chosen functionality NOT the speed with which either columns or rows are selected, both of which are virtually instantaneous. Steps to Reproduce: Open a new CALC document Format the document A4 and accept whatever are your default margin settings This produces a marquee on screen depicting the print range. Select the first cell in row 1 outside the marque Select all cells to the end of the row with ctrl+shft+right arrow Right click the column headers and select “hide” from the context menu Observe that 1000+ columns are instantly “hidden” Utilise the undo button and the columns reappear instantly NOTE: the undo button informs that the columns’ metrics are being amended they have not been hidden, their width has been set to an “invisibility” factor. Select the same columns Utilising the menu Data>Group and Outline>Group (or F12) them Conceal them utilising the “control” tab Hover over the “undo” button and observe that it is intending to “Undo: Hide details” That is a minor benchmarking exercise Leaving the columns hidden, concealed or exposed, will have zero impact upon the next steps -although it should be observed that this action has concealed 99.316% of the permissible cells Select the first cell of Column A outside the print marquee Select all rows to the end of the sheet with ctrl+shft+down arrow Utilising the menu Data>Group and Outline>Group (or F12) them - all 1,048,523 of them Conceal them utilising the “control” tab Observe the instantaneous response Hover over the “undo” button and observe that it is intending to “Undo: Hide details” Undo the action Remove the grouping (ctrl+F12) Select the same rows Right click the row header Select “Hide rows” from the context menu Go off and make a cup of coffee because despite LO reporting that it is not responding, it is in fact beavering away in the background resetting the height of 1,048,523 rows to an invisibility factor, as opposed to whatever “group” does to them at the speed of -- an i5 running at 3.4GHz The one saving grace is that undo is instantaneous. There is also the obvious workaround – use group instead of hide Actual Results: Slow performance of the command Expected Results: Fast performance of the command Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded Tested on i5 3.4GHz 12GB RAM & 8GB RAM & 4GB RAM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144563] Fields referencing numbered lists now have "." in the generated text where they did not before
https://bugs.documentfoundation.org/show_bug.cgi?id=144563 Michael Warner changed: What|Removed |Added OS|Mac OS X (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144563] Fields referencing numbered lists now have "." in the generated text where they did not before
https://bugs.documentfoundation.org/show_bug.cgi?id=144563 --- Comment #2 from Michael Warner --- I haven't checked what the behavior was in previous versions, but in 7.2.0.4, it seems to make the formatting of the reference match the formatting of the number in the list. For example, if you go to "Format"->"Bullets and Numbering...", select the "Customize" tab, and then change the "Number" field to "1, 2, 3, ...", you should see a Separator section appear in the dialog with Before and After fields. If there is a period in the After field, that period will appear both in the list item, and in a reference to a list item. If there is no period there, there will be no period in the list item nor in the reference to the list item. This is in: Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 6; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97827] Change the rhino engine for javascript macros for non Java alternative (spidermonkey/V8)
https://bugs.documentfoundation.org/show_bug.cgi?id=97827 --- Comment #11 from Spyros --- Out of curiosity I tried Rhino and QuickJS on the bench-v8 version 7 benchmark (https://github.com/mozilla/arewefastyet/tree/master/benchmarks/v8-v7), used on the official QuickJS website as a comparison with other JS micro-engines (https://bellard.org/quickjs/bench.html). I wanted to benchmark Duktape too, but it would not compile on my Debian 11 system, since the build system requires Python2 YAML (which is not available anymore at the repositories). Rhino 1.7.14-SNAPSHOT 2021 09 14 java -classpath buildGradle/libs/rhino-1.7.14-SNAPSHOT.jar org.mozilla.javascript.tools.shell.Main -opt -1 -f bench-v8/combined.js //commented out a line with console.log (Rhino does not support it) PROGRESS Richards RESULT Richards 53.6 PROGRESS DeltaBlue RESULT DeltaBlue 55.3 PROGRESS Encrypt PROGRESS Decrypt RESULT Crypto 52.0 PROGRESS RayTrace RESULT RayTrace 134 PROGRESS Earley PROGRESS Boyer RESULT EarleyBoyer 167 PROGRESS RegExp RESULT RegExp 147 PROGRESS Splay RESULT Splay 302 PROGRESS NavierStokes RESULT NavierStokes 65.7 SCORE 100 QuickJS 2021-03-27 ./qjs bench-v8/combined.js PROGRESS Richards RESULT Richards 363 PROGRESS DeltaBlue RESULT DeltaBlue 350 PROGRESS Encrypt PROGRESS Decrypt RESULT Crypto 419 PROGRESS RayTrace RESULT RayTrace 483 PROGRESS Earley PROGRESS Boyer RESULT EarleyBoyer 676 PROGRESS RegExp RESULT RegExp 125 PROGRESS Splay RESULT Splay 893 PROGRESS NavierStokes RESULT NavierStokes 751 SCORE 442 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135683] FILEOPEN DOCX: Somewhat slow opening of document containing a 222 pages table
https://bugs.documentfoundation.org/show_bug.cgi?id=135683 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #11 from Roman Kuznetsov <79045_79...@mail.ru> --- It takes around 20 sec from start of the file opening to end of all 222 pages loading and CPU usage decreasing in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: c5aef25352d20e052ec3a697f3cb979d3bbf9df6 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35092] Inking functionality: Ink drawings / annotations with Stylus, Pen or Finger on Touchscreen or Tablet
https://bugs.documentfoundation.org/show_bug.cgi?id=35092 --- Comment #118 from Ane Ak --- At Super Auto Dent Body collision repair, we take what we do very personally and know how nerve wrecking an accident can be. https://www.superautodentbody.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Buovjaga changed: What|Removed |Added Depends on||144585 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144585 [Bug 144585] button popups don't open with KF5 VCL on Wayland -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Buovjaga changed: What|Removed |Added Depends on||144585 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144585 [Bug 144585] button popups don't open with KF5 VCL on Wayland -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144585] button popups don't open with KF5 VCL on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144585 Buovjaga changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords||bibisectNotNeeded, ||regression Version|7.2.1.1 rc |7.3.0.0 alpha0+ Master CC||glo...@fbihome.de, ||ilmari.lauhakangas@libreoff ||ice.org Blocks||100156, 102495 --- Comment #1 from Buovjaga --- Yeah, they are rather wonky: they do open upon the second click, but are not placed below their parent element. Arch Linux 64-bit Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 88a6ac9f75a4375b72111af5a3e004bef4226455 CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 15 September 2021 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100156 [Bug 100156] [META] Wayland-related bugs https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE VCL backend bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144547] Changing Cell name with drag & drop. it is repeated forever in the formula
https://bugs.documentfoundation.org/show_bug.cgi?id=144547 Julien Nabet changed: What|Removed |Added Summary|Chaning Cell name with drag |Changing Cell name with |& drop. it is repeated |drag & drop. it is repeated |forever in the formula |forever in the formula -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144537] Small Calc ODS with simple chart: crash on row delete if jumbo option on
https://bugs.documentfoundation.org/show_bug.cgi?id=144537 Julien Nabet changed: What|Removed |Added CC|serval2...@yahoo.fr | --- Comment #10 from Julien Nabet --- Indeed, I had overlooked the ifdef Anyway, uncc myself since I can't help here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144591] Value for logheight in custom-shape is wrong in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=144591 --- Comment #1 from Regina Henschel --- Created attachment 175108 --> https://bugs.documentfoundation.org/attachment.cgi?id=175108=edit Screenshot with Draw and Writer side-by-side -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144591] New: Value for logheight in custom-shape is wrong in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=144591 Bug ID: 144591 Summary: Value for logheight in custom-shape is wrong in Writer Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 175107 --> https://bugs.documentfoundation.org/attachment.cgi?id=175107=edit Object with fixed rectangle height Open attached Draw document. It has an object, where the upper rectangle has a fixed height of 1cm. The object is intended to be uses with a heading in the upper rectangle and body text in the lower rectangle. Copy the object and insert it into a text document in Writer. Notice, that the upper rectangle has changed its height. For to get a fixed height for the upper rectangle, the y-coordinate where the upper rectangle ends and the lower rectangle starts is calculated as draw:formula="1000/logheight*height" ODF 1.3 specifies in 19.171 draw:formula, "logheight | The height in 1/100th mm as specified by the svg:height 19.543 attribute is used." -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144590] New: Insert an image on Calc, click on image, a new toolbar appears making the whole sheet to "down move"
https://bugs.documentfoundation.org/show_bug.cgi?id=144590 Bug ID: 144590 Summary: Insert an image on Calc, click on image, a new toolbar appears making the whole sheet to "down move" Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: elias__0...@yahoo.com Created attachment 175106 --> https://bugs.documentfoundation.org/attachment.cgi?id=175106=edit up down move - very annoying. 1) Insert an image on Calc with copy paste from eg. web, 2) click on image, a new toolbar appears 3) making the whole sheet to "down move" Think of that Case before says "not a bug". This image is a table, and someone would like to copy these data into calc manually. By clicking in the image for various reasons (move, enlarge, making smaller), This "up/down move" is very dizzy! Is there a way to cancel this behavior (ask libreoffice had no idea - told me to fill a bug)? a) Either making font toolbar permantly in order to stop apperance / disappearance b) Either by clicking on the image, to stop disappear font tollbar. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144584] Try to copy a number of 0.#### eg. 0.617 from somewhere eg. webpage, and it is pasted as 617
https://bugs.documentfoundation.org/show_bug.cgi?id=144584 --- Comment #3 from elias estatistics --- OK! :) Sorry for the incovinience! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144037] kf5: Unable to insert table from toolbar button
https://bugs.documentfoundation.org/show_bug.cgi?id=144037 Timur changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4585 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144585] button popups don't open with KF5 VCL on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144585 Timur changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4037 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124176] Use pragma once instead of include guards
https://bugs.documentfoundation.org/show_bug.cgi?id=124176 --- Comment #228 from Commit Notification --- Chris Sherlock committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e9f59e76292f815faefa4ca3877d3aacdad3be5a tdf#124176 - Use pragma once instead of include guards 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 144587] Tree item is inconsistent with dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=144587 medmedin2014 changed: What|Removed |Added OS|All |Linux (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144589] New: Down arrow has weird extra lines on right and top
https://bugs.documentfoundation.org/show_bug.cgi?id=144589 Bug ID: 144589 Summary: Down arrow has weird extra lines on right and top Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: med.medin.2...@gmail.com Created attachment 175105 --> https://bugs.documentfoundation.org/attachment.cgi?id=175105=edit Down arrow has weird extra lines on right and top On Manjaro KDE with dark Breeze theme, those small lines that appear on top and right of the arrow make it really ugly. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 008f28c9e01114e731f785e9e238236a1ed069d2 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-22_15:17:36 Calc: threaded Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.4.143-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144588] New: Base ODBC connection for Sqlite Inadequately Documented for Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=144588 Bug ID: 144588 Summary: Base ODBC connection for Sqlite Inadequately Documented for Windows Product: LibreOffice Version: 7.2.1.1 rc Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: flywi...@gmail.com CC: olivier.hal...@libreoffice.org Comments relate to BG64-BaseGuide.pdf > Accessing external databases > MySQL connection via ODBC > To connect via ODBC, you must of course have ODBC software installed. > Details of how to do this are not given here. This is totally unintelligible for ODBC, especially Windows. Maybe present the four steps briefly first before explaining details for various options for the different drivers. *** A separate section is needed for ODBC, including how to get drivers - http://ch-werner.de/sqliteodbc/ Sqlite would be a good example to save confusion with MySQL. See https://ask.libreoffice.org/t/connecting-base-to-sqlite-in-windows/68168/12 The type of info required and a sample database is covered in https://www.sqlitetutorial.net/ > Query enhancement using SQL Mode *** This doesn't explain how say sqlite works with Base. A sqlite example would be good and relatively easy to set up. Version: 7.2.0.3 (x64) / LibreOffice Community Build ID: 2a7ea282da28d665a7dc086360567b4aea27bf08 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: threaded I'd welcome the opportunity to review changes to the docs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144587] New: Tree item is inconsistent with dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=144587 Bug ID: 144587 Summary: Tree item is inconsistent with dark theme Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: med.medin.2...@gmail.com Created attachment 175104 --> https://bugs.documentfoundation.org/attachment.cgi?id=175104=edit Tree item is inconsistent with dark theme On Manjaro with KDE desktop and using Dark breeze theme, the tree component is hard to be seen and is inconsistent with system theme. See attached image for more info. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 008f28c9e01114e731f785e9e238236a1ed069d2 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-22_15:17:36 Calc: threaded Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.4.143-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144494] Resizing image causes hang (see comment 2)
https://bugs.documentfoundation.org/show_bug.cgi?id=144494 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- Confirm with attach from Comment 2 in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: c5aef25352d20e052ec3a697f3cb979d3bbf9df6 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143961] Impress crashes when inserting a videofile
https://bugs.documentfoundation.org/show_bug.cgi?id=143961 Timur changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #9 from Timur --- Since nobody reproduced, you need to find a cause yourself. If User Profile Reset: Yes means you did reset or delete user profile, you may try to install via PPA. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144586] New: The ruler doesn't show numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=144586 Bug ID: 144586 Summary: The ruler doesn't show numbers Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: moemen0...@gmail.com Created attachment 175103 --> https://bugs.documentfoundation.org/attachment.cgi?id=175103=edit No numbers on rulers There is no numbers shown on both the horizontal and the vertical rulers. I'm using Zorin OS 15. The problem persisted even after updating to LibreOffice 7.2.1.2 Version info: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.18.04.1~lo3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76946] XPrintJob::cancelJob doesn't cancel printing
https://bugs.documentfoundation.org/show_bug.cgi?id=76946 Kevin Suo changed: What|Removed |Added Keywords|patch | CC||suokunl...@126.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144584] Try to copy a number of 0.#### eg. 0.617 from somewhere eg. webpage, and it is pasted as 617
https://bugs.documentfoundation.org/show_bug.cgi?id=144584 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #2 from Mike Kaganski --- (In reply to elias estatistics from comment #0) > Try to copy a number of 0. eg. 0.617 from somewhere eg. webpage, and it > is pasted as 617. > > Try to copy eg. 0.0006 from somewhere into calc and it is pasted as 6. > > Locale: el-GR (el_GR.UTF-8); UI: en-US This is not a bug. Citing Wikipedia [1]: > Countries where a comma "," is used as decimal separator include: > ... Greece [1] https://en.wikipedia.org/wiki/Decimal_separator#Countries_using_decimal_comma -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144499] KDE: styles cannot be applied from drop down
https://bugs.documentfoundation.org/show_bug.cgi?id=144499 gera...@libreoffice.org changed: What|Removed |Added CC||jose.ve...@urjc.es --- Comment #14 from gera...@libreoffice.org --- *** Bug 144579 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 144579] Font color and character highlight buttons do not allow change color in palette
https://bugs.documentfoundation.org/show_bug.cgi?id=144579 gera...@libreoffice.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||gera...@libreoffice.org Resolution|--- |DUPLICATE --- Comment #1 from gera...@libreoffice.org --- *** This bug has been marked as a duplicate of bug 144499 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144585] New: button popups don't open with KF5 VCL on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144585 Bug ID: 144585 Summary: button popups don't open with KF5 VCL on Wayland Product: LibreOffice Version: 7.2.1.1 rc Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aro...@archlinux.org Description: In 7.2.1, and using the KF5 VCL on Wayland, button popus don't open (or rather close immediately, making them unusable). Like bug 144037, this is a regression from 9dcf5816c90e9819861332f11e014ef7b78e2fe7, but a1a83b6b3b4459de353e0cdc8cdf402370c0a5c4 does NOT fix this. Steps to Reproduce: 1.Open Writer on Wayland with the KF5 VCL 2. Try to insert a table via the toolbar button Actual Results: Button popup disappears Expected Results: Button popup opens and can be used Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.2.1-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144565] Crash in: SfxItemSet::Clone(bool, SfxItemPool *)
https://bugs.documentfoundation.org/show_bug.cgi?id=144565
Julien Nabet changed:
What|Removed |Added
CC||serval2...@yahoo.fr
--- Comment #4 from Julien Nabet ---
Created attachment 175102
--> https://bugs.documentfoundation.org/attachment.cgi?id=175102=edit
bt with debug symbols
On pc Debian x86-64 with master sources updated today + gen rendering, I got a
crash but when using printing and the bt is different.
I put it just as info since it must be another bug but did I miss something to
reproduce the original pb unless it's Windows only?
Also, gdb shows this:
i_pSetupData=0x92c6350, i_rController=...) at
vcl/unx/generic/print/genprnpsp.cxx:1162
1162size_t nBytesWritten =
fwrite(buffer.data(), 1, nBytesRead, fp);
(gdb) p buffer
$1 = std::__debug::vector of length 65536, capacity 65536 = {-123 '\205', 113
'q', -94 '\242', 19 '\023', -36 '\334', 103 'g', 127 '\177', 56 '8', 23 '\027',
-32 '\340', -45 '\323', 65 'A', -5 '\373',
-1 '\377', -118 '\212', -4 '\374', 60 '<', 55 '7', 20 '\024', 116 't', -124
'\204', 113 'q', -37 '\333', -61 '\303', 51 '3', -81 '\257', 110 'n', 60 '<',
16 '\020', 78 'N', 98 'b', 88 'X', 80 'P',
-120 '\210', 58 ':', 39 '\'', -113 '\217', -92 '\244', 0 '\000', 5 '\005', 4
'\004', 12 '\f', 28 '\034', 96 '`', -30 '\342', -32 '\340', 11 '\v', -31
'\341', -32 '\340', 43 '+', -122 '\206', -63 '\301',
21 '\025', 73 'I', -92 '\244', 35 '#', 10 '\n', -81 '\257', 8 '\b', -83
'\255', 94 '^', 3 '\003', -52 '\314', 24 '\030', 49 '1', 31 '\037', -49 '\317',
-101 '\233', 29 '\035', 25 '\031', -30 '\342', 43 '+',
-7 '\371', 17 '\021', 1 '\001', -54 '\312', 100 'd', 69 'E', -52 '\314', -119
'\211', 24 '\030', -17 '\357', 115 's', 50 '2', 117 'u', -2 '\376', 23 '\027',
26 '\032', -64 '\300', -72 '\270', 30 '\036',
19 '\023', 11 '\v', 68 'D', 3 '\003', -113 '\217', 101 'e', 34 '"', -127
'\201', -108 '\224', 15 '\017', 12 '\f', 39 '\'', -87 '\251', -128 '\200', 47
'/', -41 '\327', 72 'H', -80 '\260', 31 '\037',
-109 '\223', 72 'H', 78 'N', -88 '\250', -96 '\240', -22 '\352', 61 '=', -96
'\240', 60 '<', 97 'a', -114 '\216', -117 '\213', 4 '\004', -100 '\234', -119
'\211', 84 'T', 36 '$', 124 '|', -4 '\374',
-124 '\204', -101 '\233', 87 'W', 64 '@', -64 '\300', 72 'H', 20 '\024', -78
'\262', 17 '\021', 67 'C', 127 '\177', -119 '\211', -75 '\265', 75 'K', 66 'B',
18 '\022', -9 '\367', 118 'v', 104 'h', 81 'Q',
-67 '\275', 91 '[', 94 '^', -67 '\275', 119 'w', 121 'y', -97 '\237', 19
'\023', -101 '\233', 7 '\a', -108 '\224', -16 '\360', -76 '\264', -40 '\330',
51 '3', 120 'x', -42 '\326', -63 '\301', 68 'D', 9 '\t',
-7 '\371', 67 'C', -55 '\311', 15 '\017', -48 '\320', 48 '0', 40 '(', 37 '%',
-87 '\251', 19 '\023', 55 '7', 102 'f', -28 '\344', -11 '\365', -83 '\255', -93
'\243', -28 '\344', 38 '&', -124 '\204',
-68 '\274', -36 '\334', 24 '\030', -20 '\354', -55 '\311', 109 'm', 3 '\003',
91 '[', -96 '\240', -78 '\262', -128 '\200', -78 '\262'...}
(gdb) p nBytesRead
$2 = 65536
(gdb) p buffer.size()
$3 = 65536
Does it mean buffer is corrupted, if yes why? if not, what's the pb then?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144499] KDE: styles cannot be applied from drop down
https://bugs.documentfoundation.org/show_bug.cgi?id=144499 --- Comment #13 from Caolán McNamara --- (In reply to Julien Nabet from comment #12) > warn:legacy.osl:41864:41864:svl/source/items/custritm.cxx:70: > CntUnencodedStringItem::PutValue(): Wrong type > warn:sfx:41864:41864:sfx2/source/appl/appuno.cxx:310: Property not > convertible: Color. Could it be related with tdf#144464 ? That warning is tdf#144464, but that's not having an effect on this popup related problem which might be related to tdf#144037. Popup windows are always bizarrely difficult to get working right in all circumstances. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144552] Right click then format on a cell could be a little faster?
https://bugs.documentfoundation.org/show_bug.cgi?id=144552 Julien Nabet changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from Julien Nabet --- (In reply to m.a.riosv from comment #1) > Hi Julien, I think this kind of behavior is common with master, first use of > some procedures are slow. The same happens calling it with [Ctrl+1] > Does it happen after use it several times? Indeed I think the other times are more quicker thanks to some cache mechanism I suppose. Also, I submitted this bugtracker because I saw this on this on my wife's laptop (Windows 10 with LO 7.1.6). Now perhaps it might be already fixed too on 7.2 branch or master branch. Anyway, wonder if the Flamegraph (retrieved on master branch) could show something interesting to optimize a bit. Perhaps should we put this as an enhancement? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144584] Try to copy a number of 0.#### eg. 0.617 from somewhere eg. webpage, and it is pasted as 617
https://bugs.documentfoundation.org/show_bug.cgi?id=144584 --- Comment #1 from elias estatistics --- Go into eg.https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8169780/ Copy any table with p values into calc withou p values loosing "0.000###". Options copy as textnumber/formula do nothing. Only work --> Paste Speical ---> Paste Special --> Unformatted text or imported text. Maybe an enhancement to do that in a much fewer steps? (eg. Paste special --> Unformatted text?) I think people that copy data tables in calc with such numbers will be many! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 87720, which changed state. Bug 87720 Summary: Default insert image anchor, wrapping, and spacing (see comment #43 for summary at 2020-04-15) https://bugs.documentfoundation.org/show_bug.cgi?id=87720 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133291] Graphic style default anchor should be to character
https://bugs.documentfoundation.org/show_bug.cgi?id=133291 Bug 133291 depends on bug 87720, which changed state. Bug 87720 Summary: Default insert image anchor, wrapping, and spacing (see comment #43 for summary at 2020-04-15) https://bugs.documentfoundation.org/show_bug.cgi?id=87720 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
