[Libreoffice-bugs] [Bug 156623] - Android Viewer can't open any office files and crashed
https://bugs.documentfoundation.org/show_bug.cgi?id=156623 Michael Weghorn changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #36 from Michael Weghorn --- (In reply to eric li from comment #34) > Do you know a way or a branch which can gurantee build and run successfully? The version in F-Droid is built from commit 5c1c768e128d. But to me, the problem you're having so far doesn't look like a problem of the version you're building, but something in your local build setup. (In reply to eric li from comment #33) > I don't know why ..the jniLibs directory should be in the android/source > directory ,,but it is on the upper directory(android/)..even I changed the > path in build.gradle for it,,but it doesn't work .. It shouldn't be necessary to change any paths manually. I'd suggest to first analyse why libraries are not in the APK file and just observe the output of the default build (i.e. what `make` produces, avoiding Android Studio for the moment). What I'd suggest is this: * undo all local modifications * run `make android.clean` * run `make` * run the steps from comment 24 again and report the output here (To have an even cleaner state to start with, a `make distclean` would be even better, but then the build will take longer, let's start with the above first.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127138] GNOME / KDE dark system themes don't automatically enable corresponding dark icon themes
https://bugs.documentfoundation.org/show_bug.cgi?id=127138 Buovjaga changed: What|Removed |Added CC||lordmethe...@outlook.com --- Comment #24 from Buovjaga --- *** Bug 156245 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156245] failure to switch icon themes when system/application switches between light and dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156245 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #2 from Buovjaga --- *** This bug has been marked as a duplicate of bug 127138 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Bug 129661 depends on bug 104318, which changed state. Bug 104318 Summary: CTL, CJK, and Western Language controls in the GUI cause confusion, handling languages and script selection needs rework--comfortable for a "Global" user community https://bugs.documentfoundation.org/show_bug.cgi?id=104318 What|Removed |Added Status|RESOLVED|NEW Resolution|INSUFFICIENTDATA|--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112139] [META] Options dialog's Language settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112139 Bug 112139 depends on bug 104318, which changed state. Bug 104318 Summary: CTL, CJK, and Western Language controls in the GUI cause confusion, handling languages and script selection needs rework--comfortable for a "Global" user community https://bugs.documentfoundation.org/show_bug.cgi?id=104318 What|Removed |Added Status|RESOLVED|NEW Resolution|INSUFFICIENTDATA|--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104318] CTL, CJK, and Western Language controls in the GUI cause confusion, handling languages and script selection needs rework--comfortable for a "Global" user community
https://bugs.documentfoundation.org/show_bug.cgi?id=104318 Buovjaga changed: What|Removed |Added Resolution|INSUFFICIENTDATA|--- Status|RESOLVED|NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106547] [META] OOXML SmartArt bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=106547 Bug 106547 depends on bug 127275, which changed state. Bug 127275 Summary: Wrong text format in PPTX SmartArt after saving in ODP format https://bugs.documentfoundation.org/show_bug.cgi?id=127275 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127275] Wrong text format in PPTX SmartArt after saving in ODP format
https://bugs.documentfoundation.org/show_bug.cgi?id=127275 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9551 Status|NEW |RESOLVED Resolution|--- |FIXED Whiteboard||target:7.5.0 --- Comment #5 from Aron Budea --- This got fixed by the following commit in LO 7.5: https://cgit.freedesktop.org/libreoffice/core/commit/?id=7e23cbdbb6ec0247a29ed8a8f744c01e10963ea0 author Regina Henschel2022-06-25 00:07:43 +0200 committer Miklos Vajna 2022-07-20 08:16:03 +0200 tdf#149551 separate TextRotateAngle from TextPreRotateAngle -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135392] Paste from a non-LOO source into LOO CALC overwrites cells containing data without giving a warning
https://bugs.documentfoundation.org/show_bug.cgi?id=135392 --- Comment #9 from Dale Eltoft --- I began with a Calc spreadsheet having text data in some cells and numbers in others. I opened the Microsoft Notepad app and typed in a string of text on one line and a number on another. I selected the text from Notepad, copied it to the clipboard and pasted it into a Calc cell already containing text. There was no warning. I did the same with the number into a cell with a number and again no warning. I repeated these steps using a Writer document as the source of the clipboard data. There was no warning. Next I selected a Calc cell containing text. Then going to the Input line where the text was also displayed, I selected one word from the sentence and copied it to the clipboard using the keyboard shortcut. Then I clicked the red X to clear the Input Line update. Next I selected another cell containing text and pasted into it. Again no warning. It seems that the warning "You are pasting data into cells that already contain data." only shows up if the data being pasted is copied to the clipboard from one or more whole cells selected from an active Calc spreadsheet. To be clear from my experiments I believe that data pasted into one or more cells already containing data from any source other than whole cells copied from a currently active open Calc sheet does not provide an overlay warning. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156225] High CPU usage in Writer when opening a commented DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=156225 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #5 from Buovjaga --- (In reply to this.ven from comment #2) > I'm unsure about this. As this is my master's thesis and it contains some > personally identifiable information. Is there a way to provide the file only > to the small group of people working on that issue? You could try sanitising it: https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission If the sanitised version still exhibits the problem, you could upload it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156681] The underline line in Writer doesn't match the length of the sentence, even in simple cases.
https://bugs.documentfoundation.org/show_bug.cgi?id=156681 --- Comment #4 from ysui2...@gmail.com --- Can't produce with Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156646] When using fonts other than pure English fonts, the font height appears to be an unintended height
https://bugs.documentfoundation.org/show_bug.cgi?id=156646 ysui2...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #6 from ysui2...@gmail.com --- Not all the fonts other than pure English fonts change the height, but some do produce this error. Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156486] Automatic Spell check faulty after language change
https://bugs.documentfoundation.org/show_bug.cgi?id=156486 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #1 from Aaron --- Thank you for reporting the bug. I can not reproduce the bug in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: sw-TZ (fr_FR); UI: en-US Calc: threaded Could you provide some examples of Swahili text in an attachment? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156290] In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)
https://bugs.documentfoundation.org/show_bug.cgi?id=156290 --- Comment #2 from ysui2...@gmail.com --- can't reproduce with Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156253] Unable to control placement of connecting line between text boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=156253 --- Comment #3 from ysui2...@gmail.com --- Can't produce with Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156245] failure to switch icon themes when system/application switches between light and dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156245 --- Comment #1 from ysui2...@gmail.com --- I tried, and the icons remained unchanged. But they were still clear and easy to be seen. I'm not quite sure if it's a bug. Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156241] Opening Help > About build leads to crash with pre-compiled headers
https://bugs.documentfoundation.org/show_bug.cgi?id=156241 --- Comment #10 from ysui2...@gmail.com --- I can open helpabout, and everything seem normal. Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156225] High CPU usage in Writer when opening a commented DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=156225 --- Comment #4 from ysui2...@gmail.com --- Could you please provide a sample file? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156224] Capitalization doesn't work when sentence ends with a French quotation mark
https://bugs.documentfoundation.org/show_bug.cgi?id=156224 --- Comment #5 from ysui2...@gmail.com --- Can't produce with Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156693] Convert to pdf with page size same as original input image/page size(real desire is from Emf to pdf)
https://bugs.documentfoundation.org/show_bug.cgi?id=156693 --- Comment #7 from SATYA SRINIVAS K --- Created attachment 188893 --> https://bugs.documentfoundation.org/attachment.cgi?id=188893=edit Test_Emf_Exported_From_Libreoffice.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156693] Convert to pdf with page size same as original input image/page size(real desire is from Emf to pdf)
https://bugs.documentfoundation.org/show_bug.cgi?id=156693 --- Comment #6 from SATYA SRINIVAS K --- Created attachment 188892 --> https://bugs.documentfoundation.org/attachment.cgi?id=188892=edit Test_Emf_Converted_From_Adobe.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156693] Convert to pdf with page size same as original input image/page size(real desire is from Emf to pdf)
https://bugs.documentfoundation.org/show_bug.cgi?id=156693 --- Comment #5 from SATYA SRINIVAS K --- Created attachment 188891 --> https://bugs.documentfoundation.org/attachment.cgi?id=188891=edit Test_Emf.emf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156693] Convert to pdf with page size same as original input image/page size(real desire is from Emf to pdf)
https://bugs.documentfoundation.org/show_bug.cgi?id=156693 SATYA SRINIVAS K changed: What|Removed |Added Summary|Convert to pdf with page|Convert to pdf with page |size same as original input |size same as original input |image/page size |image/page size(real desire ||is from Emf to pdf) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156617] EDITING: Spellcheck behaves incorrectly when adding to a user dictionary
https://bugs.documentfoundation.org/show_bug.cgi?id=156617 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #1 from Aaron --- Thank you for reporting the bug. I can not reproduce the bug in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: threaded Steps 4-5 were not reproduced for me. I successfully added "ghijk" to the dictionary with the dialog greying out and the top "Resume" button appearing. Steps 7-10 were also not reproduced for me. I successfully added the error in the third line (lmnop) to the dictionary and only then the dialog "The spell check is complete" appears. However, the behaviour after this is a little unexpected. After I closed the "The spell check is complete" dialog, the word "lmnop" is no longer marked as an error in the document but in the white space area between "Not in Dictionary" and "Suggestions", it's still marked as an error. It's only when I restart the spell check then everything is fine and it shows there are no errors as expected. That seems to be the only incorrect behaviour I've found from my end. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156480] Language items should be clearer
https://bugs.documentfoundation.org/show_bug.cgi?id=156480 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156464] FIREBIRD: AutoValue shows 0 for all new Entries in Query with Alias
https://bugs.documentfoundation.org/show_bug.cgi?id=156464 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156623] - Android Viewer can't open any office files and crashed
https://bugs.documentfoundation.org/show_bug.cgi?id=156623 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156652] Export to pdf expands compressed Images if "Lossless" is chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=156652 --- Comment #14 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117085] [META] Compress image dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=117085 Bug 117085 depends on bug 156652, which changed state. Bug 156652 Summary: Export to pdf expands compressed Images if "Lossless" is chosen https://bugs.documentfoundation.org/show_bug.cgi?id=156652 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156623] - Android Viewer can't open any office files and crashed
https://bugs.documentfoundation.org/show_bug.cgi?id=156623 --- Comment #35 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146533] Some PNG images are inserted somewhat blurry
https://bugs.documentfoundation.org/show_bug.cgi?id=146533 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146533] Some PNG images are inserted somewhat blurry
https://bugs.documentfoundation.org/show_bug.cgi?id=146533 --- Comment #13 from QA Administrators --- Dear jsv, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Bug 129661 depends on bug 104318, which changed state. Bug 104318 Summary: CTL, CJK, and Western Language controls in the GUI cause confusion, handling languages and script selection needs rework--comfortable for a "Global" user community https://bugs.documentfoundation.org/show_bug.cgi?id=104318 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112139] [META] Options dialog's Language settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112139 Bug 112139 depends on bug 104318, which changed state. Bug 104318 Summary: CTL, CJK, and Western Language controls in the GUI cause confusion, handling languages and script selection needs rework--comfortable for a "Global" user community https://bugs.documentfoundation.org/show_bug.cgi?id=104318 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104318] CTL, CJK, and Western Language controls in the GUI cause confusion, handling languages and script selection needs rework--comfortable for a "Global" user community
https://bugs.documentfoundation.org/show_bug.cgi?id=104318 QA Administrators changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104318] CTL, CJK, and Western Language controls in the GUI cause confusion, handling languages and script selection needs rework--comfortable for a "Global" user community
https://bugs.documentfoundation.org/show_bug.cgi?id=104318 --- Comment #33 from QA Administrators --- Dear Toby Anderson, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153473] Program crashes when scrolling using Kensington Slimblade trackball or scrollbars
https://bugs.documentfoundation.org/show_bug.cgi?id=153473 --- Comment #4 from QA Administrators --- Dear Joseph Cardana, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53536] EDITING: Inserting text as centered jumps to another cell position.
https://bugs.documentfoundation.org/show_bug.cgi?id=53536 --- Comment #11 from QA Administrators --- Dear Muthu, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153530] Pivot total columns state not respected
https://bugs.documentfoundation.org/show_bug.cgi?id=153530 --- Comment #2 from QA Administrators --- Dear Marco Colnaghi, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50434] Text and connecting lines disappear when saving docx files
https://bugs.documentfoundation.org/show_bug.cgi?id=50434 --- Comment #26 from QA Administrators --- Dear Arno, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142795] Sized-to-fit object sometimes not resized when text font size changes
https://bugs.documentfoundation.org/show_bug.cgi?id=142795 --- Comment #5 from QA Administrators --- Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125634] Object not rotated, though it's corners visualized as rotated
https://bugs.documentfoundation.org/show_bug.cgi?id=125634 --- Comment #7 from QA Administrators --- Dear opensuse.lietuviu.kalba, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127275] Wrong text format in PPTX SmartArt after saving in ODP format
https://bugs.documentfoundation.org/show_bug.cgi?id=127275 --- Comment #4 from QA Administrators --- Dear Christian, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125514] Black fields within data source view on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=125514 --- Comment #25 from QA Administrators --- Dear Thorsten Wagner, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124611] [sal][MSVC] Wrong global variable initialization order
https://bugs.documentfoundation.org/show_bug.cgi?id=124611 --- Comment #8 from QA Administrators --- Dear Egor Pugin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124699] Configuring with --disable-report-builder causes warnings about registry when LO starts
https://bugs.documentfoundation.org/show_bug.cgi?id=124699 --- Comment #2 from QA Administrators --- Dear Tor Lillqvist, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119534] Hang when zooming in for a document containing tables
https://bugs.documentfoundation.org/show_bug.cgi?id=119534 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118105] An image in PDF imported using LO_IMPORT_USE_PDFIUM has artifacts after breaking
https://bugs.documentfoundation.org/show_bug.cgi?id=118105 --- Comment #5 from QA Administrators --- Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117942] Active/Expanded comment box doesn't adjust position when resizing the main window
https://bugs.documentfoundation.org/show_bug.cgi?id=117942 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112095] LibreOffice Draw grouped shape object is scrambled when .odt is saved as a .docx
https://bugs.documentfoundation.org/show_bug.cgi?id=112095 --- Comment #11 from QA Administrators --- Dear Bob Furber, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115350] Tools > Options > Math should be visible when editing an embedded formula
https://bugs.documentfoundation.org/show_bug.cgi?id=115350 --- Comment #7 from QA Administrators --- Dear Thomas Lendo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105204] [TASK] Check shell scripts with shellcheck
https://bugs.documentfoundation.org/show_bug.cgi?id=105204 --- Comment #25 from QA Administrators --- Dear JoNi, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100414] incorrect usage of "maj" instead of "shift" on Locale: nl-BE (nl_BE).
https://bugs.documentfoundation.org/show_bug.cgi?id=100414 --- Comment #12 from QA Administrators --- Dear Roeland, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156695] [FR] Reorder rows and columns
https://bugs.documentfoundation.org/show_bug.cgi?id=156695 --- Comment #3 from AvidSeeker --- The provided solution works for me. But several people in the discussion were facing problems with this (Especially is Alt key is used a modifier key by the desktop environment). Can the drag-and-drop feature be more intuitive? Take a look on the screencast attached. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156623] - Android Viewer can't open any office files and crashed
https://bugs.documentfoundation.org/show_bug.cgi?id=156623 --- Comment #34 from eric li --- Do you know a way or a branch which can gurantee build and run successfully? I will use git pulll to try ,,you know everytime pull and build will take at least half day ,,,really painfull thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34551] Gradient: Option to "Rotate fill effect with shape" not available
https://bugs.documentfoundation.org/show_bug.cgi?id=34551 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6704 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156704] FILEOPEN PPTX: blocks with color gradients are shaded differently (with same color)
https://bugs.documentfoundation.org/show_bug.cgi?id=156704 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=34 ||551 --- Comment #2 from Regina Henschel --- We have two features here, which are not implemented in LibreOffice and which cannot be expressed in ODF: 1. Rotate background with shape (see also bug 34551) 2. Fill of a group shape. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156334] Switching to another slide should hide the Table toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=156334 --- Comment #4 from Aaron --- (In reply to Stéphane Guillou (stragu) from comment #3) > I can reproduce in 7.5.5.2 on Linux. > Aaron, are you sure you had the cursor inside the table before switching > slides? Yes I'm sure. I clicked in the table, wrote some text then switched to the next slide and the toolbar on the right with properties and table design heading disappears and gets replaced with layouts. Is that the steps to reproduce? Because the video from the attachment 188413 is not working for me. I can't seem to play the video. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156699] Special characters in toolbar group button not read by Orca
https://bugs.documentfoundation.org/show_bug.cgi?id=156699 Stéphane Guillou (stragu) changed: What|Removed |Added OS|Windows (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156705] New: macOS keybindings for Home/End malfunctioning
https://bugs.documentfoundation.org/show_bug.cgi?id=156705 Bug ID: 156705 Summary: macOS keybindings for Home/End malfunctioning Product: LibreOffice Version: 7.5.5.2 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@mcgwiz.com Description: Using macOS 13.5, Home and End do not respect keyboard customizations. On a clean install, going into menu bar Tools > Customize > Keyboard tab, then selecting ↖︎ (Home key) from Shortcut Keys grid, shows To Line Begin as the mapped function. Therefore, it is expected that when the cursor is located in the middle of a multi-line document, pressing Home moves the cursor to the beginning of that line. However what actually happens is the cursor moves to the beginning of the document - regardless of the mapped function. This is holds when manipulating mappings with the LibreOffice radio button selected and when the Writer radio is selected. This is extremely frustrating as it does not follow any text editor conventions on any OS. OpenOffice 4.1.14 also exhibits this buggy behavior. The behavior works as expected on Windows 11 Insider Dev with LibreOffice 7.5.5.2. See discussion on Ask LibreOffice: https://ask.libreoffice.org/t/map-home-and-end-keys-to-beginning-end-of-line-on-macos/51969 Note 1: on most modern Apple hardware, Home is entered with a Fn+Left key chord. Note 2: the behavior works as expected on Windows. Steps to Reproduce: 1. Open a new document. 2. Enter two lines of text. 3. Position cursor at the end of the second line. 4. Press Home. Actual Results: Cursor moves to beginning of first line. Expected Results: Cursor moves to beginning of second line. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 12; OS: Mac OS X 13.5; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156704] FILEOPEN PPTX: blocks with color gradients are shaded differently (with same color)
https://bugs.documentfoundation.org/show_bug.cgi?id=156704 --- Comment #1 from Gerald Pfeifer --- Created attachment 188890 --> https://bugs.documentfoundation.org/attachment.cgi?id=188890=edit Visual comparison Office 365 (left) vs LibreOffice (right) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156704] New: FILEOPEN PPTX: blocks with color gradients are shaded differently (with same color)
https://bugs.documentfoundation.org/show_bug.cgi?id=156704 Bug ID: 156704 Summary: FILEOPEN PPTX: blocks with color gradients are shaded differently (with same color) Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 19 --> https://bugs.documentfoundation.org/attachment.cgi?id=19=edit Sample slide (PPTX) 1. Open sample slide in Impress as well as PowerPoint 2. Compare and see how a. on the right in blocks get darker from top to bottom instead of the other way around; b. how the "Shiva" and "Shakti" blocks do not fit in well. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 47ca3f1f762352b488d58b3bf23d5776576f1cca CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US and all the way back to version 6.4 at least. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156703] FILEOPEN PPTX:video is not cropped into a circle (plays as square instead)
https://bugs.documentfoundation.org/show_bug.cgi?id=156703 --- Comment #1 from Gerald Pfeifer --- Created attachment 18 --> https://bugs.documentfoundation.org/attachment.cgi?id=18=edit Visual comparison Office 365 (left) vs LibreOffice (right) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156703] New: FILEOPEN PPTX:video is not cropped into a circle (plays as square instead)
https://bugs.documentfoundation.org/show_bug.cgi?id=156703 Bug ID: 156703 Summary: FILEOPEN PPTX:video is not cropped into a circle (plays as square instead) Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 17 --> https://bugs.documentfoundation.org/attachment.cgi?id=17=edit Sample slide (PPTX) with two videos 1. Open sample slide. 2. Invoke presentation mode. 3. Observe how instead of two circular videos we play to square videos (and one of them at a different position even). Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 47ca3f1f762352b488d58b3bf23d5776576f1cca CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146619] Remove unused #includes from C/C++ files
https://bugs.documentfoundation.org/show_bug.cgi?id=146619 --- Comment #8 from Commit Notification --- Gabor Kelemen committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/218a7650a5cf03f895bed19c68d6f02daec536e9 tdf#146619 Remove unused includes from sal/ [system.hxx] It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101912] [META] Accessibility (a11y) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101912 Michael Weghorn changed: What|Removed |Added Depends on||156699 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156699 [Bug 156699] Special characters in toolbar group button not read by Orca -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK and GNOME Orca screen reader support
https://bugs.documentfoundation.org/show_bug.cgi?id=36549 Michael Weghorn changed: What|Removed |Added Depends on|156699 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156699 [Bug 156699] Special characters in toolbar group button not read by Orca -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156699] Special characters in toolbar group button not read by Orca
https://bugs.documentfoundation.org/show_bug.cgi?id=156699 Michael Weghorn changed: What|Removed |Added Blocks|36549 |101912 OS|Linux (All) |Windows (All) Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||m.wegh...@posteo.de --- Comment #3 from Michael Weghorn --- I can reproduce on Debian testing with Orca 44.1-2 and LO git master. NVDA 2023.1 on Windows just says "option pane" for any character, which isn't much better. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d1d07992a89ba503f1d457a8f79926063f4d3f9c CPU threads: 12; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d1d07992a89ba503f1d457a8f79926063f4d3f9c CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=36549 [Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK and GNOME Orca screen reader support https://bugs.documentfoundation.org/show_bug.cgi?id=101912 [Bug 101912] [META] Accessibility (a11y) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156687] PNG with alpha, flip and set transparency, shows original image shadow during present
https://bugs.documentfoundation.org/show_bug.cgi?id=156687 --- Comment #6 from m.a.riosv --- Then try to update the driver card from the vendor (AMD, NVIDIA, INTEL, ETC) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142900] FILEOPEN PPTX: circle shape shows solid, lacks stripes
https://bugs.documentfoundation.org/show_bug.cgi?id=142900
--- Comment #5 from Gerald Pfeifer ---
This appears fine and in line with attachment #172955 ("Visual
comparison Office 365 vs LibreOffice 7.2") and attachment #172964
("The shape in PP 2019") as of
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 47ca3f1f762352b488d58b3bf23d5776576f1cca
CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156695] [FR] Reorder rows and columns
https://bugs.documentfoundation.org/show_bug.cgi?id=156695 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Please take a look of the solution in this thread of LibreOffice forum. https://ask.libreoffice.org/t/how-to-move-columns-rows-in-calc/8234/16 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156675] unhelpful appearing message when changing sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=156675 --- Comment #3 from Rafael Lima --- Glad to hear you found a solution to your problem =) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156685] Default font color in tables is white over white background (font color should be black)
https://bugs.documentfoundation.org/show_bug.cgi?id=156685 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9571 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149571] Automatic color doesn't change when object background is dark
https://bugs.documentfoundation.org/show_bug.cgi?id=149571 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6685 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142799] 'Automatic' font color ignores table background color being black
https://bugs.documentfoundation.org/show_bug.cgi?id=142799 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6685 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156685] Default font color in tables is white over white background (font color should be black)
https://bugs.documentfoundation.org/show_bug.cgi?id=156685 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2799 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156685] Default font color in tables is white over white background (font color should be black)
https://bugs.documentfoundation.org/show_bug.cgi?id=156685 --- Comment #4 from Regina Henschel --- Some more findings: SdrObject::setSuitableOutlinerBg creates the value from the background fill of the shape. And because the table object has no own style, the default style is used. That has currently RGB(114,159,207). Then this is used in IsDark() in tools.hxx. But for RGB(114,159,207) the GetLuminance returns 151 and therefore the table is considered as "dark". So the error is not directly the mentioned commit, but the fact that the outliner does not use the actual table cell background but the SdrObject fill color. To test it, create an own new graphic style with an area fill color and assign it to the table. This does not change the table cell background. Now vary the area fill color, e.g. use a gray of 156 or a gray of 157. That error exist already in LO7.5. If the font color is set to automatic and you change the cell background to black or to a dark color, the text does not become white as it should for "automatic". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156699] Special characters in toolbar group button not read by Orca
https://bugs.documentfoundation.org/show_bug.cgi?id=156699 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- Stéphane: I think it might be useful you upgrade Ubuntu to have more recent version of software like Orca. There's also a ppa repo for Orca where you can download more recent Orca versions, see https://launchpad.net/ubuntu/+source/orca -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156209] Font size increases when copying from cell in edit mode and pasting into another in non-edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156209 --- Comment #14 from LeroyG --- (In reply to Buovjaga from comment #7) > I also noticed that if you […] close the file, […] and do > another test, you will not repro. So you have to close LibreOffice > completely to be able to repro again. Only reproducible on the first document, be it new or opened. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117085] [META] Compress image dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=117085 Jérôme changed: What|Removed |Added Depends on||99889 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99889 [Bug 99889] add "use indexed colours" checkbox in the PDF Export option dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99889] add "use indexed colours" checkbox in the PDF Export option dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=99889 Jérôme changed: What|Removed |Added Blocks||117085 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=117085 [Bug 117085] [META] Compress image dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99889] add "use indexed colours" checkbox in the PDF Export option dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=99889 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=99 ||887 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99887] new option for keeping lossless and jpeg original image file format
https://bugs.documentfoundation.org/show_bug.cgi?id=99887 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=99 ||889 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99887] new option for keeping lossless and jpeg original image file format
https://bugs.documentfoundation.org/show_bug.cgi?id=99887 Jérôme changed: What|Removed |Added Blocks||117085 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=117085 [Bug 117085] [META] Compress image dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117085] [META] Compress image dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=117085 Jérôme changed: What|Removed |Added Depends on||99887 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99887 [Bug 99887] new option for keeping lossless and jpeg original image file format -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137267] clipboard error on paste into a cell
https://bugs.documentfoundation.org/show_bug.cgi?id=137267 BogdanB changed: What|Removed |Added Blocks||113079 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113079 [Bug 113079] [META] Unformatted text paste special bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113079] [META] Unformatted text paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113079 BogdanB changed: What|Removed |Added Depends on||137267 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137267 [Bug 137267] clipboard error on paste into a cell -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102593 BogdanB changed: What|Removed |Added Depends on||135531 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135531 [Bug 135531] Pasted highlighted if the last content character is highlighted (STR comment 5) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135531] Pasted highlighted if the last content character is highlighted (STR comment 5)
https://bugs.documentfoundation.org/show_bug.cgi?id=135531 BogdanB changed: What|Removed |Added Blocks||102593 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102593 [Bug 102593] [META] Paste bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117085] [META] Compress image dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=117085 Bug 117085 depends on bug 156652, which changed state. Bug 156652 Summary: Export to pdf expands compressed Images if "Lossless" is chosen https://bugs.documentfoundation.org/show_bug.cgi?id=156652 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99887] new option for keeping lossless and jpeg original image file format
https://bugs.documentfoundation.org/show_bug.cgi?id=99887 Jérôme changed: What|Removed |Added CC||jens.d...@live.de --- Comment #3 from Jérôme --- *** Bug 156652 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156652] Export to pdf expands compressed Images if "Lossless" is chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=156652 Jérôme changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #13 from Jérôme --- *** This bug has been marked as a duplicate of bug 99887 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102593 BogdanB changed: What|Removed |Added Depends on||135392 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135392 [Bug 135392] Paste from a non-LOO source into LOO CALC overwrites cells containing data without giving a warning -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135392] Paste from a non-LOO source into LOO CALC overwrites cells containing data without giving a warning
https://bugs.documentfoundation.org/show_bug.cgi?id=135392 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||102593 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102593 [Bug 102593] [META] Paste bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156209] Font size increases when copying from cell in edit mode and pasting into another in non-edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156209 --- Comment #13 from LeroyG --- No need to copy, so the title could be: Different font size in edit mode and in non-edit mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156209] Font size increases when copying from cell in edit mode and pasting into another in non-edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156209 --- Comment #12 from LeroyG --- (In reply to LeroyG from comment #11) > Repro in: > > Version: 7.6.0.1 (x86) / LibreOffice Community > > 3. Write something in A1 Could be in whatever cell. 3. Write something in A1 (don't accept) and check the font size field: 17.6 pt. 4. Press Enter, and check the font size field: 10 pt. 5. Write something in C1 (don't accept) and check the font size field: 17.6 pt. 6. Press Enter, and check the font size field: 10 pt. 7. Write something in J9 (don't accept) and check the font size field: 17.6 pt. 8. Press Enter, and check the font size field: 10 pt. After you accept (for all cells), in Edit mode or in the formula bar you will see 17.6 pt. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156209] Font size increases when copying from cell in edit mode and pasting into another in non-edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156209 --- Comment #11 from LeroyG --- No repro in: Version: 7.5.3.2 (x86) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: es-ES Calc: threaded Repro in: Version: 7.6.0.1 (x86) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: es-ES Calc: threaded 1. Open a new spreadsheet. 2. Check the value in the font size field: 10 pt. 3. Write something in A1 (don't accept) and check the font size field: 17.6 pt. 4. Press Enter, and check the font size field: 10 pt. 5. Write something in A1 (don't accept) and check the font size field: 17.6 pt. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156673] Merged cells defined name display and creation differs in version 7.x to previous versions
https://bugs.documentfoundation.org/show_bug.cgi?id=156673 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||109178 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109178 [Bug 109178] [META] Named Cell Ranges and Formula Expressions bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109178] [META] Named Cell Ranges and Formula Expressions bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109178 BogdanB changed: What|Removed |Added Depends on||156673 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156673 [Bug 156673] Merged cells defined name display and creation differs in version 7.x to previous versions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108364] [META] Table/Row/Column/Cell management function bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108364 BogdanB changed: What|Removed |Added Depends on||156689 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156689 [Bug 156689] Deleting Columns May Remove Styling -- You are receiving this mail because: You are the assignee for the bug.
