[Libreoffice-bugs] [Bug 153395] Localisation of on MacOS without spotlight active
https://bugs.documentfoundation.org/show_bug.cgi?id=153395 Julien Nabet changed: What|Removed |Added Summary|Lokalisation of on MacOS|Localisation of on MacOS |without spotlight active|without spotlight active -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153148] Menu background color dark when Windows 11 in dark mode and Libre Office in Light mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153148 --- Comment #3 from Mike Kaganski --- IIRC, there were many similar bugs, closed somehow as "there is a proper dark mode in 7.5". Which is not what these issues are about; having proper dark menu with bright text in dark mode is not the same as having proper light menu with dark text in app's light mode when running on system with dark mode. In the light of bug 153229, this will have own significance. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141623] Qt5 refresh problem when starting LO start center and cairo (text) rendering ennabled
https://bugs.documentfoundation.org/show_bug.cgi?id=141623 Michael Weghorn changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153405] Table in 2nd column wrongly split over page break; unstable rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=153405 --- Comment #5 from Telesto --- (In reply to Jim Avera from comment #0) > === CASE 2 DESCRIPTION === > > Please see "exploded_screenshot.png" where the last table is split into many > pieces on several pages. I got this after some sequence of inserts and > pasting of copies of the table which I can't reproduce. > > After I did Save and then Reload, the rendering changed so that it was > similar to CASE 1 above. Please see "after_save_reload.png". Something > about this bug makes rendering unstable across save & reload. Steps to reproduce this/similar case 1. Open attachment 185140 2. Go to multi page view 3. Cursor in Table 5, bottom row 4. Press add row Already reported somewhere, I think. However still a nice and clean testcase, though -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141623] Qt5 refresh problem when starting LO start center and cairo (text) rendering ennabled
https://bugs.documentfoundation.org/show_bug.cgi?id=141623 --- Comment #10 from annaluss --- I really amazed to read this blog post. It is so unique and informative Fur Jackets & Coats : https://www.filmsjackets.com/Fur-Jackets -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152395] [Accessibility] LibreOffice Writer immediately crashes when entering characters and VoiceOver is running.
https://bugs.documentfoundation.org/show_bug.cgi?id=152395 --- Comment #8 from Telesto --- (In reply to Stéphane Guillou (stragu) from comment #7) > Marco, do you know what was the latest version you could use without a crash? And does it still crash with LibreOffice 7.4.5. Quite a number of macOS bugs got fixed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145709] Crash in: SwXTextRange::SetPositions (interaction with Zotero)
https://bugs.documentfoundation.org/show_bug.cgi?id=145709 Dieter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #9 from Dieter --- (In reply to Christopher J Poor from comment #8) > Hi Dieter, > I just installed LO 7.5 and tested with Zotero 6. > The bug appears to have been fixed. > Many thanks, > Chris. Thank you for testing => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140147] Position of cursor not saved correctly (see comment 46 for bibisect)
https://bugs.documentfoundation.org/show_bug.cgi?id=140147 --- Comment #61 from Aron Budea --- (In reply to MR Zenwiz from comment #60) > Last I saw this was supposed to be fixed in 7.5 and it is not. This bug being open means the issue isn't supposed to be fixed in 7.5.0. A problem was identified and fixed in bug 146988, but it apparently wasn't the same. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136372] [META] PPTX shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136372 Bug 136372 depends on bug 9, which changed state. Bug 9 Summary: FILESAVE: Shapes with Default Line Width Changed on Roundtrip (MSO 2007 theme defaults not preserved) https://bugs.documentfoundation.org/show_bug.cgi?id=9 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108226] [META] PPTX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108226 Bug 108226 depends on bug 9, which changed state. Bug 9 Summary: FILESAVE: Shapes with Default Line Width Changed on Roundtrip (MSO 2007 theme defaults not preserved) https://bugs.documentfoundation.org/show_bug.cgi?id=9 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108230] [META] OOXML document theme issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108230 Bug 108230 depends on bug 9, which changed state. Bug 9 Summary: FILESAVE: Shapes with Default Line Width Changed on Roundtrip (MSO 2007 theme defaults not preserved) https://bugs.documentfoundation.org/show_bug.cgi?id=9 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135702] Table breaks over column without flowing to bottom of page despite setting no breaks.
https://bugs.documentfoundation.org/show_bug.cgi?id=135702 --- Comment #5 from Jim Avera --- https://bugs.documentfoundation.org/show_bug.cgi?id=153405 ...might be related. Or possibly the same underlying problem (?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153405] Table in 2nd column wrongly split over page break; unstable rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=153405 --- Comment #4 from Jim Avera --- Created attachment 185143 --> https://bugs.documentfoundation.org/attachment.cgi?id=185143=edit tablesplit1_screenshot.png -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153405] Table in 2nd column wrongly split over page break; unstable rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=153405 --- Comment #3 from Jim Avera --- Unfortunately, the unstable rendering problem made "tablesplit1.odt" no longer show exactly the problem described in the original report. Instead, after reloading tablesplit1.odt, Table #6 is not split but table #7 is split across columns within the second page. No splitting of any kind should occur because none of the table have splitting enabled in their Properties. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153405] Table in 2nd column wrongly split over page break; unstable rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=153405 --- Comment #2 from Jim Avera --- Created attachment 185142 --> https://bugs.documentfoundation.org/attachment.cgi?id=185142=edit after_save_reload.png -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153405] Table in 2nd column wrongly split over page break; unstable rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=153405 --- Comment #1 from Jim Avera --- Created attachment 185141 --> https://bugs.documentfoundation.org/attachment.cgi?id=185141=edit exploded_screenshot.png -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153405] New: Table in 2nd column wrongly split over page break; unstable rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=153405
Bug ID: 153405
Summary: Table in 2nd column wrongly split over page break;
unstable rendering
Product: LibreOffice
Version: 7.6.0.0 alpha0+ Master
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: jim.av...@gmail.com
Created attachment 185140
--> https://bugs.documentfoundation.org/attachment.cgi?id=185140=edit
tablesplit1.odt (see STEPS TO REPRODUCE)
Sometimes tables are wrongly split across a page break and/or wrap into the
wrong column on the next page, and the splitting behavior is not stable over
save & reload.
Attached are a couple of test case .odt files. Each of them started as a
single page containing a SECTION with two columns (so the text before the
section is single-column).
The 2-column section contains several Tables (all but the first copy-pasted).
=== CASE 1 STEPS TO REPRODUCE ===
1. Load attached tablesplit1.odt
Notice that the last table ("table #6") is split across the page break, but the
split-off portion appears in the SECOND column of the next page, not the first
column. That is, the split portion of table #6 appears "after" table #7
(which is in the first column of the second page).
2. Put cursor in table #6
Table->Properties->Text Flow
Notice that "Allow table to split across pages and columns" is NOT checked.
RESULTS: Table #6 wrongly split with the split-off portion landing in the 2nd
column of the next page, i.e. "after" Table #7
EXPECTED RESULTS: Table #6 should have forced a skip to the next page because
there is not enough room for it in the remaining space on the first page.
=== CASE 2 DESCRIPTION ===
Please see "exploded_screenshot.png" where the last table is split into many
pieces on several pages. I got this after some sequence of inserts and
pasting of copies of the table which I can't reproduce.
After I did Save and then Reload, the rendering changed so that it was similar
to CASE 1 above. Please see "after_save_reload.png". Something about this
bug makes rendering unstable across save & reload.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145709] Crash in: SwXTextRange::SetPositions (interaction with Zotero)
https://bugs.documentfoundation.org/show_bug.cgi?id=145709 --- Comment #8 from Christopher J Poor --- Hi Dieter, I just installed LO 7.5 and tested with Zotero 6. The bug appears to have been fixed. Many thanks, Chris. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139934] FILEOPEN: Date is shown as an integer
https://bugs.documentfoundation.org/show_bug.cgi?id=139934 --- Comment #13 from Jan Kratochvil --- still valid for: 7.3.7.2 libreoffice-calc-7.3.7.2-2.fc36.x86_64 (I have tried to download and install your 7.5 but it did not start for me on Fedora 36 x86-64.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153144] Red Frame, Editing, RECORD CHANGES NOT SELECTED
https://bugs.documentfoundation.org/show_bug.cgi?id=153144 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 146148] Severe lags when working on SMB share on cursor movement and saving file
https://bugs.documentfoundation.org/show_bug.cgi?id=146148 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 153133] Libreoffice Crashes with Youtube running
https://bugs.documentfoundation.org/show_bug.cgi?id=153133 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 153133] Libreoffice Crashes with Youtube running
https://bugs.documentfoundation.org/show_bug.cgi?id=153133 --- 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 135841] font colors broken on form buttons in Base
https://bugs.documentfoundation.org/show_bug.cgi?id=135841 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135841] font colors broken on form buttons in Base
https://bugs.documentfoundation.org/show_bug.cgi?id=135841 --- Comment #5 from QA Administrators --- Dear trowelandmattock, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117073] [META] WebDAV bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=117073 Bug 117073 depends on bug 116466, which changed state. Bug 116466 Summary: Access WebDav https:// using nss client certificate https://bugs.documentfoundation.org/show_bug.cgi?id=116466 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150266] Program does not continue where it left off.
https://bugs.documentfoundation.org/show_bug.cgi?id=150266 --- Comment #5 from QA Administrators --- Dear holtecaydi, 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 116466] Access WebDav https:// using nss client certificate
https://bugs.documentfoundation.org/show_bug.cgi?id=116466 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116466] Access WebDav https:// using nss client certificate
https://bugs.documentfoundation.org/show_bug.cgi?id=116466 --- Comment #7 from QA Administrators --- Dear slavb18, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148800] Print size decreases when highlighting or replacing a word.
https://bugs.documentfoundation.org/show_bug.cgi?id=148800 --- Comment #4 from QA Administrators --- Dear howaz, 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 132961] No DPI setting written when compressing an image to PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=132961 --- Comment #7 from QA Administrators --- Dear Telesto, 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 98403] UGX currency displayed as “Ganda”
https://bugs.documentfoundation.org/show_bug.cgi?id=98403 --- Comment #23 from QA Administrators --- Dear Diarmuid O'Briain, 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 97892] Snapping to snap lines doesnt always work correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=97892 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 94238] FILEOPEN: OOXML - Radial fill not imported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=94238 --- Comment #11 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 92981] Wrong error in bracketing from xls file
https://bugs.documentfoundation.org/show_bug.cgi?id=92981 --- Comment #12 from QA Administrators --- Dear Rpnpif, 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 63201] FORMATTING: incorrect formatting of xls file created in MS Office/Open Offce
https://bugs.documentfoundation.org/show_bug.cgi?id=63201 --- Comment #11 from QA Administrators --- Dear bazilio, 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 61606] LibreOffice should import and export custom XML parts in Office Open XML documents
https://bugs.documentfoundation.org/show_bug.cgi?id=61606 --- Comment #8 from QA Administrators --- Dear Wolfgang Silbermayr, 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 139934] FILEOPEN: Date is shown as an integer
https://bugs.documentfoundation.org/show_bug.cgi?id=139934 --- Comment #12 from QA Administrators --- Dear Jan Kratochvil, 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 123153] DB links not detected properly
https://bugs.documentfoundation.org/show_bug.cgi?id=123153 --- Comment #4 from QA Administrators --- Dear Frank Brütting, 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 138637] FILEOPEN: PPTX: Vertical text is horizontal in table
https://bugs.documentfoundation.org/show_bug.cgi?id=138637 --- Comment #6 from QA Administrators --- Dear Xisco Faulí, 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 114759] FILESAVE Slides Per row saved in Normal view, but not Slide Sorter view
https://bugs.documentfoundation.org/show_bug.cgi?id=114759 --- Comment #9 from QA Administrators --- Dear Daniel Collins, 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 152724] FILESAVE FORMATTING Cell custom Format Code with _- (UI visible space width) is not saved correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=152724 Laurent Balland changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jumbo4...@yahoo.fr |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136372] [META] PPTX shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136372 Bug 136372 depends on bug 9, which changed state. Bug 9 Summary: FILESAVE: Shapes with Default Line Width Changed on Roundtrip (MSO 2010+ theme defaults not preserved) https://bugs.documentfoundation.org/show_bug.cgi?id=9 What|Removed |Added Status|VERIFIED|UNCONFIRMED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108230] [META] OOXML document theme issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108230 Bug 108230 depends on bug 9, which changed state. Bug 9 Summary: FILESAVE: Shapes with Default Line Width Changed on Roundtrip (MSO 2010+ theme defaults not preserved) https://bugs.documentfoundation.org/show_bug.cgi?id=9 What|Removed |Added Status|VERIFIED|UNCONFIRMED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108226] [META] PPTX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108226 Bug 108226 depends on bug 9, which changed state. Bug 9 Summary: FILESAVE: Shapes with Default Line Width Changed on Roundtrip (MSO 2010+ theme defaults not preserved) https://bugs.documentfoundation.org/show_bug.cgi?id=9 What|Removed |Added Status|VERIFIED|UNCONFIRMED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101912] [META] Accessibility (a11y) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101912 Luke changed: What|Removed |Added Depends on||153404 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153404 [Bug 153404] FILESAVE PPTX: Alt Text field of image is lost on save in LO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153404] FILESAVE PPTX: Alt Text field of image is lost on save in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153404 Luke changed: What|Removed |Added Blocks||101912 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101912 [Bug 101912] [META] Accessibility (a11y) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153404] FILESAVE PPTX: Alt Text field of image is lost on save in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153404 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3403 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153403] FILEOPEN PPTX: Alt Text field of image is lost on open in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153403 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3404 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153403] FILEOPEN PPTX: Alt Text field of image is lost on open in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153403 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8952 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153404] FILESAVE PPTX: Alt Text field of image is lost on save in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153404 Luke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8952 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153404] FILESAVE PPTX: Alt Text field of image is lost on save in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153404 --- Comment #1 from Luke --- Created attachment 185139 --> https://bugs.documentfoundation.org/attachment.cgi?id=185139=edit Example ODP with Alt Text Tag -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153403] FILEOPEN PPTX: Alt Text field of image is lost on open in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153403 --- Comment #1 from Luke --- Created attachment 185138 --> https://bugs.documentfoundation.org/attachment.cgi?id=185138=edit Example PPTX with Alt Text Tag -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153404] New: FILESAVE PPTX: Alt Text field of image is lost on save in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153404 Bug ID: 153404 Summary: FILESAVE PPTX: Alt Text field of image is lost on save in LO Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lukebe...@hotmail.com Steps to reproduce: 1. In Impress save Accessibility.odp as pptx (2007-365) 2. Close 3. Open pptx 4. Right click on image 5. Description -> Text Alternative Expected Results: 1. Text Alternative = "ImAltText" Actual Results: 1. Text Alternative = Blank the exported OOXML reads: when it should read: like Bug 148952 we do not handle title="ImAltText" on import. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101912] [META] Accessibility (a11y) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101912 Luke changed: What|Removed |Added Depends on||153403 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153403 [Bug 153403] FILEOPEN PPTX: Alt Text field of image is lost on open in LO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153403] FILEOPEN PPTX: Alt Text field of image is lost on open in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153403 Luke changed: What|Removed |Added Blocks||101912 Keywords||filter:pptx Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101912 [Bug 101912] [META] Accessibility (a11y) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153403] New: FILEOPEN PPTX: Alt Text field of image is lost on open in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=153403 Bug ID: 153403 Summary: FILEOPEN PPTX: Alt Text field of image is lost on open in LO Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lukebe...@hotmail.com Steps to reproduce: 1. Open Accessibility-native.pptx in Impress 2. Right click on image 3. Description -> Text Alternative Expected Results: 1. Text Alternative = "ImAltText" Actual Results: 1. Text Alternative = Blank Key OOXML: like Bug 148952 we do not handle title="ImAltText" on import. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140147] Position of cursor not saved correctly (see comment 46 for bibisect)
https://bugs.documentfoundation.org/show_bug.cgi?id=140147 --- Comment #60 from MR Zenwiz --- This remains unfixed in LO 7.5: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 32; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Last I saw this was supposed to be fixed in 7.5 and it is not. See bug 146998 for examples attached to reproduce the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119745] Scrolling with a laptop touchpad in Libreoffice way too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=119745 --- Comment #53 from Marc --- I have this bug also. In LibreOffice Calc, scrolling vertically or horizontally using the touchpad two-finger scroll is way too fast. Lenovo Legion Y740-17IRHg, Windows 10 Home. If I move my fingers the *smallest* amount possible that registers on the touchpad (~1 mm), the spreadsheet moves 3 rows vertically at a minimum. But any normal movement that scrolls a little in other apps results in most of a screen going by in Calc. About dialog: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139538] Cannot load HsqlDB other than 1.8.0
https://bugs.documentfoundation.org/show_bug.cgi?id=139538 --- Comment #4 from prrv...@gmail.com --- Just to tell you that the HsqlDBDriverOOo extension has been renamed by jdbcDriverOOo: https://prrvchr.github.io/jdbcDriverOOo/ And that it now includes several JDBC drivers (HsqlDB, H2, Apache Derby, SQLite JDBC Driver, MariaDB Connector/J, SmallSQL) I do not hide from you that apart from HsqlDB where almost complete tests have been carried out, the other drivers must suffer from some malfunctions in Base -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153399] [UI] Vertical scrolling becomes unresponsive when hide columns option is used such that the background is visible
https://bugs.documentfoundation.org/show_bug.cgi?id=153399 ady changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from ady --- I have noticed this too. We have to wonder whether this is somehow related to: https://wiki.documentfoundation.org/ReleaseNotes/7.4 quotes: * Calc now supports and uses 16384 columns ( http://llunak.blogspot.com/2022/03/enabling-calc-support-for-16384-columns.html ) . (Luboš Luňák, Collabora) * Hidden columns/rows can have an indicator per View ▸ Hidden Row/Column Indicator tdf#128258 (Heiko Tietze, TDF) among other items related to columns that were introduced in LO 7.4. BTW, changing menu VIEW > Hidden Rows/Columns Indicator doesn't seem to influence the lag. The lag is not "terrible" (i.e. not "unresponsive") in my system, but it is notable. OTOH, I admit I don't really recall whether this lag was present before 7.4.4. Repro in: Version: 7.4.4.2 (x64) / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL and in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153402] New: English (en-us) Spellcheck overactive (acceptable spelling flagged as incorrect)
https://bugs.documentfoundation.org/show_bug.cgi?id=153402 Bug ID: 153402 Summary: English (en-us) Spellcheck overactive (acceptable spelling flagged as incorrect) Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: trav...@gmail.com The word in question today is 'briar' (preferred modern spelling in en-US) but was flagged as incorrect by spellchecker, and that it should be spelled 'brier.' In fact, I had to forcibly make Google search for 'brier.' The Oxford Dictionary (also preferred by en-ca) site insists the former spelling is correct. Both should be considered acceptable. In the reference article below, there is even one version of the word that contains a 'y.' Not sure if that should be included as correct, as it is obviously extremely rare. Similar to Bug 142043, but different word. [Same repro, etc] Might fall under the broader category discussed in Bug 149521. As noted in this bug, I have also encountered this 'lexical/dialectical' spelling confusion on many occasions. This one hit me just right, enough so that I braved the 'subcategory' mire to file a bug. That said, I want you all to know I appreciate what you are doing. Thank you very much for making the world a better place by being on the LibreOffice team! Reference Article -- https://www.augustachronicle.com/story/news/local/sylvania-telephone/2009/03/05/which-one-correct-briar-brier-or-bryer/14198595007/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153394] enormous size of special characters in 'insert special characters' in Writer, LO 7.5.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=153394 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153393] Calc crashes with →Data→Sort→→Options: Language: ***any Language except Default-Locale***
https://bugs.documentfoundation.org/show_bug.cgi?id=153393 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- I can't reproduce the issue. Version: 7.1.8.1 (x86) / LibreOffice Community Build ID: e1f30c802c3269a1d052614453f260e49458c82c CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: es-AR (es_ES); UI: es-ES Calc: CL 7.0 is EOL, please could you test with a newer version? https://www.libreoffice.org/download/download-libreoffice/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153401] New: Remove "COLUMN" from the Sort Key dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=153401 Bug ID: 153401 Summary: Remove "COLUMN" from the Sort Key dropdown Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: waltp9...@gmail.com Please remove the word "COLUMN" from the sort keys to streamline choosing columns. Currently we have to scroll through all the columns when hitting a key will jump directly to the selection starting with that key. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139188] Charts on copied sheet still reference the data in the original sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=139188 m.a.riosv changed: What|Removed |Added CC||bernhard.fri...@mail.de --- Comment #7 from m.a.riosv --- *** Bug 153386 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 153386] Spreadsheet table copy does not copy diagrams correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=153386 m.a.riosv changed: What|Removed |Added Resolution|--- |DUPLICATE CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED --- Comment #3 from m.a.riosv --- Maybe because Data Series ranges addresses of charts has an absolute reference to the sheet where they are, changing it (deleting the $ in front of ranges, lets to copy fine, but the resulting charts have again absolute addresses. *** This bug has been marked as a duplicate of bug 139188 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146601] Libre Calc does not display cell entries as they are typed
https://bugs.documentfoundation.org/show_bug.cgi?id=146601 --- Comment #13 from ady --- Perhaps some high contrast and/or accessibility setting, whether in LibreOffice or in the OS itself? What about some color theme? Perhaps in LO Options > LibreOffice > Application Colors ? Maybe there is some color combination that results in White-on-White (or equivalent)? After you finished introducing the cell's content, when you go back to put the focus on the same cell, do you see the content of the cell in the formula bar (e.g. formula or whatever)? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297
--- Comment #15 from ady ---
(In reply to Winfried Donkers from comment #14)
> In the sample files that have been attached, none of the ranges looks sorted
Indeed, that was specifically mentioned.
> to me. Then all results for MATCH with 3rd argument 1, -1 or empty have no
> real meaning.
That is not completely accurate. It is true that the lookup array is expected
to be sorted, and when it isn't, the results are not "predictable". That means
that the result cannot be expressed beforehand in some generic simple words,
but rather that it depends on a case-by-case basis. But, that does not mean
that the results will be different according to whatever goes in the list after
the first matched value. IOW, the result shall still be repeatable. That is why
I added an attachment, to demonstrate exactly this non-repeatable behavior. Let
me emphasize the point...
If I am using "1" (ascending) search, and the lookup array starts with
{0;1;whatever}, then when the lookup value is "1" (without quotation marks),
the result shall be "2" (without quotation marks), always. The result cannot
vary depending on the _next_ values. MATCH() should find the first value that
accomplishes the conditions. Attachment 185129 demonstrates that this is not
currently the case (the result varies, depending on values that are _after_ the
first position that accomplishes the conditions), and if you check with LO
7.3.x (and older), you should obtain "2" as result.
So, yes, there is no generic way to know the result beforehand as a generic
rule, but the results shall still follow the conditions/rules; they are not
random, or vary according to the number of empty cells _after_ the first "OK"
value.
Please review attachment 185129 again, in order to spot these nonsensical
varying results.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152395] [Accessibility] LibreOffice Writer immediately crashes when entering characters and VoiceOver is running.
https://bugs.documentfoundation.org/show_bug.cgi?id=152395 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||haveBacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153144] Red Frame, Editing, RECORD CHANGES NOT SELECTED
https://bugs.documentfoundation.org/show_bug.cgi?id=153144 --- Comment #2 from ady --- I'm not sure there is a bug here. It might just be 2 unrelated issues (color of focused cell, and copy+paste incident). Regarding the color around the cell that has the current focus, this might just be (quote): "Cell cursor now uses the system's highlight color instead of the default font color to improve visibility tdf#142121 (Natalia Gavrilova)" which was introduced in LO 7.3: https://wiki.documentfoundation.org/ReleaseNotes/7.3#General_improvements_2 This is just a suspicion/hunch, as I don't have a real indication that what you are actually seeing is this. If it is (and even if it isn't), there are several related questions (and answers) at ask.libreoffice.org. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153400] New: Different font size after undo rejecting changes
https://bugs.documentfoundation.org/show_bug.cgi?id=153400 Bug ID: 153400 Summary: Different font size after undo rejecting changes Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Different font size after undo rejecting changes Steps to Reproduce: 1. Open attachment 179678 2. CTRL+A 3. Change Font Size to 16 4. Edit -> Track Changes -> Manage -> Reject on by one 5. Close the dialog 6. CTRL+Z everything Actual Results: Text with green highlighting being Font Size 12 Expected Results: Font Size 10 Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8ae6d1388f28c405c4de2dfe93dbfe2d8acd470 CPU threads: 8; OS: Mac OS X 12.6.3; UI render: Skia/Raster; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Telesto changed: What|Removed |Added Depends on||153306 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153306 [Bug 153306] Cursor keeps displayed when using Skia Metal on macOS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153306] Cursor keeps displayed when using Skia Metal on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 Telesto changed: What|Removed |Added Blocks||129062 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152395] [Accessibility] LibreOffice Writer immediately crashes when entering characters and VoiceOver is running.
https://bugs.documentfoundation.org/show_bug.cgi?id=152395 Telesto changed: What|Removed |Added CC||tele...@surfxs.nl Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153306] Cursor keeps displayed when using Skia Metal on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 Telesto changed: What|Removed |Added Summary|Cursor keeps displayed when |Cursor keeps displayed when |using Skia on macOS |using Skia Metal on macOS CC||tele...@surfxs.nl Hardware|ARM |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153306] Cursor keeps displayed when using Skia on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 Telesto changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Telesto --- Confirm Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8ae6d1388f28c405c4de2dfe93dbfe2d8acd470 CPU threads: 8; OS: Mac OS X 12.6.3; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded 1. Open attachment 179678 2. Press and hold arrow left, at the end of the first line of text Only with Skia/Metal (fine with Skia Raster/Software mode) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147349] Opening Writer document in second monitor does not paint the window correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=147349 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de --- Comment #4 from Dieter --- Winfried, is the problem still present in latest version (LO 7.5)? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145677] remote RTF document size reported as 0
https://bugs.documentfoundation.org/show_bug.cgi?id=145677 --- Comment #2 from Dieter --- I'm sorry, but I can't find a way to open it from bwser directly. RTF file is always opened in browser, but not in LO. If I save the file, it has a size of 46,8kB. Perhaps somebody else can help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153399] New: [UI] Vertical scrolling becomes unresponsive when hide columns option is used such that the background is visible
https://bugs.documentfoundation.org/show_bug.cgi?id=153399 Bug ID: 153399 Summary: [UI] Vertical scrolling becomes unresponsive when hide columns option is used such that the background is visible Product: LibreOffice Version: 7.4.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nialbu...@mailbox.org Description: If you select all columns, unselect a few columns, then use the "hide columns" option, everything will be hidden except the columns you select. If you unselect so few columns that you can see the blank background behind the cells, libreoffice calc becomes extremely laggy. This issue ONLY happens if the blank background is either on screen or closely cut off by the edge of the window. Performance remains stable when only a few cells are visible, as long as the edge of the window cuts off the background. This issue is also confined to the specific window where problems are occurring. If there are multiple spreadsheets open in different windows, only the spreadsheet(s) with the background visible will experience lag while the others will not. Steps to Reproduce: 1. Open localc 7.4.4.1 or later 2. Select All 3. Deselect zero or more columns 4. Hide all selected Columns 5. If many columns are not hidden, ensure that some of the background is visible on screen 6. Observe lag when scrolling up or down Actual Results: Lag is observed when scrolling up or down Expected Results: No lag is observed when scrolling up or down Reproducible: Always User Profile Reset: Yes Additional Info: I tested every version on the archives until the bug went away to determine the earliest affected version, which is 7.4.4.1, however only 7.4.4.2 shows up on the version menu. Version 7.4.4.1 took almost an hour to download from the archives while the other versions I checked took only about a minute, so it would be nice to get that fixed as well. I included version info for both 7.4.4.1 and 7.4.4.2. 7.4.4.1 Version Info: Version: 7.4.4.1 (x64) / LibreOffice Community Build ID: 988f4a351a6fa8cf4bdf2bdc873ca12cf8cbe625 CPU threads: 16; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL 7.4.4.2 Version Info: Version: 7.4.4.2 (x64) / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 16; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147558] OptimalWidth cannot be set in starbase lilo for all columns
https://bugs.documentfoundation.org/show_bug.cgi?id=147558 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO URL||https://ask.libreoffice.org ||/t/in-lilo-starbase-how-to- ||apply-optimalwidth-for-writ ||er-tables/74311 Ever confirmed|0 |1 CC||dgp-m...@gmx.de --- Comment #2 from Dieter --- Elias, you've also asked that question in https://ask.libreoffice.org/t/in-lilo-starbase-how-to-apply-optimalwidth-for-writer-tables/74311 and answer of KamilLanda has been accepted. So can we close this bug report? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147230] Ruler is distorted when Skia HW Rendering is enabled (present in LO 7.2 but not in LO 7.3)
https://bugs.documentfoundation.org/show_bug.cgi?id=147230 Dieter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from Dieter --- (In reply to Dieter from comment #9) > O. K. for me, but I'm afraid that nobody will try to fix it for 7.2, if it > works in 7.3. but let's see. Since there is no further development on LO 7.2 and it worked in 7.3 let's close it now. => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108629] [META] Ruler bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108629 Bug 108629 depends on bug 147230, which changed state. Bug 147230 Summary: Ruler is distorted when Skia HW Rendering is enabled (present in LO 7.2 but not in LO 7.3) https://bugs.documentfoundation.org/show_bug.cgi?id=147230 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153398] It does not change the color of the letter
https://bugs.documentfoundation.org/show_bug.cgi?id=153398 Juan José Armero changed: What|Removed |Added CC||jjarm...@gmail.com --- Comment #1 from Juan José Armero --- Created attachment 185137 --> https://bugs.documentfoundation.org/attachment.cgi?id=185137=edit font color (dark red 2) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153398] New: It does not change the color of the letter
https://bugs.documentfoundation.org/show_bug.cgi?id=153398 Bug ID: 153398 Summary: It does not change the color of the letter Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jjarm...@gmail.com Description: I try to change the color of the letter, but it does not respond Steps to Reproduce: 1.Open Writer or Calc 2.write a text 3.Change the color of the text Actual Results: color does not change Expected Results: the color of the letter should be in red. Reproducible: Always User Profile Reset: No Additional Info: Información de la versión Versión: 7.5.03 / LibreOffice Community Montaje: Entorno: Subprocs. CPU: 4; SO: Windows 10.0 Build 19045 Interfaz de usuario: Repres. IU: Skia/rej. píx.; VCL: win Config. regional:es-ES (es_ES); Interfaz: es-ES Otros: Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75080] 3D Chart does not display minor axis tick marks
https://bugs.documentfoundation.org/show_bug.cgi?id=75080 --- Comment #13 from Luke --- Still no minor tick marks displayed in 3D with Version: 7.5.0.0.alpha0+ (x86) Build ID: a35c18aeff3b1d8f270db7e094850fb8ba1ab84a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144459] FILEOPEN: PPTX custom layouts not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=144459 Aron Budea changed: What|Removed |Added Summary|FILEOPEN: PPTX master slide |FILEOPEN: PPTX custom |not imported|layouts not imported Severity|normal |enhancement CC||aron.bu...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147422] Crash in: SfxItemPool::Remove(SfxPoolItem const &)
https://bugs.documentfoundation.org/show_bug.cgi?id=147422 Dieter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INSUFFICIENTDATA --- Comment #6 from Dieter --- (In reply to robert.funnell from comment #5 > > I don't think I can replicate the crash. So let's close it. Feel free to reopen it as UNCONFIRMED, if you can provide steps to reproduce. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85493] VIEWING: In diagrams, tooltips shown over curve points show information about the wrong point when "Range for Name" cell values are not sorted in ascending order
https://bugs.documentfoundation.org/show_bug.cgi?id=85493 --- Comment #21 from Olivier DESCOUT --- I can still reproduce this bug with LibreOffice 7.5 : When the mouse is over a point of the graph, the data information given by the pop-up tip is wrong and does not relate to the right point in the graph, as soon as X-axis-graph data are sorted in any order different from the ascending one. A small Calc sheet, which reproduces the bug, is attached to this bug description. Please find below the detailed LO version information: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147422] Crash in: SfxItemPool::Remove(SfxPoolItem const &)
https://bugs.documentfoundation.org/show_bug.cgi?id=147422 robert.funn...@mcgill.ca changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #5 from robert.funn...@mcgill.ca --- I think I've managed to identify the file that I was working on at the time of the crash a year ago (for the record, draft7_rf.odt) but even at that time I was unable to replicate the crash with the same version of LO (comment 3). For what it's worth, with version 7.3.2.2 I've just now accepted what I think may be the same 2 deletions, attempted an undo (Ctrl-Z) which again had no effect, and then did File > Reload, which worked fine with no crash. (I've just realized that the reason the supposed undo had no effect was that (both a year ago and now) I typed Ctrl-Z when focus was still with the Manage Changes window.) I don't think I can replicate the crash. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146601] Libre Calc does not display cell entries as they are typed
https://bugs.documentfoundation.org/show_bug.cgi?id=146601 Buovjaga 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 153397] Unable to set portrait page style in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153397 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- The Default Page Style is the portrait style. You can use the default + landscape styles to for example alternate automatically between page, or change the page orientation in the Page tab of the same dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147422] Crash in: SfxItemPool::Remove(SfxPoolItem const &)
https://bugs.documentfoundation.org/show_bug.cgi?id=147422 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Dieter --- Robert, a new major relase of LO is available at https://www.libreoffice.org/download/download-libreoffice/ Could you please test, if bug is still present in actual version LO 7.5. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139375] LibreOffice Writer Spell checker F7 not working at all or set wrong language
https://bugs.documentfoundation.org/show_bug.cgi?id=139375 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #19 from Dieter --- (In reply to Dieter from comment #18) > Please press Windows key + G If bug is still present in actal version LO 7.5, please try to provide a screencast. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146148] Severe lags when working on SMB share on cursor movement and saving file
https://bugs.documentfoundation.org/show_bug.cgi?id=146148 --- Comment #2 from Dieter --- Thdeppner, nobody could confirm your report for more than a year. A new major relase of LO is available at https://www.libreoffice.org/download/download-libreoffice/ Could you please test, if bug is still present in actual version LO 7.5. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Dieter changed: What|Removed |Added Depends on||146537 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146537 [Bug 146537] Table row height dropdown icon does not work in maximized window on GNOME Wayland -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146537] Table row height dropdown icon does not work in maximized window on GNOME Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=146537 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Blocks||100156 --- Comment #6 from Dieter --- Jan, a new major relase of LO is available at https://www.libreoffice.org/download/download-libreoffice/ Could you please test, if the bug is still present in actual version LO 7.5. => NEEDINFO Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100156 [Bug 100156] [META] Wayland-related bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153380] Copying/pasting datas from QGIS makes LibreOffice hanging
https://bugs.documentfoundation.org/show_bug.cgi?id=153380 --- Comment #3 from Stéphane Guillou (stragu) --- Created attachment 185136 --> https://bugs.documentfoundation.org/attachment.cgi?id=185136=edit example QGIS project You can test with one of the "amenity_library" layers in this zipped QGIS project. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153380] Copying/pasting datas from QGIS makes LibreOffice hanging
https://bugs.documentfoundation.org/show_bug.cgi?id=153380 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- I could not reproduce the issue when copying a layer's attribute table (select a layer in QGIS, F6, Ctrl + A, Ctrl + C, paste in Calc or Writer). Tested with QGIS 3.22.15-Białowieża and LO 7.4.5 and a recent master build, on Ubuntu 20.04. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153394] enormous size of special characters in 'insert special characters' in Writer, LO 7.5.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=153394 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Can not confirm on Windows builds, font chart on Special Character dialog is well formed. Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
