[Bug 161178] Inserting text objets over image messes the result on every reopening
https://bugs.documentfoundation.org/show_bug.cgi?id=161178 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE URL|https://alhakim-e.com/detec | |ting-water-leaks-in-dubai/ | --- Comment #3 from Stéphane Guillou (stragu) --- Thanks for the report! Steps: 1. Open attachment 194205 2. Go to the first illustration in chapter 4.2 (page 18) 3. Open Navigator 4. Select the Drawing Object called "Cadre de texte 1" and see that it is behind the picture. 5. "Bring to front" this object (see that it contains the number 3) 6. Select the Drawing Object called "Cadre de texte 3" and see that it is behind the picture. 7. "Bring to front" this object (see that it contains the number 4) 8. Save and reload Result: objects brought to the top are visible, but numbers 1, 2 and 5 (respectively "Cadre de texte 4/5/6" are now hidden behind the picture. Same kind of issue if I "Send to Back" the image instead. Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 1f15d097cace14ca6e44e7652f460aa3fa7bd150 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded The issue is already tracked in bug 72367, marking as duplicate. I haven't been able to reproduce the issue with objects changing locations though, so please feel free to provide precise steps to see that, which we could track in a separate ticket. *** This bug has been marked as a duplicate of bug 72367 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 72367] FILESAVE: Z-Order of picture and text shapes doesn't save (or load) correctly in ODF
https://bugs.documentfoundation.org/show_bug.cgi?id=72367 Stéphane Guillou (stragu) changed: What|Removed |Added CC||philippem...@outlook.com --- Comment #13 from Stéphane Guillou (stragu) --- *** Bug 161178 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161409] apple keynote animations not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161409 --- Comment #4 from johnks --- https://www.youtube.com/@KeynoteClub/videos basically all keynote files available in this youtube channel are not working in impress. i dont think i should upload all the files when the tester can check them on their own -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161409] apple keynote animations not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161409 --- Comment #3 from johnks --- Created attachment 194536 --> https://bugs.documentfoundation.org/attachment.cgi?id=194536=edit 3rd apple keynote file animations not working https://www.youtube.com/watch?v=CMtuXTbmJxE https://drive.google.com/file/d/1ogGCcfcjaINljzRxqx3Go2fpwuFgp9ML/view -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161409] apple keynote animations not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161409 --- Comment #2 from johnks --- Created attachment 194535 --> https://bugs.documentfoundation.org/attachment.cgi?id=194535=edit 2nd keynote file not working https://www.youtube.com/watch?v=T9e6pNKFXWk https://drive.usercontent.google.com/download?id=1xPaZrMnXb4ehvbb18nQY-KFZDQs9tvC9=download -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161409] apple keynote animations not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161409 --- Comment #1 from johnks --- Created attachment 194534 --> https://bugs.documentfoundation.org/attachment.cgi?id=194534=edit keynote file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161409] New: apple keynote animations not working
https://bugs.documentfoundation.org/show_bug.cgi?id=161409 Bug ID: 161409 Summary: apple keynote animations not working Product: LibreOffice Version: 24.2.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: testing1237...@yahoo.com Description: the file is an apple keynote file downloaded from https://drive.usercontent.google.com/download?id=1cFozy01SktNVjaXS6z9Wbv5c3C83iI5Z=download with video explanation on https://www.youtube.com/watch?v=bhPDYrngnOg it should have the same effects in libreoffice as it does on apple keynote and in the video but slide transition is showing as "none" in libreoffice impress. seems like impress doesnt support the transitions Steps to Reproduce: 1. open file 2.compare with video 3. Actual Results: no slide animations/transitions Expected Results: there should be same transitions and animations as in apple keynote and in the video Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161408] apple keynote text box alignment issue
https://bugs.documentfoundation.org/show_bug.cgi?id=161408 --- Comment #1 from johnks --- Created attachment 194533 --> https://bugs.documentfoundation.org/attachment.cgi?id=194533=edit apple keynote presentation aligment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161408] New: apple keynote text box alignment issue
https://bugs.documentfoundation.org/show_bug.cgi?id=161408 Bug ID: 161408 Summary: apple keynote text box alignment issue Product: LibreOffice Version: 24.2.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: testing1237...@yahoo.com Description: apple keynote downloaded from https://drive.usercontent.google.com/download?id=1cFozy01SktNVjaXS6z9Wbv5c3C83iI5Z=download with video from https://www.youtube.com/watch?v=bhPDYrngnOg the file should work as in the video but there are lots of text box issues. formatting and the alignment is not correct in almost all slides Steps to Reproduce: 1. open file 2. compare with video on youtube 3. Actual Results: textboxes are out of alignment and it file is not usable as it is Expected Results: file should open as it does in the video Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161407] New: Build LO publish version failed on MacOS M2 pro
https://bugs.documentfoundation.org/show_bug.cgi?id=161407 Bug ID: 161407 Summary: Build LO publish version failed on MacOS M2 pro Product: LibreOffice Version: 24.8.0.0 alpha1+ Master Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xin3li...@qq.com Created attachment 194532 --> https://bugs.documentfoundation.org/attachment.cgi?id=194532=edit Build log Follow the building guide: https://wiki.documentfoundation.org/Development/lode when run `make check` everything is ok. It can build and run the app successfully. But when building a MacOS publish version it failed. ``` core % cat distro-configs/LibreOfficeVanillaMacAppStore.conf >> autogen.input core % cat autogen.input --enable-debug --disable-ext-numbertext --disable-firebird-sdbc --disable-lotuswordpro --disable-lpsolve --disable-odk --disable-online-update --disable-pdfimport --disable-postgresql-sdbc --enable-extension-integration --enable-macosx-sandbox --enable-mpl-subset --enable-readonly-installset --enable-release-build --enable-symbols --with-help --with-myspell-dicts --with-theme=sukapura --with-vendor=Collabora --without-java --without-package-format ./autogen.sh make check 2>&1 | tee build.log make -j 12 -rs -f /Users/liuxl/work/lode/dev/core/Makefile.gbuild unitcheck slowcheck subsequentcheck check ... file:///Users/liuxl/work/lode/dev/core//sw/qa/extras/htmlexport/data//xhtml-css.odt: (anonymous namespace)::testXHTMLUseCSS::TestBody finished in: 472ms /Users/liuxl/work/lode/dev/core/sw/qa/extras/htmlexport/htmlexport.cxx:3039: Assertion Test name: (anonymous namespace)::testReqIF_ExportFormulasAsPDF::TestBody equality assertion failed - Expected: pdf_Portable_Document_Format - Actual : generic_Text Failures !!! Run: 106 Failure total: 1 Failures: 1 Errors: 0 warn:vcl.schedule.deinit:84372:7077855:vcl/source/app/scheduler.cxx:176: DeInit task: Timer a: 1 p: 1 drawinglayer ImpTimedRefDev destroy mpVirDev 18ms (0x66782be0) warn:vcl.schedule.deinit:84372:7077855:vcl/source/app/scheduler.cxx:176: DeInit task: Timer a: 1 p: 1 MemoryManager::MemoryManager maSwapOutTimer 1000ms (0x10ccdc3d8) warn:vcl.schedule.deinit:84372:7077855:vcl/source/app/scheduler.cxx:176: DeInit task: Timer a: 1 p: 1 sc ScModule IdleTimer 150ms (0x12cd79340) (ignored) warn:vcl.schedule.deinit:84372:7077855:vcl/source/app/scheduler.cxx:197: DeInit active tasks: 3 (ignored: 1) Error: a unit test failed, please do one of: make CppunitTest_sw_htmlexport CPPUNITTRACE="lldb --" # for interactive debugging on macOS make CppunitTest_sw_htmlexport VALGRIND=memcheck# for memory checking You can limit the execution to just one particular test by: make CppunitTest_sw_htmlexport CPPUNIT_TEST_NAME="testXYZ" ...above mentioned params... make[1]: *** [/Users/liuxl/work/lode/dev/core/solenv/gbuild/CppunitTest.mk:130: /Users/liuxl/work/lode/dev/core/workdir/CppunitTest/sw_htmlexport.test] Error 1 make[1]: *** Waiting for unfinished jobs ``` -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108728] [META] Dictionaries bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108728 Shantanu changed: What|Removed |Added Depends on||98627 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98627 [Bug 98627] Spell check options on right click shows junk characters -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98627] Spell check options on right click shows junk characters
https://bugs.documentfoundation.org/show_bug.cgi?id=98627 Shantanu changed: What|Removed |Added Blocks||108728 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108728 [Bug 108728] [META] Dictionaries bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161406] New: Crash in: basegfx::BGradient::operator=(basegfx::BGradient const &)
https://bugs.documentfoundation.org/show_bug.cgi?id=161406 Bug ID: 161406 Summary: Crash in: basegfx::BGradient::operator=(basegfx::BGradient const &) Product: LibreOffice Version: 24.2.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: chr_k...@web.de This bug was filed from the crash reporting server and is br-fb08aeff-5525-47fe-b509-f9a81f2badb2. = 1.) Open an empty Impress document (ignore templates) 2.) Choose slide background: color gradient 3.) Direct crash of LibreOffice. There is no crash if you choose without background, a single color, pattern, hatching or a picture. Expected behaviour: Some sort of color picker to choose the gradiant of the background in the slide. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161397] Issues with copy & pasting Arabic/Persian text with colored characters
https://bugs.documentfoundation.org/show_bug.cgi?id=161397 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161161] Incorrect positioning of unprintable characters with different style
https://bugs.documentfoundation.org/show_bug.cgi?id=161161 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161384] Insert Rows Above duplicates formatting of next row above
https://bugs.documentfoundation.org/show_bug.cgi?id=161384 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161182] Advanced search and replace not finding direct formatted words
https://bugs.documentfoundation.org/show_bug.cgi?id=161182 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158074] Writer crash if type F4 on an image
https://bugs.documentfoundation.org/show_bug.cgi?id=158074 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161384] Insert Rows Above duplicates formatting of next row above
https://bugs.documentfoundation.org/show_bug.cgi?id=161384 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.
[Bug 158074] Writer crash if type F4 on an image
https://bugs.documentfoundation.org/show_bug.cgi?id=158074 --- Comment #4 from QA Administrators --- Dear Thorsten, 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.
[Bug 158070] Adding the link in LibreOffice writer it shows the error
https://bugs.documentfoundation.org/show_bug.cgi?id=158070 --- Comment #3 from QA Administrators --- Dear Lakshmi, 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.
[Bug 158070] Adding the link in LibreOffice writer it shows the error
https://bugs.documentfoundation.org/show_bug.cgi?id=158070 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 135869, which changed state. Bug 135869 Summary: Anchor a chart behaves differently/wonky compared to an image https://bugs.documentfoundation.org/show_bug.cgi?id=135869 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135869] Anchor a chart behaves differently/wonky compared to an image
https://bugs.documentfoundation.org/show_bug.cgi?id=135869 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135869] Anchor a chart behaves differently/wonky compared to an image
https://bugs.documentfoundation.org/show_bug.cgi?id=135869 --- Comment #11 from QA Administrators --- Dear Telesto, 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.
[Bug 158528] EDITING, TABLE Writer crashes in a document with large images
https://bugs.documentfoundation.org/show_bug.cgi?id=158528 --- Comment #3 from QA Administrators --- Dear Luke, 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.
[Bug 158507] Impress FILEOPEN: Write Error. The file could not be written (while opening ODP file)
https://bugs.documentfoundation.org/show_bug.cgi?id=158507 --- Comment #7 from QA Administrators --- Dear Dario, 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.
[Bug 144801] Miss some data when I import calc files from GDrive
https://bugs.documentfoundation.org/show_bug.cgi?id=144801 --- Comment #4 from QA Administrators --- Dear pedroivanc, 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.
[Bug 158308] EDITING - CTRL-Shift-; didn't work at first and now overwrites existing format
https://bugs.documentfoundation.org/show_bug.cgi?id=158308 --- Comment #3 from QA Administrators --- Dear alex 070, 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.
[Bug 51672] FILEOPEN XLS Issues with wordart gradients and shadow
https://bugs.documentfoundation.org/show_bug.cgi?id=51672 --- Comment #10 from QA Administrators --- Dear Valek Filippov, 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.
[Bug 56541] Spreadsheet created in MS Excel 2010 does not translate VB script correctly in Spreadsheet program
https://bugs.documentfoundation.org/show_bug.cgi?id=56541 --- Comment #9 from QA Administrators --- Dear D. Charlie Curcija, 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.
[Bug 94216] Unable to Install x86 5.0.1.2 on x86-64 W10: Error 1303
https://bugs.documentfoundation.org/show_bug.cgi?id=94216 --- Comment #40 from QA Administrators --- Dear Robertjm, 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.
[Bug 158458] FILESAVE : after closing the file it contains unrecognizable garbage
https://bugs.documentfoundation.org/show_bug.cgi?id=158458 --- Comment #6 from QA Administrators --- Dear Matthias Mittelstein, 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.
[Bug 62163] [WMF] FILEOPEN: Formulas incorrectly displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=62163 --- Comment #11 from QA Administrators --- Dear dmitriy566, 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.
[Bug 149434] MySQL/MariaDB: Database name with dot will be split at first dot, rest will added to table names
https://bugs.documentfoundation.org/show_bug.cgi?id=149434 --- Comment #21 from QA Administrators --- Dear Shlomo belleli, 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.
[Bug 148415] More detailed, better explained loplugin errors
https://bugs.documentfoundation.org/show_bug.cgi?id=148415 --- Comment #2 from QA Administrators --- Dear Gabor Kelemen (allotropia), 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.
[Bug 148252] (LO Calc) Background Colours Malfunction = when an image is sent to background, while Value Highlighting is active
https://bugs.documentfoundation.org/show_bug.cgi?id=148252 --- Comment #5 from QA Administrators --- Dear David Smith, 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.
[Bug 132900] 2 seconds delay when opening customize dialog the first time (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=132900 --- Comment #28 from QA Administrators --- Dear Dieter, 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.
[Bug 131414] FILESAVE PPT: video insertion in slideshow (Comment 20)
https://bugs.documentfoundation.org/show_bug.cgi?id=131414 --- Comment #21 from QA Administrators --- Dear bachibouzouc, 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.
[Bug 120978] dxf file missing text
https://bugs.documentfoundation.org/show_bug.cgi?id=120978 --- Comment #9 from QA Administrators --- Dear david chen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 121792] Main table inherits table style of the inserted embedded table
https://bugs.documentfoundation.org/show_bug.cgi?id=121792 --- Comment #7 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.
[Bug 114390] Enter can't be assigned to insert a manual row break
https://bugs.documentfoundation.org/show_bug.cgi?id=114390 --- Comment #9 from QA Administrators --- Dear Sophie Freud, 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.
[Bug 109526] FILEOPEN: ODT: Glitches displayed on first time at import time
https://bugs.documentfoundation.org/show_bug.cgi?id=109526 --- 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.
[Bug 107002] EDITING: Selecting multiple slide transitions in a row will rendered all transitions sequentially
https://bugs.documentfoundation.org/show_bug.cgi?id=107002 --- 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.
[Bug 108728] [META] Dictionaries bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108728 Bug 108728 depends on bug 151914, which changed state. Bug 151914 Summary: Allow to add / edit words with tags in custom dictionaries https://bugs.documentfoundation.org/show_bug.cgi?id=151914 What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 96000] [META] Spelling checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=96000 Bug 96000 depends on bug 151914, which changed state. Bug 151914 Summary: Allow to add / edit words with tags in custom dictionaries https://bugs.documentfoundation.org/show_bug.cgi?id=151914 What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151914] Allow to add / edit words with tags in custom dictionaries
https://bugs.documentfoundation.org/show_bug.cgi?id=151914 Shantanu changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|REOPENED --- Comment #8 from Shantanu --- >> "crowdfund" is the new word (missing from the American English dictionary), >> and "fund" is the model word in the new "Grammar By" field. This enhancement request suggest that please allow crowdfund/xy (assuming the original dict file has an entry like fund/xy) Using hunspell tags directly in custom dict is very useful option for power-users. They do not need to guess the matching entry. If no tags are used then the user is free to use "Grammar By" option. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161405] New: ScriptForge's RunApplication functions cannot be opened if the filename contains CJK
https://bugs.documentfoundation.org/show_bug.cgi?id=161405
Bug ID: 161405
Summary: ScriptForge's RunApplication functions cannot be
opened if the filename contains CJK
Product: LibreOffice
Version: 24.8.0.0 alpha1+ Master
Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: BASIC
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: tac...@hotmail.co.jp
Description:
ScriptForge's RunApplication functions cannot be opened if the filename
contains CJK.
Steps to Reproduce:
1. open new calc and save as "D:\表.ods"
2. execute basic macro
Sub OpenFile_hyou_jp
GlobalScope.BasicLibraries.LoadLibrary("ScriptForge")
Dim session As Variant
session = CreateScriptService("Session")
session.RunApplication("D:\表.ods")
End Sub
Actual Results:
3. Error
The following script will also fail.
session.RunApplication(ConvertToURL("D:\表.ods"))
Expected Results:
3. Open "D:\表.ods".
Reproducible: Always
User Profile Reset: No
Additional Info:
The script below works.
Sub OpenFile_hyou_jp_Shell
Shell("soffice.exe", 1, "D:\表.ods")
End Sub
Reproducible with
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: f4ef5435df5560e6b6b061ce4053c71e2819bf51
CPU threads: 4; OS: Windows 10.0 Build 10240; UI render: Skia/Raster; VCL: win
Locale: ja-JP (ja_JP); UI: ja-JP
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 161339] UI freeze when saving
https://bugs.documentfoundation.org/show_bug.cgi?id=161339 Tracey C changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #3 from Tracey C --- I am experiencing this same bug with Libre Office 24.2.2.2. I'm happy to provide any information that might help the developers fix this. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: kf6 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I was only able to reproduce this on Plasma 6, not the Budgie desktop environment (on Linux). When launching from command line, I see this output after the freeze: ❯ libreoffice --calc qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) kf.kio.filewidgets.kfilefiltercombo: Could not find file filter QAbstractAnimation::pause: Cannot pause a stopped animation System information Operating System: Solus 4.5 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-292.current (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161404] Background is sometimes saved sometimes not saved with exporting from Draw as PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=161404 --- Comment #3 from DrC --- Created attachment 194531 --> https://bugs.documentfoundation.org/attachment.cgi?id=194531=edit this one turned out without a backfround I tried w/ and w/o transparency and got the same output -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161404] Background is sometimes saved sometimes not saved with exporting from Draw as PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=161404 --- Comment #2 from DrC --- Created attachment 194530 --> https://bugs.documentfoundation.org/attachment.cgi?id=194530=edit this one turned out the way I expected -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161404] Background is sometimes saved sometimes not saved with exporting from Draw as PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=161404 --- Comment #1 from DrC --- Created attachment 194529 --> https://bugs.documentfoundation.org/attachment.cgi?id=194529=edit source file (draw file) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161404] New: Background is sometimes saved sometimes not saved with exporting from Draw as PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=161404 Bug ID: 161404 Summary: Background is sometimes saved sometimes not saved with exporting from Draw as PNG Product: LibreOffice Version: 24.2.3.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kevin.coo...@gmail.com Description: I exported a very simple diagram as PNG. my artistic efforts were limited to giving a 0.5" x 1" page a blue background and a text box with three characters. When I export it as a PNG (default settings except I changed the DPI to 300). I change one character, re-export it with the same settings and now it has no background (which is problem since the characters are white...makes it really hard to see). It seemed like switching off the save transparency fixed the problem--but the next time I went to save something (granted I had chanced a whole two characters this time!) it did not matter whether it was selected or not (there is no transparency in the background color, BTW). So, a bit perplexed why sometimes it saves the page background color when it exports to PNG and otherwise doesn't bother. Steps to Reproduce: 1. Export -> PNG -> works 2. Export -> PNG -> does not work 3. Export -> PNG -> maybe works Actual Results: No background /transparent. Expected Results: My background color Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.9; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155251] Relative size of image changes when opening image properties & pressing OK without touching anything
https://bugs.documentfoundation.org/show_bug.cgi?id=155251 Stéphane Guillou (stragu) changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #7 from Stéphane Guillou (stragu) --- Verified in: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 1f15d097cace14ca6e44e7652f460aa3fa7bd150 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded No change in size, but still an "Apply attributes" undo step - which I feel is pretty standard in many dialogs when clicking OK without changing anything. Not the focus here anyway. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159746] MacMini M2Pro (Mac OS Sonoma 14.3.1) HUNG while editing a .docx document using LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159746 Patrick Luby (volunteer) changed: What|Removed |Added CC||guibomac...@gmail.com --- Comment #12 from Patrick Luby (volunteer) --- (In reply to Alex Thurgood from comment #9) > The Apple dump file you provided shows a sigtramp being generated: > > 11 -[AquaA11yWrapper accessibilityAttributeNames] + 272 > (libvclplug_osxlo.dylib + 290612) [0x100aeef34] > 11 SwAccessibleGraphic::getAccessibleRole() + 60 (libswlo.dylib + 87324) > [0x3b91d951c] > 11 _sigtramp + 56 (libsystem_platform.dylib + 14884) [0x186bc1a24] > 11 (anonymous namespace)::signalHandlerFunction(int, __siginfo*, void*) + > 152 (libuno_sal.dylib.3 + 213896) [0x100e14388] > 11 callSignalHandler(oslSignalInfo*) + 40 (libuno_sal.dylib.3 + 33280) > [0x100de8200] > 11 VCLExceptionSignal_impl(void*, oslSignalInfo*) + 340 (libvcllo.dylib + > 4077336) [0x1058df718] > > related to the accessibility code, but this might be a red herring. I cannot reproduce this bug with my local build, but the above snippet of dump file looks like LibreOffice's macOS accessibility code is trying to query a LibreOffice object that has already been deleted. I recently committed a fix for a similar "macOS querying deleted LibreOffice objects" bug while working on tdf#158914. That fix will be in the upcoming LibreOffice 24.2.4 release (expected release is within the next week). When LibreOffice 24.2.4 is released, can you see if the bug still exists in that version? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||161150 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161150 [Bug 161150] Rename "phonetic reading" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||161150 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161150 [Bug 161150] Rename "phonetic reading" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161150] Rename "phonetic reading"
https://bugs.documentfoundation.org/show_bug.cgi?id=161150 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||83066, 89606 CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Looks like it's mostly used for the Index Entry dialog. See: * source: https://opengrok.libreoffice.org/search?project=core=%22phonetic+reading%22===1=full=full * help page: https://help.libreoffice.org/latest/en-US/text/swriter/01/04120100.html >From help page: > # Phonetic reading > Enter the phonetic reading for the corresponding entry. For example, if a > Japanese Kanji word has more than one pronunciation, enter the correct > pronunciation as a Katakana word. The Kanji word is then sorted according to > the phonetic reading entry. This option is only available if Asian language > support is enabled. To see it in the UI: 1. Tools > Options > Languages and Locales > Default languages for documents > Asian (ticked) 2. Insert > Table of Contents and Index > Index Entry I see how some might want to make the wording more consistent with the Asian Phonetic Guide feature, but my understanding is that Rubi characters refer to text annotations and their placement along text, whereas the Index dialog only refers to prononciation for sorting. So maybe the wording needs to remain distinct. (In reply to Tuomas Hietala from comment #0) > In LO, it appears to be related to the readings of Japanese kanji. In > English, the readings of kanji are called just "readings", though: > https://en.wikipedia.org/wiki/Kanji#Readings > I suggest that "phonetic reading" should be changed to "reading", unless it > for some reason refers to e.g. on'yomi specifically (as opposed to > kun'yomi), in which case it would be better to change it to "on'yomi". I'm wondering if it should be kept generic, e.g. using the term "pronunciation", as users might use the feature for other languages than Japanese. (I have no first-hand knowledge of CJK languages so would refer to the language communities here.) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83066 [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues https://bugs.documentfoundation.org/show_bug.cgi?id=89606 [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108456] [META] Style modify dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108456 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||161388 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161388 [Bug 161388] Rename 'Organizer' to 'General' in style dialogs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161402] [LOCALHELP] Rename 'Organizer' to 'General' in style dialogs Help pages
https://bugs.documentfoundation.org/show_bug.cgi?id=161402 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||1388 Status|UNCONFIRMED |NEW --- Comment #1 from Stéphane Guillou (stragu) --- Since bug 161388 and 797e879990f9db3373197a5a83639ad5aebba8c8. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161398] auto-filter very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=161398 --- Comment #3 from ady --- I can reproduce the problem on MS Windows too with recent LO 24.8 alpha. Anything I do with attachment 194528 is slow. Even opening the file is so slow that Calc does not respond for several seconds (i.e. it temporarily hangs). After testing several features, I found out that: 1. removing the second worksheet, named "lookup", 2. then save the file, close and reopen it, ...anything that was slow before is now much, much faster. I am not saying that other factors are not relevant, but the factor that impacted more was removing the second worksheet. So, maybe the formula on the "lookup" worksheet is what makes everything slow, and not the AutoFilter in particular. If others can confirm the behavior I am describing, then the Summary field should be changed from the current "auto-filter very slow" into something more relevant to what actually makes attachment 194528 so slow (up to temporal hanging) in Calc. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161398] auto-filter very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=161398 --- Comment #2 from Pierre Fortin --- Created attachment 194528 --> https://bugs.documentfoundation.org/attachment.cgi?id=194528=edit spreadsheet which has issue Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 1f15d097cace14ca6e44e7652f460aa3fa7bd150 CPU threads: 20; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161394] The buttons on some spreadsheets with embedded images go to a solid colour obscuring the button's text.
https://bugs.documentfoundation.org/show_bug.cgi?id=161394 --- Comment #3 from Michael --- I just realized one other thing. If the Sacramento spreadsheet is saved with "good buttons", it is about 13 M in size. When the spreadsheet is opened, the buttons will be opaque. If the spreadsheet is then saved, the size of the spreadsheet will be twice as large. The image files are about 13 M in size. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151878] LibreCalc buttons change color, horizontal lines from the top and bottoms of buttons radiate across a background image and buttons briefly appear and disappear in the wrong place.
https://bugs.documentfoundation.org/show_bug.cgi?id=151878 --- Comment #19 from Michael --- (In reply to Michael from comment #18) > I just realized one other thing. If the Sacramento spreadsheet is saved with > "good buttons", it is about 13 M in size. When the spreadsheet is opened, > the buttons will be opaque. If the spreadsheet is then saved, the size of > the spreadsheet will be twice as large. The image files are about 13 M in > size. Sorry, wrong bug. Bad eyes on y part. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151878] LibreCalc buttons change color, horizontal lines from the top and bottoms of buttons radiate across a background image and buttons briefly appear and disappear in the wrong place.
https://bugs.documentfoundation.org/show_bug.cgi?id=151878 --- Comment #18 from Michael --- I just realized one other thing. If the Sacramento spreadsheet is saved with "good buttons", it is about 13 M in size. When the spreadsheet is opened, the buttons will be opaque. If the spreadsheet is then saved, the size of the spreadsheet will be twice as large. The image files are about 13 M in size. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161403] LibreOffice writer fails in calculations inside table cells when the origin cells are spanned between pages
https://bugs.documentfoundation.org/show_bug.cgi?id=161403 --- Comment #4 from acastan --- Created attachment 194527 --> https://bugs.documentfoundation.org/attachment.cgi?id=194527=edit file with a table . The cells to add are spanned in two pages. The formula at left cell add all 10 cells at right. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161384] Insert Rows Above duplicates formatting of next row above
https://bugs.documentfoundation.org/show_bug.cgi?id=161384 --- Comment #2 from s...@neonspecter.com --- This occurs with 24.2.3.2 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157449] add to dictionary -- not like "word" but "word*" wild char...
https://bugs.documentfoundation.org/show_bug.cgi?id=157449 --- Comment #2 from László Németh --- Since LibreOffice 6.0, it's possible to specify a dictionary word for every custom word to allow affixation and compound word support: https://wiki.documentfoundation.org/ReleaseNotes/6.0/id#%E2%80%9CGrammar_By%E2%80%9D_spell_checking Screencast: https://www.youtube.com/watch?v=EsS3gaBTfOo (In Hungarian: http://libreoffice.hu/innovacio-a-libreoffice-6-0-ban/) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 96000] [META] Spelling checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=96000 Bug 96000 depends on bug 151914, which changed state. Bug 151914 Summary: Allow to add / edit words with tags in custom dictionaries https://bugs.documentfoundation.org/show_bug.cgi?id=151914 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151914] Allow to add / edit words with tags in custom dictionaries
https://bugs.documentfoundation.org/show_bug.cgi?id=151914 László Németh changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG Keywords|needsDevEval| --- Comment #7 from László Németh --- Since LibreOffice 6.0, it's possible to specify a dictionary word for every custom word to allow affixation and compound word support: https://wiki.documentfoundation.org/ReleaseNotes/6.0/id#%E2%80%9CGrammar_By%E2%80%9D_spell_checking Screencast: https://www.youtube.com/watch?v=EsS3gaBTfOo -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108728] [META] Dictionaries bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108728 Bug 108728 depends on bug 151914, which changed state. Bug 151914 Summary: Allow to add / edit words with tags in custom dictionaries https://bugs.documentfoundation.org/show_bug.cgi?id=151914 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161403] LibreOffice writer fails in calculations inside table cells when the origin cells are spanned between pages
https://bugs.documentfoundation.org/show_bug.cgi?id=161403 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120883] [META] Hyphenation bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120883 Bug 120883 depends on bug 160518, which changed state. Bug 160518 Summary: DOCX: fix layout of hyphenated text by supporting allowHyphenationAtTrackBottom and useWord2013TrackBottomHyphenation https://bugs.documentfoundation.org/show_bug.cgi?id=160518 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160518] DOCX: fix layout of hyphenated text by supporting allowHyphenationAtTrackBottom and useWord2013TrackBottomHyphenation
https://bugs.documentfoundation.org/show_bug.cgi?id=160518 László Németh changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Assignee|nem...@numbertext.org |libreoffice-b...@lists.free ||desktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160170] FILEOPEN .DOCX: words pulled together, characters overlap in some line of hyphenated paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=160170 László Németh changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |nem...@numbertext.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77388] Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed.
https://bugs.documentfoundation.org/show_bug.cgi?id=77388 --- Comment #17 from László Németh --- Created attachment 194526 --> https://bugs.documentfoundation.org/attachment.cgi?id=194526=edit screenshots: also zero padding resulted missing border before left: missing border because of zero padding (missing left and top borders) and cropping by cell bondary (missing right and bottom borders). right: visible borders after the fix -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77388] Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed.
https://bugs.documentfoundation.org/show_bug.cgi?id=77388 --- Comment #16 from László Németh --- Created attachment 194525 --> https://bugs.documentfoundation.org/attachment.cgi?id=194525=edit screenshot about the problem (missing border), and its resolution -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161399] Support Spilled range reference (# operator) in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=161399 Óvári changed: What|Removed |Added Summary|Support Spilled range |Support Spilled range |operator in Calc|reference (# operator) in ||Calc -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161399] Support Spilled range operator in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=161399 Óvári changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148154] Reordering Conditional Formats in Manage CF dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=148154 --- Comment #6 from barruel --- It is worth noticing that the condition being applied is always the matching condition with an older creation date. This is a nightmare when it comes to manage even an amount as small as 2 o 3 overlapping ranges. I've just found out that editing the conditions for a range or even the range itself doesn't change the creation date of the rule. Because there is no way to debug the priority of the rules, this leads to the weird situation that it becomes easier and faster to delete the whole range than to edit it, which won't change priority because the ranges, even when edited, keep their original creation date and thus the priority remains unchanged. In the current state of the main "Manage conditional formatting" dialog, it is impossible to tell which is the priority with which the ranges (with their set of rules) are being applied. If not a way to change the priorities in such dialog, at least an indication of which range is older and is then taking priority is absolutely needed, because otherwise the is no point in changing the ranges when there are overlapping ranges involved. Even with a couple of up and down buttons to reorder the ranges as proposed above, they would be meaningless if the creation date of the range (which determines its priority) or a number showing the priority is not shown. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161403] LibreOffice writer fails in calculations inside table cells when the origin cells are spanned between pages
https://bugs.documentfoundation.org/show_bug.cgi?id=161403 --- Comment #2 from acastan --- Created attachment 194524 --> https://bugs.documentfoundation.org/attachment.cgi?id=194524=edit The same table. I just added some lines at the start of the page. Now the cells to add are in the same page. The result is fine, 38 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161403] LibreOffice writer fails in calculations inside table cells when the origin cells are spanned between pages
https://bugs.documentfoundation.org/show_bug.cgi?id=161403 --- Comment #1 from acastan --- Created attachment 194523 --> https://bugs.documentfoundation.org/attachment.cgi?id=194523=edit The cells to add are spanned in two pages. The result should be 38 but only adds 16 (the cells tha remains in first page) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160844] Ctrl+F6 does not switch to (bring the focus back to) the document
https://bugs.documentfoundation.org/show_bug.cgi?id=160844 Caolán McNamara changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |caolan.mcnamara@collabora.c |desktop.org |om Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161403] New: LibreOffice writer fails in calculations inside table cells when the origin cells are spanned between pages
https://bugs.documentfoundation.org/show_bug.cgi?id=161403 Bug ID: 161403 Summary: LibreOffice writer fails in calculations inside table cells when the origin cells are spanned between pages Product: LibreOffice Version: 24.2.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: a...@probeta.net Description: Excuse my poor English LibreOffice writer fails in calculations inside table cells when the origin cells are spanned between pages. The bug is easily reproducible: Look this two screenshots. Look the marked cells. The cell in the left column is a formula adding the the nine cells at right column. In the first screenshot, all the cells are in the same page and the calculations is fine. In the second screenshot I had to move the table few lines down and now the cells used for the calculation are spanned in two pages, As you can see, now the formula for a strange reason is adding only the cells in the firs page. This is unexpected behavior Steps to Reproduce: 1.Create a table with two columns and many rows, Merge the cells of the left column. 2. Write numbers in the right cells. Add a Table formula in the left cell adding all the right cells. 3. The result is fine, but if you move the table down in the way that some rows are in firs page and some rows are in second page, the formula only adds the rows in one page Actual Results: If the table rows to add are spanned in two pages, it only add the rows of one page Expected Results: If the table rows to add are spanned in two pages, still should add all the rows of the formula Reproducible: Always User Profile Reset: Yes Additional Info: LibreOffice 24.2.3.2 3 june 2024 Linux Debian Testing amd64 I can send you screenshots where you see clearly the bug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160836] unable to resize table row height with mouse, if contains an image which cropped by the fixed row height
https://bugs.documentfoundation.org/show_bug.cgi?id=160836 --- Comment #6 from László Németh --- This fixes also the missing (hovered) cell border of https://bugs.documentfoundation.org/attachment.cgi?id=193871 (tdf#160836 test document). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160836] unable to resize table row height with mouse, if contains an image which cropped by the fixed row height
https://bugs.documentfoundation.org/show_bug.cgi?id=160836 László Németh changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=77 ||388 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103302] [META] Writer's web layout/view bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103302 Bug 103302 depends on bug 77388, which changed state. Bug 77388 Summary: Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed. https://bugs.documentfoundation.org/show_bug.cgi?id=77388 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Bug 103152 depends on bug 77388, which changed state. Bug 77388 Summary: Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed. https://bugs.documentfoundation.org/show_bug.cgi?id=77388 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77388] Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed.
https://bugs.documentfoundation.org/show_bug.cgi?id=77388 László Németh changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0836 Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77388] Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed.
https://bugs.documentfoundation.org/show_bug.cgi?id=77388 --- Comment #15 from László Németh --- Commit description: tdf#77388 sw: fix missing table border at cropped images At images cropped by the bottom or right cell boundaries, or at images with zero padding in table cells (e.g, in test document of tdf#160836), table borders were hovered by the image, resulting missing table borders. First paint the cell content, and after that the DOCX-like "collapsing" cell borders in SwTabFrame::PaintSwFrame. Note: this doesn't modify painting of the objects anchored to characters (which still hovers the cell borders), and painting of the text content of the cells (which are still hovered by the cell borders at zero padding, despite their non-transparent background color). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77388] Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed.
https://bugs.documentfoundation.org/show_bug.cgi?id=77388 --- Comment #14 from Commit Notification --- László Németh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/03aa8a1d9bfe4af2f37df0bde42193c2cf90ffb4 tdf#77388 sw: fix missing table border at cropped images It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77388] Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed.
https://bugs.documentfoundation.org/show_bug.cgi?id=77388 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Bug 103152 depends on bug 155251, which changed state. Bug 155251 Summary: Relative size of image changes when opening image properties & pressing OK without touching anything https://bugs.documentfoundation.org/show_bug.cgi?id=155251 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155251] Relative size of image changes when opening image properties & pressing OK without touching anything
https://bugs.documentfoundation.org/show_bug.cgi?id=155251 Caolán McNamara changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Caolán McNamara --- This seems to be fixed now since: commit a3150fc8a59662ce8630cfc64fec9cd083ac7d36 (HEAD) Author: Miklos Vajna Date: Fri May 24 12:06:55 2024 +0200 tdf#145972 sw image dialog: fix bad rel width w/ pt units and kept aspect ratio -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161255] Expand heuristic for enabling RTL-CTL and/or CJK language support when installing/creating new profile
https://bugs.documentfoundation.org/show_bug.cgi?id=161255 Eyal Rozenberg changed: What|Removed |Added Summary|Heuristically enable|Expand heuristic for |RTL-CTL and/or CJK language |enabling RTL-CTL and/or CJK |support when installing |language support when ||installing/creating new ||profile --- Comment #12 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #9) > I further said explicitly, that it is *expected* > that this locale setting is *set* automatically according to the OS settings > (whichever algorithm there is). Ok, so that's what I misunderstood. Anyway, I'm not even sure that makes sense. I mean, if I download a localized version from the libreoffice.org website, shouldn't that locale trump whatever LO determines as the OS locale? Regardless of what locale is set, there's the > I even wrote explicitly, that *if* it doesn't work for a *specific* OS, or a > specific locale, then that is a bug TBH I don't know whether it _ever_ works, as I always get Hindi CTL locale for some reason, and assumed that's some hard-coded default. Guess I'll go file that bug. Anyway, limiting the bug's scope to reflect what you've said. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161399] Support Spilled range operator in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=161399 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- +1, If it is affordable, it is promising. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161398] auto-filter very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=161398 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please attach the sample file here, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161397] Issues with copy & pasting Arabic/Persian text with colored characters
https://bugs.documentfoundation.org/show_bug.cgi?id=161397 Eyal Rozenberg changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120543] [META] Bugs and enhancements around hyperlinks in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=120543 BogdanB changed: What|Removed |Added Depends on||161329 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=161329 [Bug 161329] If you copy a shape the hyperlink property is not copied -- You are receiving this mail because: You are the assignee for the bug.
[Bug 161329] If you copy a shape the hyperlink property is not copied
https://bugs.documentfoundation.org/show_bug.cgi?id=161329 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Summary|If you copy a shape the |If you copy a shape the |hyperlink property is not |hyperlink property is not |copied. |copied Blocks||120543 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120543 [Bug 120543] [META] Bugs and enhancements around hyperlinks in Calc -- You are receiving this mail because: You are the assignee for the bug.
