[Libreoffice-bugs] [Bug 152736] Editing the resolution of jpg or png exports changes physical image size by default
https://bugs.documentfoundation.org/show_bug.cgi?id=152736 Robert Großkopf changed: What|Removed |Added OS|Windows (All) |All Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Version|unspecified |7.2.0.4 release CC||rob...@familiegrosskopf.de Ever confirmed|0 |1 Keywords||regression --- Comment #1 from Robert Großkopf --- The dialog is irritating at this moment. If you set the resolution from 96 dpi up to 300 dpi it doesn't change the field for the dimension, but it creates an image, which will need the same memory as the image with 96 dpi. Click in the radio button for Modify dimensions: Width and height will be changed immediately. Now change the width to the width of the page and the needed memory grows by a factor of ten. The dialog with the radio buttons has been created for changing dpi without changing dimension, as it was before up to LO 7.1.*. New introduced radio buttons are a regression, because they show the old dimension and still will change the content to a new dimension. Tested with LO 7.4.4.2 on OpenSUSE 15.3 64bit rpm Linux. Also tested with older versions. New dialog appears first with LO 7.2. LO 7.1.5.2 won't show the radio buttons. Changing of dpi will directly show a changing of dimensions. So you see: Oh, I have to adjust dimensions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105681] 5.3.0.3 installer hangs when custom option to install to d: drive selected
https://bugs.documentfoundation.org/show_bug.cgi?id=105681 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #12 from Stéphane Guillou (stragu) --- Jean-Baptiste's link to the French mailing list doesn't work anymore, here is a working one: https://www.mail-archive.com/users@fr.libreoffice.org/msg40909.html The issue was reported in 2018 for LO 5.4, Windows 10. The reporter says the installer tries to install to the C drive anyway. Paul replied via email and said he wasn't able to test because of different hardware. Duplicate bug 112895 could be a false-positive related to the unpacking of the installer on a nearly-full C drive. Tempted to close as "works for me" because no one has reproduced since 2018 and LO 5.4. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153019] New: LibreOffice calc recovery does not recover hours of unsaved work
https://bugs.documentfoundation.org/show_bug.cgi?id=153019 Bug ID: 153019 Summary: LibreOffice calc recovery does not recover hours of unsaved work Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: documentationfoundat...@jen.fastmail.org Description: My desktop (Fedora 37) running LibreOffice 7.4.3.2 was asleep after I closed the lid. Upon opening the lid, the unlock screen was unresponsive to keyboard or mouse presses; attempting to switch to the console (F1) was also unsuccessful. I had to press and hold the power button to force the system to turn off. Upon reboot, I launched LibreOffice Calc and recovered the .xlsx file I had been editing. Unfortunately, there was very little if any recovery data, and I had lost hours of work. This is unexpected behavior; earlier versions of LibreOffice Calc (on Fedora 36) would recover most if not all of the cached changes. Steps to Reproduce: 1.Open an .xlsx file 2.Type in cells, create a sheet. 3.Wait 20 minutes. 4.Power off and reboot the system. 5.Launch LibreOffice Calc and recover the file. Actual Results: No (or very little) recovery occurs. Expected Results: Almost--if not all--recovery occurs. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 7.4.3.2 Build ID: 40(Build:2) CPU threads: 16; OS: Linux 6.0; UI render: default; VCL: gtk3 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 39936] UI: Right Click on Row/Column -> Insert Copied Cells... (paste + shift cells in one click)
https://bugs.documentfoundation.org/show_bug.cgi?id=39936 Greg changed: What|Removed |Added CC||greg...@hotmail.com --- Comment #65 from Greg --- I've wanted to see this feature added to Calc for years, and wondered why it's never been addressed. The "drag" method works, but is hard to use if scrolling is involved -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72504] EDITING: Unable to edit .odb file with non-local URL
https://bugs.documentfoundation.org/show_bug.cgi?id=72504 --- Comment #40 from triumphg...@gmail.com --- Tested today as per request #39 from QA Administrators. Test done with: LibreOffice version 7.3.6.2. Environment: CPU threads: 16; OS: Linux 5.15 User Interface: UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Misc: Ubuntu package version: 1.7.3.6.2-0ubuntu0.22.04.2. Calc: threaded Problem still exists, as per error message box: "The connection to the data source "Database name" could not be established. SQL Status: HY000 The given URL contains no valid local file system path. Please check the location of your database file. ./connectivity/source/commontools/dbexception.cxx:413" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104271] New comment box should automatically re-position and re-size appropriately based on the shape of text pasted into it
https://bugs.documentfoundation.org/show_bug.cgi?id=104271 --- Comment #24 from giaverma --- Thank you for sharing this amazing and great site and knowledge with us. http://www.callgirlfriendrelationship.com/ http://www.callgirlfriendrelationship.com/night-partner-in-hyderabad-call-girls.html http://www.callgirlfriendrelationship.com/chennai-call-girl-number-whatsapp.html http://www.callgirlfriendrelationship.com/bangalore-call-girl-number.html http://www.callgirlfriendrelationship.com/sexy-bhabhi-whatsapp-number.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104271] New comment box should automatically re-position and re-size appropriately based on the shape of text pasted into it
https://bugs.documentfoundation.org/show_bug.cgi?id=104271 --- Comment #23 from giaverma --- This is great post here. Gratitude for getting some margin to post such important data. Quality substance generally gets the guests coming. https://www.pinkjaipurescorts.com/ https://www.pinkjaipurescorts.com/russian-escorts-jaipur.html https://www.pinkjaipurescorts.com/independent-escorts-jaipur.html https://www.pinkjaipurescorts.com/hotel-escorts-jaipur.html https://www.pinkjaipurescorts.com/alwar-escorts.html https://www.pinkjaipurescorts.com/ajmer-escorts.html https://www.pinkjaipurescorts.com/jodhpur-escorts.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104271] New comment box should automatically re-position and re-size appropriately based on the shape of text pasted into it
https://bugs.documentfoundation.org/show_bug.cgi?id=104271 --- Comment #22 from giaverma --- I have been looking at a couple of your accounts and I can state very great stuff. I will bookmark your blog. https://www.callgirlsservicejaipur.com/ https://www.dirtyescortsmodels.in/ https://www.callgiral.in/ https://www.agraescort.co.in/ https://www.babesofcochin.in/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120230] Palette of colors on tool bar 'Color Bar' cannot be set directly; palette chosen elsewhere is used only after restart
https://bugs.documentfoundation.org/show_bug.cgi?id=120230 --- Comment #8 from V Stuart Foote --- Issue remains, the Draw 'Color bar' does not refresh with palette selection, and no drop list widget with the color bar to directly change it. Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153018] New: The entire document loses formatting done when I use the clone formatting tool
https://bugs.documentfoundation.org/show_bug.cgi?id=153018 Bug ID: 153018 Summary: The entire document loses formatting done when I use the clone formatting tool Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jacc90...@gmail.com Description: Working with numbered schemes in writer, when cloning formatting from one paragraph to another, all document formatting is lost (font, size, tables, etc.). The same thing happened when inserting rows or columns into a table. Steps to Reproduce: 1.I have an schemes list in a table. 2.When I insert a new row, all the table an its content lost them previous format (font, size, color background, etc.) 3.When I clone the format of the list happen the same issue Actual Results: All the table an its content lost them previous format (font, size, color background, etc.) Expected Results: The table should keep its previuos format Reproducible: Always User Profile Reset: No Additional Info: SO Ubuntu 20.04 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152920] LO Writer: User Input fields in header or footer not visible in freshly opened documents
https://bugs.documentfoundation.org/show_bug.cgi?id=152920 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152743] Table elements not accessible in field formulas and text field formulas not available in table cells
https://bugs.documentfoundation.org/show_bug.cgi?id=152743 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 152730] Trying to open a file from StartCenter gets some warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152730 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 152739] Round ROUND_HALF_UP is OK in Python, but NO in Basic when call the same Python def.
https://bugs.documentfoundation.org/show_bug.cgi?id=152739 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 152741] Single line plain text content control created with MS Word not recognized by Libre Office
https://bugs.documentfoundation.org/show_bug.cgi?id=152741 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 152999] UI: Document background color in settings overrides cell background colors in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152999 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152736] Editing the resolution of jpg or png exports changes physical image size by default
https://bugs.documentfoundation.org/show_bug.cgi?id=152736 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 152742] Writer tells me I'm writing Afrikaans - but I never chose that
https://bugs.documentfoundation.org/show_bug.cgi?id=152742 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 152742] Writer tells me I'm writing Afrikaans - but I never chose that
https://bugs.documentfoundation.org/show_bug.cgi?id=152742 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149419] Footnote numbers aren't reset between letters in mail merge
https://bugs.documentfoundation.org/show_bug.cgi?id=149419 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 149419] Footnote numbers aren't reset between letters in mail merge
https://bugs.documentfoundation.org/show_bug.cgi?id=149419 --- Comment #3 from QA Administrators --- Dear c+lobug, 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 90407] AutoFit option not exported in ppt
https://bugs.documentfoundation.org/show_bug.cgi?id=90407 --- Comment #22 from QA Administrators --- Dear Ljiljan, 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 89089] Editing: no keyboard shortcut to simultaneously apply default Paragraph Style while removing any applied character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=89089 --- Comment #13 from QA Administrators --- Dear Cor Nouws, 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 86896] FRAMEWORK: Command line help not translated
https://bugs.documentfoundation.org/show_bug.cgi?id=86896 --- Comment #11 from QA Administrators --- Dear Olivier Hallot, 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 72504] EDITING: Unable to edit .odb file with non-local URL
https://bugs.documentfoundation.org/show_bug.cgi?id=72504 --- Comment #39 from QA Administrators --- Dear TriumphGuru, 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 139213] Formatting depends on fonts used
https://bugs.documentfoundation.org/show_bug.cgi?id=139213 --- Comment #5 from QA Administrators --- Dear Prince Singh Tomar, 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 122473] FILEOPEN XLSX, Pivot table’s labels lose their orientation in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=122473 --- Comment #7 from QA Administrators --- Dear NISZ LibreOffice Team, 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 122024] merged cells become unmerged when deleting first row or column
https://bugs.documentfoundation.org/show_bug.cgi?id=122024 --- Comment #9 from QA Administrators --- Dear raal, 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 121751] Cursor overlaps comment when shown in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=121751 --- Comment #7 from QA Administrators --- Dear Dan Dascalescu, 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 121741] Clicking in of text box with placeholder text generates an Undo step
https://bugs.documentfoundation.org/show_bug.cgi?id=121741 --- Comment #6 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121455] hang: Doesn't open embedded PDF file from .odt
https://bugs.documentfoundation.org/show_bug.cgi?id=121455 --- Comment #14 from QA Administrators --- Dear Maarten van Druten, 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 112781] loadComponentFromUrl forces the window to full-screen
https://bugs.documentfoundation.org/show_bug.cgi?id=112781 --- Comment #8 from QA Administrators --- Dear Stéphane Aulery, 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 120230] Palette of colors on tool bar 'Color Bar' cannot be set directly; palette chosen elsewhere is used only after restart
https://bugs.documentfoundation.org/show_bug.cgi?id=120230 --- Comment #7 from QA Administrators --- Dear Cor Nouws, 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 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 --- Comment #9 from Regina Henschel --- In this place is nothing more to do. The wrong size in docx and the wrong handle position in rtf have to be solved somewhere else. Unit test will come, but I first need to update and build my repository, which takes some time. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152656] "Drawing Style" should be renamed "Drawing Object Style" or "Shape Style"
https://bugs.documentfoundation.org/show_bug.cgi?id=152656 Eyal Rozenberg changed: What|Removed |Added Summary|"Drawing Style" should be |"Drawing Style" should be |renamed "Drawing Object |renamed "Drawing Object |Style" |Style" or "Shape Style" --- Comment #6 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) > We discussed the topic in the design meeting. While Stuart agrees, Roman, > Cor and me would recommend to keep it short ... short where? In the sidebar tooltip? Because other than that, it's icons. Also, why is "Fill format mode" considered short enough, but "Drawing Object Style" isn't? > Precision is not always an improvement for usability. Perhaps, but truth, as opposed to untruth, is. A "Drawing style" is not a style of drawing. > Cor and me would recommend to keep it ... simple. "Drawing style" is short, but it would only be simple if it were true - which it isn't. This reminds me of the "heading"/"outline"/"chapter" numbering conundrum. It's very short and simple to talk about "chapter numbering"; but - it's not true. "Drawing object style" is simple, because the user knows about objects. They align objects. They insert objects. They have drawing object properties toolbar ... ... hmm. Now that I think about it, maybe I'm over fixated on "Drawing Objects". While this is still a pretty good choice of name, I was assuming we need to keep the word "drawing". Maybe, instead, we should call them "shape styles". The word "shapes" appears more often in the UI than "Drawing object": * Shape menu * Arrow shapes, star shapes etc menubutton * Navigator shows shapes so that's something to consider as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 --- Comment #8 from Julien Nabet --- Is it ok now and I can cherry-pick this on 7.5 or is there still something to do here? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153017] printer chaos
https://bugs.documentfoundation.org/show_bug.cgi?id=153017 --- Comment #1 from alignedtrain...@outlook.com --- problem also persists in safe mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153017] New: printer chaos
https://bugs.documentfoundation.org/show_bug.cgi?id=153017 Bug ID: 153017 Summary: printer chaos Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alignedtrain...@outlook.com Description: I had the misfortune to have to change the page layout / printer settings on one document .. and now every single one inherits those settings .. total utter chaos and each document is ruined to the point I cant even get the old settings back. Steps to Reproduce: 1.open document 2.get annoyed 3. Actual Results: utter chaos .. Expected Results: individual printer settings for each document are retained .. as they used to be Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153008] FILEOPEN PPTX: images (clipped against a shape) appear horizontally compressed
https://bugs.documentfoundation.org/show_bug.cgi?id=153008 Aron Budea changed: What|Removed |Added Attachment #184636|application/vnd.ms-powerpoi |application/vnd.openxmlform mime type|nt |ats-officedocument.presenta ||tionml.presentation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153008] FILEOPEN PPTX: images (clipped against a shape) appear horizontally compressed
https://bugs.documentfoundation.org/show_bug.cgi?id=153008 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0714 CC||aron.bu...@gmail.com Status|UNCONFIRMED |NEW Blocks||139902 Ever confirmed|0 |1 Version|7.1.6.2 release |7.1.3.2 release Keywords||bibisected, bisected --- Comment #2 from Aron Budea --- Confirmed using LO 7.6.0.0.alpha0+ (d993327eab0a2c9c8820c6528075b01de68b0ec6) / Ubuntu. The mentioned change comes from bug 140714 's fix, as found by reverse bibisecting it. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139902 [Bug 139902] [META] PPTX Image issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139902] [META] PPTX Image issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139902 Aron Budea changed: What|Removed |Added Depends on||153008 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153008 [Bug 153008] FILEOPEN PPTX: images (clipped against a shape) appear horizontally compressed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116280] [META] Regressions introduced by the image handling refactoring
https://bugs.documentfoundation.org/show_bug.cgi?id=116280 Aron Budea changed: What|Removed |Added Depends on||147704 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=147704 [Bug 147704] FILEOPEN PPTX: image appears vertically compressed (by a factor of two) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147704] FILEOPEN PPTX: image appears vertically compressed (by a factor of two)
https://bugs.documentfoundation.org/show_bug.cgi?id=147704 Aron Budea changed: What|Removed |Added Blocks||116280 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=116280 [Bug 116280] [META] Regressions introduced by the image handling refactoring -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153014] FILEOPEN PPTX: slide build-up with animations/effects very, very choppy
https://bugs.documentfoundation.org/show_bug.cgi?id=153014 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Reproducible Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153016] Duplicated comment with action description in .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=153016 --- Comment #1 from Marcin Segit --- Created attachment 184654 --> https://bugs.documentfoundation.org/attachment.cgi?id=184654=edit Added/deleted comments -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153016] New: Duplicated comment with action description in .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=153016 Bug ID: 153016 Summary: Duplicated comment with action description in .doc file Product: LibreOffice Version: 7.4.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: s...@onet.pl Description: In a doc with track changes turned on after adding or deleting a comment and saving and closing the file upon reopening an additional comment appears stating "Comment added/deleted", thus doubling the number of comments in the text. Steps to Reproduce: 1. Create doc file with Writer. 2. Type some text. 3. Turn on track changes. 4. Make changes in the text. 5. Add a comment. 6. Save. 7. Quit. 8. Open the .doc file again. Actual Results: Additional comment appears. Expected Results: There is only one comment that was left by me. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.4.4.2 (x64) / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: pl-PL (pl_PL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153003] Copying a query and pasting as table in same database impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=153003 Julien Nabet changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | --- Comment #4 from Julien Nabet --- (In reply to Julien Nabet from comment #3) > I've submitted this first patch: > https://gerrit.libreoffice.org/c/core/+/145499 > > but then I've got: > warn:dbaccess:165069:165069:dbaccess/source/ui/uno/copytablewizard.cxx:1421: > com.sun.star.sdbc.SQLException message: "This operation is not supported in > statement [ALTER TABLE "qry_Name1" ALTER "ID" RESTART WITH 3] at > /home/julien/lo/libreoffice/connectivity/source/drivers/jdbc/Object.cxx:172" > SQLState: S1000 ErrorCode: -73 > wrapped: void message: "at > /home/julien/lo/libreoffice/comphelper/source/misc/diagnose_ex.cxx:66" It seems due to the fact that "ID" field in "tbl_Name' is not an IDENTITY column. To change this, you must set "autoincrement" to "yes" and then it works. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153012] FILEOPEN PPTX: ring segment renders black (or transparent?) instead of grey
https://bugs.documentfoundation.org/show_bug.cgi?id=153012 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #2 from m.a.riosv --- Reproducible it's imported with black color instead grey. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153003] Copying a query and pasting as table in same database impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=153003 Julien Nabet changed: What|Removed |Added CC||noelgran...@gmail.com, ||serval2...@yahoo.fr --- Comment #3 from Julien Nabet --- I've submitted this first patch: https://gerrit.libreoffice.org/c/core/+/145499 but then I've got: warn:dbaccess:165069:165069:dbaccess/source/ui/uno/copytablewizard.cxx:1421: com.sun.star.sdbc.SQLException message: "This operation is not supported in statement [ALTER TABLE "qry_Name1" ALTER "ID" RESTART WITH 3] at /home/julien/lo/libreoffice/connectivity/source/drivers/jdbc/Object.cxx:172" SQLState: S1000 ErrorCode: -73 wrapped: void message: "at /home/julien/lo/libreoffice/comphelper/source/misc/diagnose_ex.cxx:66" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153011] FILEOPEN PPTX: rectangular shapes are missing shadows
https://bugs.documentfoundation.org/show_bug.cgi?id=153011 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #2 from m.a.riosv --- Reproducible, seems for shapes it's imported, but not for graphics. Version: 7.4.4.2 (x64) / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122945] VIEWING: Tab colors of protected worksheets not shown in Excel 2007 spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=122945 --- Comment #10 from Ben Elliston --- I vote for mimicking MS Excel behaviour. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153015] FILEOPEN PPTX: narrow slices of background appear between rectangles (in presentation mode only)
https://bugs.documentfoundation.org/show_bug.cgi?id=153015 --- Comment #1 from Gerald Pfeifer --- Created attachment 184653 --> https://bugs.documentfoundation.org/attachment.cgi?id=184653=edit Screenshot in presentation mode - respective areas marked (in green) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153015] New: FILEOPEN PPTX: narrow slices of background appear between rectangles (in presentation mode only)
https://bugs.documentfoundation.org/show_bug.cgi?id=153015 Bug ID: 153015 Summary: FILEOPEN PPTX: narrow slices of background appear between rectangles (in presentation mode only) Product: LibreOffice Version: 6.4 all versions Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 184652 --> https://bugs.documentfoundation.org/attachment.cgi?id=184652=edit Sample slide (PPTX) If we view the sample documentation in edit mode, the actual slide background is not visible. In presentation mode - in Impress, not so in PowerPoint, there are three places where it comes through. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5b3fd1af1247d4096451e5a768c3438fbccec2b2 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US (and back to 6.4 at least) Disclaimer: I am not arguing this is a well designed slide. It still renders differently in Impress than it does in PowerPoint. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153013] Rendering regression in Writer 7.5rc1: Text/font is rendered sometimes blury, sometimes sharp
https://bugs.documentfoundation.org/show_bug.cgi?id=153013 --- Comment #2 from Gerry --- Created attachment 184651 --> https://bugs.documentfoundation.org/attachment.cgi?id=184651=edit Second screenshot Please open the screenshot. Again, in this screenshot you see that the first three lines are rendered blury, but the last line is rendered correctly (= sharp). The interesting difference to the "First screenshot" is that the third line/paragraph changed its state from sharp to blury when I entered the fourth line/pargraph. If you don't see this immediately in the screenshot, please zoom the screenshot to e.g. 450% and compare the rendering. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152999] UI: Document background color in settings overrides cell background colors in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152999 --- Comment #3 from Jens --- Created attachment 184650 --> https://bugs.documentfoundation.org/attachment.cgi?id=184650=edit Libreoffice Writer UI with text colors and "Libreoffice" theme Similarly in Libreoffice Writer. Currently it doesn't seem possible to have a dark mode Desktop theme but a white document background color AND have content backgrounds within the document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153013] Rendering regression in Writer 7.5rc1: Text/font is rendered sometimes blury, sometimes sharp
https://bugs.documentfoundation.org/show_bug.cgi?id=153013 --- Comment #1 from Gerry --- Created attachment 184649 --> https://bugs.documentfoundation.org/attachment.cgi?id=184649=edit First screenshot Please open the screenshot. You see that the third line (paragraph) in the document is rendered sharp while the two first lines are rendered blury. If you don't see this immediately in the screenshot, please zoom the screenshot to e.g. 450% and compare the rendering. It looks to me that antialising works fine for all lines, but the display of the first two lines is just blury. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153014] New: FILEOPEN PPTX: slide build-up with animations/effects very, very choppy
https://bugs.documentfoundation.org/show_bug.cgi?id=153014 Bug ID: 153014 Summary: FILEOPEN PPTX: slide build-up with animations/effects very, very choppy Product: LibreOffice Version: 6.4 all versions Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 184648 --> https://bugs.documentfoundation.org/attachment.cgi?id=184648=edit Sample slide (PPTX) I got a presentation with the slide included here. In Office 365 (web version) the build is not perfectly smooth, but okayish. In Impress with a (three year old) quad core CPU and 16GB the build-up with animation/effects is very, very, very choppy. Essentially unbearable. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5b3fd1af1247d4096451e5a768c3438fbccec2b2 CPU threads: 8; OS: Linux 6.0; 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 153007] LibreOffice 7.4.3.2 very slow with VCL GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=153007 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- Do you have any accessibility tool enabled? If yes, could you disable them just for the test? Indeed, contrary to gen rendering, gtk3 and kf5 use accessibility part. It could also be due to Skia or graphic driver, could you apply advice from the link https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29 ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153013] New: Rendering regression in Writer 7.5rc1: Text/font is rendered sometimes blury, sometimes sharp
https://bugs.documentfoundation.org/show_bug.cgi?id=153013 Bug ID: 153013 Summary: Rendering regression in Writer 7.5rc1: Text/font is rendered sometimes blury, sometimes sharp Product: LibreOffice Version: 7.5.0.1 rc Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gerry.trep...@googlemail.com Description: I encounter a regression in the rendering of text/fonts in LibreOffice Writer 7.5rc1. I did not see the problem in any previous LibreOffice version such as 7.4.x, 7.3.x. The rendering of text is sometimes blury and sometimes sharp (see attached screenshots). It changes the state of text rendering from blury to sharp and the other way around. It is also possible, that some paragraphs are sharp while other are blury. I did not really figure out a pattern in that behaviour of LO Writer, but it seems to be to me that the last line is more likely sharp than the prevous ones. But sometimes, it is the other way around or everything is blury. Steps to Reproduce: 1. open empty LibreOffice writer text 2. start typing a couple of lines/paragraphs Actual Results: 3. LibreOffice will show all or some of the text blury or sharp Expected Results: Text/fonts should be rendered normally (sharp) Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded System: Ubuntu 22.04 with vanilla Gnome Shell Lenovo ThinkPad T14s Gen 1 AMD® Ryzen 7 pro 4750u with radeon graphics × 16 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152999] UI: Document background color in settings overrides cell background colors in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152999 --- Comment #2 from Jens --- Created attachment 184647 --> https://bugs.documentfoundation.org/attachment.cgi?id=184647=edit Libreoffice Calc UI with text colors and "Libreoffice" theme Hello, Thank you for helping! I am using this theme. However, all colors seem inverted. Also, cell background colors are not applied. I can set the "Document background color" to white manually but then also all background and fill colors *within the document* are also ignored. Note that this is also regardless of the icon theme (I chose one with good contrast). How can I fix this? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153007] LibreOffice 7.4.3.2 very slow with VCL GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=153007 Julien Nabet changed: What|Removed |Added Summary|LibreOffice 7.4.3.2 very|LibreOffice 7.4.3.2 very |slow with VLC GTK3 |slow with VCL GTK3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 --- Comment #7 from Commit Notification --- Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/11319f419988443af85cf3c60dbed12d67fc183f tdf#153000: file types MSO_SPT=25 to 31 are wrongly rendered It will be available in 7.6.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 152994] Daily Screenshot Build failure
https://bugs.documentfoundation.org/show_bug.cgi?id=152994 Caolán McNamara changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | --- Comment #6 from Caolán McNamara --- reported works, done in trunk, backport to 7-5 in gerrit -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153012] FILEOPEN PPTX: ring segment renders black (or transparent?) instead of grey
https://bugs.documentfoundation.org/show_bug.cgi?id=153012 --- Comment #1 from Gerald Pfeifer --- Created attachment 184646 --> https://bugs.documentfoundation.org/attachment.cgi?id=184646=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 153012] New: FILEOPEN PPTX: ring segment renders black (or transparent?) instead of grey
https://bugs.documentfoundation.org/show_bug.cgi?id=153012 Bug ID: 153012 Summary: FILEOPEN PPTX: ring segment renders black (or transparent?) instead of grey Product: LibreOffice Version: 6.4 all versions Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 184645 --> https://bugs.documentfoundation.org/attachment.cgi?id=184645=edit Sample slide (PPTX) Compare the sample slide in Impress vs PowerPoint and notice how a segment of the ring shown is black (or the background color) instead of grey. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5b3fd1af1247d4096451e5a768c3438fbccec2b2 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US and back to version 6.4. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152712] Support setting style attributes relative to parent style
https://bugs.documentfoundation.org/show_bug.cgi?id=152712 --- Comment #9 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #8) > Do you know the "Document Theme" (available in the sidebar if experimental > features is on)? Not what you are looking for but improvements there make > more sense. No, and - I didn't realize there was a toggle for experimental features. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131386] Hidden linebreaks are ignored on creating pdf from rtf document
https://bugs.documentfoundation.org/show_bug.cgi?id=131386 --- Comment #10 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a25eda715591cfa96136bcfd95360156516239d1 tdf#131386 writerfilter: RTF import paragraph mark formatting It will be available in 7.6.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 131386] Hidden linebreaks are ignored on creating pdf from rtf document
https://bugs.documentfoundation.org/show_bug.cgi?id=131386 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153011] FILEOPEN PPTX: rectangular shapes are missing shadows
https://bugs.documentfoundation.org/show_bug.cgi?id=153011 --- Comment #1 from Gerald Pfeifer --- Created attachment 184644 --> https://bugs.documentfoundation.org/attachment.cgi?id=184644=edit Visual comparison: Powerpoint (left) vs Impress (right) Ignore the top left item - something apparently was lost on the way - and focus on the lower row. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153011] New: FILEOPEN PPTX: rectangular shapes are missing shadows
https://bugs.documentfoundation.org/show_bug.cgi?id=153011 Bug ID: 153011 Summary: FILEOPEN PPTX: rectangular shapes are missing shadows Product: LibreOffice Version: 7.1.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 184643 --> https://bugs.documentfoundation.org/attachment.cgi?id=184643=edit Sample slide (PPTX) On the sample slide, all but on of the rectangular shapes are not showing a shadow in Impress (that they are showing in PowerPoint). Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5b3fd1af1247d4096451e5a768c3438fbccec2b2 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US back to at least Version: 7.1.8.0.0+ / LibreOffice Community Build ID: 4784990eda6098f0408276b4d424e81382a50460 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-7-1, Time: 2021-10-15_11:37:03 Interestingly the top left shape does show a shadow (and used to do in LibreOffice 7.0 already, also not correct there.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152997] SVG: circle based upon combination of solid lines + dashes, only renders as solid line
https://bugs.documentfoundation.org/show_bug.cgi?id=152997 Telesto changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords||bibisectRequest, regression Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152999] UI: Document background color in settings overrides cell background colors in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152999 Rafael Lima changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||rafael.palma.l...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Rafael Lima --- When using a dark theme in KDE, if you want the document background to be white (with black text), you need to use the "LibreOffice" color scheme. To do that: 1) Go to Tools - Options - Application Colors 2) Under "Color scheme" choose "LibreOffice" 3) Make sure all colors are set to "Automatic" 4) Click OK This should fix the problem. Let me know if the problem persists. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113610] FILEOPEN XLSX: modern "form control" checkboxes not loaded
https://bugs.documentfoundation.org/show_bug.cgi?id=113610 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||7266 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117266] FILESAVE: xlsm- spreedsheet looses macro-linked buttons (and links) after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=117266 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3610 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 --- Comment #6 from Julien Nabet --- Ok then I've submitted the patch here: https://gerrit.libreoffice.org/c/core/+/145491 As I indicated in it, you're the one who did the work! :-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 --- Comment #5 from Regina Henschel --- (In reply to Julien Nabet from comment #2) > I attached a patch, is it what you meant or did I miss something? (except > the 3D rendering). That is exactly what I meant. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150451] Some text boxes in dialogs do not have borders in dark mode (kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=150451 --- Comment #16 from Rafael Lima --- (In reply to Michael Weghorn from comment #14) > Thanks. Looks pretty much the same as I have, so unfortunately I'm running > out of ideas on what may be causing the issue for you without being able to > reproduce here, unless you have done any other theming/style-related changes > in KDE settings. I'm running out of ideas as well... at first I thought it was because I'm using Ubuntu packages... but Pierre is using Mageia and it's packaging is completely different. So I have no clue whats going on. (In reply to Pierre Fortin from comment #15) > Twilight Zone... now the borders are visible... > OK... thinking about this logically... Last thing I did was blow away my > user profile and start in safe mode. Today, this issue is no longer > present... ;? I've just restarted LO in safe mode (again) and reset the entire user profile, but this did not fix the problem. > However... there is a difference... the Conditional Formatting dialog > currently has a white background in the Conditions box. I may be > remembering wrong; but I think the background was previously light gray... > If so, the border may have been there all along; just 'invisible' if its > color was the same as the background... The background is white. I personally don't like it very much, but it's the correct color. I guess it's to improve contrast with the rest of the dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39650] Shift+F4 conversion from relative to absolute does not work for R1C1 syntax
https://bugs.documentfoundation.org/show_bug.cgi?id=39650 --- Comment #7 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d4d046bb9c5d17cdd432b362c38914cc7b0a75f1 tdf#39650: move UItest to CppUnittest It will be available in 7.6.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 39650] Shift+F4 conversion from relative to absolute does not work for R1C1 syntax
https://bugs.documentfoundation.org/show_bug.cgi?id=39650 Commit Notification changed: What|Removed |Added Whiteboard|target:6.3.0|target:6.3.0 target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153010] Inconsistency and confusing strings when numeric field's numbering format is not available for a language
https://bugs.documentfoundation.org/show_bug.cgi?id=153010 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2985 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152371] Hidden cells create a new empty page
https://bugs.documentfoundation.org/show_bug.cgi?id=152371 --- Comment #7 from Robert Großkopf --- If I remove the hidden cell the page won't be shown, if suppressing empty pages will be enabled. So hidden cells seems to be like content on the page for printing - but it shouldn't, because it isn't visible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152985] Page number field formats displayed wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=152985 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard||target:7.5.0 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3010 Resolution|WORKSFORME |FIXED --- Comment #19 from Stéphane Guillou (stragu) --- Thanks Khaled! Marking this specific case here as fixed by László Németh with core commit 6064b3382102bcbc153156f5874fbc8dfde97b98. I opened bug 153010 for tracking improvements to when the format is not available for the selected language (fallback string + inconsistency depending on the field). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 --- Comment #4 from Julien Nabet --- I gave a try on the rtf file with the patch, it's not perfect but it's far better. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111942] [META] User locale bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=111942 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153010 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153010 [Bug 153010] Inconsistency and confusing strings when numeric field's numbering format is not available for a language -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108746] [META] Page number field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108746 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153010 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153010 [Bug 153010] Inconsistency and confusing strings when numeric field's numbering format is not available for a language -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107575] [META] Number format bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107575 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153010 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153010 [Bug 153010] Inconsistency and confusing strings when numeric field's numbering format is not available for a language -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153010] New: Inconsistency and confusing strings when numeric field's numbering format is not available for a language
https://bugs.documentfoundation.org/show_bug.cgi?id=153010 Bug ID: 153010 Summary: Inconsistency and confusing strings when numeric field's numbering format is not available for a language Product: LibreOffice Version: Inherited From OOo Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: low Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org Blocks: 107575, 108746, 111942 Created attachment 184642 --> https://bugs.documentfoundation.org/attachment.cgi?id=184642=edit test ODT with Page Number fields vs other Statistics fields If a Page Number field's numbering format (likely provided by libnumbertext) is not available for a specific language, a replacement string is used. It can be confusing to the user. Steps: 1. Open attachment Results: If the localised formatting is not available for the language set on the field, some fallbacks are used. For example: * "Ordinal-number 1" for format "1st, 2nd, 3rd..." * "Ordinal 1" for format "First, Second, Third..." * "1" for format "One, Two, Three" This is different to what happens with number fields of the Statistics type. For those, the fallback is first the format for LibreOffice's current locale, and then those same fallback strings if the current LO locale doesn't have the format available either. So there are two things to fix: 1) Inconsistency between "Page number" and "Statistics" fields. Fallback sequence should be consistent for all numeric fields. 2) The fallback strings can be improved, especially for non-English speakers. I see two options to replace the strings: A) Fall back to the default numbering "1, 2, 3.." (solution proposed by Khaled in bug 152985 comment 18) B) Or display a (translatable) string that explains the issue to the user, e.g. "[numbering format not available for this language]". More informative as to what the issue is, but not very elegant since this big string is displayed in place of what is often a small number field. A more involved solution that will make it less likely to see a fallback is to modify the Insert Field and Edit Field dialogs so the field's language can be changed in the dialog and only available formats are displayed, like in Calc Format Cell's dialog. However, unless the language can only be changed in the Edit Field dialog, a sensible fallback will still be needed when the language is later changed (for example when changing a whole paragraph's language). More info: The inconsistency in fallback started with 6.2 (previous versions didn't have the intermediate LO locale fallback for Statistics fields): Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded Still present in master build from today: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 197e5f81213d14fdcbff40edf73385ecd4cd9815 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107575 [Bug 107575] [META] Number format bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108746 [Bug 108746] [META] Page number field bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=111942 [Bug 111942] [META] User locale bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152371] Hidden cells create a new empty page
https://bugs.documentfoundation.org/show_bug.cgi?id=152371 --- Comment #6 from Robert Großkopf --- Created attachment 184641 --> https://bugs.documentfoundation.org/attachment.cgi?id=184641=edit First page with normal cell, second page empty (hidden cell), third page with normal cell There will appear 3 pages here - also the empty page. But the printer is set in the options to suppress empty pages. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 --- Comment #3 from Regina Henschel --- Created attachment 184640 --> https://bugs.documentfoundation.org/attachment.cgi?id=184640=edit similar file in RichTextFormat The wrong size is a different problem and is specific for docx. Import von RTF has the correct size, but the handle position is wrong. Both problems should go to new bugreports. BTW, the shapes are in VML format in docx. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153008] FILEOPEN PPTX: images (clipped against a shape) appear horizontally compressed
https://bugs.documentfoundation.org/show_bug.cgi?id=153008 --- Comment #1 from Gerald Pfeifer --- Created attachment 184639 --> https://bugs.documentfoundation.org/attachment.cgi?id=184639=edit Visual comparison Impress (left) vs PowerPoint (right) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150451] Some text boxes in dialogs do not have borders in dark mode (kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=150451 --- Comment #15 from Pierre Fortin --- Twilight Zone... now the borders are visible... OK... thinking about this logically... Last thing I did was blow away my user profile and start in safe mode. Today, this issue is no longer present... ;? However... there is a difference... the Conditional Formatting dialog currently has a white background in the Conditions box. I may be remembering wrong; but I think the background was previously light gray... If so, the border may have been there all along; just 'invisible' if its color was the same as the background... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153000] FILEOPEN DOCX file types MSO_SPT=25 to 31 are wrongly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=153000 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- Created attachment 184638 --> https://bugs.documentfoundation.org/attachment.cgi?id=184638=edit patch On pc Debian x86-64 with master sources updated today, I could reproduce this. I attached a patch, is it what you meant or did I miss something? (except the 3D rendering). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153009] Android Viewer: Title and text placeholder misplaced when creating new presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=153009 Michael Weghorn changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | Ever confirmed|0 |1 CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- Was mentioned during F-Droid MR review. I can confirm and am working on a fix. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153009] New: Android Viewer: Title and text placeholder misplaced when creating new presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=153009
Bug ID: 153009
Summary: Android Viewer: Title and text placeholder misplaced
when creating new presentation
Product: LibreOffice
Version: 7.6.0.0 alpha0+ Master
Hardware: All
OS: Android
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Android Viewer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: m.wegh...@posteo.de
Created attachment 184637
--> https://bugs.documentfoundation.org/attachment.cgi?id=184637=edit
Screenshot of the issue
As mentioned in [1]: When creating a new presentation in Android Viewer, the
text placeholders for the title etc. ("Click to add Title", "Click to add
Text") are misplaced.
Steps to reproduce:
1) enable experimental mode in Android Viewer
2) start Android Viewer
3) create a new presentation: tap on the "+" symbol on the bottom right, then
"New Presentation"
Actual result:
Placeholder text is on the top left and overlaps each other, unreadable (s.
attached screenshot)
Expected result:
Placeholder texts should be in a proper location and readable, as is the case
for the desktop version of Impress
Version: 7.6.0.0.alpha0+
Build ID: 402ab3d145a1
Note: The text is properly placed when opening an existing presentation that
actually has text instead.
[1] https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12380#note_1230039774
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152371] Hidden cells create a new empty page
https://bugs.documentfoundation.org/show_bug.cgi?id=152371 --- Comment #5 from m.a.riosv --- (In reply to Robert Großkopf from comment #4) > ... But looks to me, that the issue it's with the option Menu/Tools/Options/LibreOffice Calc/Print - Pages - Suppress output of empty pages not working properly when enabled, and hidden cells makes a blank page. Adding a third page with text a deleting 'Page TWO' text, don't show page two. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152742] Writer tells me I'm writing Afrikaans - but I never chose that
https://bugs.documentfoundation.org/show_bug.cgi?id=152742 --- Comment #8 from Eyal Rozenberg --- (In reply to Stéphane Guillou (stragu) from comment #7) > Can you try to find steps to reproduce it from a fresh profile? I don't think so... I don't play with my user profile, but I do play with the UI and various settings as part of my LO QA work. > Including exactly what language settings are used in the LO options. > Anything else changed appart from en-US UI and en-IL locale? Changed when I reset the profile? I'm not sure... I do think I saw a change in the button icon theme . Anything specific to check for? > If not, the other option is to share the user profile (being careful with > any personal info it might contain) but it would make it trickier to debug. I could do that, but - how can I minimize the amount of personal information I'm sharing? Can you link to somewhere explaining how to do that? I'm not familiar with the profile folder contents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152990] Embedded OLE objects scaled wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=152990 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | --- Comment #2 from Caolán McNamara --- I think the canvas code that parses the metafile actions doesn't do it the same same as vcl does and while it scales the text postions as expected, it doesn't handle the font size as expected. So glyphs are positioned where they should be, but the size isn't right. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138455] FILEOPEN DOCX OLE objects replacement image horizontally shrunk
https://bugs.documentfoundation.org/show_bug.cgi?id=138455 Gerald Pfeifer changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3008 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153008] New: FILEOPEN PPTX: images (clipped against a shape) appear horizontally compressed
https://bugs.documentfoundation.org/show_bug.cgi?id=153008 Bug ID: 153008 Summary: FILEOPEN PPTX: images (clipped against a shape) appear horizontally compressed Product: LibreOffice Version: 7.1.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 184636 --> https://bugs.documentfoundation.org/attachment.cgi?id=184636=edit Sample slide (PPTX) This sample slide has three images that are clipped (against a shape). When opened in Impress all three appear horizontally compressed. This may or may not be related to bug#147704 FILEOPEN PPTX: image appears vertically compressed (by a factor of two) bug#138455 - FILEOPEN DOCX OLE objects replacement image horizontally shrunk Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5b3fd1af1247d4096451e5a768c3438fbccec2b2 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US and all the way back to LibreOffice 7.1 LibreOffice 7.0 does *not* exhibit this horizontal crush, but also do not do the clipping against a shape. I guess this speaks to an implementation error in the clipping functionality. -- You are receiving this mail because: You are the assignee for the bug.
