[Libreoffice-bugs] [Bug 156832] Symbol names in Math examples are not localized
https://bugs.documentfoundation.org/show_bug.cgi?id=156832 --- Comment #1 from Theppitak Karoonboonyanan --- FYI, I have untranslated all symbol names for Thai in master. It's also more appropriate for Thai users to use original English names in codes, as there are several localized versions in use in text books, although there is a standardization effort by the Royal Academy. With the untranslated names, the problem is gone. But the inconsistency of symbol names in examples is still a valid bug. They should still be localized anyway. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156640] REPORTBUILDER: Blank Window after change of Data Field Type
https://bugs.documentfoundation.org/show_bug.cgi?id=156640 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 156598] Custom list numbering from DOCX import is not available in UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156598 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 156662] Always using direct connection to api.languagetool.org
https://bugs.documentfoundation.org/show_bug.cgi?id=156662 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 156826] Impossible de pré-formater des cellules
https://bugs.documentfoundation.org/show_bug.cgi?id=156826 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156674] UI: formula help still displayed when editing cell formatted as text
https://bugs.documentfoundation.org/show_bug.cgi?id=156674 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 156676] Spreadsheet: converting formulas formatted as text to show formula result
https://bugs.documentfoundation.org/show_bug.cgi?id=156676 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 156826] Impossible de pré-formater des cellules
https://bugs.documentfoundation.org/show_bug.cgi?id=156826 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156606] Fileopen DOTX: poorly converted in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156606 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156606] Fileopen DOTX: poorly converted in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156606 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152925] LibreOffice: no visibility of menu when I open "Formatvorlagen verwalten"
https://bugs.documentfoundation.org/show_bug.cgi?id=152925 --- Comment #3 from QA Administrators --- Dear steam2, 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 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152925] LibreOffice: no visibility of menu when I open "Formatvorlagen verwalten"
https://bugs.documentfoundation.org/show_bug.cgi?id=152925 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 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151838] EDITING: Find hard carriage return does not work.
https://bugs.documentfoundation.org/show_bug.cgi?id=151838 --- Comment #4 from QA Administrators --- Dear f.pignal, 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 151838] EDITING: Find hard carriage return does not work.
https://bugs.documentfoundation.org/show_bug.cgi?id=151838 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 142347] add ability to change the background and font colours of the new tabbed/ribbon view (LibreOffice writer)
https://bugs.documentfoundation.org/show_bug.cgi?id=142347 --- Comment #7 from QA Administrators --- Dear joe-pringle, 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 142347] add ability to change the background and font colours of the new tabbed/ribbon view (LibreOffice writer)
https://bugs.documentfoundation.org/show_bug.cgi?id=142347 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 151644] Full system stop for a minute and then libre office exel crash with the need to recover files as they become corrupt
https://bugs.documentfoundation.org/show_bug.cgi?id=151644 --- Comment #8 from QA Administrators --- Dear igor2001wilczynski, 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 151399] LibreOffice 7.3.6.2 Impress freezes when saving on Ubuntu 22.04
https://bugs.documentfoundation.org/show_bug.cgi?id=151399 --- Comment #3 from QA Administrators --- Dear Henry, 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 143899] FILEOPEN DOCX Shapes overlap margin in CompatibilityMode15
https://bugs.documentfoundation.org/show_bug.cgi?id=143899 --- Comment #5 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 83762] FORMATTING: Cursor can be Positioned beyond Paper Margins by Using Negative Indentation Values
https://bugs.documentfoundation.org/show_bug.cgi?id=83762 --- Comment #12 from QA Administrators --- Dear Harald Koester, 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 115292] FILEOPEN open PDF - picture shifted
https://bugs.documentfoundation.org/show_bug.cgi?id=115292 --- Comment #8 from QA Administrators --- Dear solar020, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 140450] PDF export 1.6: The document does not conform to the requested standard.
https://bugs.documentfoundation.org/show_bug.cgi?id=140450 --- Comment #2 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104185] Better Autoinput for functions (or different default than ENTER)
https://bugs.documentfoundation.org/show_bug.cgi?id=104185 --- Comment #10 from QA Administrators --- Dear Mieszko, 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 156787] docx format not entirely correct
https://bugs.documentfoundation.org/show_bug.cgi?id=156787 --- Comment #4 from hoang.hano...@gmail.com --- Hi Vladimir, I have tested both Microsoft Office docx file and Libre Office docx file uploaded to the website with your provided account. I have not seen any issue with uploading the Libre Office version as I expected. Your issue could probably comes from the inner content of the file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156791] LibreOffice 7.5.5 has memory leak
https://bugs.documentfoundation.org/show_bug.cgi?id=156791 --- Comment #7 from vxs2...@yahoo.com --- I do have the latest drivers. After disabling Vulkan the memory leak appears to be fixed. So I guess that means either your use of the Vulkan API is bugged or AMD's drivers are buggy which wouldn't be surprising considering I recently filed a different bug report (https://bugs.chromium.org/p/chromium/issues/detail?id=1463267) caused by AMD's drivers -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156869] New: Document isn't saved when opening a .docx file by dragging it from an encrypted .zip file to LibreOffice main screen
https://bugs.documentfoundation.org/show_bug.cgi?id=156869 Bug ID: 156869 Summary: Document isn't saved when opening a .docx file by dragging it from an encrypted .zip file to LibreOffice main screen Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lotanb...@gmail.com Description: After consulting with the AskLibre forum, I reached this site. I've tried numerous archiving software, I'm usually using the portable version, but tried it both on the installed one and the portable (7.5.4 and 7.4.7). When saving it shows the saving dialogue (2007 docx or odt format), I click one of them (doesn't matter, same result), and exit the file. Usually, when I use word office to edit the document, I get a pop up from the archiving software saying "update modified files?". but when opening it with LibreOffice - nothing. Perhaps it would be of any help if I tell you the zip is encrypted AND the file is encrypted, but I'll be honest I haven't tried to examine this particular point properly, and do not know if it's linked Steps to Reproduce: 1.open an archived file in archiving software 2.open LibreOffice main screen 3.drag the file from the archiving software to the main screen 4.make some changes and save 5. open it again and check if the file is saved Actual Results: the file isn't saved Expected Results: the file should be saved Reproducible: Always User Profile Reset: Yes Additional Info: Well, I like your software very much, it seems like you did a great job and created a great alternative for the pricey ms office. I'm using your software' portable version daily now, the only downside, is that I can't edit documents from my encrypted zip... Please help! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed if schema could be chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #30 from prrv...@gmail.com --- The integration in Base is finished. There remains, despite everything, the management of the combobox. I'm stuck for adding XConnection2 interface in the file: connectivity/source/drivers/jdbc/JConnection.cxx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156868] Find function should highligh all instances of found keyword
https://bugs.documentfoundation.org/show_bug.cgi?id=156868 --- Comment #1 from Juergen --- Created attachment 189103 --> https://bugs.documentfoundation.org/attachment.cgi?id=189103=edit Multiple instance search display in Firefox -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156868] New: Find function should highligh all instances of found keyword
https://bugs.documentfoundation.org/show_bug.cgi?id=156868 Bug ID: 156868 Summary: Find function should highligh all instances of found keyword Product: LibreOffice Version: 7.3.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: all.onl...@posteo.eu Description: When using the Find function the searched phrase is only highlighted one by one. In other softwares all instances are highlighted at once. This is very helpful to detect repetitions when writing a book for example. Steps to Reproduce: 1. load any text 2. enter search word in Find function 3. Actual Results: Only one instance at a time is shown Expected Results: All instances should be shown. Example Firefox search function, see screen shot Reproducible: Always User Profile Reset: No Additional Info: All instances should be shown. Example Firefox search function, see screen shot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156858] LibreCalc wrong subtraction of numbers 0, 0000000000001
https://bugs.documentfoundation.org/show_bug.cgi?id=156858 --- Comment #3 from ady --- (In reply to m.a.riosv from comment #2) > It works fine with > Version: 7.5.7.0.0+ (X86_64) / LibreOffice Community Are you sure? Have you tried expanding the width of the column? My guess is that this behavior is related to floating-point math capabilities, but I'll leave it to others with relevant knowledge of the matter to answer (with a proper reply, rather than a guess). Whether this particular subtraction is supposed to be exact, or with some inaccuracy because of floating-point math, IDK. https://wiki.documentfoundation.org/Faq/Calc/Accuracy -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156842] Export to PDF that includes PDF images are incorrect in size (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156842 Telesto changed: What|Removed |Added Summary|Export to PDF that includes |Export to PDF that includes |PDF images are incorrect in |PDF images are incorrect in |size|size (macOS) --- Comment #6 from Telesto --- Confirm with macOS Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e60ef8651cfb30335471d1622e58c13eebc7d58b CPU threads: 8; OS: Mac OS X 13.4.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156854] Menu icons are broken on macOS with Skia
https://bugs.documentfoundation.org/show_bug.cgi?id=156854 --- Comment #4 from Patrick Luby --- (In reply to خالد حسني from comment #0) > When Skia is enable, menu icons on macOS are rendered as hallowed > rectangles. This might be related to bug 156853, but it happens only when > Skia is used (while bug 156853 happens all the time). I think you are right: it sure looks like it is another case of an alpha mask that needs to be inverted. This bug does not occur in LibreOffice 7.6.0.3 so it is likely due to the recent transparency->alpha patch. I can take a look at it tomorrow. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156854] Menu icons are broken on macOS with Skia
https://bugs.documentfoundation.org/show_bug.cgi?id=156854 Telesto changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Telesto --- Confirm Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e60ef8651cfb30335471d1622e58c13eebc7d58b CPU threads: 8; OS: Mac OS X 13.4.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156867] LibreOffice logo in start center not properly rendered (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156867 --- Comment #1 from Telesto --- Created attachment 189102 --> https://bugs.documentfoundation.org/attachment.cgi?id=189102=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156867] New: LibreOffice logo in start center not properly rendered (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156867 Bug ID: 156867 Summary: LibreOffice logo in start center not properly rendered (macOS) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: LibreOffice logo in start center not properly rendered (macOS) Steps to Reproduce: 1. Launch LibreOffice.app 2. Look at the logo in the left bottom corner 3. Launch Writer from Start Center 4. Close Writer -> OK Note I have LibreOffice light mode activated in LibreOffice -> preferences -> view . macOS system setting is set to dark-mode Actual Results: See screenshot Expected Results: readable logo Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e60ef8651cfb30335471d1622e58c13eebc7d58b CPU threads: 8; OS: Mac OS X 13.4.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156701] JRE errors messages still appearing for Macros
https://bugs.documentfoundation.org/show_bug.cgi?id=156701 --- Comment #3 from LucasLibre --- > So you should give that feedback as comment in bug 156161, if the problem > isn't fixed. I wasn't sure about any of this, so checked with Mike, who seemed to be the only one working on these issues; he suggested starting a new bug (i.e. this one) and copying him in, which I've done. Will revive the old bug request now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156866] Logo in help about not properly rendered with Skia Raster/Metal (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156866 --- Comment #1 from Telesto --- Created attachment 189101 --> https://bugs.documentfoundation.org/attachment.cgi?id=189101=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156866] New: Logo in help about not properly rendered with Skia Raster/Metal (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156866 Bug ID: 156866 Summary: Logo in help about not properly rendered with Skia Raster/Metal (macOS) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Logo in help about not properly rendered with Skia Raster/Metal Steps to Reproduce: 1. LibreOffice -> about in menubar Actual Results: See screenshot Expected Results: Logo Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e60ef8651cfb30335471d1622e58c13eebc7d58b CPU threads: 8; OS: Mac OS X 13.4.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156714] .uno:IndexMarktoIndex does not work (and is functionally unclear)
https://bugs.documentfoundation.org/show_bug.cgi?id=156714 sdc.bla...@youmail.dk changed: What|Removed |Added Summary|.uno:IndexMarktoIndex |.uno:IndexMarktoIndex does |crashes the application |not work (and is |(and is functionally|functionally unclear) |unclear)| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77963] FILEOPEN: WPS DOC - Text has wrong font and image not aligned correctly (fixed by round-tripping with Word)
https://bugs.documentfoundation.org/show_bug.cgi?id=77963 Justin L changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156865] New: copying multiple HTML files with tables to Writer causes Writer to go berserk
https://bugs.documentfoundation.org/show_bug.cgi?id=156865 Bug ID: 156865 Summary: copying multiple HTML files with tables to Writer causes Writer to go berserk Product: LibreOffice Version: 7.5.5.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: r...@unidot.com Description: Several times I have copied a number of HTML files to Writer and had it go into an unrecoverable state but not a crash. When this occurs the last item inserted seems to be repeated numerous times and Writer does not seem to be able to recover. The last page has in the lower right corner a red triangle and appears to have a hairline beneath the triangle. This only seems to occur when multiple tables are copied, and has never occurred when simple text is copied. Steps to Reproduce: 1. open a new Writer document 2. Open an HTML document with several tables 3. Copy (ctl-C) the HTML document 4. Paste (ctl-V) the HTML document into the Writer document 5. Repeat step 5 a number of times until the page count is around 25 6. Suddenly the document gets pasted a number of times and stops when the red triangle is at the bottom of the page. Nothing appears to work after that. Actual Results: Suddenly the document gets pasted a number of times and stops when the red triangle is at the bottom of the page. Nothing appears to work after that. Expected Results: Only one copy of the HTML document should be pasted with each ctl-V Reproducible: Always User Profile Reset: No Additional Info: VersionL 7.6.0.3 (X86-64) / LibreOffice Community Build: 69edd8b8ebc41d00b4de3915d Environment: CPU threads: 16: OS: Windows 10.0 Build 19045 User Interfact: UL render: default; VCL: win Locale: en-US(en-US): UL en-US Misc: Calc: CL threaded the same problem occurs on my previous version of LibreOffice; 7.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156864] New: Active tab/button is unreadable on Mac with Increase Contrast enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156864 Bug ID: 156864 Summary: Active tab/button is unreadable on Mac with Increase Contrast enabled Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pfat...@uchicago.edu Description: MacOS Monterey 12.6.7 [M1], MacOS Ventura 13.3.1 [Intel]. LibreOffice 7.6. In System Preferences, Accessibility, Display, Increase Contrast is turned on (checked). With this system setting, the active tab in LibreOffice setting windows is unreadable. Similarly, buttons in some windows are also unreadable. Steps to Reproduce: 1. Enable Increase Contrast in System Preferences/Settings. 2. Open a dialog window in LibreOffice which has tabs, such as File-->Export As-->Export as PDF or Format-->Paragraph [Writer] or Data-->Sort [Calc]. The text label of the selected tab is unreadable. 3. Go to Help-->Restart in Safe Mode. The leftmost button in that dialog is unreadable, the rightmost button "Restart" is readable as expected. 4. When you have restarted in safe mode, the Safe Mode dialog button second from the left also exhibits the same problem. Actual Results: The text label of the active tab or a button is unreadable. Expected Results: It should be possible to read the text label of the active tab and all buttons. Likely the text color and/or the background color needs to be changed. Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) [Tested on Monterey and Ventura, Intel and M1 architectures] OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156853] Exporting bitmap color fonts to PDF is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=156853 Patrick Luby changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |plub...@neooffice.org |desktop.org | Status|NEW |ASSIGNED --- Comment #6 from Patrick Luby --- I can reproduce this as well. Unfortunately, the initial fix caused the same bug to now occur with all transparent images and shapes. So I will see if I can find what is unique about emoji bitmaps. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156861] FILEOPEN XLS, Function with logic answer gives back 1 or 0 in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=156861 --- Comment #3 from ady --- (In reply to ady from comment #2) > might be needed to force the convertion. s/convertion/conversion -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156861] FILEOPEN XLS, Function with logic answer gives back 1 or 0 in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=156861 --- Comment #2 from ady --- FWIW... LO does not really have a boolean or logical category of values; they are numbers really. * Zero = FALSE; all other numbers equal TRUE. * TRUE = 1 and FALSE = 0. https://help.libreoffice.org/latest/en-US/text/scalc/01/04060105.html MS Excel uses the TRUE() and FALSE() functions for compatibility with other tools. Excel does indeed have a boolean or logical category of values; they are not really numbers. Numbers are _usually_ "automatically" interpreted as needed, and logical/boolean values are _usually_ "automatically" interpreted as numbers when needed. Multiplying by 1 usually forces the logical value into a number (0 or 1, respectively). In some rare cases, the N() function might be needed to force the convertion. https://support.microsoft.com/en-gb/office/true-function-7652c6e3-8987-48d0-97cd-ef223246b3fb -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154929] [META] Accessibility Check sidebar deck, Automatic Accessibility Checking
https://bugs.documentfoundation.org/show_bug.cgi?id=154929 Bug 154929 depends on bug 156654, which changed state. Bug 156654 Summary: A11Y sidebar: not fixable warning about "Document default language is not set." https://bugs.documentfoundation.org/show_bug.cgi?id=156654 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156835] FILEOPEN XLSX Password protected file with SHA-384 encryption does not open
https://bugs.documentfoundation.org/show_bug.cgi?id=156835 Balázs Varga (allotropia) changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |balazs.varga...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142074] [META] Application Colours settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142074 BogdanB changed: What|Removed |Added Depends on||156846 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156846 [Bug 156846] Automatic Font color for DataTable is white instead black -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156846] Automatic Font color for DataTable is white instead black
https://bugs.documentfoundation.org/show_bug.cgi?id=156846 BogdanB changed: What|Removed |Added Blocks||142074 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142074 [Bug 142074] [META] Application Colours settings bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117082] Add the option to remove cropped areas to the "Compress Image" dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=117082 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=83 ||734 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83734] EDITING: Cropped image gets distorted when Compress Graphic is used
https://bugs.documentfoundation.org/show_bug.cgi?id=83734 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||7082 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153425] Calc shows different representations (TRUE/FALSE/1/0) of boolean data types stored in .xlsx starting near row 50
https://bugs.documentfoundation.org/show_bug.cgi?id=153425 --- Comment #16 from ady --- (In reply to ady from comment #15) > 3. Save the file as ODS, close and reopen it. > > Result, as described in comment 13: > * shows all TRUE/FALSE values as TRUE and FALSE respectively, > * cell content is (values) TRUE and FALSE respectively, > * with cell format as Boolean. To be clear, since LO considers those strings as meaning the same as the respective functions (while working in English), this is probably OK for ODS. Importing/exporting from other tools in ODS might have different results, but I have not tested such scenario. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153425] Calc shows different representations (TRUE/FALSE/1/0) of boolean data types stored in .xlsx starting near row 50
https://bugs.documentfoundation.org/show_bug.cgi?id=153425 --- Comment #15 from ady --- (In reply to Justin L from comment #14) > > On the same LO Dev version, saving/exporting as ODS and reopening: > > * cell content is (values) TRUE and FALSE respectively, > That seems unlikely, and I can't reproduce. I still see formula =True(). I shall clarify my steps then: 1. New Calc worksheet (do not start from a previously-saved file). 2. Introduce the following string values, not as functions, not as numbers, and with the default standard cell format: A1: TRUE A2: FALSE 3. Save the file as ODS, close and reopen it. Result, as described in comment 13: * shows all TRUE/FALSE values as TRUE and FALSE respectively, * cell content is (values) TRUE and FALSE respectively, * with cell format as Boolean. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156847] Transparency in drop-down lists Line and Width on Sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=156847 Rafael Lima changed: What|Removed |Added Status|ASSIGNED|NEW Assignee|rafael.palma.l...@gmail.com |libreoffice-b...@lists.free ||desktop.org --- Comment #3 from Rafael Lima --- I had accidentally assigned it to myself. Changing it to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113545] [META] Paragraph spacing above and below and related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113545 Bug 113545 depends on bug 101895, which changed state. Bug 101895 Summary: Paragraph dialog units shown as "ch" and "lines" when "Enable char unit" is enabled by default https://bugs.documentfoundation.org/show_bug.cgi?id=101895 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113546] [META] Paragraph indent bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113546 Bug 113546 depends on bug 101895, which changed state. Bug 101895 Summary: Paragraph dialog units shown as "ch" and "lines" when "Enable char unit" is enabled by default https://bugs.documentfoundation.org/show_bug.cgi?id=101895 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Bug 83066 depends on bug 101895, which changed state. Bug 101895 Summary: Paragraph dialog units shown as "ch" and "lines" when "Enable char unit" is enabled by default https://bugs.documentfoundation.org/show_bug.cgi?id=101895 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107642] [META] Paragraph dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107642 Bug 107642 depends on bug 101895, which changed state. Bug 101895 Summary: Paragraph dialog units shown as "ch" and "lines" when "Enable char unit" is enabled by default https://bugs.documentfoundation.org/show_bug.cgi?id=101895 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156857] FILEOPEN PPTX: text boxes (with more text) expand vertically to fit text (when they don't in PowerPoint)
https://bugs.documentfoundation.org/show_bug.cgi?id=156857 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #3 from Gabor Kelemen (allotropia) --- Repro in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4403b4e6bac19d89afded080d80de049aaa294ca CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded from bibisect-242 repo. But for me only the "Global Events" is two lines, the Web/Organic fits in one line (even back to bibisect-6.0). The font is also called "Poppins Light" which is something I don't have locally, but may be substituted differently under Linux/fontconfig and Windows. Also under Windows it is all one line. I'm not sure if this is a plain pptx import issue, I don't see anything weird with the textboxes settings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123417] File with lots of comments opens slower compared to LibO 4.4.7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=123417 ady changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Bug 88278 depends on bug 129356, which changed state. Bug 129356 Summary: VIEWING: SVG image are incorrectly rendered (CSS combinators) https://bugs.documentfoundation.org/show_bug.cgi?id=129356 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124117] FILESAVE: Wrap Text is not saved to *.xls
https://bugs.documentfoundation.org/show_bug.cgi?id=124117 --- Comment #11 from ady --- (In reply to Oliver Brinzing from comment #6) > - open attached file > - select cell A39 > - press "Wrap Text" from Toolbar > -> layout changes > - save *.xls > - reload *.xls It still fails for these STR on the attached file from comment 2 – whether setting "wrap text" ON or OFF, the changed attribute is not saved to the file. The attribute (ON or OFF) is saved correctly in a new clean file (such as in attachment from comment 7). IDK what exactly triggers the problem. I wonder whether it can be reproduced with some other file, or in safe mode, or... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 --- Comment #6 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) > Mind to elaborate? Let me clarify: I am _not_ asking for another place in which the existing "heading rows repeat" command can be used. What I'm asking for is the ability to add one row to the existing repeating heading rows; and to remove one row from that set of repeating heading rows. And - I'm asking that this be accessible as an item on the table row context menu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154227] Clone Formatting doesn't work on background color
https://bugs.documentfoundation.org/show_bug.cgi?id=154227 Andreas Mantke changed: What|Removed |Added CC||ma...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Andreas Mantke --- I tested as in your video with background color of text. I started with yellow background and used the brush and could add with it the background color to another string (new paragraph). I tried this again with that line and could apply the background color with the brush to a third text line (also in a new paragraph). Then I changed the background color in the third line and used the brush in the reverse direction (from string 3 to 1) and it works also. Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded Thus the issue is resolved at least in the current version 7.5.5. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156856] Assertion failed opening a specific PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=156856 Mike Kaganski changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156856] Assertion failed opening a specific PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=156856 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156856] Assertion failed opening a specific PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=156856 --- Comment #1 from Commit Notification --- Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3cf3e0e21d2f7fa33abced5e2f7291de6e4441eb tdf#156856: close write access before using AlphaMask It will be available in 24.2.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 156842] Export to PDF that includes PDF images are incorrect in size
https://bugs.documentfoundation.org/show_bug.cgi?id=156842 --- Comment #5 from cytan...@yahoo.com --- I reproduced this bug on MacOS Ventura 13.5 MacOS Monterey 12.6.8 running LibreOffice 7.6.0.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156530] FIREBIRD: Copying a table from one database file to another gives wrong decimal numbers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156530 --- Comment #9 from Alex Thurgood --- (In reply to Xisco Faulí from comment #8) > (In reply to Alex Thurgood from comment #6) > Hi Alex, > any chance you could revert it and test it ? or bisect it ? Unfortunately, I haven't been able to build environment for LO on Mac for several years now, or even a bibisect environment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138751] Not localized items in notebookbar customization
https://bugs.documentfoundation.org/show_bug.cgi?id=138751 --- Comment #10 from Stanislav Horacek --- I see it still not localized in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 47ca3f1f762352b488d58b3bf23d5776576f1cca CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156842] Export to PDF that includes PDF images are incorrect in size
https://bugs.documentfoundation.org/show_bug.cgi?id=156842 --- Comment #4 from Telesto --- No issue with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 518fa99dd7693d64a53e404a065090aedc0002b1 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149736] EDITING: Delete key after pasting in a selected table cell does not delete the cell content
https://bugs.documentfoundation.org/show_bug.cgi?id=149736 LeroyG changed: What|Removed |Added Version|7.2.3.2 release |6.4.7.2 release --- Comment #6 from LeroyG --- Testing with: Version: 7.6.0.2 (x86) / LibreOffice Community Build ID: 41d6f628ba3f046f16b5fa9fa8db8d4c2ab3b582 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: en-US Calc: threaded (In reply to LeroyG from comment #0) > Steps to Reproduce: > […] > Actual Results: > Cell selection is lost but cell content is not deleted. Still here. (In reply to Tudor Bocean from comment #3) > Version: 7.3.4.2 (x64) / LibreOffice Community 1. > - After pasting text from one cell to one or more other cells, putting the > Writer program in background, copying a word from a different place and > pasting it in Writer (cells are still selected) will result in the new text > being put AFTER the existing one and not replacing it as it would be > expected ===> Wrong behavior I can confirm here. Extrange. But this "feature" don't dislike me. Could it be a possibility? Must be documented. Ups! But it don't work if the new source text is from the same document. 2. > - After pasting text from one cell to one or more other cells, using the Cut > feature CTRL + X will result in no text deletion ===> Wrong behavior ===> > however, the cells Cut were correctly copied ===> Expected Ctrl + X works here. 3. > - After pasting text from one cell to one or more other cells, while cells > are still selecting, pasting again will result in the text being added a > second time ===> Probably a wrong behavior (?) I can confirm here. But won't work if the source text is the whole cell. Related to *1*. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156842] Export to PDF that includes PDF images are incorrect in size
https://bugs.documentfoundation.org/show_bug.cgi?id=156842 --- Comment #3 from cytan...@yahoo.com --- Bug reproduced in LibreOffice 7.6.0.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155353] unable to export as PDF in 7.5
https://bugs.documentfoundation.org/show_bug.cgi?id=155353 --- Comment #13 from N.P. --- > Is the working 7.4.7 also packaged by LibreItalia? We had a different third > party creating the appimages before. I guess it is some conflict in what the > appimage provides vs. what you have built for your user space. My apologies in not responding sooner. I have just tested this again on three AppImages packaged by LibreItalia: LibreOffice-7.4.7.2.standard.help-x86_64.AppImage LibreOffice-7.5.5.2.standard.help-x86_64.AppImage LibreOffice-7.6.0.3.standard.help-x86_64.AppImage Unfortunately, I now feel more confused than ever. LibreOffice-7.4.7.2: worked perfectly LibreOffice-7.5.5.2: worked perfectly LibreOffice-7.6.0.3: failed exactly as described above -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149625] FORMATTING: Pasting a table cell, pastes the source cell in the upper/actual cell as an inner table cell
https://bugs.documentfoundation.org/show_bug.cgi?id=149625 --- Comment #21 from LeroyG --- (In reply to Mike Kaganski from comment #19) > I couldn't repro *that* piece using 7.6.0.3. Nor with version 7.6.0.2 (just tested). So, the bug to which the title refers (*3.a* in comment #0) was partially solved somewhere between versions 7.5.0.0.alpha0+ and 7.6.0.2. (In reply to Mike Kaganski from comment #17) > 3. Putting cursor into the first paragraph (no matter which position inside > that paragraph; selecting some characters starting from that paragraph works > the same) inside the target cell, and pasting, replaces the target cell with > the copied cell (no inner cell); The same in version 7.4.7.2. But this behavior has been evolving: i.e., in version 6.4.7.2 this results in an inner cell inserted at the text cursor position (in part like *4* in comment #17), except when the cursor is at the beginning of the cell. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141579] Create Query in Design View Query Builder build SQL that aliases table name to itself causing some ODBC and JDBC database queries to fail
https://bugs.documentfoundation.org/show_bug.cgi?id=141579 --- Comment #2 from ianbstu...@gmail.com --- This bug still occurs at LibreOffice version 7.4.3.2 on OpenSuse leap 15.5 and Windows 10 To summarise: In LibreOffice Base when using Edit\Database\Advanced Settings there is an option to select/de-select "Append the table alias name on SELECT statements" as well the option "Use keyword AS before table alias names" Even when these options are "not" checked the resulting SQL query includes the aliasing of the table being selected with same name. EG: SELECT "AT_ID", "NAME1" FROM "CM" "CM" The only option related to using a table alias that is honoured is the "Use keyword AS before table alias names" When "Append the table alias name on SELECT statements" is "not" checked and and "Use keyword AS before table alias names" "is" checked: SELECT "AT_ID", "NAME1" FROM "CM" AS "CM" >From this one can deduce that the option "Append the table alias name on SELECT statements" is being ignored. The database using this JDBC driver requires that if a table is aliased it be to a unique name eg T1.CM - this is commonly done in many BI tools as well Because the options are not being honoured the query has to be manually edited to remove the alias. This can get complex when there many tables in the query. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156861] FILEOPEN XLS, Function with logic answer gives back 1 or 0 in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=156861 Justin L changed: What|Removed |Added Version|4.1 all versions|4.2 all versions Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Justin L --- for export, sc/source/filter/excel/xetable.cxx says: /* Xcl doesn't know Boolean number formats, we write "TRUE";"FALSE" (language dependent). Don't do it for automatic formula formats, because Excel gets them right. */ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156858] LibreCalc wrong subtraction of numbers 0, 0000000000001
https://bugs.documentfoundation.org/show_bug.cgi?id=156858 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- It works fine with Version: 7.5.7.0.0+ (X86_64) / LibreOffice Community Build ID: f847a74a2ceffe3938736cb5ee88f81b2160a6b7 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed if schema could be chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #29 from prrv...@gmail.com --- Thanks for your help. This first part is done on the other hand it remains: - Setting up a listener on the two comboboxes? - The generation of the default name of the table which must take into account the default catalog as well as the default schema. I have no idea about the handler/listener implementation on comboboxes. It seems to me that the default table name should be constructed there: https://opengrok.libreoffice.org/xref/core/dbaccess/source/ui/tabledesign/TableController.cxx?r=91ba9654#275 but I don't really understand the code... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155351] Bug in the Whole Sheet export feature
https://bugs.documentfoundation.org/show_bug.cgi?id=155351 --- Comment #3 from Vladimir Sokolinskiy --- Problems with the example file also occur with Print preview (Ctrl+Shift+O). Scale set too small for printing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156863] Warning message reported during PDF/A-1b (ISO 19005) export
https://bugs.documentfoundation.org/show_bug.cgi?id=156863 --- Comment #1 from ricky.t...@gmail.com --- Created attachment 189098 --> https://bugs.documentfoundation.org/attachment.cgi?id=189098=edit PDF/A-1b export -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156863] New: Warning message reported during PDF/A-1b (ISO 19005) export
https://bugs.documentfoundation.org/show_bug.cgi?id=156863 Bug ID: 156863 Summary: Warning message reported during PDF/A-1b (ISO 19005) export Product: LibreOffice Version: 7.5.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ricky.t...@gmail.com Description: Hello. Event reported as problem during PDF/A-1b (ISO 19005) export in Writer. Steps to Reproduce: Create an archive in the PDF/A-1b format. Actual Results: Warning message produced: "PDF/A forbids transparency.". Probably not a generality because during PDF/A-2b/3b (ISO 19005) exports this warning message is not produced. $ file -b 0.pdf PDF document, version 1.4 Expected Results: Warning message produced accordingly, therefore "PDF/A-1b (ISO 19005) forbids transparency.". Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.5.2 (X86_64); Build ID: 50(Build:2); CPU threads: 4; OS: Linux 6.4; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI: en-US; Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed if schema could be chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #28 from Lionel Elie Mamane --- (In reply to Julien Nabet from comment #27) > I don't want to click on Start Review because I think it'll remove WIP > status. Click there, then "Send as WiP" (not "Send and Start Review", that's what I did). > const Reference< XConnection2 > xCon2(_xConnection, UNO_QUERY); > or > const Reference< XConnection2 > xCon2(_xConnection, UNO_QUERY_THROW); > now I'm not sure which one we should use and why. That's important to understand. UNO_QUERY (which I think/hope is the default and can just be omitted, but I'm a bit rusty on details) means that if _xConnection does not implement the XConnection2 interface, then xCon2 will be a NULL reference. UNO_QUERY_THROW means that if _xConnection does not implement the XConnection2 interface, then a RuntimeException will be thrown; execution of the code block is _stopped_, and everything goes up scope by scope until the exception is caught. Generally, UNO_QUERY is good when the situation (the requested interface is not implemented) is handled locally, with an "if (xCon2.is())" as I suggested should be done in this case. Generally, UNO_QUERY_THROW is good when the code just cannot continue in this situation, and the error must go up the stack until the error is handled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135922] Accessibility Text allignment is not announced when using screenreader
https://bugs.documentfoundation.org/show_bug.cgi?id=135922 Michael Weghorn changed: What|Removed |Added Summary|Accessibility Text |Accessibility Text |allignment is not annouced |allignment is not announced |when using screenreader |when using screenreader -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156856] Assertion failed opening a specific PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=156856 Julien Nabet changed: What|Removed |Added Version|unspecified |24.2.0.0 alpha0+ Master -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156776] Base Save As New Table Name not refreshed if schema could be chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=156776 --- Comment #27 from Julien Nabet --- (In reply to prrvchr from comment #26) > I managed to put the correction in work in progress: > > https://gerrit.libreoffice.org/c/core/+/155950 > > But I still get an error while compiling: > > /home/prrvchr/github/libreoffice/dbaccess/source/ui/dlg/dlgsave.cxx: In > constructor ‘dbaui::OSaveAsDlg::OSaveAsDlg(weld::Window*, sal_Int32, const > com::sun::star::uno::Reference&, > const com::sun::star::uno::Reference&, > const rtl::OUString&, const dbaui::IObjectNameCheck&, SADFlags)’: > /home/prrvchr/github/libreoffice/dbaccess/source/ui/dlg/dlgsave.cxx:136:56: > error: invalid initialization of reference of type ‘const > com::sun::star::uno::Reference&’ from > expression of type ‘const > com::sun::star::uno::Reference’ > 136 | const Reference< XConnection2 >& xCon2(_xConnection); > |^~~~ > > I'm sorry, I'm going to have to learn, thanks for your help... I can't succeed in commenting the gerrit patch, wonder if it's because it's WIP. I don't want to click on Start Review because I think it'll remove WIP status. Anyway, changing: const Reference< XConnection2 > xCon2(_xConnection); by: const Reference< XConnection2 > xCon2(_xConnection, UNO_QUERY); or const Reference< XConnection2 > xCon2(_xConnection, UNO_QUERY_THROW); should work. There are some explanation here: https://opengrok.libreoffice.org/xref/core/include/com/sun/star/uno/Reference.h?r=53c39db4=4987=157#157 now I'm not sure which one we should use and why. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156767] [META] Technical Writer (EDITING) Suggested bug fixes, enhancements and features for technical writers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156767 Davide changed: What|Removed |Added Depends on||156862 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156862 [Bug 156862] Copy anything from an application doesn't past onto Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156862] Copy anything from an application doesn't past onto Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156862 Davide changed: What|Removed |Added Blocks||156767 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156767 [Bug 156767] [META] Technical Writer (EDITING) Suggested bug fixes, enhancements and features for technical writers. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156862] New: Copy anything from an application doesn't past onto Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156862 Bug ID: 156862 Summary: Copy anything from an application doesn't past onto Writer Product: LibreOffice Version: 7.6.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: davide.p...@gmail.com Description: An old issue (from 7.1 in my experience) very frequently appears in 7.6.0.3 starting today. Copy anything from anywhere and pasting to LO Writer doesn't paste Restarting Writer solves for some paste operations only. Steps to Reproduce: 1.Copy something from somewhere 2.Paste to Writer 3.Nothing is pasted Restart LibreOffice 4. Copy something from somewhere 5. Paste in Writer 6. Paste is succesfull for some times Actual Results: After some paste operations the paste is not succesfull Expected Results: Copy and paste works every time. Reproducible: Always User Profile Reset: Yes Additional Info: I noticed this problem since release 7.1 but I can't esclude it occurred in previous versions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153425] Calc shows different representations (TRUE/FALSE/1/0) of boolean data types stored in .xlsx starting near row 50
https://bugs.documentfoundation.org/show_bug.cgi?id=153425 --- Comment #14 from Justin L --- (In reply to ady from comment #13) > FWIW, I can still see some inconsistencies, or at least differences, > depending on format. However, these really are rather disconnected from this particular bug, which is talking about xlsx format (almost exclusively). > I am not saying that the results are incorrect; just that the > exporting/saving is slightly different depending on file format. Generally you could say the results are incorrect. At least for something as "simple" as true/false verses 1/0 or cell format. > On a "recent" LO Dev 24.2, saving/exporting as XLS and reopening: > * shows all TRUE/FALSE values as 1 and 0 respectively, Sounds like the XLS bug equivalent of 8f5d8669ca74fed8608e438a8436c173e35d43a6 tdf#122098 xlsx im/export: let formulas guess their number format Reported as new bug 156861. > On the same LO Dev version, saving/exporting as ODS and reopening: > * cell content is (values) TRUE and FALSE respectively, That seems unlikely, and I can't reproduce. I still see formula =True(). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109072] [META] XLS (binary) format bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=109072 Justin L changed: What|Removed |Added Depends on||156861 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156861 [Bug 156861] FILEOPEN XLS, Function with logic answer gives back 1 or 0 in LO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156861] New: FILEOPEN XLS, Function with logic answer gives back 1 or 0 in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=156861 Bug ID: 156861 Summary: FILEOPEN XLS, Function with logic answer gives back 1 or 0 in LO Product: LibreOffice Version: 4.1 all versions Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, filter:xls, regression Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Blocks: 109072 Function in xls with logic formula shows 0 or 1 in LO while in Excel it shows TRUE or FALSE. This is the XLS version of XLSX bug 122098 (broken from 4.2-7.3.2). Steps to reproduce: -Open attachment 185193 (seriesexport.xlsx) from bug 153425. Notice true/false. -export as XLS format and reload. notice 0/1. History: Starting in LO 4.2, importing the xlsx (or the round-tripped xls) showed general-number-formatted logic functions as 0/1 instead of true/false with linux bibisect commit 8e7bade4e7314a340c77edd9042e230f61f0323d Bibisect: This commit covers the following source commit(s) which failed to build (at which point we have a total re-write of how cells store formula data) https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=c7bdee8dbd1cf260a8513a0d31b36f90daa70f1c..ec0080c40cfdb26896537f47a4c2e0439f9afd However, the underlying "stuff" in xls export is unchanged because in older versions it still showed as true/false. In fact, 24.2's export to XLS looks fine in OOo 3.3 - 4.2. FYI: In Excel 2010, the resulting XLS file opens and shows true/false. The formula in XLSX in Excel is =TRUE(), but in XLS in Excel the formula is =TRUE. LO shows the formula as =TRUE() [The difference is whether the '()' are used.] Excel UI does not seem to have a "Boolean" format category like LO does - although the XLSX format DOES have a boolean specifier, so maybe XLS does too. Since LO only "displays" boolean when the formatting is boolean, at least import needs to be smarter about this. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109072 [Bug 109072] [META] XLS (binary) format bug tracker -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51510] FILESAVE: Exporting documents with embedded SVG to doc or docx converts the image to low-resolution pixel graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=51510 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #31 from Regina Henschel --- For export to docx I would expect, that the SVG image is exported as SVG, because modern MS Office are able to render SVG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156859] Wrong fractional value
https://bugs.documentfoundation.org/show_bug.cgi?id=156859 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mike Kaganski --- The default fractional format (used in your sample file) is #" "?/? which uses a single '?' for numerator, and a single '?' for denominator. This way, it uses single-digit fraction. Use two '?'s (in denominator - that's where it's important; in numerator, it will use as many digits as needed), that's how you control the precision of your fraction. This also happens when you use the number format dialog's Denominator places. Closing NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156860] installing routine for "LibreOffice-Help Pack (German)" shows buggy message
https://bugs.documentfoundation.org/show_bug.cgi?id=156860 --- Comment #2 from Schneider --- Created attachment 189097 --> https://bugs.documentfoundation.org/attachment.cgi?id=189097=edit Screenshot 2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156860] installing routine for "LibreOffice-Help Pack (German)" shows buggy message
https://bugs.documentfoundation.org/show_bug.cgi?id=156860 Schneider changed: What|Removed |Added CC||h...@post.uni-dortmund.de --- Comment #1 from Schneider --- Created attachment 189096 --> https://bugs.documentfoundation.org/attachment.cgi?id=189096=edit Screenshot 1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156860] New: installing routine for "LibreOffice-Help Pack (German)" shows buggy message
https://bugs.documentfoundation.org/show_bug.cgi?id=156860 Bug ID: 156860 Summary: installing routine for "LibreOffice-Help Pack (German)" shows buggy message Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: h...@post.uni-dortmund.de Description: Message is buggy when installing the LibreOffice-Help Pack (German). Steps to Reproduce: 1. Download the file "LibreOffice_7.6.0_Win_x86-64_helppack_de.msi" 2. Install the LibreOffice Help Pack (German) of version 7.6.0.3 Actual Results: I find empty space between "von" and "muss". Expected Results: Instead I expected the name & number of the installed programm and version. Reproducible: Always User Profile Reset: No Additional Info: my installed Version: gerrit.libreoffice.org / core / 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156859] Wrong fractional value
https://bugs.documentfoundation.org/show_bug.cgi?id=156859 Massimo changed: What|Removed |Added CC||pincopall...@orange.fr --- Comment #1 from Massimo --- Created attachment 189095 --> https://bugs.documentfoundation.org/attachment.cgi?id=189095=edit A Calc file with the steps I have described in the bug report A Calc file with the steps I have described in the bug report -- You are receiving this mail because: You are the assignee for the bug.
