[Libreoffice-bugs] [Bug 156906] New: Be as good as MS Word
https://bugs.documentfoundation.org/show_bug.cgi?id=156906 Bug ID: 156906 Summary: Be as good as MS Word Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: schus...@praxis-schuster.ch Description: For me, one of the most important differences to MS Word is that Word already suggests the correct save name when saving the document by inserting the title of the document in the save mask. surely it would be easy to do that with Libreoffice as well. Thank you very much! Actual Results: s. above Expected Results: s. above Reproducible: Always User Profile Reset: No Additional Info: s. above -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103270] [META] Image/Picture dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103270 Bug 103270 depends on bug 86628, which changed state. Bug 86628 Summary: Add new undo / reset / un- crop function to context menu and dialog https://bugs.documentfoundation.org/show_bug.cgi?id=86628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86349] [META] Context menu bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=86349 Bug 86349 depends on bug 86628, which changed state. Bug 86628 Summary: Add new undo / reset / un- crop function to context menu and dialog https://bugs.documentfoundation.org/show_bug.cgi?id=86628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86899] [META] Requests for the addition of UNO commands
https://bugs.documentfoundation.org/show_bug.cgi?id=86899 Bug 86899 depends on bug 86628, which changed state. Bug 86628 Summary: Add new undo / reset / un- crop function to context menu and dialog https://bugs.documentfoundation.org/show_bug.cgi?id=86628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108280] [META] Image crop bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108280 Bug 108280 depends on bug 86628, which changed state. Bug 86628 Summary: Add new undo / reset / un- crop function to context menu and dialog https://bugs.documentfoundation.org/show_bug.cgi?id=86628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107833] [META] Writer paragraph style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107833 BogdanB changed: What|Removed |Added Depends on||156897 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156897 [Bug 156897] Font changes when copy and paste multiple lines with incomplete first line -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108844] [META] Cut/copy bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108844 BogdanB changed: What|Removed |Added Depends on||156897 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156897 [Bug 156897] Font changes when copy and paste multiple lines with incomplete first line -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156897] Font changes when copy and paste multiple lines with incomplete first line
https://bugs.documentfoundation.org/show_bug.cgi?id=156897 BogdanB changed: What|Removed |Added Summary|font changes when |Font changes when copy and |copypasting multiple lines |paste multiple lines with |with incomplete first line |incomplete first line Blocks||107833, 108844 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107833 [Bug 107833] [META] Writer paragraph style bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108844 [Bug 108844] [META] Cut/copy bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107331] [META] Document themes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107331 BogdanB changed: What|Removed |Added Depends on||156888 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156888 [Bug 156888] Duplicate entry in document themes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156888] Duplicate entry in document themes
https://bugs.documentfoundation.org/show_bug.cgi?id=156888 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||107331 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107331 [Bug 107331] [META] Document themes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123103] FILEOPEN PPTX Font size is smaller compared to MSO because LO doesn't recognize Autofit Text to Placeholder
https://bugs.documentfoundation.org/show_bug.cgi?id=123103 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |2023| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122023] FILEOPEN PPTX shape with "Shrink text on overflow": Calibri Light font size 55, 7 instead of 54 and text splits a word into two lines
https://bugs.documentfoundation.org/show_bug.cgi?id=122023 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=10 | |7694, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |3103| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107694] Impress: "Shrink text on overflow" text box option not recognized from PPTX, text overlapping
https://bugs.documentfoundation.org/show_bug.cgi?id=107694 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |2023| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156900] Delete row with track changes ON and show OFF doesn't hide the deleted row
https://bugs.documentfoundation.org/show_bug.cgi?id=156900 Telesto changed: What|Removed |Added Summary|Delete row with track |Delete row with track |changes ON doesn't hide the |changes ON and show OFF |deleted row |doesn't hide the deleted ||row -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51132] After one success, PRINTING of #10 ENVELOPES failed to print properly, apparently due to incorrect formatting of the envelope document by the 'Insert Envelope' wizard.
https://bugs.documentfoundation.org/show_bug.cgi?id=51132 --- Comment #37 from mkass...@internode.net --- Cannot print DL envelopes. Please try to fix. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153209] Filesave, fileclose- calc crashes on exit when three or four calc files open simultaneously
https://bugs.documentfoundation.org/show_bug.cgi?id=153209 --- Comment #3 from QA Administrators --- Dear irontopp18, 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 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 --- Comment #20 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108914] [META] Password protected file bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108914 Bug 108914 depends on bug 150083, which changed state. Bug 150083 Summary: FILESAVE ODS Saving modified spreadsheet with File open & File edit password and Shared mode leads to General I/O Error https://bugs.documentfoundation.org/show_bug.cgi?id=150083 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153198] 6.4 libreoffice word issues
https://bugs.documentfoundation.org/show_bug.cgi?id=153198 --- Comment #3 from QA Administrators --- Dear danariaves, 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 150254] The style preview menu loses its formatting and confuses and mixes up all
https://bugs.documentfoundation.org/show_bug.cgi?id=150254 --- Comment #5 from QA Administrators --- Dear FERNANDO, 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 150083] FILESAVE ODS Saving modified spreadsheet with File open & File edit password and Shared mode leads to General I/O Error
https://bugs.documentfoundation.org/show_bug.cgi?id=150083 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 150058] Libre Draw doesn't export dotted lines and underlined text in eps and other file types
https://bugs.documentfoundation.org/show_bug.cgi?id=150058 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 150083] FILESAVE ODS Saving modified spreadsheet with File open & File edit password and Shared mode leads to General I/O Error
https://bugs.documentfoundation.org/show_bug.cgi?id=150083 --- Comment #5 from QA Administrators --- Dear Gabor Kelemen (allotropia), 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 150058] Libre Draw doesn't export dotted lines and underlined text in eps and other file types
https://bugs.documentfoundation.org/show_bug.cgi?id=150058 --- Comment #4 from QA Administrators --- Dear Kemo Kemic, 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 149874] LibreOffice Writer 7.3.4.2 corrupts previously saved documents
https://bugs.documentfoundation.org/show_bug.cgi?id=149874 --- Comment #10 from QA Administrators --- Dear john, 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 147643] EDITING Loss of OLE objects (Math formulas) in Libreoffice Writer when using experimental visual editor
https://bugs.documentfoundation.org/show_bug.cgi?id=147643 --- Comment #10 from QA Administrators --- Dear Dmitry, 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 149855] libreoffice calculating with the sum function is fooled somehow by formatting bugs, that keep changing back to default, I think
https://bugs.documentfoundation.org/show_bug.cgi?id=149855 --- Comment #3 from QA Administrators --- Dear Mark Keller, 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 153477] LibreOffice Writer adds empty lines to some pages of the document after closing and opening again
https://bugs.documentfoundation.org/show_bug.cgi?id=153477 --- Comment #5 from QA Administrators --- Dear sri_ni_vas_s, 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 96635] FILEOPEN PDF: Wrong masking, box shown over triangle in arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=96635 --- Comment #17 from QA Administrators --- Dear ZioTibia81, 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 142747] Cannot apply emphasis animation effects to selections of text
https://bugs.documentfoundation.org/show_bug.cgi?id=142747 --- Comment #3 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 130888] Basic is Faulty in creating / deleting User Defined Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=130888 --- Comment #5 from QA Administrators --- Dear atemple, 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 113936] Importing a PDF is slower compared to 5.4
https://bugs.documentfoundation.org/show_bug.cgi?id=113936 --- Comment #12 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 32249] Make it easier to edit text in imported PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=32249 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6507 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156507] Ability to remove non-printing/"atypical" characters in a stretch of text
https://bugs.documentfoundation.org/show_bug.cgi?id=156507 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=32 ||249 --- Comment #12 from V Stuart Foote --- (In reply to Eyal Rozenberg from comment #11) > (In reply to خالد حسني from comment #10) > > They understand enough to know they're getting some junk in addition to the > text they want; keyboard traversal is weird, and the "junk" may be affecting > rendering behavior. > > Just because it's easier if users simply not do this, does not mean that > they don't (or that they shouldn't). You could argue that there is no > reasonable way this could work; perhaps, but - I very much doubt it. While > we have not demonstrated that there can be no reasonable choice of > characters to filter (say, a language-specific or locale-specific choice) - > we should entertain the possibility that it does exist. And assuming it > exists - I believe should offer it, to make this kind of work easier for > users. With +F10 exposing NPC, an +X toggle will show Unicode for the specific NPC at the text cursor--and then toggle it back. Then knowing the Unicode, it is trivial to find/delete (or edit) via Find-Replace dialog. It is not dynamic (requiring linear progression of codepoints being removed from the text) but it is already functional. Otherwise I don't see a need for providing a new dialog as a core capability as it is very much a corner case, and dev effort is not justified. More on point would be dev work to complete the residual NPC toggle exposure from bug 58434 And if the use case is only for parsing PDF--a new Writer paragraph oriented "reflow" implementation, replacing Justin's text box 'combine' based PDF import done for bug 32249, is really the ask. And implementing a new PDF parser/reflow would be the opportunity to selectively clean up any NPC or malformed text runs from PDF source. While completing the per word /ActualText support of bug 117428 would move quality of our PDF exports (optionally as it has a real performance and size cost). Either dupe this to bug 32249, or more simply it becomes => WF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156905] [Regression] Copy and paste formula, now paste value
https://bugs.documentfoundation.org/show_bug.cgi?id=156905 --- Comment #1 from Óvári --- Created attachment 189140 --> https://bugs.documentfoundation.org/attachment.cgi?id=189140=edit Table with formulae in first and last columns not working -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156905] New: [Regression] Copy and paste formula, now paste value
https://bugs.documentfoundation.org/show_bug.cgi?id=156905 Bug ID: 156905 Summary: [Regression] Copy and paste formula, now paste value Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ovari...@zoho.com Description: LibreOffice 7.5: correct copy and paste of formula LibreOffice 7.6: (bug/regression) incorrect copy and paste of value Steps to Reproduce: LibreOffice 7.5: correct copy and paste of formula LibreOffice 7.6: (bug) incorrect copy and paste of value Table with first column and last column with formulae. First column formula, which has the value ‘2’ =+1 Last column formula, which has the value ‘2’ in the first column =+ 1. Update LibreOffice to version 7.6.0.3 2. Select in the first column the value which shows ‘2’, so it will look like: `Image in attached file` 3. Copy that cell (Ctrl+C) 4. Highlight some cells, say ‘4’ to ‘9’ `Image in attached file` 5. Paste (Ctrl+V) 6. Now the cell contain ‘2’, not the formula `Image in attached file` 7. Seems like there are more bugs as the last column (pg) does not update when penultimate column (pp.) is changed. Actual Results: Paste value Expected Results: Paste formula Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156900] Delete row with track changes ON doesn't hide the deleted row
https://bugs.documentfoundation.org/show_bug.cgi?id=156900 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #1 from Aaron --- Thanks for reporting. I cannot reproduce 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: en-AU (fr_FR); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156897] font changes when copypasting multiple lines with incomplete first line
https://bugs.documentfoundation.org/show_bug.cgi?id=156897 Aaron changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156897] font changes when copypasting multiple lines with incomplete first line
https://bugs.documentfoundation.org/show_bug.cgi?id=156897 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #1 from Aaron --- Thanks for reporting. I can reproduce 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: en-AU (fr_FR); UI: en-US Calc: threaded I've noticed from testing that the issue occurs only when the formatting style is anything except 'default paragraph style'. The first copied line will change to 'default paragraph style' and the second copied line retains the original formatting. This results in the change in font as described. The defect also only seems to happen with liberation font styles and not other fonts like 'Times New Roman' for example. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155875 --- Comment #47 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/a002539ad82004b15916510d2feaec5771a9c198 tdf#155875 Tab'd UI cmds Writer/Format in Help(18) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156904] FILEOPEN PPTX: text rendered green instead of white in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156904 --- Comment #1 from Gerald Pfeifer --- Created attachment 189139 --> https://bugs.documentfoundation.org/attachment.cgi?id=189139=edit Screenshot of Impress in presentation mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156904] New: FILEOPEN PPTX: text rendered green instead of white in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=156904 Bug ID: 156904 Summary: FILEOPEN PPTX: text rendered green instead of white in presentation mode Product: LibreOffice Version: 6.0.7.3 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 189138 --> https://bugs.documentfoundation.org/attachment.cgi?id=189138=edit Sample slide (PPTX) In edit mode the sample document looks identical in Impress and PowerPoint - text is rendered in white. In presentation mode Impress renders that same text as green (whereas PowerPoint stays with white). Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5aaf194866c5e416167cb54d37f9f04dabc5375 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US ...back to 6.4 at least. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107899] [META] PPTX paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107899 Bug 107899 depends on bug 123103, which changed state. Bug 123103 Summary: FILEOPEN PPTX Font size is smaller compared to MSO because LO doesn't recognize Autofit Text to Placeholder https://bugs.documentfoundation.org/show_bug.cgi?id=123103 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122023] FILEOPEN PPTX shape with "Shrink text on overflow": Calibri Light font size 55, 7 instead of 54 and text splits a word into two lines
https://bugs.documentfoundation.org/show_bug.cgi?id=122023 --- Comment #19 from Gabor Kelemen (allotropia) --- *** Bug 123103 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 123103] FILEOPEN PPTX Font size is smaller compared to MSO because LO doesn't recognize Autofit Text to Placeholder
https://bugs.documentfoundation.org/show_bug.cgi?id=123103 Gabor Kelemen (allotropia) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #10 from Gabor Kelemen (allotropia) --- I think this is actually the same issue as bug 122023. *** This bug has been marked as a duplicate of bug 122023 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122023] FILEOPEN PPTX shape with "Shrink text on overflow": Calibri Light font size 55, 7 instead of 54 and text splits a word into two lines
https://bugs.documentfoundation.org/show_bug.cgi?id=122023 --- Comment #18 from Gabor Kelemen (allotropia) --- Created attachment 189137 --> https://bugs.documentfoundation.org/attachment.cgi?id=189137=edit The third slide of the new example file in PP 2016 and Impress master -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148328] When opening an odt document, the graphic object is not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=148328 Rajasekaran Karunanithi changed: What|Removed |Added CC||rajasekara...@gmail.com --- Comment #5 from Rajasekaran Karunanithi --- I opened in LO 24.2.0.0 alpha release and also in https://odfviewer.nsspot.net/ and I see the graphic object.No problem at all. Can't reproduce in LO 24.2.0.0 alpha release under Windows 10(x64). Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5aaf194866c5e416167cb54d37f9f04dabc5375 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122023] FILEOPEN PPTX shape with "Shrink text on overflow": Calibri Light font size 55, 7 instead of 54 and text splits a word into two lines
https://bugs.documentfoundation.org/show_bug.cgi?id=122023 --- Comment #17 from Gabor Kelemen (allotropia) --- Created attachment 189136 --> https://bugs.documentfoundation.org/attachment.cgi?id=189136=edit The second slide of the new example file in PP 2016 and Impress master -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122023] FILEOPEN PPTX shape with "Shrink text on overflow": Calibri Light font size 55, 7 instead of 54 and text splits a word into two lines
https://bugs.documentfoundation.org/show_bug.cgi?id=122023 --- Comment #16 from Gabor Kelemen (allotropia) --- Created attachment 189135 --> https://bugs.documentfoundation.org/attachment.cgi?id=189135=edit The first slide of the new example file in PP 2016 and Impress master Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122023] FILEOPEN PPTX shape with "Shrink text on overflow": Calibri Light font size 55, 7 instead of 54 and text splits a word into two lines
https://bugs.documentfoundation.org/show_bug.cgi?id=122023 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #15 from Gabor Kelemen (allotropia) --- Created attachment 189134 --> https://bugs.documentfoundation.org/attachment.cgi?id=189134=edit Modified example file from PP 2016 There seems to be a bit of a difference in case of Title type placeholders and the "Shrink text on overflow" setting. This file demonstrates the setting with 60, 40 and 20 pt font sizes and small placeholder boxes. The key is that the same setting operates a different resizing algorithm, depending on the placeholder type: - if it's a Title, then the font size is reduced by exactly 10%. So we get 54pt, 36pt and 18 pt, but overall the text happily overflows the small boxes. - if it's not a Title, but Subtitle, Content then the font size is reduced as much as is needed for the text to fit inside the available box. So we get around 10-20 pt font sizes for the lower boxes. Impress does the latter algorithm for all textboxes (approximately correctly), but for Title type boxes, should do the "10% font size reduction" one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156887] Exporting csv or xlsx to dbf
https://bugs.documentfoundation.org/show_bug.cgi?id=156887 --- Comment #3 from ady --- (In reply to Dick Hildreth from comment #0) > The data set contains PII, so sharing example data must be handled carefully > and properly. Sharing a file in bug reports means it is publicly available. https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156903] FILEOPEN PPTX: line renders orange instead of blue
https://bugs.documentfoundation.org/show_bug.cgi?id=156903 --- Comment #1 from Gerald Pfeifer --- Created attachment 189133 --> https://bugs.documentfoundation.org/attachment.cgi?id=189133=edit Visual comparison PowerPoint (top) vs Impress (bottom) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156903] New: FILEOPEN PPTX: line renders orange instead of blue
https://bugs.documentfoundation.org/show_bug.cgi?id=156903 Bug ID: 156903 Summary: FILEOPEN PPTX: line renders orange instead of blue Product: LibreOffice Version: 7.0 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 189132 --> https://bugs.documentfoundation.org/attachment.cgi?id=189132=edit Sample slide (PPTX) This may be due to the tips/arrows of the line rendering orange in PowerPoint and only the rest rendering blue. Maybe this is somehow a missing feature in LibreOffice? Still, if so, the line should render completely blue, not completely orange? Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5aaf194866c5e416167cb54d37f9f04dabc5375 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US All the way back to 7.0 (and 6.4, though the line does not render properly there). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156886] Calc fails to format date as requested
https://bugs.documentfoundation.org/show_bug.cgi?id=156886 --- Comment #3 from ady --- FWIW, if this happens when importing from a csv, the import dialogue allows to select each column and set the format, for example as d/m/y (or similar), among other possibilities and options. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51945] UI: Edit Changes : adding the ability to switch "show" mode during accept & reject
https://bugs.documentfoundation.org/show_bug.cgi?id=51945 --- Comment #2 from Justin L --- This will not be quite as easy as it sounded: -only Writer has FN_REDLINE_SHOW. (Calc doesn't have an equivalent) -the "manage" code is shared between calc and writer. I would expect that placing a .uno:ViewTrackChanges button beside List/Filter would be the best place. svx/uiconfig/ui/redlinecontrol.ui svx/source/dialog/ctredlin.cxx? Perhaps https://gerrit.libreoffice.org/c/core/+/153775 would be useful as a code pointer: it did something vaguely similar. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156889] dark mode with black items (please put them in light color)
https://bugs.documentfoundation.org/show_bug.cgi?id=156889 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Have you selected the icons? Menu/Tools/Options/LibreOffice/View – Appearance/Icon themes? Please paste here the information on Menu/Help/About LibreOffce (There is an icon to copy) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156888] Duplicate entry in document themes
https://bugs.documentfoundation.org/show_bug.cgi?id=156888 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Confirmed Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156887] Exporting csv or xlsx to dbf
https://bugs.documentfoundation.org/show_bug.cgi?id=156887 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #2 from m.a.riosv --- Please attach a sample file. And explain what you are trying to do step by step. e.g. opening a csv file, ..., save as dbf? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156902] FILEOPEN PPTX: graphics not shown (edit mode and presentation mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=156902 --- Comment #1 from Gerald Pfeifer --- The distorted/missing text close to the blue cow is covered by bug #156901. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156901] FILEOPEN PPTX: text not shown (properly) in presentation mode (only)
https://bugs.documentfoundation.org/show_bug.cgi?id=156901 --- Comment #3 from Gerald Pfeifer --- The missing logo is covered by bug #156902. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156880] LibreOffice spellcheck/dictionary issues in 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156880 BogdanB changed: What|Removed |Added Resolution|NOTABUG |WORKSFORME CC||buzea.bog...@libreoffice.or ||g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156901] FILEOPEN PPTX: text not shown (properly) in presentation mode (only)
https://bugs.documentfoundation.org/show_bug.cgi?id=156901 Gerald Pfeifer changed: What|Removed |Added Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156886] Calc fails to format date as requested
https://bugs.documentfoundation.org/show_bug.cgi?id=156886 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- There is not a bug. Seems the date were wrongly imported. For dates that can be misinterpreted as dd/mm/ or mm/dd/, a "'" it's added to mark it as text like '1/3/2023, for those that cannot the single quotation is not needed. Please add your question in https://ask.libreoffice.org/c/english/5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156901] FILEOPEN PPTX: text not shown (properly) in presentation mode (only)
https://bugs.documentfoundation.org/show_bug.cgi?id=156901 Gerald Pfeifer changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6902 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156902] New: FILEOPEN PPTX: graphics not shown (edit mode and presentation mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=156902 Bug ID: 156902 Summary: FILEOPEN PPTX: graphics not shown (edit mode and presentation mode) Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisectRequest, regression Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Using the document from attachment #189129 of bug #156901 the blue cow does not appear in Impress - neither in edit mode nor in presentation mode. How it should look like: attachment #189130 of bug #156901. How it looks like: attachment #189131 of bug #156901. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5aaf194866c5e416167cb54d37f9f04dabc5375 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Not showing the blue *cow* of the logo is a regression that happened between Version: 6.4.8.0.0+ Build ID: 99b065ec31d032fc08ab14f66430dac4fef904a5 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-6-4, Time: 2020-10-08_08:57:08 Locale: en-US (en_US.UTF-8); UI-Language: en-US and Version: 7.0.7.0.0+ Build ID: 54e9dd41dc9dd45af12c9346199f601ea4a5994d CPU threads: 8; OS: Linux 6.4; 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-0, Time: 2021-05-07_08:22:18 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96635] FILEOPEN PDF: Wrong masking, box shown over triangle in arrows
https://bugs.documentfoundation.org/show_bug.cgi?id=96635 --- Comment #16 from ZioTibia81 --- Still... Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156901] FILEOPEN PPTX: text not shown (properly) in presentation mode (only)
https://bugs.documentfoundation.org/show_bug.cgi?id=156901 --- Comment #2 from Gerald Pfeifer --- Created attachment 189131 --> https://bugs.documentfoundation.org/attachment.cgi?id=189131=edit How LibreOffice currently renders it -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156901] FILEOPEN PPTX: text not shown (properly) in presentation mode (only)
https://bugs.documentfoundation.org/show_bug.cgi?id=156901 --- Comment #1 from Gerald Pfeifer --- Created attachment 189130 --> https://bugs.documentfoundation.org/attachment.cgi?id=189130=edit How it should look like (PowerPoint) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156901] New: FILEOPEN PPTX: text not shown (properly) in presentation mode (only)
https://bugs.documentfoundation.org/show_bug.cgi?id=156901 Bug ID: 156901 Summary: FILEOPEN PPTX: text not shown (properly) in presentation mode (only) Product: LibreOffice Version: 7.3.7.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 189129 --> https://bugs.documentfoundation.org/attachment.cgi?id=189129=edit Sample slide (PPTX) 1. Open document, observe how "Rancher by SUSE" is rendered. 2. Enter presentation mode. 3. Observe how "Rancher by SUSE" hardly is visible any longer. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5aaf194866c5e416167cb54d37f9f04dabc5375 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Not showing the *text* of the logo properly is regression that happened between Version: 7.2.8.0.0+ / LibreOffice Community Build ID: d293877ff029ae7c161ccfbade992485fd92fe75 CPU threads: 8; OS: Linux 6.4; 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-2, Time: 2022-04-26_20:29:27 and Version: 7.3.8.0.0+ / LibreOffice Community Build ID: 0f7fb0a2decec3f8869098ae5e47ee6055545486 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 156880] LibreOffice spellcheck/dictionary issues in 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156880 John Schuetz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #6 from John Schuetz --- I'm not sure I'm doing this right with the status but . . . I uninstalled 7.6, re-installed 7.5.5, and the spell-checking was working as per usual. I then uninstalled 7.5.5, re-installed 7.6, and now it seems to be working fine. So I guess something got messed up when I updated 7.5.5 to 7.6. I believe this bug can be closed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156312] UI rendering errors with kf5 and qt5
https://bugs.documentfoundation.org/show_bug.cgi?id=156312 Stéphane Guillou (stragu) changed: What|Removed |Added URL||https://bugs.kde.org/show_b ||ug.cgi?id=416048 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102345 Eyal Rozenberg changed: What|Removed |Added Depends on|156507 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156507 [Bug 156507] Ability to remove non-printing/"atypical" characters in a stretch of text -- 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 Eyal Rozenberg changed: What|Removed |Added Depends on||156507 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156507 [Bug 156507] Ability to remove non-printing/"atypical" characters in a stretch of text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156507] Ability to remove non-printing/"atypical" characters in a stretch of text
https://bugs.documentfoundation.org/show_bug.cgi?id=156507 Eyal Rozenberg changed: What|Removed |Added Blocks|102345 |102593 --- Comment #11 from Eyal Rozenberg --- (In reply to خالد حسني from comment #10) They understand enough to know they're getting some junk in addition to the text they want; keyboard traversal is weird, and the "junk" may be affecting rendering behavior. Just because it's easier if users simply not do this, does not mean that they don't (or that they shouldn't). You could argue that there is no reasonable way this could work; perhaps, but - I very much doubt it. While we have not demonstrated that there can be no reasonable choice of characters to filter (say, a language-specific or locale-specific choice) - we should entertain the possibility that it does exist. And assuming it exists - I believe should offer it, to make this kind of work easier for users. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102345 [Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and enhancements 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 156507] Ability to remove non-printing/"atypical" characters in a stretch of text
https://bugs.documentfoundation.org/show_bug.cgi?id=156507 --- Comment #10 from خالد حسني --- If users understand what these characters are, they can use advanced search and replace to strip them, if they don’t understand what these are then we shouldn’t be giving them functionality that is more likely than not to do the wrong thing. WONFIX from me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115733] "Open with" dialog menu items have no icons next the name "Libreoffice"
https://bugs.documentfoundation.org/show_bug.cgi?id=115733 --- Comment #15 from Al M. --- You may close this, as I tested and it's fixed as of August 2023. Al -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152971] Table row stays visible after redo of deletion (track changes enabled)
https://bugs.documentfoundation.org/show_bug.cgi?id=152971 Telesto changed: What|Removed |Added Regression By||László Németh -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156900] Delete row with track changes ON doesn't hide the deleted row
https://bugs.documentfoundation.org/show_bug.cgi?id=156900 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6784 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156784] LO freezes if delete the first column on the table and the TC are hidden, pressing Ctrl+A
https://bugs.documentfoundation.org/show_bug.cgi?id=156784 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6900 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156900] New: Delete row with track changes ON doesn't hide the deleted row
https://bugs.documentfoundation.org/show_bug.cgi?id=156900 Bug ID: 156900 Summary: Delete row with track changes ON doesn't hide the deleted row Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Delete row with track changes ON doesn't hide the deleted row Steps to Reproduce: 1. Open attachment 188994 (bug 156784) 2. Edit -> track changes -> Show (disabled) (like default) 3. Press delete row (for say the first row) Actual Results: Nothing happens Expected Results: The row with 'A' in cell A1 disappears Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122104] FILEOPEN XLSX, Conditional formatting with a gradient background changes to a single color background in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=122104 --- Comment #7 from Michaela --- Still repro with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e46e663cc350d89e4997095466d675b875eb2e04 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 Bug 99746 depends on bug 113936, which changed state. Bug 113936 Summary: Importing a PDF is slower compared to 5.4 https://bugs.documentfoundation.org/show_bug.cgi?id=113936 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113936] Importing a PDF is slower compared to 5.4
https://bugs.documentfoundation.org/show_bug.cgi?id=113936 Telesto changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from Telesto --- 9 seconds with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded Good enough, IMHO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156312] UI rendering errors with kf5 and qt5
https://bugs.documentfoundation.org/show_bug.cgi?id=156312 --- Comment #6 from RGB --- (In reply to Stéphane Guillou (stragu) from comment #5) > OK, thank you for looking into it further! > Please do link to a relevant issue here if you find one on openSUSE or Qt > forums or trackers. Finally, I found the correct bug report from KDE project Morphing Popups effect: glitch when the size of a tooltip is reduced https://bugs.kde.org/show_bug.cgi?id=416048 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99986] EDITING: formula use in LO and save as XSLX give error in excel (function IF accept invalid reference)
https://bugs.documentfoundation.org/show_bug.cgi?id=99986 --- Comment #11 from Eike Rathke --- Code errors are evaluated during run time, not resulting in overall formula errors during compile time (with a few exceptions), hence if the faulty code is not executed in an IF() path no error occurs. Reason is that any error condition can be further evaluated using IFERROR() or ERROR.TYPE() or similar. If we stopped and set an error during compilation already that would not be possible or yield different results. What we maybe could do is catching the name error during formula cell input already, like is done for missing operators and operands and such. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 --- Comment #6 from Andreas Mantke --- I tested with 'Testingx' and 'Testing' remain highlighted after putting the before the 'x'. Thus I couldn't confirm your issue report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 --- Comment #5 from Adrian Thewlis --- Line break should be AFTER the space, not before. So text should be as follows: Testing X The trailing space, at the end of the line, doesn't hilite. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144252] Compatibility issues with cell summation formulas across worksheets
https://bugs.documentfoundation.org/show_bug.cgi?id=144252
--- Comment #6 from Eike Rathke ---
Fwiw, in test.xlsx for B3 the formula is saved as
SUM(1:10!B3:B3)
#NAME?
and apparently it was resaved after having been loaded and recalculated faulty
already (#NAME? error as value); not containing the $ absolute reference flag
is ok, as Excel does not know relative sheet references at all and sheet
references are always absolute.
Saving =SUM($'1'.B3:$'3'.B3) to .xlsx results in
SUM(1:10!B3:B3) as well so that part seems ok and
import as =SUM('1':$'10'.B3:B3) is broken.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 Andreas Mantke changed: What|Removed |Added CC||ma...@gmx.de --- Comment #4 from Andreas Mantke --- Tested it with 7.5.5.2 on Windows 10 and can't reproduce the behavior. If I follow your steps the space after 'Testing' remain highlighted after the line break before the 'x'. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156899] Designation of table rows as headers should be consistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156899 Eyal Rozenberg changed: What|Removed |Added Blocks||103100 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103100 [Bug 103100] [META] Writer table bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Eyal Rozenberg changed: What|Removed |Added Depends on||156899 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156899 [Bug 156899] Designation of table rows as headers should be consistent -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156899] Designation of table rows as headers should be consistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156899 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6455 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6899 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156899] Designation of table rows as headers should be consistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156899 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com, ||rb.hensc...@t-online.de --- Comment #1 from Eyal Rozenberg --- Note that the ODF spec defines very clearly and generally which rows are the headers: > The element represents header rows in a table. > It is composed of adjacent 9.1.3 elements. See here: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#__RefHeading__1415596_253892949 ... and everything should conform to that and affect that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #3 from raal --- No repro with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dedf098e742550622cec6fdc639550371d9e58cf CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130020] No warning displayed even if error/warning code was set when spreadsheet data fails to save to dBASE format
https://bugs.documentfoundation.org/show_bug.cgi?id=130020 --- Comment #12 from Eike Rathke --- I don't remember.. but assume it's resolved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156507] Ability to remove non-printing/"atypical" characters in a stretch of text
https://bugs.documentfoundation.org/show_bug.cgi?id=156507 --- Comment #9 from Eyal Rozenberg --- (In reply to خالد حسني from comment #7) > The notion here is fundamentally flawed, there is no such thing as exotic > characters in a multilingual and multicultural piece of software, this is > very monolingual way of thinking. It's not about what's not in a particular language. It's about what people don't generate with their keyboards. Yes, that could be different for every language; and if you can generate ZWNJ with a Persian keyboard - then ZWNJ is a poor example, or it should be considered atypical only in certain contexts. > Also, don’t copy text from PDF, that is your actual problem. PDF is not a > text exchange format, despite what PDF stakeholders want to sell people. But users have to copy text from PDFs, because they are provided PDFs rather than original editable documents, and they need the text. (In fact, sometimes, they need to edit the PDF in place.) Indeed, PDF is not a text exchange format, and PDF export code may and does add all sorts of non-printing characters, which users need to filter out. That's the motivating use case. (In reply to V Stuart Foote from comment #8) > expanded coverage for toggle display of non-printing and formatting > Unicode via +F10 That is unlikely to help - unless you start indicating which non-printing character is which, and then you have something like a source view, or a few-characters-per-line view, which doesn't look like the original text. I agree with Khaled's observation that question of what to filter out is non-trivial and language-dependent. But it is a (somewhat) common use-case to want to perform such filtering. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156899] New: Designation of table rows as headers should be consistent
https://bugs.documentfoundation.org/show_bug.cgi?id=156899 Bug ID: 156899 Summary: Designation of table rows as headers should be consistent Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com A table heading row is a table heading row. Specifically, if one marks certain rows as the header rows, for the purposes of repeating across pages - the formatting for header rows, applied when using "Table | AutoFormat Styles...", should apply to all of them. Similarly, any and all feature regarding table heading rows should respect the same number of rows recognized by AutoFormat and by Heading Rows Repeat. And - if being a header row is not already reflected in ODF - it should be. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99308] Amordegrc using obsolete values for degressive amortisation
https://bugs.documentfoundation.org/show_bug.cgi?id=99308 --- Comment #8 from Eike Rathke --- Came across this by chance.. changing some constants that exist for old Excel interoperability (as all the Analysis plugin functions are) most likely is not the way to go. Existing documents suddenly would calculate amortisation differently. Furthermore, changing them to a French standard (if I understood that document at all) would be even more unexpected. If at all, then a new function taking coefficients as arguments would be the way to go. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156455] Allow toggling repeating-header property of a row in row context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156455 --- Comment #19 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #18) > I don't think the rare use case justifies a context menu item. But Eyal > thinks so and the doer may decide. I would say the rare case - or no case at all - is what we currently have on the Table menu. That's a confusing toggle which people now use because that's the only UI there is (... ignoring the table properties dialog, which I believe very few users know holds this setting as well). I claim it is the intuitive thing, when you want to act on a row (or a set of rows), to enter its context menu. More intuitive than going to the Table menu. On a semi-related note: If we had proper table styles (bug 152711), which included/linked to heading row styles, then the user would get an immediate visual indication of such toggling; and it would also be easier for the user to understand which rows they can toggle into or out of the set of heading rows. -- You are receiving this mail because: You are the assignee for the bug.
