[Libreoffice-bugs] [Bug 158168] Cannot create a keyboard shortcut for a hidden text in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=158168 --- Comment #2 from Jeroným klimeš --- Dear Mr. Guillou, there is a attribute of text so called "hidden text" similar as say "bold" or "italic". I wanted to mark text hidden the same way as CTRL+B marks Bold text. I could not to do it because in Custumization there is not a category "hidden text". Is it clearer? Thank you anyway for you help. Sincerely JK -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157943] LibreOffice 7.6.2.1 - opened files can be modified by someone else without first person's knowledge, even when .lock file exists
https://bugs.documentfoundation.org/show_bug.cgi?id=157943 --- Comment #7 from r...@um.jaworzno.pl --- Created attachment 190803 --> https://bugs.documentfoundation.org/attachment.cgi?id=190803=edit File opened by someone - LO7.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157943] LibreOffice 7.6.2.1 - opened files can be modified by someone else without first person's knowledge, even when .lock file exists
https://bugs.documentfoundation.org/show_bug.cgi?id=157943 --- Comment #6 from r...@um.jaworzno.pl --- Created attachment 190802 --> https://bugs.documentfoundation.org/attachment.cgi?id=190802=edit File opened by someone - LO6.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157943] LibreOffice 7.6.2.1 - opened files can be modified by someone else without first person's knowledge, even when .lock file exists
https://bugs.documentfoundation.org/show_bug.cgi?id=157943 r...@um.jaworzno.pl changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #5 from r...@um.jaworzno.pl --- Hello, I checked few of our employees' computers with LibreOffice 6.4 and 7.5 installed and uploaded 2 screenshots - as you can see, in LibreOffice 6.4 users couldn't modify file opened by someone - there is no such option (translation:"Open read-only","Open copy","Cancel"). In LibreOffice 7.5 users CAN modify this file by clicking "Open". Also in LO 7.6 happens the same. AFAIR in LibreOffice 7.4 had the same dialog window as LO 7.5, so @tsulayaiv can be right. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158190] Calc ROUND() function issue in specific range
https://bugs.documentfoundation.org/show_bug.cgi?id=158190 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=96 ||821, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||8360 --- Comment #4 from Mike Kaganski --- Note that the special casing was introduced for bug 96821 in commit b97a0df0f3234b4c1140ba1418d4b96a592afa4a, to mitigate rtl::math::round issues for large numbers like 2^52+1; and at that time, the general case code doing rounding wasn't guarded by conditions introduced later in commit ecfcd99abd3f7dfe68a306dd8045d2da79e42d74. The latter commit mage the former one obsolete. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136306] Dutch spell checker produces debatable suggestions
https://bugs.documentfoundation.org/show_bug.cgi?id=136306 Lars Jødal changed: What|Removed |Added CC||l...@rn.dk --- Comment #10 from Lars Jødal --- I do not read Dutch, but as I understand the discussion, the problem derives from compounding of words that in themselves are correct words, but which become gibberish when compounded. Right? This is not the fault of Hunspell or LibreOffice, but it is still something we would like to handle. Here follows some tips from the Danish dictionary. Danish has a similar problem: Very many correct possibilities of compounding, but also very many possibilities of nonsense within the normal compound rules. To minimize the problem, the Danish dictionary has for many years (since 2012) switched off compounded words from suggestions by this Hunspell option (in the .aff file): MAXCPDSUGS 0 This instructs Hunspell to give at most zero (i.e., none) compound words in the list of suggestions. As an example, "kaffe" (coffee) and "klaver" (piano) are both in the dictonary, and "kaffe" is marked for compounding with no added letters. If the user writes "kaffeklaver" (coffee piano), then it is accepted as a possible word, but "kaffeklaver" will not be suggested by the dictionary. The quite common compound word "kaffebønne" (coffee bean) is in the dictionary, so "kaffebønne" can be suggested, not a as a compound word, but as word in itself. More recently, as a current developer of the Danish dictionary, I have myself added this option to the .aff file: CHECKCOMPOUNDREP This option asks Hunspell to check a possible compound word against the REP list of common mistakes (as defined in the .aff file). If a possible compounding differs only by a common mistake from a word that is already in the dictionary (.dic file), then the word is rejected, even though it follows the compound rules. Adding this rule will reduce the number of nonsense-compoundings that are recognized. It will also once in a while weed out a valid compound word, but these valid words can be added to the dictionary. I.e., if you are a dictionary developer, it is worth checking the dictionary on a group of texts after adding the CHECKCOMPOUNDREP option, to catch common words that was earlier recognized as compounds, but which should better be added as dictionary words. As for the new LibreOffice option, I consider it a valuable possibility to give the normal user the possibility to disallow compounding. Dictionary developers like myself do our best to make good dictionary, including compounding, but it will always be the case that some users will have different needs than another, so adding this choice to the individual user is a sure bonus. Thanks to László Németh for this option. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 158171, which changed state. Bug 158171 Summary: Crash when double-clicking DeepL translation dialog OK button https://bugs.documentfoundation.org/show_bug.cgi?id=158171 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157834] Add simple arithmetic to pdf forms
https://bugs.documentfoundation.org/show_bug.cgi?id=157834 --- Comment #7 from Mike Kaganski --- IMO: 1. There is no built-in means to do calculations in form fields in LibreOffice, other than writing own macros. LibreOffice *must not* put into PDFs anything absent in the source document itself, so any document with simple form fields (but without macros) must never obtain any scripting capability on export - because LibreOffice is not a PDF authoring tool, but its PDF export is designed to just store the document in another format, as is. 2. Even if there is a macro in the document, it is not a LibreOffice task to serve as a AI to convert *programs* from one programming language (say, Basic) and one document model (namely, LibreOffice/UNO document model) into another language (JavaScript) and another document model (PDF API). Not only the two document models are completely different; not only the correct automatic translation of this kind is yet impossible even for most sophisticated AI available currently. It is also a new security risk, which mitigation would be put on TDF. And then, it would still rely on an implementation of this API in other PDF viewers, giving raise to bugs like "your PDF doesn't calculate in Reader X"... WONTFIX IMO. Ref: https://opensource.adobe.com/dc-acrobat-sdk-docs/acrobatsdk/pdfs/acrobatsdk_jsapiref.pdf https://helpx.adobe.com/acrobat/using/javascripts-pdfs-security-risk.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158191] Shows the error when typing Infosys and Sri
https://bugs.documentfoundation.org/show_bug.cgi?id=158191 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Thanks for the report. Can you please let us know: - which language is the text in? - which dictionary are you using for spellchecking? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157834] Add simple arithmetic to pdf forms
https://bugs.documentfoundation.org/show_bug.cgi?id=157834 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org URL||https://ask.libreoffice.org ||/t/dynamic-pdf-fields/96101 ||/4 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||6475 Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #6 from Stéphane Guillou (stragu) --- This has been brought up on ask.LO before: - https://ask.libreoffice.org/t/dynamic-pdf-fields/96101/4 - https://ask.libreoffice.org/t/math-calculations-in-pdf-forms/12208/4 I understand comment 4 to be the current workaround "recipe" to use a layout created in LibreOffice, export as PDF, open it in Scribus to then add the calculated fields (which uses JavaScript) and export again to PDF. Adobe Acrobat (Pro and Sign as far as I can tell) also allows creating those too. So I guess the enhancement request is twofold: - support calculated fields in a form created with Writer document (is there anything in ODF for that?) - support their export as PDF (In reply to Mike Sapsard from comment #4) > Although LO can do arithmetic in Base and Calc forms, this cannot be > exported to pdf for a standalone fillable form. Any chance you could also attach an example Calc file that has such form controls? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106475] FILEOPEN PDF: Javascript commands imported as text
https://bugs.documentfoundation.org/show_bug.cgi?id=106475 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7834 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158190] Calc ROUND() function issue in specific range
https://bugs.documentfoundation.org/show_bug.cgi?id=158190 --- Comment #3 from Mike Kaganski --- Note that the range you identified is not something special; e.g., the same error would happen with =ROUND(1.143541958418614 * 9283; 0) and the only thing that matters is that the floating-point number is very close to X.5, but a bit less, by a few ULPs - so something like 10939.4998. The range between 16 and 24 makes the specific multiplier of 650 expose many of these; but for a different multiplier, a different range would exhibit the same problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158191] New: Shows the error when typing Infosys and Sri
https://bugs.documentfoundation.org/show_bug.cgi?id=158191 Bug ID: 158191 Summary: Shows the error when typing Infosys and Sri Product: LibreOffice Version: 7.6.2.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lakshmihk2...@gmail.com Description: no spelling mistakes but it shows the error Steps to Reproduce: 1.Go to LO writer 2.type a word Infosys , Sri or sri 3. Actual Results: shows the error Expected Results: Don't shows the error Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37887] Autotext does not function within comments
https://bugs.documentfoundation.org/show_bug.cgi?id=37887 --- Comment #13 from mike breac --- When it comes to exploring the vibrant markets and serene lakes of Srinagar, https://www.srinagarcabservice.com/;>Cab Service in Srinagar ensures you don't miss a thing. The drivers are not just guides; they are enthusiasts eager to share the beauty of their city with you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37887] Autotext does not function within comments
https://bugs.documentfoundation.org/show_bug.cgi?id=37887 --- Comment #12 from mike breac --- [url=www.srinagarcabservice.com/] Srinagar cab service [/url] CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Status|NEW |NEEDINFO --- Comment #10 from Buovjaga --- With the steps in the description, the default is "For the current document only". Andras: did you leave this option checked? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 127547, which changed state. Bug 127547 Summary: Freeze/crash in Microsoft Print to PDF dialog when trying to paste (Ctrl-V) a filename in the 'Save Print Output As' dialog https://bugs.documentfoundation.org/show_bug.cgi?id=127547 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127547] Freeze/crash in Microsoft Print to PDF dialog when trying to paste (Ctrl-V) a filename in the 'Save Print Output As' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=127547 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|WORKSFORME |--- Status|RESOLVED|NEW --- Comment #13 from Buovjaga --- Still repro. However, in bug 149998 comment 1 Stuart said "happens with other applications as well. Word 2019 for example". So it might be notourbug. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c0c8cffd3541e3cd616c96791b04e7ebf2b2ed03 CPU threads: 2; OS: Windows 10.0 Build 22621; 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 158124] Holding down delete key doesn't work and causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=158124 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|WORKSFORME |--- Status|RESOLVED|UNCONFIRMED --- Comment #7 from Buovjaga --- Back to unconfirmed. WFM would be for when you can repro with an older version, but not with a newer one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104862] When opening documents of multiple types at the same time, they open as untitled on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=104862 --- Comment #11 from Buovjaga --- I can't repro either, but I don't have Windows 7 at the moment. Let's keep as WFM for now. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c0c8cffd3541e3cd616c96791b04e7ebf2b2ed03 CPU threads: 2; OS: Windows 10.0 Build 22621; 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 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 Buovjaga changed: What|Removed |Added Keywords||bibisected, bisected, ||implementationError -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158190] Calc ROUND() function issue in specific range
https://bugs.documentfoundation.org/show_bug.cgi?id=158190 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Mike Kaganski --- As you correctly identified in https://gerrit.libreoffice.org/c/core/+/159193, it is caused by a special handling of nDecPlaces == 0 with rtl_math_RoundingMode_Corrected in rtl_math_round, when it doesn't use rtl::math::approxFloor, as used with other values of nDecPlaces. This makes the nDecPlaces == 0 ti actually not use "corrected" behavior, as defined in the API [1]: > Like HalfUp, but corrects roundoff errors The special casing of nDecPlaces == 0 with rtl_math_RoundingMode_Corrected looks unneeded there at all, so as I suggested there in the change, the preferred solution would be not fixing the special casing, but removing it, and allowing the general case code to do its job. Thank you! [1] https://opengrok.libreoffice.org/xref/core/include/rtl/math.h?r=b1fb6338=2922=108#106 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158190] Calc ROUND() function issue in specific range
https://bugs.documentfoundation.org/show_bug.cgi?id=158190 --- Comment #1 from Po-Yen Huang --- Created attachment 190801 --> https://bugs.documentfoundation.org/attachment.cgi?id=190801=edit As bug example -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158190] New: Calc ROUND() function issue in specific range
https://bugs.documentfoundation.org/show_bug.cgi?id=158190 Bug ID: 158190 Summary: Calc ROUND() function issue in specific range Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jeff.hu...@ossii.com.tw Description: For math formula in ROUND() function: 1. If the integer is below 15 (inclusive) or above 25 (inclusive), the result will be correct regardless of the decimal. 2. The integer part falls between 16 and 24. As long as the first decimal is 3 or 8, the ROUND() function will not round. But if ROUND a number but not formula, we can get correct result. Steps to Reproduce: 1. Insert a number in a cell like description above (for example, 16.83 or 16.33) 2. Insert a number (that can be multiplied with step 1 to X.5) in another cell 3. Insert =ROUND(A1*B1,0) in another cell (multiply step 1 and step 2 number and ROUND it) Actual Results: It seems to be rounding down (for example, ROUND(16.33*650) shows 10614) Expected Results: It should be rounding (for example, ROUND(16.33*650) should be 10615) Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+xcb) Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW 7.6.2-3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742 Bug 107742 depends on bug 141205, which changed state. Bug 141205 Summary: FORM CONTROLS: Saving while a text box is focused will focus the next select input https://bugs.documentfoundation.org/show_bug.cgi?id=141205 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141205] FORM CONTROLS: Saving while a text box is focused will focus the next select input
https://bugs.documentfoundation.org/show_bug.cgi?id=141205 --- Comment #8 from QA Administrators --- Dear Matheod, 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 141205] FORM CONTROLS: Saving while a text box is focused will focus the next select input
https://bugs.documentfoundation.org/show_bug.cgi?id=141205 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 155336] EDITING: freeze and crash after editing header
https://bugs.documentfoundation.org/show_bug.cgi?id=155336 --- Comment #4 from QA Administrators --- Dear sunnypony03, 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 155339] XAccessibleStateSet Raise error on import in LO 7.5
https://bugs.documentfoundation.org/show_bug.cgi?id=155339 --- Comment #9 from QA Administrators --- Dear vibrationoflife, 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 155317] Numbering of sections if there are hidden ones
https://bugs.documentfoundation.org/show_bug.cgi?id=155317 --- Comment #2 from QA Administrators --- Dear Vladimir, 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 98774] Splash screen does not show up under Mac OS X after first launch in desktop session.
https://bugs.documentfoundation.org/show_bug.cgi?id=98774 --- Comment #17 from QA Administrators --- Dear Emilio Rezzonico, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155233] Saving then reopening a document with tables
https://bugs.documentfoundation.org/show_bug.cgi?id=155233 --- Comment #2 from QA Administrators --- Dear TonyB, 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 61633] VIEWING: Drawing objects anchored to paragraphs inside frames display incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=61633 --- Comment #12 from QA Administrators --- Dear bram.wayman, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155215] Sometimes the file doesn't open
https://bugs.documentfoundation.org/show_bug.cgi?id=155215 --- Comment #2 from QA Administrators --- Dear Andrius, 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 137590] FILEOPEN DOCX Image in table incorrectly imported position
https://bugs.documentfoundation.org/show_bug.cgi?id=137590 --- Comment #4 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128607] Firebird database not writable via BASIC from Calc even when ODB registered.
https://bugs.documentfoundation.org/show_bug.cgi?id=128607 --- Comment #19 from QA Administrators --- Dear Nukool Chompuparn, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113540] Setting the alignment of a cell to "Filled" does not show an arrow on overflowing content
https://bugs.documentfoundation.org/show_bug.cgi?id=113540 --- Comment #6 from QA Administrators --- Dear sworddragon2, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107857] Incorrect formatting logic when replacing formatted selected text (should be true replace instead of delete+insert)
https://bugs.documentfoundation.org/show_bug.cgi?id=107857 --- Comment #26 from QA Administrators --- Dear Kevin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117454] EDITING Writer crashes when manipulating variables in Compress window
https://bugs.documentfoundation.org/show_bug.cgi?id=117454 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu --- Comment #12 from Steven Casey --- Can't repro, calculate size button works and returns "39 KiB (0% reduction)". Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 --- Comment #9 from Steven Casey --- (In reply to m.a.riosv from comment #8) > What language do you set up in? > Menu/Tools/Options/Language settings/Default languages for documents. Using the provided steps from the report, it doesn't save. Changing the default languages using the steps you provided (comment 8) does persist however. Perhaps this is not a bug like I initially thought and could just be a misunderstanding as it isn't super clear it is only for that document. Hopefully Andras can confirm. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 127547, which changed state. Bug 127547 Summary: Freeze/crash in Microsoft Print to PDF dialog when trying to paste (Ctrl-V) a filename in the 'Save Print Output As' dialog https://bugs.documentfoundation.org/show_bug.cgi?id=127547 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127547] Freeze/crash in Microsoft Print to PDF dialog when trying to paste (Ctrl-V) a filename in the 'Save Print Output As' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=127547 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #12 from Steven Casey --- Not reproducible for me. Considering sdc (comment 10) can't reproduce either, going to mark this report as WORKSFORME. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 149998, which changed state. Bug 149998 Summary: Libre Office Writer crashes with Save As PDF https://bugs.documentfoundation.org/show_bug.cgi?id=149998 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127547] Freeze/crash in Microsoft Print to PDF dialog when trying to paste (Ctrl-V) a filename in the 'Save Print Output As' dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=127547 Steven Casey changed: What|Removed |Added CC||bill-ho...@telus.net --- Comment #11 from Steven Casey --- *** Bug 149998 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 149998] Libre Office Writer crashes with Save As PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=149998 Steven Casey changed: What|Removed |Added Resolution|--- |DUPLICATE CC||stca...@csumb.edu Status|NEW |RESOLVED --- Comment #5 from Steven Casey --- Marking as duplicate of https://bugs.documentfoundation.org/show_bug.cgi?id=127547 to keep everything in one place. *** This bug has been marked as a duplicate of bug 127547 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104862] When opening documents of multiple types at the same time, they open as untitled on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=104862 Steven Casey changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME CC||stca...@csumb.edu --- Comment #10 from Steven Casey --- No longer reproducible. Marking as WORKSFORME. Tested with password protected documents as attached here, and non-protected as mentioned in the duplicate bug. Both worked as intended. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108075] [META] Scrolling and Page up/down issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108075 Bug 108075 depends on bug 58510, which changed state. Bug 58510 Summary: UI: distorted screen during scrolling. https://bugs.documentfoundation.org/show_bug.cgi?id=58510 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58510] UI: distorted screen during scrolling.
https://bugs.documentfoundation.org/show_bug.cgi?id=58510 Steven Casey changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #12 from Steven Casey --- Marking as WORKSFORME, no longer reproducible. Searched for similar reports since its been awhile since the last repro and came up with nothing. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158139] Writer, Word Completion does not function
https://bugs.documentfoundation.org/show_bug.cgi?id=158139 --- Comment #5 from MW --- Tried what RGB described on 2023-11-11 22:40:36 UTC with a 129 page document (not that it needed to be that long) and that's it. The document needs words/phrases to autocomplete/suggest. If the intent of the auto complete function was to work without prementioned words then its a bug. If it works based on what's already there in the document then its working as intended. There is limit max entry of words (65536) and a min word length (5). Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; 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 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 --- Comment #8 from m.a.riosv --- What language do you set up in? Menu/Tools/Options/Language settings/Default languages for documents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83660] VIEWING: In slide show windows taskbar doesnt disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=83660 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu --- Comment #21 from Steven Casey --- Not repro for me on W11. Keep Presentation always on top setting is unchecked. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158189] New: Hidden page break with multiple columns and table at the page beginning
https://bugs.documentfoundation.org/show_bug.cgi?id=158189 Bug ID: 158189 Summary: Hidden page break with multiple columns and table at the page beginning Product: LibreOffice Version: 7.6.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: de...@web.de Created attachment 190800 --> https://bugs.documentfoundation.org/attachment.cgi?id=190800=edit example file with not displayed page break Description: The blue dashed line between two pages, which indicates a manual page break, is hidden (as if there were no manual page break) if the page layout is set to several columns (e.g. 2) and a table is inserted at the very beginning of the second page. Steps to Reproduce: 1. Create a new Text Document 2. Apply on the "Default Page Style" the Setting "Columns: 2" (There should now be 2 cols) 5. Hit Ctrl+Return to create a man. page break 6. Hit Ctrl+F12 to insert an empty two by two table Actual Results: The blue dashed line is gone and the page break cant be removed. Expected Results: The page break should be visible. Reproducible: Always User Profile Reset: Yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100376] Line jumps to footer after deleting triangle behind it
https://bugs.documentfoundation.org/show_bug.cgi?id=100376 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu --- Comment #10 from Steven Casey --- Still reproducible. Ctrl + z after creates more of an issue as mentioned. Attempting to close the file after using ctrl + z does not result in a popup, but reopening the file shows only one triangle. That single triangle is now missing the line however. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133965] Content copied outside the selection
https://bugs.documentfoundation.org/show_bug.cgi?id=133965 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu --- Comment #6 from Steven Casey --- Not sure if this is a bug. It seems to also change the page style as a whole. May be intended. Like Bogdan noticed, it doesn't occur when just the image or text is copied. Only if they are copied together. Still repro in: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158185] VBA Support 1: The Range.Find method interprets "#" as a wildcard character
https://bugs.documentfoundation.org/show_bug.cgi?id=158185 Eike Rathke changed: What|Removed |Added CC||er...@redhat.com Version|unspecified |Inherited From OOo --- Comment #1 from Eike Rathke --- It looks like the Calc implementation assumed that # in VBA is not supposed to find a literal # character, but is a wildcard matching a single digit instead. See https://learn.microsoft.com/en-us/office/vba/Language/Reference/User-Interface-Help/wildcard-characters-used-in-string-comparisons . So returning $A$2 as the first match looks to be correct according to that. But, with Find() Excel apparently (to be verified) does not do what that documentation says.. and indeed https://learn.microsoft.com/en-us/office/vba/api/excel.range.find says for What only "Can be a string or any Microsoft Excel data type." and only later in Remarks mentions "To find cells that match more complicated patterns, use a For Each...Next statement with the Like operator." It seems Calc implemented that Like operator behaviour with the Find() function (translating those wildcard operators to regular expressions). Code pointers: sc/source/ui/vba/vbarange.cxx ScVbaRange::Find() and ScVbaRange::Replace() and their calls to VBAToRegexp(sWhat) and see use of SC_UNO_SRCHREGEXP property. That may be wrong, but caveat, changing it may as well break existing VBA code created with OOo/LibreOffice that relies on it.. though maybe people didn't dive that far into it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158124] Holding down delete key doesn't work and causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=158124 Steven Casey changed: What|Removed |Added Resolution|--- |WORKSFORME CC||stca...@csumb.edu Status|UNCONFIRMED |RESOLVED --- Comment #6 from Steven Casey --- Unable to repro here as well. del key and backspace do not result in a crash for me. I am on Windows however. Marking as WORKSFORME since Stephane, steve, and ToanTran can't repro. tested with: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158186] Mismatching config key name and property name in UI code
https://bugs.documentfoundation.org/show_bug.cgi?id=158186 --- Comment #2 from MW --- I couldn't reproduce this on win 10 version. There is an option for "Bullet and number list. Bullet symbol" but no "Bulleted and numbered lists immediate after pressing space" option. Also the option that is there does not reset when restarting LO. Potentially Linux specific. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; 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 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 Steven Casey changed: What|Removed |Added CC||stca...@csumb.edu Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #7 from Steven Casey --- Hello Andras, thank you for your report. I can confirm it is reproducible even in Windows. Languages do not save regardless of the selected language. It stays for the document it is changed on, but does not apply to new/old documents. Tested with: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155224] Libreoffice Writer Freezes and Crashes with multiple windows open and languageTool extension installed
https://bugs.documentfoundation.org/show_bug.cgi?id=155224 --- Comment #13 from agap...@hotmail.com --- Actually, testing it again I get a crash every time I enable "check spelling as you type" option. If i disable that, the crashes disappear. It seems to be related to this feature. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155224] Libreoffice Writer Freezes and Crashes with multiple windows open and languageTool extension installed
https://bugs.documentfoundation.org/show_bug.cgi?id=155224 agap...@hotmail.com changed: What|Removed |Added Status|NEEDINFO|REOPENED --- Comment #12 from agap...@hotmail.com --- It seems that this issue has mostly disappeared with the new LibreOffice versions with the updated extension. However, it still appears sometimes but I haven't been able to consistently reproduce it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158168] Cannot create a keyboard shortcut for a hidden text in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=158168 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Summary|Cannot create a keyboard|Cannot create a keyboard |shortcut for a hidden text |shortcut for a hidden text |in Write|in Writer Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- What exactly do you mean by the "hide text" action? >From what I understand, one needs to create a field to have either hidden text or paragraph, and associate it to a condition. I don't know of an command to simply "hide text" without using a condition. https://help.libreoffice.org/latest/en-US/text/swriter/guide/hidden_text.html In that sense, it's not a single-step action, and therefore is not suitable for a keyboard shortcut. There's already Ctrl + F2 to access the Fields dialog, in which such hidden fields can be created. Alternative would be to create a macro and associate a keyboard shortcut to it. Or am I misundestanding? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 --- Comment #15 from Mike Kaganski --- (In reply to Mike Kaganski from comment #14) Sorry, BIG, not "bit". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 --- Comment #14 from Mike Kaganski --- And bit THANK YOU to J22Gim, who finally created the *really* useful report on this really bad issue, resulted in tens of complaints on Ask already, and who knows how many corrupt documents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126345] Underlining of links is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=126345 Matthew Kogan changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #10 from Matthew Kogan --- For me it's never underlined. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||4823 --- Comment #13 from Mike Kaganski --- Regression after commit b5c616d10bff3213840d4893d13b4493de71fa56 (tdf#104823: support for sdt plain text fields, 2021-12-20). Implementation error. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 --- Comment #6 from m.a.riosv --- Because, some other person, not the reporter, must confirm it, that's all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 Mike Kaganski changed: What|Removed |Added Version|7.3.7.2 release |7.3.0.3 release OS|Linux (All) |All Keywords||filter:docx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #12 from Mike Kaganski --- Username is not important; the bug shows without. The important piece is the range of deletion: in step 2 of comment 0, the selection should start *immediately after "to"*,and go one character after "OpenOffice.org" i.e., it must also select two spaces around the field. Enabling formatting marks can help. (A remark: please, pay attention to the level of details you provide. A screencast is nice, when shows the reproduction on the same attached documents; and/or exact description, including how you enable track change mode - from menu / from shortcut; how you select - using mouse / keyboard (or maybe you don't select, just put cursor in front of...); how you delete - using Backspace or Delete...) In this case, only the range of selection mattered - but you never know before analysing! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158188] New: Trying to sign a PDF destroys the file
https://bugs.documentfoundation.org/show_bug.cgi?id=158188 Bug ID: 158188 Summary: Trying to sign a PDF destroys the file Product: LibreOffice Version: 7.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wolf-dieter.gr...@gmx.de Created attachment 190799 --> https://bugs.documentfoundation.org/attachment.cgi?id=190799=edit Original "unsigned.pdf" and "destroyed.pdf" as a result of the signing attempt. In the past, I have used LibreOffice Draw to easily digitally sign PDFs (X.509). With the last update this function is broken. The Digital Signatures window does not close as usual, and the signed PDF is no longer automatically loaded to verify the signature. If you close the window and then the PDF manually and then try to open it again, the error message "This PDF file is encrypted and can't be opened." is shown. This doesn't seem to be the full truth, as pdfinfo says: $ pdfinfo destroyed.pdf Syntax Error: Invalid object stream Syntax Error: Couldn't find trailer dictionary Syntax Error: Catalog object is wrong type (null) Syntax Error: Couldn't find trailer dictionary Internal Error: xref num -1 not found but needed, try to reconstruct<0a> Syntax Error: Couldn't find trailer dictionary Syntax Error: Couldn't find trailer dictionary Syntax Error: Catalog object is wrong type (null) Syntax Error: Couldn't read page catalog Attachment: - "unsigned.pdf": Original file - "destroyed.pdf": destroyed copy after the signing (attempt). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 --- Comment #11 from Mike Kaganski --- (In reply to J22Gim from comment #7) > Yep, still present: Did you try to open an already corrupted document - which would indeed give the error; or did you try to do the steps from comment 0, to see if the new version corrupts the good documents? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153197] FILEOPEN RTF Paragraph style tabulator deleted by DF is not removed
https://bugs.documentfoundation.org/show_bug.cgi?id=153197 Gabor Kelemen (allotropia) changed: What|Removed |Added Resolution|--- |FIXED See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8044 Status|NEW |RESOLVED --- Comment #4 from Gabor Kelemen (allotropia) --- Verified in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded No extra tabs are now imported, after https://git.libreoffice.org/core/commit/fce18155052821756466ea043c638f4ed72f41d6 tdf#158044 handling of paragraph attributes in RTF import -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158044] RTF import paragraph style attribute handling wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=158044 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3197 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113340] [META] RTF (text) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113340 Bug 113340 depends on bug 153197, which changed state. Bug 153197 Summary: FILEOPEN RTF Paragraph style tabulator deleted by DF is not removed https://bugs.documentfoundation.org/show_bug.cgi?id=153197 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158044] RTF import paragraph style attribute handling wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=158044 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113340] [META] RTF (text) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113340 Bug 113340 depends on bug 158044, which changed state. Bug 158044 Summary: RTF import paragraph style attribute handling wrong https://bugs.documentfoundation.org/show_bug.cgi?id=158044 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158044] RTF import paragraph style attribute handling wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=158044 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Gabor Kelemen (allotropia) --- Verified in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded Document now looks like in Word. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157982] Last used documents not reflected in ~/.local/share/recently-used.xbel
https://bugs.documentfoundation.org/show_bug.cgi?id=157982 --- Comment #1 from wisedev...@gmail.com --- I've noted a different behavior. Saved docs (.docx in my case) are added to gtk recent files. But when you save as pdf, the file is stored without ".pdf" extension and so the link refers to non existent file and won't be shown in recent directory. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158187] [feature request] copy rules from Manage < Conditional Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=158187 --- Comment #1 from mattia.b89 --- Created attachment 190798 --> https://bugs.documentfoundation.org/attachment.cgi?id=190798=edit mockup -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158187] New: [feature request] copy rules from Manage < Conditional Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=158187 Bug ID: 158187 Summary: [feature request] copy rules from Manage < Conditional Formatting Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mattia@gmail.com Description: Issue was born here [https://ask.libreoffice.org/t/conditional-formatting-multiple-range/98131] originally. Long story short: conditional rules cannot have multiple ranges. Easiest way to overcome this problem is to simply copy rules, then change cell range manually, case-by-case; Unfortunately when you copy the conditional formatting*, LO does not create a new rule but "increases" the cell range** in existing rule. *by copying the cell with the conditional formatting, Edit > Paste Special, uncheck “Paste all” and uncheck all boxes in the Selection area except Formats; **maybe this is a desired behaviour since condition is the same... With a simple "Copy" button in the conditional formatting, we can fix this issue. --- a simple mockup is attached below. Steps to Reproduce: try to copy a conditional formatted rule Actual Results: you cannot Expected Results: you can Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: it-IT (en_GB.UTF-8); UI: en-GB 7.6.2-3 Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158186] Mismatching config key name and property name in UI code
https://bugs.documentfoundation.org/show_bug.cgi?id=158186 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 190797 --> https://bugs.documentfoundation.org/attachment.cgi?id=190797=edit After restart, it's disabled again -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158186] New: Mismatching config key name and property name in UI code
https://bugs.documentfoundation.org/show_bug.cgi?id=158186 Bug ID: 158186 Summary: Mismatching config key name and property name in UI code Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Keywords: implementationError Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com CC: szymon.k...@collabora.com Created attachment 190796 --> https://bugs.documentfoundation.org/attachment.cgi?id=190796=edit The option is first enabled While searching for unused config keys, I found in Writer.xcs the ApplyBulletsAfterSpace which is seemingly not used by the code. This was added recently in commit https://cgit.freedesktop.org/libreoffice/core/commit/?id=c4fc18308074634e9578ad12d94d937f259aa22a but when the code wants to save it, the property name in SvxSwAutoCorrCfg::GetPropertyNames is "Format/ByInput/ApplyNumberingAfterSpace", //48 which is not the same. Changing the value in the UI won't be remembered after restart of LO. 1. Open Writer, go to Tools - AutoCorrect - AutoCorrect options 2. Go to the Options tab, and in the list enable the new "Bulleted and numbered lists immediate after pressing space" option 3. Press OK, restart LO 4. Go back to the AutoCorrect options - Options tab -> "Bulleted and numbered lists immediate after pressing space" option is unchecked Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 41d9584179ef7b4e18eda47c2c0a955df8c087a5 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147746] Navigator: Makes comments that are marked resolved sensitive to resolved comments show state
https://bugs.documentfoundation.org/show_bug.cgi?id=147746 Jim Raykowski changed: What|Removed |Added Resolution|INVALID |WORKSFORME --- Comment #3 from Jim Raykowski --- After reading the Status help, RESOLVED INVALID isn't correct. RESOLVED WORKSFORME seems a better fit to me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157255] Identify the layer of the object in focus
https://bugs.documentfoundation.org/show_bug.cgi?id=157255 --- Comment #10 from Stéphane Guillou (stragu) --- (In reply to Jim Raykowski from comment #9) > Created attachment 190794 [details] > demo of possible enhancement to identify objects in a layer by mouse hover > over layer tab > > (In reply to Stéphane Guillou (stragu) from comment #2) > > Alternatively, with the current UI, an x-ray / negative highlight on > > hovering the layer's tab? > Maybe like what is shown in the attached demo? Looks great, thank you Jim! It think that's a great improvement, please do submit a patch. Dapgo, does Jim's feature + Regina's suggestion in comment 1 cover your original issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113300] [META] Language detection bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113300 Bug 113300 depends on bug 152706, which changed state. Bug 152706 Summary: TRANSLATION: "Requested clipboard format is not available" error message when using DeepL translation feature https://bugs.documentfoundation.org/show_bug.cgi?id=152706 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152706] TRANSLATION: "Requested clipboard format is not available" error message when using DeepL translation feature
https://bugs.documentfoundation.org/show_bug.cgi?id=152706 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #17 from Stéphane Guillou (stragu) --- (In reply to Sebastiaan Veld from comment #16) > It works for me using the latest daily build Ok, let's mark as "works for me" then. Dieter, if you still have issues with a master build, please set back to unconfirmed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155302] Table reformatting causes font colour switches or reversions
https://bugs.documentfoundation.org/show_bug.cgi?id=155302 glibgu...@protonmail.com changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #4 from glibgu...@protonmail.com --- Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.8 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Bug 106179 depends on bug 147746, which changed state. Bug 147746 Summary: Navigator: Makes comments that are marked resolved sensitive to resolved comments show state https://bugs.documentfoundation.org/show_bug.cgi?id=147746 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 147746, which changed state. Bug 147746 Summary: Navigator: Makes comments that are marked resolved sensitive to resolved comments show state https://bugs.documentfoundation.org/show_bug.cgi?id=147746 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147746] Navigator: Makes comments that are marked resolved sensitive to resolved comments show state
https://bugs.documentfoundation.org/show_bug.cgi?id=147746 Jim Raykowski changed: What|Removed |Added Resolution|--- |INVALID Status|ASSIGNED|RESOLVED Assignee|rayk...@gmail.com |libreoffice-b...@lists.free ||desktop.org --- Comment #2 from Jim Raykowski --- Removing myself from assignee and setting to RESOLVED INVALID? since comment visibility state in the Navigator has been addressed by the patch given in the link in the above comment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152706] TRANSLATION: "Requested clipboard format is not available" error message when using DeepL translation feature
https://bugs.documentfoundation.org/show_bug.cgi?id=152706 --- Comment #16 from Sebastiaan Veld --- It works for me using the latest daily build, I can now translate a scentence to another language. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 50add2043752c7b07beccef9a509bea6c09619f8 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158185] New: VBA Support 1: The Range.Find method interprets "#" as a wildcard character
https://bugs.documentfoundation.org/show_bug.cgi?id=158185
Bug ID: 158185
Summary: VBA Support 1: The Range.Find method interprets "#" as
a wildcard character
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: so...@comec92.ru
Run the following macro on a Calc document that has Sheet1:
Option VBASupport 1
Option Explicit
Sub test()
With Worksheets("Sheet1")
Dim r As Range
.Range("A1").Value = "#a"
.Range("A2").Value = "1a"
Set r = .Cells.Find(What:="#a", LookIn:=xlValues, LookAt:=xlPart, _
SearchOrder:=xlByRows, SearchDirection:=xlNext, MatchCase:=False,
SearchFormat:=False)
If Not (r Is Nothing) Then MsgBox "Found " & r.Address
End With
End Sub
Result: Found $A$2
Excel VBA shows: Found $A$1
Possible reason for the discrepancy: Calc interprets the # sign as a wildcard
character, Excel does not.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125580] Wrong value when adding two dates
https://bugs.documentfoundation.org/show_bug.cgi?id=125580
N.A. Hoijtink changed:
What|Removed |Added
Status|NEW |UNCONFIRMED
Ever confirmed|1 |0
--- Comment #18 from N.A. Hoijtink ---
I can confirm a similar (same?) issue with off calculations:
if you enter a date+time value in the first row, and then add for e.g.
timevalue("00:15:00,000") to the previous cell and the use fill (drag it down)
at some point the datetime displayed equals ../../.. xx:59:59
for example enter in the first cell =datevalue(2023;12;3)+timevalue(0,15,0),
next cell = "previous cell"+timevalue("00:15:00,000") at some point it results
in a unexpected value (1 second less), in my case example at the 25th row.
so to be exact:
A103-12-2023 00:00:00,000 (enter some date/time combo in first
cell)
A2=A1+TIMEVALUE("00:15:00,000")(formula to drag down from cell 2
onwards) results 03-12-2023 00:15:00
.
.
.
.
A25 =A24+TIMEVALUE("00:15:00,000") results
03-12-2023 05:59:59
There seems to be some sort of a precision issue and it happens really
fast.
My system is a AMD Ryzen 7 5700G running Windows 10 24H1 OS Build 19043.3208
(Dutch), LibreOffice 7.6.0.3 (x86+64) Dutch
Not sure if it is the exact same issue or a more specific date/time issue
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 --- Comment #10 from Roman --- > > However, _not_ reproduced with: > > Version: 7.6.2.1 (X86_64) / LibreOffice Community > Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 > CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 > Locale: en-AU (en_AU.UTF-8); UI: en-US > Calc: threaded > > Can you please test again with 7.6.2.1? Уточните наличие поведения при заполненном ФИО Check if there is any behavior when your full name is filled in -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157985] Corrupt DOCX document after saving (track changes involved) 2
https://bugs.documentfoundation.org/show_bug.cgi?id=157985 Buovjaga changed: What|Removed |Added Ever confirmed|1 |0 Status|NEW |UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157985] Corrupt DOCX document after saving (track changes involved) 2
https://bugs.documentfoundation.org/show_bug.cgi?id=157985 Roman changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #13 from Roman --- https://bugs.documentfoundation.org/show_bug.cgi?id=157326#c8 157326 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157985] Corrupt DOCX document after saving (track changes involved) 2
https://bugs.documentfoundation.org/show_bug.cgi?id=157985 Buovjaga changed: What|Removed |Added Ever confirmed|1 |0 CC||ilmari.lauhakangas@libreoff ||ice.org Status|NEW |UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 Buovjaga changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157326] track changes on input fields result in exception and not able to open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=157326 Roman changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #9 from Roman --- https://bugs.documentfoundation.org/show_bug.cgi?id=157985 Эх оказывается я запоздал, но у уже один как приятно. Eh, it turns out I’m late, but I’m already alone, how nice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158184] help contains unminified html, js and css files
https://bugs.documentfoundation.org/show_bug.cgi?id=158184 Jérôme changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158184] New: help contains unminified html, js and css files
https://bugs.documentfoundation.org/show_bug.cgi?id=158184 Bug ID: 158184 Summary: help contains unminified html, js and css files Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jerome.bo...@laposte.net CC: olivier.hal...@libreoffice.org Minifying those files could slightly lower their size and speed-up their loading/parsing. The online help could be slightly faster. In addition, the size of installation archives could be reduced. I mean "minification" as defined here : https://en.wikipedia.org/wiki/Minification_(programming) -- You are receiving this mail because: You are the assignee for the bug.
