[Libreoffice-bugs] [Bug 141642] RFE: Add opportunity to select only empty cells in selected range
https://bugs.documentfoundation.org/show_bug.cgi?id=141642 Buovjaga changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Whiteboard| QA:needsComment| --- Comment #2 from Buovjaga --- UX team: is there a need for this command in the core? Or would this be better left as a macro exercise for the user? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152704] WRITER: Linked image does not update after selecting another file in Properties dialog.
https://bugs.documentfoundation.org/show_bug.cgi?id=152704 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| --- Comment #1 from Dieter --- (In reply to tomasz.szte...@polon-alfa.pl from comment #0) > Steps to reproduce: > 1.Prepare two images, one very wide (A), second (B) tall and narrow and of > both sizes larger than sizes of image A. The difference in proportions do > help to expose the bug. Thnak you for reporting the bug. But I don't understand how to create a narrow image, with a larger whidth than a very wide image. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93605] [Request] Rename opened file from File > Rename?
https://bugs.documentfoundation.org/show_bug.cgi?id=93605 Buovjaga changed: What|Removed |Added CC||jeffshumphr...@gmail.com --- Comment #8 from Buovjaga --- *** Bug 141632 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 141632] FILESAVE: Rename in-place an open document with opt "Rename As..." under File menu
https://bugs.documentfoundation.org/show_bug.cgi?id=141632 Buovjaga changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Buovjaga --- This was discussed back in 2015 in bug 93605 and the conclusion was that this should derive from the operating system level (as we use the file dialogs of the operating systems). That said, Microsoft Office does have this under Save As. *** This bug has been marked as a duplicate of bug 93605 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109312] [META] Paths options bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109312 Bug 109312 depends on bug 141616, which changed state. Bug 141616 Summary: Allow separate My Documents path options per application https://bugs.documentfoundation.org/show_bug.cgi?id=141616 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59764] Unable to set different data paths per component
https://bugs.documentfoundation.org/show_bug.cgi?id=59764 Heiko Tietze changed: What|Removed |Added CC||remout...@gmail.com --- Comment #6 from Heiko Tietze --- *** Bug 141616 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 141616] Allow separate My Documents path options per application
https://bugs.documentfoundation.org/show_bug.cgi?id=141616 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Heiko Tietze --- It has been decided on bug 59764 to keep one path since the common workflow is to store documents from different modules together per task. *** This bug has been marked as a duplicate of bug 59764 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59764] Unable to set different data paths per component
https://bugs.documentfoundation.org/show_bug.cgi?id=59764 Heiko Tietze changed: What|Removed |Added Resolution|WORKSFORME |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45261] EDITING: unbalanced distribution of text between columns
https://bugs.documentfoundation.org/show_bug.cgi?id=45261 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2705 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152705] SECTION COLUMNS: Wrong text distribution
https://bugs.documentfoundation.org/show_bug.cgi?id=152705 Dieter changed: What|Removed |Added Keywords||needsUXEval Ever confirmed|0 |1 Summary|Error in Writer in columns |SECTION COLUMNS: Wrong text ||distribution CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Status|UNCONFIRMED |NEW See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=45 ||261 Whiteboard| QA:needsComment| OS|Linux (All) |All Hardware|x86-64 (AMD64) |All Blocks||107836 --- Comment #1 from Dieter --- I confirm the described behaviour with Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL Additinal information Option "Uniformous distribution of content between columns" is checked But I'm not sure, if it is a bug or expected behaviour, because we work with columns of a section and not with columns of a table. So I add design-team for a double check Referenced Bugs: 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||152705 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152705 [Bug 152705] SECTION COLUMNS: Wrong text distribution -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109312] [META] Paths options bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109312 Buovjaga changed: What|Removed |Added Depends on||141616 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141616 [Bug 141616] Allow separate My Documents path options per application -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141616] Allow separate My Documents path options per application
https://bugs.documentfoundation.org/show_bug.cgi?id=141616 Buovjaga changed: What|Removed |Added Keywords||needsUXEval Summary|LibreOffice discards|Allow separate My Documents |designated file folder |path options per |names when moving from |application |Writer to Calc and vice | |versa | CC||libreoffice-ux-advise@lists ||.freedesktop.org Whiteboard| QA:needsComment| OS|Windows (All) |All Blocks||109312 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109312 [Bug 109312] [META] Paths options bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102012] FILEOPEN DOCX Frame with table inside it positioned wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=102012 --- Comment #21 from Paolo Devoti --- Still true with attached test case Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 --- Comment #8 from افشین --- @hossein Would you please also test? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 --- Comment #7 from افشین --- Created attachment 184605 --> https://bugs.documentfoundation.org/attachment.cgi?id=184605&action=edit Bug Field Page Number -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 --- Comment #6 from افشین --- Created attachment 184604 --> https://bugs.documentfoundation.org/attachment.cgi?id=184604&action=edit Bug Field Page Number -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 --- Comment #5 from افشین --- I tested this bug in Safe Mode and except for two formats (a..aa..aaa & A..AA..AAA) the rest of other formats were correct! I attached 2 screenshot. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 --- Comment #4 from افشین --- Version: 7.4.3.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fa-IR (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.4.3~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org --- Comment #3 from Stéphane Guillou (stragu) --- Thank you for your report! Could not reproduce in: Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded nor in: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Could you please: - paste here the information from Help > About LibreOffice - test in safe mode (Help > Safe mode > Continue in safe mode) to see if it still happens Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 --- Comment #2 from افشین --- Created attachment 184603 --> https://bugs.documentfoundation.org/attachment.cgi?id=184603&action=edit Bug Field Page Number -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 --- Comment #1 from افشین --- Created attachment 184602 --> https://bugs.documentfoundation.org/attachment.cgi?id=184602&action=edit Bug Field Page Number -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] New: Format page number
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 Bug ID: 152985 Summary: Format page number Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: afs...@libreoffice.ir Created attachment 184601 --> https://bugs.documentfoundation.org/attachment.cgi?id=184601&action=edit Bug Field Page Number Hello. When I insert the page number (using Insert >> Field >> Page Number) and double click on the page number field, the edit fields window opens and I can select one of those formats. But there is a bug: When I select the format "one, two, three,...", the number "1" is inserted instead of "one"! And when I select the "1st, 2nd, 3rd" format, the word "Ordinal-number1" is inserted! And when I select "a ..aa ..aaa" format, the word "1" is inserted! And when I selct "First,Second,Third", the word "Ordinal 1" is inserted! I attached the screenshots. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117447] FILEOPEN Floating table in attached DOC(X) is lost(hidden) during import
https://bugs.documentfoundation.org/show_bug.cgi?id=117447 --- Comment #10 from Aron Budea --- Still in LO 7.6.0.0.alpha0+ (d993327eab0a2c9c8820c6528075b01de68b0ec6) / Ubuntu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137550] FILEOPEN DOCX Floating table unnecessarily opens in frame
https://bugs.documentfoundation.org/show_bug.cgi?id=137550 --- Comment #4 from Aron Budea --- Still in LO 7.6.0.0.alpha0+ (d993327eab0a2c9c8820c6528075b01de68b0ec6) / Ubuntu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152972] Javamaker fails with "unknown entity"
https://bugs.documentfoundation.org/show_bug.cgi?id=152972 --- Comment #4 from David Lochrin --- Many thanks, Stephan and Julien, for your help, that did indeed solve the problem. There's no doubt the LO API is a great thing as it allows a user to leverage the power of Calc by many orders, especially when Calc cell formulae become so complex their further development begins to be impracticable. (I'm doing some amateur Covid epidemiology.) However the API documentation is not very coherently presented IMO; for example, the intention behind the three versions of the 'setsdkenv*' utility only becomes clearer when the scripts are directly compared. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152673] docx/xlsx/pptx format can't read and write chart's descr property
https://bugs.documentfoundation.org/show_bug.cgi?id=152673 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 152726] Pasting Selection to Sheet as BMP Image, Text of Button is getting bigger.
https://bugs.documentfoundation.org/show_bug.cgi?id=152726 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152707] Properties pane in side bar misses all properties in case of Fontwork shape
https://bugs.documentfoundation.org/show_bug.cgi?id=152707 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 152704] WRITER: Linked image does not update after selecting another file in Properties dialog.
https://bugs.documentfoundation.org/show_bug.cgi?id=152704 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 152705] Error in Writer in columns
https://bugs.documentfoundation.org/show_bug.cgi?id=152705 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 152911] VIEWING - High CPU and lag when scrolling on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=152911 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 152699] infinitely spread window on libre office calc when apply base filter - by clicking filtermenu
https://bugs.documentfoundation.org/show_bug.cgi?id=152699 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 152911] VIEWING - High CPU and lag when scrolling on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=152911 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152639] Review fields is too long
https://bugs.documentfoundation.org/show_bug.cgi?id=152639 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 152639] Review fields is too long
https://bugs.documentfoundation.org/show_bug.cgi?id=152639 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99822] FILEOPEN: Floating table objects in tables horizontal position relative to margin is wrong in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=99822 --- Comment #13 from QA Administrators --- Dear RomaNick, 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 149385] LibreOffice crashed repeadely (see very specific crash report in Description)
https://bugs.documentfoundation.org/show_bug.cgi?id=149385 --- Comment #3 from QA Administrators --- Dear gpspilot1, 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 99763] Memory leaks when creating, moving, editing and deleting objects
https://bugs.documentfoundation.org/show_bug.cgi?id=99763 --- Comment #21 from QA Administrators --- Dear Gaétan RYCKEBOER, 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 93423] Memory leak in SbMethod::Broadcast
https://bugs.documentfoundation.org/show_bug.cgi?id=93423 --- Comment #3 from QA Administrators --- Dear Stephan Bergmann, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 93409] Memory leak when setting cell value from a macro: EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=93409 --- Comment #13 from QA Administrators --- Dear Mikhail Zemlyanukha, 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 92482] MEMORY LEAK: LO does not clear previously opened documents from RAM
https://bugs.documentfoundation.org/show_bug.cgi?id=92482 --- Comment #10 from QA Administrators --- Dear Yan Pas, 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 85603] Filesave (Export) as (X)HTML increases memory usage and shows false statusbar indication
https://bugs.documentfoundation.org/show_bug.cgi?id=85603 --- Comment #9 from QA Administrators --- Dear Alexander Berg, 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 81285] Embedded Math object doesn't resize itself
https://bugs.documentfoundation.org/show_bug.cgi?id=81285 --- Comment #12 from QA Administrators --- Dear A. Syukri Abdollah, 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 80869] FILEOPEN: illegal DOC DOCX with floating table and negative position to margin opens with wrong left margin as 0
https://bugs.documentfoundation.org/show_bug.cgi?id=80869 --- Comment #19 from QA Administrators --- Dear Gabriel, 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 77760] FILEOPEN: DOCX Text and Tables switch position - table with unchecked "Move with text"
https://bugs.documentfoundation.org/show_bug.cgi?id=77760 --- Comment #12 from QA Administrators --- Dear Vinaya Mandke, 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 71169] EDITING: Impress custom animations 'Lighten' and 'Contrasting Color' don't work with pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=71169 --- Comment #9 from QA Administrators --- Dear Teo91, 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 62306] Fileopen DOCX: Floating table part inside paragraph shown with paragraph color, not with page background color
https://bugs.documentfoundation.org/show_bug.cgi?id=62306 --- Comment #11 from QA Administrators --- Dear Regina Henschel, 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 69189] SLIDESHOW: focus of "Go to slide" drop down menu should be current slide, not always at Slide 1
https://bugs.documentfoundation.org/show_bug.cgi?id=69189 --- Comment #8 from QA Administrators --- Dear jidanni, 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 55018] FILESAVE: Merged table cells containing font-work cause table distortion after save to DOC, DOCX (example in Comment 3, status in Comment 14)
https://bugs.documentfoundation.org/show_bug.cgi?id=55018 --- Comment #25 from QA Administrators --- Dear V.K., 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 59365] FILESAVE: Memory usage after autorecovery/manual savings
https://bugs.documentfoundation.org/show_bug.cgi?id=59365 --- Comment #5 from QA Administrators --- Dear karolismatjosaitis, 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 47809] [donut chart] [FORMATTING] Colour won't be updated
https://bugs.documentfoundation.org/show_bug.cgi?id=47809 --- Comment #11 from QA Administrators --- Dear Florian Reisinger, 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 41288] undefined: Memory leaks when open, get document text and close document by UNO
https://bugs.documentfoundation.org/show_bug.cgi?id=41288 --- Comment #15 from QA Administrators --- Dear Anatoly, 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 139049] Copy image from left-to-right sheet and paste into right-to-left (RTL) sheet gives wrong image position
https://bugs.documentfoundation.org/show_bug.cgi?id=139049 --- Comment #4 from QA Administrators --- Dear Regina Henschel, 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 137550] FILEOPEN DOCX Floating table unnecessarily opens in frame
https://bugs.documentfoundation.org/show_bug.cgi?id=137550 --- Comment #3 from QA Administrators --- Dear Aron Budea, 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 136768] FILEOPEN DOCX: page-gap in table until click in title(or lots of other things) for this particular file.
https://bugs.documentfoundation.org/show_bug.cgi?id=136768 --- Comment #5 from QA Administrators --- Dear Timur, 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 134947] Dragging an image up down anchored to character/paragraph changes flow of footnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=134947 --- Comment #4 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 133522] FILEOPEN: DOCX: LayoutInCell: position of textbox incorrect.
https://bugs.documentfoundation.org/show_bug.cgi?id=133522 --- Comment #5 from QA Administrators --- Dear Justin L, 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 122925] Selecting table row & scrolling down isn't working
https://bugs.documentfoundation.org/show_bug.cgi?id=122925 --- Comment #5 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 132264] docx document with picture shown in wrong place
https://bugs.documentfoundation.org/show_bug.cgi?id=132264 --- Comment #6 from QA Administrators --- Dear ajg02, 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 119263] MacOS: Memory usage build up when pasting image back and forward between sheets (persistent after closing of the document)
https://bugs.documentfoundation.org/show_bug.cgi?id=119263 --- Comment #9 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 119144] unsuitable field value appearance for "delay between characters" setting in animation
https://bugs.documentfoundation.org/show_bug.cgi?id=119144 --- Comment #7 from QA Administrators --- Dear Regina Henschel, 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 118398] Memory usage keeps increasing when playing around with Chart wall background
https://bugs.documentfoundation.org/show_bug.cgi?id=118398 --- Comment #3 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 119043] Memory usage is still substantial after closing the presentation (especially with OpenGL enabled)
https://bugs.documentfoundation.org/show_bug.cgi?id=119043 --- Comment #4 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 117447] FILEOPEN Floating table in attached DOC(X) is lost(hidden) during import
https://bugs.documentfoundation.org/show_bug.cgi?id=117447 --- Comment #9 from QA Administrators --- Dear Aron Budea, 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 114455] SfxVoidItem::Clone(SfxItemPool*) leaks memory with multiple invocations
https://bugs.documentfoundation.org/show_bug.cgi?id=114455 --- Comment #10 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 113672] Unnecessarily floated table HORIZONTAL position not correct for DOCX when converted to inline table (comment 5)
https://bugs.documentfoundation.org/show_bug.cgi?id=113672 --- Comment #6 from QA Administrators --- Dear seven, 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 113581] Using Notebookbar and Hitting Shift while in Custom properties (reduces available system memory until complete system hang w/ gtk2 or hangs up LO w/ gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=113581 --- Comment #15 from QA Administrators --- Dear Eduardo, 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 112265] Certain fonts in a frame graphic do not have the correct position.
https://bugs.documentfoundation.org/show_bug.cgi?id=112265 --- Comment #18 from QA Administrators --- Dear dynapb, 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 112657] SfxUndoManager_Data::SfxUndoManager_Data leaks memory with multiple invocations
https://bugs.documentfoundation.org/show_bug.cgi?id=112657 --- Comment #9 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 108637] Memory usage increases considerably when deleting rows in a document with a 1000 empty sheets (see comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=108637 --- Comment #11 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 108270] Reloading presentation created with Focus template leaks memory leaks more memory every time (see comment 1)
https://bugs.documentfoundation.org/show_bug.cgi?id=108270 --- Comment #9 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 105261] FILEOPEN DOCX: small vertical spacing difference with table
https://bugs.documentfoundation.org/show_bug.cgi?id=105261 --- Comment #14 from QA Administrators --- Dear Marina Latini (SUSE), 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 103869] FILEOPEN LibO doesn't open .docx file with two table separated by a page break correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=103869 --- Comment #10 from QA Administrators --- Dear m_josenhans, 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 103250] Autocorrect does not recognise Greek punctuation characters « and »
https://bugs.documentfoundation.org/show_bug.cgi?id=103250 --- Comment #5 from QA Administrators --- Dear Jordi, 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 102012] FILEOPEN DOCX Frame with table inside it positioned wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=102012 --- Comment #20 from QA Administrators --- Dear Paolo Devoti, 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 152984] New: FORMATTING: support formatted paste from Google Sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=152984 Bug ID: 152984 Summary: FORMATTING: support formatted paste from Google Sheets 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: avidseek...@protonmail.com Related forum post: https://ask.libreoffice.org/t/support-formatted-paste-from-google-sheets/86358/4 Reproduce: 1. Have a styled sheet in Google 2. Select all, 3. Paste in Libreoffice Calc One expects to have the (1) style and (2) merged cells all imported to Libreoffice just by pasting. Actual result is that it’s no different that “paste unformatted”, and cells are left unmerged. However, the opposite works. Try this: Copy a styled spreadsheet in Libreoffice and paste it in Google Sheets. It will import all colors and merged cells. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152980] LibreOffice is modifying a cell entry (text) after saving to XLSX format
https://bugs.documentfoundation.org/show_bug.cgi?id=152980 m.a.riosv changed: What|Removed |Added OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152980] LibreOffice is modifying a cell entry (text) after saving to XLSX format
https://bugs.documentfoundation.org/show_bug.cgi?id=152980 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- Please don't set up as new, someone must do it after verify the issue. Reproducible Version: 7.4.4.1 (x64) / LibreOffice Community Build ID: 988f4a351a6fa8cf4bdf2bdc873ca12cf8cbe625 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150975] View > Navigator (F5) summons a second navigator instead of opening the sidebar deck (comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=150975 --- Comment #13 from Stéphane Guillou (stragu) --- Incidentally, I saw a bug report today in which the reporter's common setup has the navigator docked next to the sidebar: bug 151504. I imagine this will end up as a "won't fix" because the Navigator might be the one dialog/panel that users want to have always available, across components. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152589] TRANSLATION: Help for new translation feature is needed
https://bugs.documentfoundation.org/show_bug.cgi?id=152589 Olivier Hallot changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |olivier.hallot@libreoffice. |desktop.org |org --- Comment #2 from Olivier Hallot --- Patch submitted https://gerrit.libreoffice.org/c/help/+/145366 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152726] Pasting Selection to Sheet as BMP Image, Text of Button is getting bigger.
https://bugs.documentfoundation.org/show_bug.cgi?id=152726 raal changed: What|Removed |Added OS|Windows (All) |All Status|UNCONFIRMED |NEW CC||r...@post.cz Ever confirmed|0 |1 Keywords||regression --- Comment #4 from raal --- Confirm with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d993327eab0a2c9c8820c6528075b01de68b0ec6 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded but not in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152723] NatNum12 modifier, in the Spanish locales that have comma as decimal separator, the format spell out point not coma.
https://bugs.documentfoundation.org/show_bug.cgi?id=152723 --- Comment #3 from m.a.riosv --- Created attachment 184600 --> https://bugs.documentfoundation.org/attachment.cgi?id=184600&action=edit Format cell vs NUMBERTEXT function Hi @raal, thanks. But the issue doesn't happen with the extension and NUMBERTEXT() function. To see the file, the extension is needed. The last 1.0.11 2022-11-13. https://extensions.libreoffice.org/en/extensions/show/numbertext-1 So not clear for me where the issue happens. The UI English/Spanish does not affect. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152799] Crash with ungroup shapes and also gets some warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152799 Telesto changed: What|Removed |Added CC||libreoff...@nisz.hu --- Comment #10 from Telesto --- @Bogdan The bug is probably caused by the work done by Attila Bakos (NISZ) related to textbox grouping. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152983] Won't open a word doc
https://bugs.documentfoundation.org/show_bug.cgi?id=152983 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #4 from Julien Nabet --- I gave a try with https://gerrit.libreoffice.org/c/core/+/145364 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152969] 7.6.0 fails to start due to u_strToLower
https://bugs.documentfoundation.org/show_bug.cgi?id=152969 Pierre Fortin changed: What|Removed |Added Resolution|--- |INVALID Status|NEEDINFO|RESOLVED --- Comment #6 from Pierre Fortin --- (In reply to Michael Weghorn from comment #5) > Was there any recent update of ICU on your system as well, or just Qt? Looks like ICU also: $ rpm -qa --last | grep icu lib64icu-devel-72.1-1.mga9.x86_64 Sun 08 Jan 2023 08:08:18 AM EST lib64icu72-72.1-1.mga9.x86_64 Sun 08 Jan 2023 08:05:05 AM EST icu72-data-72.1-1.mga9.noarch Sun 08 Jan 2023 08:05:05 AM EST ### The following are still in the system lib64icu71-71.1-2.mga9.x86_64 Mon 20 Jun 2022 09:15:09 AM EDT icu71-data-71.1-2.mga9.noarch Mon 20 Jun 2022 09:15:09 AM EDT lib64basicusageenvironment1-2021.06.25-3.mga9.x86_64 Thu 24 Mar 2022 11:54:19 AM EDT lib64icu69-69.1-2.mga9.x86_64 Thu 24 Mar 2022 11:48:03 AM EDT icu69-data-69.1-2.mga9.noarch Thu 24 Mar 2022 11:48:03 AM EDT > Some commands you might check: What do these commands output for you? > (You'll have to adapt paths to where the libraries are on Mageia). Following > what I see on Debian testing): > > > $ nm -gD /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 | grep u_str > U u_strToLower_72 > U u_strToUpper_72 $ nm -gD /lib64/libQt5Core.so.5 | grep u_str U u_strToLower U u_strToUpper > $ ldd /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 | grep icu > libicui18n.so.72 => /lib/x86_64-linux-gnu/libicui18n.so.72 > (0x7f6ef1e0) > libicuuc.so.72 => /lib/x86_64-linux-gnu/libicuuc.so.72 > (0x7f6ef1c02000) > libicudata.so.72 => /lib/x86_64-linux-gnu/libicudata.so.72 > (0x7f6eef60) $ ldd /lib64/libQt5Core.so.5 | grep icu libicui18n.so.72 => /lib64/libicui18n.so.72 (0x7fae2be0) libicuuc.so.72 => /lib64/libicuuc.so.72 (0x7fae2bc0a000) libicudata.so.72 => /lib64/libicudata.so.72 (0x7fae2c133000) > $ nm -gD /lib/x86_64-linux-gnu/libicuuc.so.72 | grep -i u_strToLower > 00143330 T u_strToLower_72 $ nm -gD /lib64/libicuuc.so.72 | grep -i u_strToLower 0013b0c0 T u_strToLower > (In reply to Pierre Fortin from comment #3) > > Operating System: Mageia 9 > > Is that a stable Mageia release or (as a quick look on the Mageia website > suggests) some alpha/pre-release? Other than LOTS of updates; I've been using it as my primary OS since Feb/22 when I acquired the machine. On the whole, I have no problem with alpha/beta software; support tends to be better than with released software... :) > > > You can try this: > > > - launch a terminal/console > > > - type: > > > export SAL_USE_VCLPLUGIN=gen > > > - scalc & > > > > Splash and quits; no error message with this var. Just installed today's > > build; same... For completeness: $ scalc --safe-mode warn:sal.osl:377911:377911:sal/osl/unx/module.cxx:152: dlopen(/home/pfortin/libreoffice/opt/libreofficedev7.6/program/libvclplug_kf5lo.so, 257): /lib64/libQt5Core.so.5: undefined symbol: u_strToLower warn:sal.osl:377911:377911:sal/osl/unx/module.cxx:152: dlopen(/home/pfortin/libreoffice/opt/libreofficedev7.6/program/libvclplug_gtk3_kde5lo.so, 257): /lib64/libQt5Core.so.5: undefined symbol: u_strToLower warn:desktop.app:377911:377911:unotools/source/ucbhelper/localfilehelper.cxx:87: error removing directory file:///home/pfortin/libreoffice/opt/libreofficedev7.6/program/../../UserInstallation/user/extensions The last line is new. $ ll libreoffice/opt/UserInstallation/user/ total 16 drwxr-xr-x 2 pfortin pfortin 4096 Jan 11 14:58 config/ drwxr-xr-x 2 pfortin pfortin 4096 Jan 11 14:58 extensions/ -rw--- 1 pfortin pfortin 329 Jan 11 14:58 registrymodifications.xcu drwxr-xr-x 13 pfortin pfortin 4096 Jan 11 14:57 SafeMode/ $ ll libreoffice/opt/UserInstallation/user/extensions/ total 4 -rw-r--r-- 1 pfortin pfortin 40 Jan 11 14:58 buildid > Does this still happen after deleting your LO profile or when you start in > safe mode? Safe mode: see above. $ mv libreoffice/opt/UserInstallation/user libreoffice/opt/UserInstallation/user.off No change. > Does it also happen when you start 'soffice --writer' or just 'soffice' > instead of 'scalc'? Interesting: 'soffice --writer' & 'soffice --calc' both start up. 'scalc' and 'swriter' fail as originally reported... > Does the LibreOffice installed via Mageia packages work, in particular the > kf5 VCL plugin (i.e. the one that says "VCL: kf5 (...)" in "Help" -> "About > LibreOffice"? (Don't know whether Mageia provides that as a package.) Never saw VCL (whatever that is)... Here's the version info: Version: 7.4.3.2 Build ID: 40(Build:2) CPU threads: 20; OS: Linux 6.1; UI render: default;
[Libreoffice-bugs] [Bug 152624] LIST STYLES: Numbered Lists in LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152624 --- Comment #9 from John La Fountain --- Dieter, Thanks! John L. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152983] Won't open a word doc
https://bugs.documentfoundation.org/show_bug.cgi?id=152983 raal changed: What|Removed |Added Keywords||bibisected, bisected, ||regression CC||michael.st...@allotropia.de ||, r...@post.cz Regression By||Michael Stahl --- Comment #3 from raal --- This seems to have begun at the below commit. Adding Cc: to Michael Stahl ; Could you possibly take a look at this one? Thanks f1d8f96bc30af74cb43934749ca2304d828bd66f is the first bad commit commit f1d8f96bc30af74cb43934749ca2304d828bd66f Author: Jenkins Build User Date: Tue Nov 17 01:14:39 2020 +0100 source sha:b9ef71476fd70bc13f50ebe80390e0730d1b7afb https://gerrit.libreoffice.org/c/core/+/105810 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152861] LibreOffice DRAW crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=152861 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #6 from Julien Nabet --- If it's Skia related, could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29 ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106731] No indication macro is read-only
https://bugs.documentfoundation.org/show_bug.cgi?id=106731 Rafael Lima changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147488] The Basic IDE does not display the Object Catalog Panel when you open an empty standard macro library
https://bugs.documentfoundation.org/show_bug.cgi?id=147488 Rafael Lima changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #7 from Rafael Lima --- This actually happens whenever you choose a script document that has no modules in it. A simpler way to reproduce this issue is: 1) Open Writer (a fresh new document Untitled 1) 2) Go to Tools - Macros - Edit Macros 3) In the toolbar, use the Library Selector to choose [Untitled 1].Standard (which is by default an empty library) 4) Notice the blank screen without the Object Catalog I studied this code today and simply showing the Object Catalog is not that simple, because it must be associated with a LayoutWindow that needs to be either a dialog or a module. A simple solution would be to create a default Module window whenever the Library contains nothing. A proposed solution can be found here: https://gerrit.libreoffice.org/c/core/+/145309 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103369 Dieter changed: What|Removed |Added Depends on||152624 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152624 [Bug 152624] LIST STYLES: Numbered Lists in LibreOffice Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103369 Bug 103369 depends on bug 152624, which changed state. Bug 152624 Summary: LIST STYLES: Numbered Lists in LibreOffice Writer https://bugs.documentfoundation.org/show_bug.cgi?id=152624 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152624] LIST STYLES: Numbered Lists in LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152624 Dieter changed: What|Removed |Added Blocks||103369 Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED Summary|Numbered Lists in |LIST STYLES: Numbered Lists |LibreOffice Writer |in LibreOffice Writer --- Comment #8 from Dieter --- (In reply to John La Fountain from comment #7) I consider this behavior is a bug, not a feature! > John L. Couldn't find informations in LO Help or Writer Guide. So let's change back to UNCONFIRMED and ask design-team for their input and decision. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103369 [Bug 103369] [META] Bullet, numbered, and outline list bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152983] Won't open a word doc
https://bugs.documentfoundation.org/show_bug.cgi?id=152983 Julien Nabet changed: What|Removed |Added Keywords||haveBacktrace Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152983] Won't open a word doc
https://bugs.documentfoundation.org/show_bug.cgi?id=152983 --- Comment #2 from Julien Nabet --- Created attachment 184599 --> https://bugs.documentfoundation.org/attachment.cgi?id=184599&action=edit bt with debug symbols + console logs On pc Debian x86-64 with master sources updated today, I could reproduce this. I attached bt + console logs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152911] VIEWING - High CPU and lag when scrolling on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=152911 --- Comment #2 from b...@irreversibly.org --- Upon further testing the problem does seem to be fractional scaling, since setting scaling to 1x and only then opening a new instance of LO has no issues. Since KDE renders at double the resolution to achieve fractional scaling, it may just be my computer not being able to render LO scrolling at 4K (AMD Ryzen 5 laptop). The Flatpak version runs better (still choppy), the non-Flatpak skips all the graphics tests so I may be missing something graphics related as well. I'll leave it up to you whether to close this one. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150975] View > Navigator (F5) summons a second navigator instead of opening the sidebar deck (comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=150975 --- Comment #12 from Roman Kuznetsov <79045_79...@mail.ru> --- I think we discussed it hundred times already. I fully agree with Comment 11, I have the same use case for using Navigator as different thing in addition to the Sidebar -1 from my side -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152978] [UI/UX enhancement] Open object preferences or options with F4 (and add description to context menus)
https://bugs.documentfoundation.org/show_bug.cgi?id=152978 --- Comment #5 from Roman Kuznetsov <79045_79...@mail.ru> --- We use F4 for cell link mode change in Calc. I'm not sure we need F4 for another action.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152799] Crash with ungroup shapes and also gets some warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152799 --- Comment #9 from Noel Grandin --- (In reply to BogdanB from comment #6) > Recently was this commit. Could be this the cause? > > https://gerrit.libreoffice.org/c/core/+/143205 Nope, problem pre-dates that commit. -- You are receiving this mail because: You are the assignee for the bug.
