[Libreoffice-bugs] [Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 --- Comment #3 from henny hall --- I learned a lot from your blog, and I want to thank the website's developer for making such a fantastic resource. I'm hoping users will get a lot from it. https://wordle2.io/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91539] PDF: Scrollable comments in margins
https://bugs.documentfoundation.org/show_bug.cgi?id=91539 --- Comment #8 from henny hall --- Your article gave me a lot of useful information, thanks to the developer for creating this great website. I hope it will bring many benefits to users https://heardlegame.co/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125811] [META] Toolbars tab of Customization dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=125811 Bug 125811 depends on bug 131049, which changed state. Bug 131049 Summary: navigation buttons should be active when adding a UNO to a menu/toolbar when "assigned command" does not have focus https://bugs.documentfoundation.org/show_bug.cgi?id=131049 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131049] navigation buttons should be active when adding a UNO to a menu/toolbar when "assigned command" does not have focus
https://bugs.documentfoundation.org/show_bug.cgi?id=131049 Dieter changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Dieter --- Can't reproduce with Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151068] Add calculated tooltips to cells
https://bugs.documentfoundation.org/show_bug.cgi?id=151068 --- Comment #4 from rob...@prino.org --- This just slipped into my mind, but in "essence" you could see the tooltip "cell" as one in the third dimension, the spreadsheet becomes a (very limited) spread-cube. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103164] [META] Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103164 Dieter changed: What|Removed |Added Depends on||150775 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150775 [Bug 150775] Adding footnotes conflicts with columns (document specific?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150775] Adding footnotes conflicts with columns (document specific?)
https://bugs.documentfoundation.org/show_bug.cgi?id=150775 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| Summary|Adding footnotes conflicts |Adding footnotes conflicts |with columns (unwanted page |with columns (document |break, too short footnotes, |specific?) |no columns are used)| CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO Blocks||107836, 103164 Severity|normal |minor Ever confirmed|0 |1 --- Comment #1 from Dieter --- Thank you for reporting the bug. I can reproduce it with your document, but not in a new document. Steps: 1. Open attachment 182199 2. Insert a new section with three columns and insert some text in first column 3. Insert footnote in first column Actual result: Section expands to the bottom of the text and footnote is added to column Expected result: Section doesn't change height and footnote is at normal position. This is also the actual result with steps 2 and 3 in a new document. Additional information Doesn't happen if section has only one column. Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Csongor, could you confirm the findings and can you explain it? Is there something special with your document? => NEEDINFO Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103164 [Bug 103164] [META] Footnote and Endnote bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=107836 [Bug 107836] [META] Page and section column bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107836] [META] Page and section column bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107836 Dieter changed: What|Removed |Added Depends on||150775 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150775 [Bug 150775] Adding footnotes conflicts with columns (document specific?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151041] Changing right page margin changes horizontal scrolling position
https://bugs.documentfoundation.org/show_bug.cgi?id=151041 --- Comment #6 from fml2 --- > Then why do you perceive the behavior as incorrect... Because now the focus of my actions is changing the margin, and I wouldn't expect to be taken away from that without me doing something that gives a hint that I want to change the focus. Such "doing something giving a hint" could be e.g. a click into the writing area. This would be a clear sign that I'm done with changing the margin, and would thus justify making the insertion mark visible (and changing the view). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151099] New: Add "Insert > Field >Custom Properties" in DRAW
https://bugs.documentfoundation.org/show_bug.cgi?id=151099 Bug ID: 151099 Summary: Add "Insert > Field >Custom Properties" in DRAW Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: v.maro...@gmail.com Created attachment 182590 --> https://bugs.documentfoundation.org/attachment.cgi?id=182590&action=edit Custom properties dialog window Both in Writer and in Draw it is possible to add "Custom Properties" to a document. But in Draw it is not possible to add them in text fields. It would be very helpful, e.g. in multi-page diagrams to have a "Revision" field replicated the same on all pages, which coulfd be updated simply editing the Custom Property. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151098] New: lists from same document look different on Windows than on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=151098 Bug ID: 151098 Summary: lists from same document look different on Windows than on Linux Product: LibreOffice Version: 7.3.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: r...@oemail.nl Description: I use LO both on Windows and on Linux. I made a .odt doc yesterday on my Windows PC, that I am opening today on my Linux laptop, but many lists in the document look very different now (incorrect formatting, nonexisting bullets, switching from regular lists to numbered lists). Happy to share the file or some screenshots. On 7.3.5.2 on Linux. Will add later the version I am on on Windows. Steps to Reproduce: 1. make a few lists in an .odt doc on LO writer on windows 2. open the .odt file on LO on Linux 3. Lists now look different and are formatted incorrectly Actual Results: Lists don't look the same on LO for windows and linux Expected Results: Lists look the same on LO for windows and linux Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92880] CopyFromRecordset function not working since 4.x
https://bugs.documentfoundation.org/show_bug.cgi?id=92880 --- Comment #23 from Benchmark Document Attestation --- https://www.certificateattestation.ae/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150664] Formula bar in Calc is moved to down
https://bugs.documentfoundation.org/show_bug.cgi?id=150664 Mike Kaganski changed: What|Removed |Added CC||yan...@gmail.com --- Comment #9 from Mike Kaganski --- *** Bug 151093 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 151093] Formula bar sliding down in an Excel file
https://bugs.documentfoundation.org/show_bug.cgi?id=151093 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 150664 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151058] Loose of correction tracks on ODT files between WORD and WRITER
https://bugs.documentfoundation.org/show_bug.cgi?id=151058 --- Comment #5 from Gigiux --- I do not understand last comment. Do I need to provide further information? Tx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151055] Table is corrupted when vertical Text Orientation is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=151055 Kevin Suo changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Kevin Suo --- Tested with a master build as of today and it seems fixed by 11ec622b8405dcaabc359e3d6e38c8a9142dad6b *** This bug has been marked as a duplicate of bug 150642 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150642] FILEOPEN DOCX Table structure destroyed if cell with vertical text direction exists
https://bugs.documentfoundation.org/show_bug.cgi?id=150642 Kevin Suo changed: What|Removed |Added CC||suokunl...@126.com --- Comment #7 from Kevin Suo --- *** Bug 151055 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 151096] Impress Animation: The smiley face incorrectly dims/disappears after the appearance event occurs
https://bugs.documentfoundation.org/show_bug.cgi?id=151096 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1097 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151097] Impress Animation: The smiley face does not dim to the desired color after the appearance event occurs
https://bugs.documentfoundation.org/show_bug.cgi?id=151097 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1096 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151097] New: Impress Animation: The smiley face does not dim to the desired color after the appearance event occurs
https://bugs.documentfoundation.org/show_bug.cgi?id=151097 Bug ID: 151097 Summary: Impress Animation: The smiley face does not dim to the desired color after the appearance event occurs Product: LibreOffice Version: 7.3.5.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Steps to Reproduce: 1. Open attachment 182588 in bug 151096 with Impress. 2. Click on the smiley face, click on the "Options" icon button in the Effects section of the Animation sidebar pane. 3. In "Effect" tab, change the "After Animation" from "Don't Dim" to "Dim with Color", then select a dim color in the color dropdown. OK. 4. Start presentation. Current Result: The smiley face does not dim to the selected color after its appearance. Expected Result: The smiley face dims to the selected color after its appearance animation. Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: b52fd544b9c128d3e28de6355286f6480b618e93 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: en-US Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.4-CN Calc: threaded Fedora 36 wayland. Also in 7.3 branch. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151096] Impress Animation: The smiley face incorrectly dims/disappears after the appearance event occurs
https://bugs.documentfoundation.org/show_bug.cgi?id=151096 --- Comment #1 from Kevin Suo --- Created attachment 182589 --> https://bugs.documentfoundation.org/attachment.cgi?id=182589&action=edit settings.pdf This is screenshot showning the animation settings used. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151096] New: Impress Animation: The smiley face incorrectly dims/disappears after the appearance event occurs
https://bugs.documentfoundation.org/show_bug.cgi?id=151096 Bug ID: 151096 Summary: Impress Animation: The smiley face incorrectly dims/disappears after the appearance event occurs Product: LibreOffice Version: 7.3.5.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Created attachment 182588 --> https://bugs.documentfoundation.org/attachment.cgi?id=182588&action=edit test.odp The attached test odp file contains a smiley face (i.e. Shape 1) and a rectangle (i.e. Shape 2). The animations are set on the smiley face, so that when one clicks on the rectangle the smiley face appears (but does not dim or disappear). However, during presentation when I click on the rectangle the smiley face disappears shortly after it appears. Steps to Reproduce: 1. Open the attached odp file. Observe that the "effect" for the smiley face is set to "Appear", the effect options are set to "Trigger: Start on click of Shape 2", effect: After animation - Don't dim. 2. Slide Show - Start from the first slide. Click on the rectangle. Current Result: The smiley face disappears shortly after it appears. Expected Result: The smiley face keeps its appearance after I click on the rectangle. This bug is initially reported in the LibreOffice Chinese discussion forum: https://bbs.libreofficechina.org/forum.php?mod=viewthread&tid=3240 debian testingļ¼Version 7.4.1.1. I can reproduce it on 7.3 branch as well as Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: b52fd544b9c128d3e28de6355286f6480b618e93 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: en-US Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.4-CN Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151095] Linux Libre Word bold rendering of Adobe OTF ex Linotype fonts fails
https://bugs.documentfoundation.org/show_bug.cgi?id=151095 PeterSergej changed: What|Removed |Added Summary|Libre Word bold rendering |Linux Libre Word bold |of Adobe OTF ex Linotype|rendering of Adobe OTF ex |fonts fails |Linotype fonts fails -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150822] FILEOPEN DOCX vertical text direction is not detected in OOXML strict
https://bugs.documentfoundation.org/show_bug.cgi?id=150822 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 151086] Writer crashes when insert SVG image
https://bugs.documentfoundation.org/show_bug.cgi?id=151086 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 151086] Writer crashes when insert SVG image
https://bugs.documentfoundation.org/show_bug.cgi?id=151086 --- 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 151058] Loose of correction tracks on ODT files between WORD and WRITER
https://bugs.documentfoundation.org/show_bug.cgi?id=151058 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 151058] Loose of correction tracks on ODT files between WORD and WRITER
https://bugs.documentfoundation.org/show_bug.cgi?id=151058 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150892] Base: Form window lost title in KDE
https://bugs.documentfoundation.org/show_bug.cgi?id=150892 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 148107] LibreOffice not start (hungs on open screen) try to fix but reportw an error vkEnumeratePhysicalDevices failed: -3
https://bugs.documentfoundation.org/show_bug.cgi?id=148107 --- Comment #7 from QA Administrators --- Dear Simos Dalkiriadis, 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 150892] Base: Form window lost title in KDE
https://bugs.documentfoundation.org/show_bug.cgi?id=150892 --- Comment #13 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147208] In Office Libre power point information not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=147208 --- Comment #3 from QA Administrators --- Dear ashlee.hitchc...@gmail.com, 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 92726] Presentation Minimizer does not preserve animations when making static replacements for OLE objects
https://bugs.documentfoundation.org/show_bug.cgi?id=92726 --- Comment #7 from QA Administrators --- Dear Shimi Chen, 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 83454] Aliases do not work in queries of a database connected to a *.mdb-file
https://bugs.documentfoundation.org/show_bug.cgi?id=83454 --- Comment #28 from QA Administrators --- Dear Andrzej Sygiel, 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 128103] FILESAVE: XLS: Chart key names lost
https://bugs.documentfoundation.org/show_bug.cgi?id=128103 --- Comment #6 from QA Administrators --- Dear Jonny Grant, 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 128250] [FILESAVE] TextBox remains disabled after read-only file is Saved As a new one
https://bugs.documentfoundation.org/show_bug.cgi?id=128250 --- Comment #2 from QA Administrators --- Dear Marco Burato, 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 151095] Libre Word bold rendering of Adobe OTF ex Linotype fonts fails
https://bugs.documentfoundation.org/show_bug.cgi?id=151095 --- Comment #1 from PeterSergej --- Created attachment 182587 --> https://bugs.documentfoundation.org/attachment.cgi?id=182587&action=edit Libre Writer document with screenshots -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151095] New: Libre Word bold rendering of Adobe OTF ex Linotype fonts fails
https://bugs.documentfoundation.org/show_bug.cgi?id=151095 Bug ID: 151095 Summary: Libre Word bold rendering of Adobe OTF ex Linotype fonts fails Product: LibreOffice Version: 7.4.1.2 release Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: peter.s.strem...@gmail.com Description: Steps 1.Install Libre Office, Adobe Garamond Pro, Helvetica LT Std, New Century Schoolbok LT Std, Impressum Std on Linux 2. Open Libre Writer, type sample text, repeat for 16 lines 3. Apply Adobe Garamond Pro typeface to first four lines, Helvetica LT Std to second four lines, New Century Schoolbook LT Std to third four lines, and Impression Std to fiianl four lines. 4. For each typeface quad, apply bold to second line, italic to third line, and underline to dourth line. 5. Save document (without font embedding). Copy to Windows machine. 6. One Windows machine, install, or have already installed, Libre Office and the four fonts mentioned. 7. Observe that bold for the LT (stands for LinoType) Std (stands for standard) does not render in Libre Office for Linux, but does render in Libre Office for Windows. Attached Libre Writer document includes screenshots of font rendering as per technical specs below. The document was created in Libre Office on Linux. Libre Office on Linux specs: Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: gtk3 Locale: en-GB (en_AU.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.1~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded Libre Office on Windows specs: Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: CL Steps to Reproduce: 1.Install Libre Office, Adobe Garamond Pro, Helvetica LT Std, New Century Schoolbok LT Std, Impressum Std on Linux 2. Open Libre Writer, type sample text, repeat for 16 lines 3. Apply Adobe Garamond Pro typeface to first four lines, Helvetica LT Std to second four lines, New Century Schoolbook LT Std to third four lines, and Impression Std to fiianl four lines. 4. For each typeface quad, apply bold to second line, italic to third line, and underline to dourth line. 5. Save document (without font embedding). Copy to Windows machine. 6. One Windows machine, install, or have already installed, Libre Office and the four fonts mentioned. 7. Observe that bold for the LT (stands for LinoType) Std (stands for standard) does not render in Libre Office for Linux, but does render in Libre Office for Windows. Actual Results: Checked square boxes instead of text appear for bold font style in LO Writer on Linux. Expected Results: Legible characters should have appeared for all bold text in LO Writer for Linux or Windows. Reproducible: Always User Profile Reset: No Additional Info: Libre Office on Linux specs: Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: gtk3 Locale: en-GB (en_AU.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.1~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded Libre Office on Windows specs: Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151083] Systematic crash when accepting restart after extension installation (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=151083 --- Comment #2 from Michael Warner --- I didn't have a problem when rebooting after install of DirectColourManager-L-1.2.7. I tried installing the two extensions called out in Comment 0. They both require having a JDK installed, which I do not have installed. In my case, I received a normal pop-up box telling me I needed to install a JDK to use the extensions, and then LO started normally. This was in: Version: 7.4.0.2 / LibreOffice Community Build ID: 1512ce97d7ed39dce3121f7e15651fd8895f950e CPU threads: 10; OS: Mac OS X 12.5; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I downloaded JDK 19 from: https://www.oracle.com/java/technologies/downloads/#jdk19-mac To install the JDK, I tried: 1. Download and unpack the .tar.gz 2. Open Options - LibreOffice - Advanced 3. Click Add... 4. Pointing LO at the top-level folder and various subfolders within it, only to be told each time that the folder I selected does not contain a Java runtime environment. 5. Download the .dmg 6. Open the .dmg and run the package installer 7. Restart LO 8. Be greeted with the same message as I saw earlier, telling me that I needed to install the JDK 8. Open Options - LibreOffice - Advanced 9. No JRE listed It not being able to detect a JRE despite those 9 steps above may be another issue. Also, an opportunity for enhancement would be for the extensions manager to warn me that the extension requires Java and that I do not have a JDK (or JRE) installed *before* installing the extension. But those would be issues for separate bug reports. In any case, I wasn't able to reproduce a crash. @Alex, what version of JDK are you using? How did you install it? It might be relevant to this since these plugins require Java. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146765] Base Form - crash when scrolling in dual form & "data as table" display (macOS Arm)
https://bugs.documentfoundation.org/show_bug.cgi?id=146765 --- Comment #13 from Michael Warner --- No repro for me in: Version: 7.3.1.3 / LibreOffice Community Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951 CPU threads: 10; OS: Mac OS X 12.5; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded nor: Version: 7.4.0.2 / LibreOffice Community Build ID: 1512ce97d7ed39dce3121f7e15651fd8895f950e CPU threads: 10; OS: Mac OS X 12.5; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I am using an M1. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140185] XLSX file doesn't save border padding for styles
https://bugs.documentfoundation.org/show_bug.cgi?id=140185 --- Comment #16 from Justin L --- Do MS formats allow for specifying the border spacing? I don't see any evidence of that in Excel 2003. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141864] Enhancement: Default padding in LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=141864 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #6 from Justin L --- (In reply to Bimal from comment #5) > -- But this is already different. I am just making is compatible. I compared > cell by taking screenshot and found they are different and 0.71 is perfect. My guess - you are saving in.xls format (not .xlsx). I see hints that .xls uses .71 while .xlsx uses 0.35. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140185] XLSX file doesn't save border padding for styles
https://bugs.documentfoundation.org/show_bug.cgi?id=140185 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #15 from Justin L --- Saving as XLS has a similar problem, except that it likes 0.71mm instead. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151074] LibreOffice from macOS appstore - can not create connection to mysql database
https://bugs.documentfoundation.org/show_bug.cgi?id=151074 Sierk Bornemann changed: What|Removed |Added Blocks||42082 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=42082 [Bug 42082] [META] Make LibreOffice shine and glow on macOS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151073] MacOS appstore LibreOffice fails to provide means to create new database in default configuration settings.
https://bugs.documentfoundation.org/show_bug.cgi?id=151073 Sierk Bornemann changed: What|Removed |Added Blocks||42082 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=42082 [Bug 42082] [META] Make LibreOffice shine and glow on macOS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=42082 Sierk Bornemann changed: What|Removed |Added Depends on||151073, 151074 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151073 [Bug 151073] MacOS appstore LibreOffice fails to provide means to create new database in default configuration settings. https://bugs.documentfoundation.org/show_bug.cgi?id=151074 [Bug 151074] LibreOffice from macOS appstore - can not create connection to mysql database -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149327] Can't type accented letters at the end of a paragraph in Writer (EDITING)
https://bugs.documentfoundation.org/show_bug.cgi?id=149327 --- Comment #6 from spiros la --- Ī¤he line break problem when typing accent (see above, 2022-09-20 21:46:59 UTC) is probably caused by the ibus. I uninstall ibus (which is required dependency for zoom) and the problem does not appear. But should I end up choosing between having zoom or having libreoffice with correct accent typing? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127469] Allow import of color palettes in some "popular" formats
https://bugs.documentfoundation.org/show_bug.cgi?id=127469 --- Comment #11 from V Stuart Foote --- (In reply to servalli from comment #10) > Why is it a seldom used feature? Reality, and we certainly don't have folks clamoring for the feature. How often and common work flows for the suite dictate what areas of the UI needs/gets dev attention. > Using consistent palettes across different applications is very useful and > might be important for business uses when brand colors are enforced. > > It is extremely frustrating having to manually create a .sog file in a text > editor and have to copy it somewhere as a root or write a script for > conversions Two minutes work to stream edit from .gpl to .soc, not seeing an issue. .SOG is the gradient palette--don't think you meant that. > Having a UI option to import a .gpl would be so much better. Why, the .gpl GIMP palettes can already be directly read as palettes in LibreOffice--the color picker is the importer. Otherwise one just needs to copy it from GIMP's share/gimp/2.0/palettes directory to the Libreoffice's share/palette directory. Certainly not a core functional component, but broader palette management remain fertile ground for an extension. Code is welcome. > There is currently no extension allowing to load an external palette in any > way. OK, but it is trivial in any os/DE to edit format for a .soc pallet--and to drop a correctly formatted .SOC file into share/pallete directory. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151041] Changing right page margin changes horizontal scrolling position
https://bugs.documentfoundation.org/show_bug.cgi?id=151041 --- Comment #5 from V Stuart Foote --- (In reply to fml2 from comment #4) Then why do you perceive the behavior as incorrect when having zoomed in the view of the page to such an extent that making a margin change reorients the page and then perfectly consistently moves the vcl view port of the canvas to the only meaningful point--the edit cursor? It would make little sense to hold the vcl canvas view on a part of the page that no longer has any importance to inputting textual content. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103035] UI: Changing text formatting in Header/Footer dialog can be confusing
https://bugs.documentfoundation.org/show_bug.cgi?id=103035 Hossein changed: What|Removed |Added Whiteboard||reviewed:2022 --- Comment #11 from Hossein --- Re-evaluating the EasyHack in 2022 This enhancement is still relevant. This is about creating a better way to format text in a UI (headerfootercontent.ui). The suggested path to achieve this is to use a new design for the UI, as shown in attachment 127850. Btw, I had to read the comments more than once to understand the whole problem. :-) I suggest that anyone who wants to fix this issue should read the all the comments thoroughly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149327] Can't type accented letters at the end of a paragraph in Writer (EDITING)
https://bugs.documentfoundation.org/show_bug.cgi?id=149327 --- Comment #5 from spiros la --- I have the same problem after the LibreOffice Version 7.2.3 I have OpenSuse Leap 15.4 with KDE desktop Writing in Greek, when I type an accent at the end of a paragraph, if the paragraph I am writing is not the last paragraph of the text, i.e. there is at least one more paragraph below the one I am working on, then a) the text editor changes paragraph, b) the letter the accent was going is lost, and c) whatever letter I insert puts it at the beginning of the next paragraph (i.e the accent triggers the line break). Steps to reproduce (reproducible always): 1) Open a text in the writer, 2) press 2 enter, 3) place the cursor at the beginning of the first paragraph, 4) Write in the first paragraph a word with an accent (without another letter or space before inserting the accent, i.e. always type letters at the end of the paragraph) Example: If I write in the first paragraph āĪĻ ĻĻ Ī®ĻĪ±Ī½ā it will become: ĪĻ ĻĀ“ Ā“ ĻĪ±Ī½ The correct text would be AĻ ĻĻ Ī®ĻĪ±Ī½ This problem does not occur if 1) the stress is inserted in a letter before the end of the paragraph, 2) there is no other paragraph after. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151041] Changing right page margin changes horizontal scrolling position
https://bugs.documentfoundation.org/show_bug.cgi?id=151041 --- Comment #4 from fml2 --- > Same issue when you scroll down and resize the bottom margin Yes! Also not what I'd expect. > What should happen when you click at the canvas? What do you mean by "click at the canvas"? I'm not familiar with the internal LO terminology (which the expression seems to be). If you by that mean the page area where one writes the text then it depends whether the click location contains the text. If it does then the insertion mark should be placed where the user clicked (or the nearest possible place). If the page is blank there (e.g. if it's scrolled down and the text ends somewhere above) then I'd probably expect the view to jump so that the insertion mark is visible. The reason is that if I click on the page then my mental focus is on the page (writing text). Hence making the mark visible (and jumping to it if necessary) is justified. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148181] Libreoffice dosn't work with JAWS
https://bugs.documentfoundation.org/show_bug.cgi?id=148181 --- Comment #6 from Michael Weghorn --- (In reply to Michael Weghorn from comment #2) > A while ago, I analyzed an issue with JAWS and Calc where the problem was > that JAWS was requesting accessible objects for all children of the Calc > table, which are more than 4 billion, which is the reason why LibreOffice > hangs and then crashes when it runs out of memory. From what I could see > back then, LibreOffice was behaving correctly though and the solution would > in my understanding be a better handling on the JAWS side. Note that this is not the same problem, the crash described here actually happens right when starting Calc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64431] FILESAVE: Broken hyperlink to another file in PPT
https://bugs.documentfoundation.org/show_bug.cgi?id=64431
Julien Nabet changed:
What|Removed |Added
CC||er...@redhat.com
--- Comment #13 from Julien Nabet ---
On pc Debian x86-64 with master sources updated today, I could reproduce this.
First, since the hyperlink from the ppt seemed to succeed before reopening and
failed after reopening, I thought it was import pb
(sd/source/filter/ppt/pptin.cxx:410 (aPropItem.Read( aHyperlink.aTarget ))
but in fact it's in export part. I must recognize I don't know why it succeeds
before the reloading.
Anyway, with this patch, it works:
diff --git a/sd/source/filter/eppt/epptso.cxx
b/sd/source/filter/eppt/epptso.cxx
index eae0e5d8c4ab..c2232bbf3ba3 100644
--- a/sd/source/filter/eppt/epptso.cxx
+++ b/sd/source/filter/eppt/epptso.cxx
@@ -342,14 +342,6 @@ sal_uInt32 PPTWriter::ImplInsertBookmarkURL( const
OUString& rBookmarkURL, const
sal_uInt32 nHyperId = ++mnExEmbed;
OUString sBookmarkURL( rBookmarkURL );
-INetURLObject aBaseURI( maBaseURI );
-INetURLObject aBookmarkURI( rBookmarkURL );
-if( aBaseURI.GetProtocol() == aBookmarkURI.GetProtocol() )
-{
-OUString aRelUrl( INetURLObject::GetRelURL( maBaseURI, rBookmarkURL )
);
-if ( !aRelUrl.isEmpty() )
-sBookmarkURL = aRelUrl;
-}
maHyperlink.emplace_back( sBookmarkURL, nType );
mpExEmbed->WriteUInt16( 0xf )
Eike: I noticed this commit:
6ad3c553a9bd3b8fb91c45204f0c833f52c52431
impress212: #i97241# added relative links
* found as LGPLv3-only fix at svn rev 1167624
(http://svn.apache.org/viewvc?view=revision&revision=1167624)
from 2011 (!!).
I'm afraid to break something here but do you know which use case it would
break?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151094] New: FILESAVE: Writer crashes on save after deleting a paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=151094 Bug ID: 151094 Summary: FILESAVE: Writer crashes on save after deleting a paragraph style Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gerry.trep...@googlemail.com Created attachment 182586 --> https://bugs.documentfoundation.org/attachment.cgi?id=182586&action=edit Crash on saving after deleting paragraph style .odt Writer always crashes after I delete a style sheet and try to save the file. It crashes on saving. Steps to reproduce: 1. Open attached file 2. Open Styles -> Manage Styles (Formatvorlagen verwalten) or hit F11. 3. Go to the paragraph style "TEXT" and perform a right mouse click on it and delete this paragraph style. 4. Save the file --> Writer crashes immediately. Reproducibility: Always Here several crash reports: * https://crashreport.libreoffice.org/stats/crash_details/8fdbf192-2178-4a8e-ae57-e5005ce43da3 * https://crashreport.libreoffice.org/stats/crash_details/7d37b7ec-aac2-4e11-8476-9f74020ad941 * https://crashreport.libreoffice.org/stats/crash_details/f9486b7f-3e14-4dc8-a7cf-c1cab4e70639 * https://crashreport.libreoffice.org/stats/crash_details/b12a482a-ab64-4de8-a714-0a22edf1d01d * https://crashreport.libreoffice.org/stats/crash_details/1674ac2e-0efd-4eb8-a989-126d75bc0b06 Version: 7.4.1.2 / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148181] Libreoffice dosn't work with JAWS
https://bugs.documentfoundation.org/show_bug.cgi?id=148181 --- Comment #5 from Michael Weghorn --- The JAWS version I used is JAWS 2022.2207.25 - July 2022. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148181] Libreoffice dosn't work with JAWS
https://bugs.documentfoundation.org/show_bug.cgi?id=148181 --- Comment #4 from Michael Weghorn --- Created attachment 182585 --> https://bugs.documentfoundation.org/attachment.cgi?id=182585&action=edit Backtrace I can reproduce with LO master as of commit 349e3af0c5dd. Attached is a backtrace. However, I can't see anything obviously wrong on LO side (state of the objects/variables looks OK to me at first glance) and the same code path is run e.g. with NVDA just fine. The last call in the backtrace that happens from within LO is this one [1]: NotifyWinEvent( EVENT_OBJECT_FOCUS,hAcc, OBJID_CLIENT,dChildID ); Everything else is then in the handling of the event in the platform a11y layer, so the crash might be caused by the event handling in JAWS and thus be an issue with JAWS rather than LO. I have filled the support form for JAWS on the FreedomScientific website and added a link to this report. (I don't have a JAWS license, just used the download from the website that can be run for 40 minutes, not sure whether that will be a problem regarding the support request...) I currently don't see what else could be done on LO side. [1] https://git.libreoffice.org/core/+/349e3af0c5dd5ed495ed61aab526f63c16f0e215/winaccessibility/source/service/AccObjectWinManager.cxx#246 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127469] Allow import of color palettes in some "popular" formats
https://bugs.documentfoundation.org/show_bug.cgi?id=127469 --- Comment #10 from servalli --- Why is it a seldom used feature? Using consistent palettes across different applications is very useful and might be important for business uses when brand colors are enforced. It is extremely frustrating having to manually create a .sog file in a text editor and have to copy it somewhere as a root or write a script for conversions Having a UI option to import a .gpl would be so much better. There is currently no extension allowing to load an external palette in any way. The existing custom palette export extension does not address this problem. Why was such a useful feature removed? I truly hope it is added again. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150645] Writer crashes after longer usage session
https://bugs.documentfoundation.org/show_bug.cgi?id=150645 --- Comment #9 from V Stuart Foote --- Just need the first from the OpenGL Report, and down to the Device ID: stanza in the Vulkan report. So for my nVidia K2000 daily driver: Renderer: Quadro K2000/PCIe/SSE2 Vendor: NVIDIA Corporation Version: 4.6.0 NVIDIA 473.81 Shading language version: 4.60 NVIDIA Vulkan Layer (1) Quadro K2000 API Version: 1.2.175 Driver Version: 473.324.0 Vendor ID: 10deh Device ID: ffeh as compared to the LibreOffice generated skia.log RenderMethod: vulkan Vendor: 0x10de Device: 0xffe API: 1.2.175 Driver: 473.324.0 DeviceType: discrete DeviceName: Quadro K2000 Denylisted: no So hope you can see what we'd need from the GLView utility reports. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150645] Writer crashes after longer usage session
https://bugs.documentfoundation.org/show_bug.cgi?id=150645 --- Comment #8 from Poolitzer --- The other checkbox does not appear checked, no, but I can imagine that this is the reason using the software. Running that software is fine, what exactly do you want me to do there? The rendering test? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151093] New: Formula bar sliding down in an Excel file
https://bugs.documentfoundation.org/show_bug.cgi?id=151093 Bug ID: 151093 Summary: Formula bar sliding down in an Excel file Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: yan...@gmail.com Description: Calc is opening an Excel file with formula bar slid down. Steps to Reproduce: 1. Open an Excel file 2. Look at the formula bar Actual Results: Formula bar slid down. Office Open XML Workbook : https://i.postimg.cc/9V88wJm5/Excel.png Expected Results: Formula bar should be at the default location. OpenDocument Spreadsheet : https://i.postimg.cc/cZ4kJVNB/Calc.png Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: tr-TR (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85677] Dragging on a touchscreen display highlights instead of scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=85677 --- Comment #27 from servalli --- Any LibreOffice applications are unusable in tablet mode also on Ubuntu 18.04 - 22.04 on a Dell Latitude 2-in-1. The scrolling works neither via dragging nor using the scroll bar. The latter is not a touchscreen sensitivity issue as it works in Firefox. Another desired behaviour for a touchscreen device would be zooming by pinch, also not implemented. At the same time, touch scrolling works in drop-down menus, such as font style. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150645] Writer crashes after longer usage session
https://bugs.documentfoundation.org/show_bug.cgi?id=150645
--- Comment #7 from V Stuart Foote ---
(In reply to Poolitzer from comment #6)
> So only the first checkbox ('Use Skia for all rendering') got activated,
> which produces the log, but with the clang result...
OK, believe that will happen if your GPU fails some graphics testing on
startup--to give you a usefull fall-back to Skia lib software rendering (the
other check-box will toggle checked).
If you are inclined, a third party utility like RealTech-VR.com's glview [1]
utility has a Vulkan test module that can provide the same details as our
internal Vulkan module tests.
=-ref-=
[1] https://www.realtech-vr.com/home/glview
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 --- Comment #7 from Piotr Osada --- Created attachment 182584 --> https://bugs.documentfoundation.org/attachment.cgi?id=182584&action=edit 3 When another application window overlaps the CALC window and when it does not overlap Issue #3 And there is a different behavior because of the way to reach the spreadsheet area. If there is another window above the CALC window, then when we "fall" onto the CALC window, the spreadsheet does not move. However, when the windows do not overlap, then hovering over CALC causes the sheet to be moved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151092] New: LO 7.4.1 unable to create lock - opens Calc files in read only mode and impossible to "save as" or export as pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=151092 Bug ID: 151092 Summary: LO 7.4.1 unable to create lock - opens Calc files in read only mode and impossible to "save as" or export as pdf Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@mithouard.com Description: Hello After install of version 7.4.1, problem with Calc : * opens xls ans xlsx files in read-only mode, stating unability to lock the file for modification or wait for an alert as Calc is unable to lock the file * also "save as" impossible, and also export to pdf Verified security permissions on directories ==> OK Uninstalled 7.4.1 and went back to 7.3.5.2 : problem solved Hope it helps. Didier Steps to Reproduce: 1.Install LO 7.4.1 alongside Office 2016 2.Documents folder automatically synced to Onedrive 3. Calc document does not open but a windows requesting to open in Read only mode or wait for an alert as Calc is unable to lock the file 4. Save as or export to pdf not possible as Calc cannt access the file Uninstall and clen install of LO 7.3.5.2 solved the problem Actual Results: Impossible to modify the xls files Expected Results: normal opening and save of tje Calc files when nack to 6.3.5.2 Reproducible: Always User Profile Reset: No Additional Info: Perform opening, save or export of files should work as usual -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 --- Comment #6 from Piotr Osada --- Created attachment 182583 --> https://bugs.documentfoundation.org/attachment.cgi?id=182583&action=edit 2 Non-smooth scrolling, jamming, disproportionate acceleration Issue #2 The second suggestion is to redesign in some way the action of moving the spreadsheet in a certain direction when the cursor hovers over the edge of the spreadsheet area. As it stands, this function is clunky to me. That is, I never know how far I will get by "waiting" with the cursor on the edge. I would see this function designed to accommodate a wide range of motion acceleration: 1) Stopping the cursor stationary at the edge. --> I think here a better behavior than stopping scrolling would be to scroll, for example, at a rate of one cell per 0.5 seconds (or some other well-responsive time that would be long enough to feel like you have control over the movement. Not only for smart MMO RPG players, but also for old grandparents xD). 2) Moving the mouse near the edge of the spreadsheet area. --> It would be convenient to be able to scroll the spreadsheet at a speed of, say, 2 cells per second, up to 10,000 cells per second, depending on how fast you "shake" the cursor in that area. Re. 2) But probably more important and useful than scrolling speed ranges from the point of view of convenience would be to detect the ends of the data ranges with which the cells are filled. That is, if we have values from row #1 to 1234, then if we scroll it would be good if the scrolling stopped at the end of that range (e.g. row 1234 + 1 row for aesthetic separation). And then it would stop at subsequent areas filled with data. Sort of like a pull to filled cells. To make it easier to digest at the beginning and end of the data area. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150645] Writer crashes after longer usage session
https://bugs.documentfoundation.org/show_bug.cgi?id=150645
--- Comment #6 from Poolitzer ---
So only the first checkbox ('Use Skia for all rendering') got activated, which
produces the log, but with the clang result...
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83568] FORMATTING: Row Height not changing below 10pt since LO 4.2 (see also comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=83568 Julien Nabet changed: What|Removed |Added CC||er...@redhat.com, ||serval2...@yahoo.fr --- Comment #28 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. With this patch: diff --git a/sc/source/core/data/column2.cxx b/sc/source/core/data/column2.cxx index 08391bd24150..e1e3c6d468d9 100644 --- a/sc/source/core/data/column2.cxx +++ b/sc/source/core/data/column2.cxx @@ -855,9 +855,6 @@ static sal_uInt16 lcl_GetAttribHeight( const ScPatternAttr& rPattern, sal_uInt16 if (nHeight > STD_ROWHEIGHT_DIFF) nHeight -= STD_ROWHEIGHT_DIFF; -if (nHeight < ScGlobal::nStdRowHeight) -nHeight = ScGlobal::nStdRowHeight; - return nHeight; } the scaling process works even with font size < 10. Eike: any thoughts here? I mean perhaps there would be wrong side effects Kohei wanted to avoid? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151076] Python script InsertText.py fails with error message
https://bugs.documentfoundation.org/show_bug.cgi?id=151076 Rafael Lima changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from Rafael Lima --- A simple fix is to add the following line at the end of InsertText.py. g_exportedScripts = () This would make the script no longer appear in the Run Macro dialog. And it would still work when called from another macro, as in the example I gave in Comment #2. Let's leave this as UNCONFIRMED for now to see if anyone else has other ideas on this matter. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117764] using context menu item "Conditional formatting" opens dialogue "Conditional formatting for ..." with wrong cell range
https://bugs.documentfoundation.org/show_bug.cgi?id=117764 Julien Nabet changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | Status|NEW |ASSIGNED --- Comment #9 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I could reproduce this. I gave a try with https://gerrit.libreoffice.org/c/core/+/140258 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 --- Comment #5 from Piotr Osada --- (In reply to Piotr Osada from comment #1) > Created attachment 182579 [details] > 1 Unwanted movement of a spreadsheet after smoothly sliding into the CALC > window > > Actually this movement takes place from any direction. Issue #1 So, in my opinion, for a better use of LO, the operation should be changed so that a straight smooth movement does not activate the scrolling function after hovering over the edge of the spreadsheet area. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 --- Comment #4 from Piotr Osada --- Created attachment 182582 --> https://bugs.documentfoundation.org/attachment.cgi?id=182582&action=edit 1d From the bottom -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 --- Comment #3 from Piotr Osada --- Created attachment 182581 --> https://bugs.documentfoundation.org/attachment.cgi?id=182581&action=edit 1c From the right -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 --- Comment #2 from Piotr Osada --- Created attachment 182580 --> https://bugs.documentfoundation.org/attachment.cgi?id=182580&action=edit 1b From the top -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 --- Comment #1 from Piotr Osada --- Created attachment 182579 --> https://bugs.documentfoundation.org/attachment.cgi?id=182579&action=edit 1 Unwanted movement of a spreadsheet after smoothly sliding into the CALC window Actually this movement takes place from any direction. Whichever side you hover over the spreadsheet area, it will be scrolled to that side. As shown in the following videos: 1b 1c 1d -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151069] When running Calc the program crashes immediately if JAWS (screen reader) is in use. JAWS version is 2022 latest build. I have tested with NVDA and Narrator and both wo
https://bugs.documentfoundation.org/show_bug.cgi?id=151069 Timur changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Timur --- Seems duplicate of bug 148181 where user answer is requested. *** This bug has been marked as a duplicate of bug 148181 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148181] Libreoffice dosn't work with JAWS
https://bugs.documentfoundation.org/show_bug.cgi?id=148181 Timur changed: What|Removed |Added CC||petetor...@cwgsy.net --- Comment #3 from Timur --- *** Bug 151069 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 151076] Python script InsertText.py fails with error message
https://bugs.documentfoundation.org/show_bug.cgi?id=151076
--- Comment #2 from Rafael Lima ---
TBH I really don't know why this macro is even accessible via Toos - Macros -
Run Macro, because it requires a positional "text" argument to work. See:
https://opengrok.libreoffice.org/xref/core/scripting/examples/python/InsertText.py
So it seems the "InsertText" function is meant to be called by other scripts
only and not as a standalone script.
For instance, create a Writer document and open an APSO Python shell. Now type:
from InsertText import InsertText
InsertText("Hello")
The code above will insert "Hello" where your cursor is located.
The only weird thing is that the InsertText macro should not be reachable via
the Run Macro menu. The script isn't even exported using g_exportedScripts, so
I don't see why it is listed to the user.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150892] Base: Form window lost title in KDE
https://bugs.documentfoundation.org/show_bug.cgi?id=150892 Timur changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #12 from Timur --- I'm testing with bibisect repos. This may well stem from qt5ct, I intend to check when I can, so I set Needinfo for myself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151076] Python script InsertText.py fails with error message
https://bugs.documentfoundation.org/show_bug.cgi?id=151076 Rafael Lima changed: What|Removed |Added Hardware|ARM |All Ever confirmed|0 |1 OS|macOS (All) |All CC||rafael.palma.l...@gmail.com Status|UNCONFIRMED |NEW --- Comment #1 from Rafael Lima --- Repro with Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1 Calc: threaded Indeed the macro does not work even in a new LO installation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150645] Writer crashes after longer usage session
https://bugs.documentfoundation.org/show_bug.cgi?id=150645 --- Comment #5 from V Stuart Foote --- (In reply to Poolitzer from comment #4) > > Sorry for the long wait time, yes, it definitely improved things. I have > tried finding the skia.log file, but was unable to, where would it be? On Windows it would be %APPDATA%\LibreOffice\4\cache (or C:\Users\\AppData\Roaming\LibreOffice\4\cache). But you may need to first try renable Skia Vulkan rendering briefly so the skia.log gets populated with the Vulkan details--otherwise is will just show: RenderMethod: raster Compiler: Clang which is what the non-accelerated raster only software libs for Skia will show. The Vulkan related stanzas are what we need to judge a denylist action or possibly additional dev effort. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151088] Rename "Invoice Paper" to "Kraft Paper"
https://bugs.documentfoundation.org/show_bug.cgi?id=151088 Rafael Lima changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | Ever confirmed|0 |1 CC||rafael.palma.l...@gmail.com Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Rafael Lima --- Indeed, the discussion happened 2 years ago and it seems the correct wording is "Kraft paper" indeed. I also took a look at the dialog and it definitely is not "Invoice Paper" but rather "Kraft Paper". Code pointer is: https://opengrok.libreoffice.org/xref/core/include/svx/strings.hrc?r=a9c8ac06#840 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113088] [META] Writer table properties dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113088 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||151002 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151002 [Bug 151002] Confusing radio button placement in Text flow tab of Table Properties dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151002] Confusing radio button placement in Text flow tab of Table Properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=151002 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||113088 Ever confirmed|0 |1 Severity|minor |enhancement CC||79045_79...@mail.ru Status|UNCONFIRMED |NEW --- Comment #5 from Roman Kuznetsov <79045_79...@mail.ru> --- (In reply to Heiko Tietze from comment #2) > Another option is to use dropdown controls like > > [x] Break > at [Page] by placing [Before] > With Page Style [] > Starting with [ ] Page Number [ 1 ] I thought about the same, so +1 to that solution Set to NEW as valid enhancement (it isn't a bug in general) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113088 [Bug 113088] [META] Writer table properties dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150645] Writer crashes after longer usage session
https://bugs.documentfoundation.org/show_bug.cgi?id=150645 --- Comment #4 from Poolitzer --- (In reply to V Stuart Foote from comment #3) > And if that improves things, please copy paste content of the skia.log from > the LO user cache taken while Vulkan GPU is enabled. > > Content we need look like these: > > RenderMethod: vulkan > Vendor: 0x8086 > Device: 0x8a52 > API: 1.2.151 > Driver: 0.402.661 > DeviceType: integrated > DeviceName: Intel(R) Iris(R) Plus Graphics > Denylisted: no Sorry for the long wait time, yes, it definitely improved things. I have tried finding the skia.log file, but was unable to, where would it be? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151091] copy chart from liberoffice calc to libreoffice writer is copied wrongly loosing values
https://bugs.documentfoundation.org/show_bug.cgi?id=151091 --- Comment #2 from elias estatistics --- As GDI or BMP is copied OK. Note I copied my user profile from 7.4.0dev to 7.4.1.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151091] copy chart from liberoffice calc to libreoffice writer is copied wrongly loosing values
https://bugs.documentfoundation.org/show_bug.cgi?id=151091 --- Comment #1 from elias estatistics --- Created attachment 182578 --> https://bugs.documentfoundation.org/attachment.cgi?id=182578&action=edit how chart copied to my writer document. how chart copied to my writer document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151091] New: copy chart from liberoffice calc to libreoffice writer is copied wrongly loosing values
https://bugs.documentfoundation.org/show_bug.cgi?id=151091 Bug ID: 151091 Summary: copy chart from liberoffice calc to libreoffice writer is copied wrongly loosing values Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: elias__0...@yahoo.com Created attachment 182577 --> https://bugs.documentfoundation.org/attachment.cgi?id=182577&action=edit calc file with chart copy chart from liberoffice calc to libreoffice writer is copied wrongly loosing values Try to copy the chart from calc to libreoffice writer. Then chart looses its values with some irrelevant values. Version: 7.4.1.2 / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140760] (PIVOTTABLE) selection of invalid constraint values possible and probably this irreversibly results in an empty pivot table
https://bugs.documentfoundation.org/show_bug.cgi?id=140760 --- Comment #7 from Roman Kuznetsov <79045_79...@mail.ru> --- MS Excel shows absolutely the same behavior -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145080] make sure cell selection colors use good contrast when following system highlight color on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=145080 Kollien changed: What|Removed |Added Version|7.3.0.0 alpha0+ |7.3.0.3 release --- Comment #26 from Kollien --- The problem still persists specially in MacOS 12.x and raised with version 7.3 of LO. Using the default selection color of the OS, the cell selection border is nearly invisible. Changing the gridline color in LO doesn't help, as the cellselection color is so massive dimmed, that it is nearly invisible. Changing the selection color in the MacOS system settings to a darker one is a workaround, but as this affects the text selection color in all other applications too, this is very unpleasant. It would be much better when the cell selection color could be set inside LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128065] BASIC Runtime Error on start LOCalc
https://bugs.documentfoundation.org/show_bug.cgi?id=128065
Julien Nabet changed:
What|Removed |Added
CC||andreas.heini...@yahoo.de,
||mikekagan...@hotmail.com
--- Comment #7 from Julien Nabet ---
I gave a new try with master sources updated today and could reproduce this.
After having added some debug traces, I found that the pb was in last line of
this block:
Function setupKOSheet(startingSheetName AS String, startingCell as String,
Optional numParticipants As Integer, _
Optional vertSpacing As Integer, Optional horSpacing As Integer,
Optional nameWidth As Integer, Optional redColor, Optional blueColor)
Dim Document As Object
Document = ThisComponent
'Get Sheet object
If Not IsMissing(startingSheetName) And
Document.Sheets.hasByName(startingSheetName) Then
If startingSheetName = Document.CurrentController.ActiveSheet.Name Then
Indeed "Document" seems not exist at this moment. (it would confirm the initial
description)
Now if I go to the first sheet "Befehle" in A6 and do a recalculate, it works.
(this sheet contains =SETUPKOSHEET("Beispiel";"C2";16))
I wanted to know how the macro was launched at the start, so searched in
Tools/Customize/Events and found nothing. It's after a while I saw it was in a
formula.
Mike/Andreas: thought you might be interested in this one.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151089] formula with underbrace block libreoffice impress (when the formula contain more than 17 characters)
https://bugs.documentfoundation.org/show_bug.cgi?id=151089 --- Comment #1 from Rafael Lima --- Not repro with Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1 Calc: threaded The formula works as expected in Linux. Is it maybe a MacOS-only issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32700] UI: Make Track Changes Color "by author" adjustable
https://bugs.documentfoundation.org/show_bug.cgi?id=32700 --- Comment #12 from servalli...@gmail.com --- Also here to ask for the addition of this setting. The default setting makes the changes completely unreadable in dark mode for some of the colors,for instance, the blue. The colors either need to be changed to be visible both on white and dark grey, or a possibility to change the palette should be added. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123026] LibreOffice ignore xlsxwriter 'text_wrap' formatting option, seems optimal height for row is not being set to hold cells with wrapped text
https://bugs.documentfoundation.org/show_bug.cgi?id=123026 --- Comment #8 from Justin L --- I might try https://gerrit.libreoffice.org/c/core/+/140260 for LO 7.6. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125595] FORMATTING: Validity cell range with invisible characters (e.g. newline) stripped
https://bugs.documentfoundation.org/show_bug.cgi?id=125595 --- Comment #8 from Justin L --- (In reply to Teraslilja from comment #7) > only minor complain of pulldown menu showing otherwise invisible char(7) > character as unknown character (00/07 block). I don't see that (on Linux). Do you have Arial font installed? (I do.) That's the only thing I can think of - it sounds like a font-substitution. > How ever, if the attached test is saved as the last choice of selection and > opening the document again, VLookup test fails and return #N/A I don't see that - even in 7.3. It always opens up with the last A-E result, never N/A. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151090] New: [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 Bug ID: 151090 Summary: [UI] The spreadsheet shifts when we drag'n'drop content from outside the window Product: LibreOffice Version: 7.3.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: piotr.os...@gmail.com Description: When we quickly want to drag and drop, for example, text or an image in a spreadsheet, we immediately know in which cell we want to drop it. Therefore, we do not want the cell we are looking at to scroll when we hover over spreadsheet window. Steps to Reproduce: 1) CALC and web browser windows are side by side (CALC - left, WWW - right. Windows do not overlap). 2) Drag but do not drop from the right side of e.g. a link. 3) After smoothly entering the window, the spreadsheet view shifted. Actual Results: . Expected Results: I would expect the spreadsheet view to not move after smoothly moving content to the CALC window. Only after stopping with the content on one of the pages of the sheet, I would expect the content scrolling to be activated. Reproducible: Always User Profile Reset: No Additional Info: . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140760] (PIVOTTABLE) selection of invalid constraint values possible and probably this irreversibly results in an empty pivot table
https://bugs.documentfoundation.org/show_bug.cgi?id=140760 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords||needsUXEval Ever confirmed|0 |1 --- Comment #6 from Mike Kaganski --- (In reply to Eike from comment #1) > 5. With this small spreadsheet I am not able to reproduce the deadlock event > though. This happens with a spreadsheet with about 0.5 million cells. 6. Change B11 from 3 to 1 7. Right-click A1, and select Refresh => now you can't make the pivot table to show column for constraint 2, thus you will not be able to reset the filtering done there. Now the question is: which UI would be reasonable in this case? What does Excel provide here? Maybe it would have some fail-safe behavior preventing this situation in the first place? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109182] [META] Cell freezing/fixing/locking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109182 Aron Budea changed: What|Removed |Added Depends on||142250 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142250 [Bug 142250] [EDITING] Frozen Rows/Columns reset when unfolding an outline-group causes the border outside of window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142250] [EDITING] Frozen Rows/Columns reset when unfolding an outline-group causes the border outside of window
https://bugs.documentfoundation.org/show_bug.cgi?id=142250 Aron Budea changed: What|Removed |Added Blocks||109182 CC||aron.bu...@gmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109182 [Bug 109182] [META] Cell freezing/fixing/locking bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151075] FILEOPEN XLSX: Outline Folding/Expanding is not correct
https://bugs.documentfoundation.org/show_bug.cgi?id=151075 --- Comment #4 from Bartosz --- Created attachment 182576 --> https://bugs.documentfoundation.org/attachment.cgi?id=182576&action=edit outline.ods file exported to .xlsx by MS Excel -- You are receiving this mail because: You are the assignee for the bug.
