[Libreoffice-bugs] [Bug 154459] "Change three dots with ellipsis." is not correct English
https://bugs.documentfoundation.org/show_bug.cgi?id=154459 Buovjaga changed: What|Removed |Added Resolution|--- |FIXED CC||ilmari.lauhakangas@libreoff ||ice.org Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154459] "Change three dots with ellipsis." is not correct English
https://bugs.documentfoundation.org/show_bug.cgi?id=154459 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 154459] "Change three dots with ellipsis." is not correct English
https://bugs.documentfoundation.org/show_bug.cgi?id=154459 --- Comment #1 from Commit Notification --- Ilmari Lauhakangas committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/dictionaries/commit/ff606081bb42acb96611ff232f5606dd76f411bf tdf#154459 Improve grammar for hlp_ellipsis -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: dictionaries
dictionaries |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 1b52ec38dd338932255aa94411ad90f83ed02d9e Author: Ilmari Lauhakangas AuthorDate: Tue Apr 4 08:35:21 2023 +0300 Commit: Gerrit Code Review CommitDate: Tue Apr 4 07:35:21 2023 +0200 Update git submodules * Update dictionaries from branch 'master' to ff606081bb42acb96611ff232f5606dd76f411bf - tdf#154459 Improve grammar for hlp_ellipsis Change-Id: Ia488470069a9a4818dd3152250cc053842d161a2 Reviewed-on: https://gerrit.libreoffice.org/c/dictionaries/+/150006 Tested-by: Ilmari Lauhakangas Reviewed-by: Ilmari Lauhakangas diff --git a/dictionaries b/dictionaries index bcf7f049315d..ff606081bb42 16 --- a/dictionaries +++ b/dictionaries @@ -1 +1 @@ -Subproject commit bcf7f049315dee2001cc2f7c7eabfbcb0b8ef21a +Subproject commit ff606081bb42acb96611ff232f5606dd76f411bf
[Libreoffice-commits] dictionaries.git: en/dialog pt_BR/dialog
en/dialog/en_en_US.properties |2 +- pt_BR/dialog/pt_BR_en_US.properties |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) New commits: commit ff606081bb42acb96611ff232f5606dd76f411bf Author: Ilmari Lauhakangas AuthorDate: Tue Apr 4 08:25:03 2023 +0300 Commit: Ilmari Lauhakangas CommitDate: Tue Apr 4 07:35:20 2023 +0200 tdf#154459 Improve grammar for hlp_ellipsis Change-Id: Ia488470069a9a4818dd3152250cc053842d161a2 Reviewed-on: https://gerrit.libreoffice.org/c/dictionaries/+/150006 Tested-by: Ilmari Lauhakangas Reviewed-by: Ilmari Lauhakangas diff --git a/en/dialog/en_en_US.properties b/en/dialog/en_en_US.properties index c25a6e0..0e43ded 100644 --- a/en/dialog/en_en_US.properties +++ b/en/dialog/en_en_US.properties @@ -26,7 +26,7 @@ hlp_minus=Change hyphen characters to real minus signs. minus=Minus sign hlp_apostrophe=Change typewriter apostrophe, single quotation marks and correct double primes. apostrophe=Apostrophe -hlp_ellipsis=Change three dots with ellipsis. +hlp_ellipsis=Replace three dots with ellipsis. ellipsis=Ellipsis others=Others hlp_metric=Measurement conversion from \u00b0F, mph, ft, in, lb, gal and miles. diff --git a/pt_BR/dialog/pt_BR_en_US.properties b/pt_BR/dialog/pt_BR_en_US.properties index 41cfa0e..e029eb6 100644 --- a/pt_BR/dialog/pt_BR_en_US.properties +++ b/pt_BR/dialog/pt_BR_en_US.properties @@ -26,7 +26,7 @@ hlp_minus=Change hyphen characters to real minus signs. minus=Minus sign hlp_apostrophe=Change typewriter apostrophe, single quotation marks and correct double primes. apostrophe=Apostrophes -hlp_ellipsis=Change three dots with ellipsis. +hlp_ellipsis=Replace three dots with ellipsis. ellipsis=Ellipsis others=Others hlp_metric=Identify redundant terms: "criar novo", "subir para cima", "beco sem sa\u00EDda", "regra geral".
[Libreoffice-bugs] [Bug 141148] FILESAVE RTF Table border width changes upon save
https://bugs.documentfoundation.org/show_bug.cgi?id=141148 --- Comment #3 from Buovjaga --- Still repro Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 56ae7d01505fdae421109cfc78449230ba589d79 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154244] Print and Print preview does not show Textbox second line if the text is a double line. Only shows and print the first line.
https://bugs.documentfoundation.org/show_bug.cgi?id=154244 Lesline changed: What|Removed |Added CC||leslinetest...@gmail.com --- Comment #3 from Lesline --- Hello Georg. Thanks for reporting the bug. I was not able to reproduce it in the following version: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Kind Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154276] Missing Menue Entry in calc Libreoffice version 7.4.6.2
https://bugs.documentfoundation.org/show_bug.cgi?id=154276 Lesline changed: What|Removed |Added CC||leslinetest...@gmail.com --- Comment #3 from Lesline --- Hello Dietmar. Thank you for reporting the bug. I was not able to reproduce the bug. When I click on View > Freeze Cell, I see the submenu: Freeze First Column Freeze First Row The versions tested are as follows: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a834bbad8295cba0ca88a91a524aad48640271ec CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Kind Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154270] Colours reset to defaults
https://bugs.documentfoundation.org/show_bug.cgi?id=154270 Lesline changed: What|Removed |Added CC||leslinetest...@gmail.com --- Comment #3 from Lesline --- Hello Maison. Thank you for reporting the bug. I was not able to reproduce the bug using the following versions: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a834bbad8295cba0ca88a91a524aad48640271ec CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Kind Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154572] Scroll by mouse wheel not correctly when rows are fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=154572 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150759] [UI] Options are shown highlighted in dark gray when selecting file type in the Save As dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=150759 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154270] Colours reset to defaults
https://bugs.documentfoundation.org/show_bug.cgi?id=154270 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 154290] crash if I open page layout , under more options and under area tab , , clicking none crashes app
https://bugs.documentfoundation.org/show_bug.cgi?id=154290 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 154292] CALC becomes unstable depending upon the manner in which a block of assorted fonts is changed
https://bugs.documentfoundation.org/show_bug.cgi?id=154292 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 154272] "English Sentence Checking" options look cropped
https://bugs.documentfoundation.org/show_bug.cgi?id=154272 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 153537] FIELD DIALOG: Add possibility to assign character style to the field
https://bugs.documentfoundation.org/show_bug.cgi?id=153537 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153537] FIELD DIALOG: Add possibility to assign character style to the field
https://bugs.documentfoundation.org/show_bug.cgi?id=153537 --- Comment #13 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153537] FIELD DIALOG: Add possibility to assign character style to the field
https://bugs.documentfoundation.org/show_bug.cgi?id=153537 --- Comment #13 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153537] FIELD DIALOG: Add possibility to assign character style to the field
https://bugs.documentfoundation.org/show_bug.cgi?id=153537 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 150759] [UI] Options are shown highlighted in dark gray when selecting file type in the Save As dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=150759 --- Comment #5 from QA Administrators --- Dear ferherlon, 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 58062] VIEWING: form of database too big for screen
https://bugs.documentfoundation.org/show_bug.cgi?id=58062 --- Comment #12 from QA Administrators --- Dear Horst, 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 144645] UI: Tooltip is squished/stretched and truncated on change
https://bugs.documentfoundation.org/show_bug.cgi?id=144645 --- Comment #7 from QA Administrators --- Dear Concerned User, 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 141148] FILESAVE RTF Table border width changes upon save
https://bugs.documentfoundation.org/show_bug.cgi?id=141148 --- Comment #2 from QA Administrators --- Dear Buovjaga, 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 122532] Some expressions' first letters eligible to be capitalized are not capitalized.
https://bugs.documentfoundation.org/show_bug.cgi?id=122532 --- Comment #5 from QA Administrators --- Dear ricky.tigg, 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 130056] Hyperlink format overridden by direct formatting when converting .ODT to .DOC/DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=130056 --- Comment #6 from QA Administrators --- Dear yoddle, 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 116244] FILEOPEN XLS: The xls importer should use the new anchor type
https://bugs.documentfoundation.org/show_bug.cgi?id=116244 --- Comment #6 from QA Administrators --- Dear Luke, 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 111736] Sidebars' underline popup always shows "(Without)" item as selected
https://bugs.documentfoundation.org/show_bug.cgi?id=111736 --- Comment #6 from QA Administrators --- Dear Tamás Zolnai, 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 106523] CALC discrepancies and gaps
https://bugs.documentfoundation.org/show_bug.cgi?id=106523 --- Comment #25 from QA Administrators --- Dear gmarco, 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 99222] While typing, some characters appear out of order from how they are typed.
https://bugs.documentfoundation.org/show_bug.cgi?id=99222 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||4255 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114255] Keystrokes sent in wrong order under high cpu load
https://bugs.documentfoundation.org/show_bug.cgi?id=114255 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=99 ||222 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125217] Replace Mozilla themes with a proprietary tool reusing the existing
https://bugs.documentfoundation.org/show_bug.cgi?id=125217 --- Comment #19 from Leandro Martín Drudi --- (In reply to Eyal Rozenberg from comment #18) > I don't understand what this bug is about: > > 1. LO is a FOSS project; why do we need proprietary tools? > 2. What Mozilla themes? We use Mozilla themes? Perhaps you mean Mozilla-like > theming? > 3. "reuse the existing" - existing what? themes? dialog? Do you really think that your comment contributes something to the issue? A constructive opinion can be useful, but a comment where only by technicalities you reject something that has been perfectly clarified does not contribute anything and obstructs an effective communication. The report has been here for years because it was proposed to use LibO tools to make themes to replace Mozilla Themes as they were used until a few years ago. If you want more information, read the previous posts and comment something constructive. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154594] New: LibreOffice quickstarter option deselected after every update
https://bugs.documentfoundation.org/show_bug.cgi?id=154594 Bug ID: 154594 Summary: LibreOffice quickstarter option deselected after every update Product: LibreOffice Version: 7.5.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: samm71...@gmail.com Description: every time I update libreoffice the option to to load libreoffice quickstarter durring system startup gets deselected Steps to Reproduce: 1.enable the setting to load quickstarter during startup (windows 11) 2.update libreoffice Actual Results: quickstarter is nolonger enabled Expected Results: kept the setting from the previous installation Reproducible: Always User Profile Reset: Yes Additional Info: this has happened for the last few updates, not sure when the issue began. Windows 11, and windows 10 are affected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144804] FILEOPEN DOCX Textbox anchored to paragraph wrapping an image disappears
https://bugs.documentfoundation.org/show_bug.cgi?id=144804 Justin L changed: What|Removed |Added Version|7.3.0.0 alpha0+ |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 67997] Wrapping arround a frame does not work when two frames are nearby
https://bugs.documentfoundation.org/show_bug.cgi?id=67997 Justin L changed: What|Removed |Added Hardware|Other |All --- Comment #20 from Justin L --- The following code change makes this bug report's documents seem to work better. However, it fails lots of unit tests, and some of those look awful. Our algorithms don't work good when the available space is very low - the 1 inch wrap minimum is easily ignored in many situations. https://gerrit.libreoffice.org/c/core/+/149897 Just providing this patch as a code pointer. Perhaps it - along with many other changes - could be part of a "new wrapping algorithm". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154577] Calc assumes blank cell has value of 1 instead of zero
https://bugs.documentfoundation.org/show_bug.cgi?id=154577 --- Comment #7 from BugMagnet --- Might it be possible then to have some alternative options to this? Perhaps when such a column is defined as being numeric, to then assume blank is to be 0 for function purposes. Or the option to populate the column with 0 then an option to hide the 0? As you might guess, I do not use spreadsheets much, so was not at all aware that this was common behavior for other apps also. It just seems not to be intuitive and I could imagine create some serious errors if one is to rely on the mathematical functions that operate this way. For me, since this is an isolated use, now that I am aware of this behavior, I can do a workaround for my purposes, such as pre-populating all the quantity cells with 0s, which would then be changed to positive digit(s) for the items to be ordered. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154590] document fonts changed when saved document reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=154590 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please attach a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154588] Exporting selection to PDF results in incorrect selection/exported PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154588 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please attach a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154587] FILEOPEN Calc doesn't open XLSX archive
https://bugs.documentfoundation.org/show_bug.cgi?id=154587 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 opens in excel. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c4a58634753a84b09f20f7271d6525a6656522d3 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 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #5 from V Stuart Foote --- I'm not saying dump the "functional" 'User Interface..' dialog pop-up on new profile use. As agreed/implmented for bug 137931 that remains acceptable. What is NOT acceptable is a Welcome dialog popped open from the UI, it would be far more efficient to open a web browser and link WiKi and tailored help content for getting users started. I am saying the 'User interface...' dialog is sufficient, anything more needs to go to the Tools -> Options dialog panels. That where the now defunct 'Personalization' panel would be a reasonable location to consolidate some of the emerging UI configuration decisions/settings that folks might like to adjust. Lots of opportunity to do something functional there. A Welcome screen though would just be "fluff" that new users/or on profile reset will be blow through, non-functional other than self-advertising and a waste of dev effort to implement/maintain that could be better spent elsewhere. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #5 from V Stuart Foote --- I'm not saying dump the "functional" 'User Interface..' dialog pop-up on new profile use. As agreed/implmented for bug 137931 that remains acceptable. What is NOT acceptable is a Welcome dialog popped open from the UI, it would be far more efficient to open a web browser and link WiKi and tailored help content for getting users started. I am saying the 'User interface...' dialog is sufficient, anything more needs to go to the Tools -> Options dialog panels. That where the now defunct 'Personalization' panel would be a reasonable location to consolidate some of the emerging UI configuration decisions/settings that folks might like to adjust. Lots of opportunity to do something functional there. A Welcome screen though would just be "fluff" that new users/or on profile reset will be blow through, non-functional other than self-advertising and a waste of dev effort to implement/maintain that could be better spent elsewhere. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #4 from Eyal Rozenberg --- (In reply to John Mills from comment #3) > "we WANT people to read the manual and spend time on forum, maillist, even > ASK on how to use/configure LibreOffice." > > This sounds incredibly elitist and not in the spirit of an inclusive > community. Well, we might _like_ users to do that, but it is unrealistic to assume they would. So we certainly can't _expect_ them to do so. Anyway, that's irrelevant, because it's a settled matter! I don't know why Stuart is opening this discussion up again. (And just think what would happen if LO became more popular, and 2 Billion people would start filling the mailing lists and IRC channels with mundane questions...) > This is very much the sentiment on "JRTFM" that you see hard-core > Linux types express to newbie users, I'm a hard-code Linux type and my slogan is: If the user needs to read the manual for basic usage, then the developer/UX designer has failed. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #4 from Eyal Rozenberg --- (In reply to John Mills from comment #3) > "we WANT people to read the manual and spend time on forum, maillist, even > ASK on how to use/configure LibreOffice." > > This sounds incredibly elitist and not in the spirit of an inclusive > community. Well, we might _like_ users to do that, but it is unrealistic to assume they would. So we certainly can't _expect_ them to do so. Anyway, that's irrelevant, because it's a settled matter! I don't know why Stuart is opening this discussion up again. (And just think what would happen if LO became more popular, and 2 Billion people would start filling the mailing lists and IRC channels with mundane questions...) > This is very much the sentiment on "JRTFM" that you see hard-core > Linux types express to newbie users, I'm a hard-code Linux type and my slogan is: If the user needs to read the manual for basic usage, then the developer/UX designer has failed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 5cc29848b78b6c5ab01aa7a66b1dd7caff5f9385 Author: Seth Chaiklin AuthorDate: Tue Apr 4 00:39:48 2023 +0200 Commit: Gerrit Code Review CommitDate: Tue Apr 4 00:39:48 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 17ff420d14f2d7289bcee4ce7c652b4dfeb5a4d9 - add missing < to embedvar Change-Id: Ief1b8c7f78f6756d178c70d27020f6b483abfb24 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/149977 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/helpcontent2 b/helpcontent2 index 1964fcaee644..17ff420d14f2 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 1964fcaee6441a576976a8730287ebd955f9128e +Subproject commit 17ff420d14f2d7289bcee4ce7c652b4dfeb5a4d9
[Libreoffice-commits] help.git: source/text
source/text/swriter/01/06060100.xhp |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 17ff420d14f2d7289bcee4ce7c652b4dfeb5a4d9 Author: Seth Chaiklin AuthorDate: Tue Apr 4 00:36:36 2023 +0200 Commit: Seth Chaiklin CommitDate: Tue Apr 4 00:39:47 2023 +0200 add missing < to embedvar Change-Id: Ief1b8c7f78f6756d178c70d27020f6b483abfb24 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/149977 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/source/text/swriter/01/06060100.xhp b/source/text/swriter/01/06060100.xhp index a9b76e745b..90e40aadbb 100644 --- a/source/text/swriter/01/06060100.xhp +++ b/source/text/swriter/01/06060100.xhp @@ -111,7 +111,7 @@ a,... aa,... aaa,... - embedvar href="text/shared/01/06050500.xhp#aaanumbering"/> +
[Libreoffice-bugs] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #3 from John Mills --- (In reply to V Stuart Foote from comment #1) > Why? We should NOT pester people with this kind of nonsense, we should > provide functional defaults that let them get on with using the application. > > If they choose to poke around with customization and personalization--fine! > > Bet we should not FORCE it on them, there are other documentation > avenues/getting started help that is more appropriate than an "in-your-face" > do this before you can start doing anything. > > The UI picker as evolved was sufficient, it hinted that the MUFFIN > assemblages were available as alternatives. Beyond that we WANT people to > read the manual and spend time on forum, maillist, even ASK on how to > use/configure LibreOffice. > > We don't need to do hand-holding to walk folks through it--that's just > insulting to even the average user. As a very experienced user of LibreOffice you certainly do not need "hand-holding" but for many users this would be incredibly useful. To attract new users to LibreOffice we need to meet them in the middle and provide some help in the beginning, then you can direct them to user manuals after. How many users of LibreOffice do you think go to the effort of what you advocate in your opening statement? "we WANT people to read the manual and spend time on forum, maillist, even ASK on how to use/configure LibreOffice." This sounds incredibly elitist and not in the spirit of an inclusive community. This is very much the sentiment on "JRTFM" that you see hard-core Linux types express to newbie users, which wasn't helpful 20 years ago and isn't helpful now when you wish to grow the LibreOffice community and bring FLOSS software to a market dominated by commercial corporations that restrict the essential freedom of users. We can do better. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #3 from John Mills --- (In reply to V Stuart Foote from comment #1) > Why? We should NOT pester people with this kind of nonsense, we should > provide functional defaults that let them get on with using the application. > > If they choose to poke around with customization and personalization--fine! > > Bet we should not FORCE it on them, there are other documentation > avenues/getting started help that is more appropriate than an "in-your-face" > do this before you can start doing anything. > > The UI picker as evolved was sufficient, it hinted that the MUFFIN > assemblages were available as alternatives. Beyond that we WANT people to > read the manual and spend time on forum, maillist, even ASK on how to > use/configure LibreOffice. > > We don't need to do hand-holding to walk folks through it--that's just > insulting to even the average user. As a very experienced user of LibreOffice you certainly do not need "hand-holding" but for many users this would be incredibly useful. To attract new users to LibreOffice we need to meet them in the middle and provide some help in the beginning, then you can direct them to user manuals after. How many users of LibreOffice do you think go to the effort of what you advocate in your opening statement? "we WANT people to read the manual and spend time on forum, maillist, even ASK on how to use/configure LibreOffice." This sounds incredibly elitist and not in the spirit of an inclusive community. This is very much the sentiment on "JRTFM" that you see hard-core Linux types express to newbie users, which wasn't helpful 20 years ago and isn't helpful now when you wish to grow the LibreOffice community and bring FLOSS software to a market dominated by commercial corporations that restrict the essential freedom of users. We can do better. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 132112] UI broken, Writer unusable when formula is wider than the page (gtk3, gen)
https://bugs.documentfoundation.org/show_bug.cgi?id=132112 --- Comment #5 from Caolán McNamara --- There is a certain glyph scaling factor (which varies with versions of freetype IIRC) where rendering fails and has reappeared over the years in different places. This sounds like that. The underlying freetype failure "poisons" the cairo case and no rendering takes place after entering the fail state. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #2 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #1) > Why? ... we should > provide functional defaults that let them get on with using the application. > > But we should not FORCE it on them, there are other documentation > avenues/getting started help that is more appropriate than an "in-your-face" > do this before you can start doing anything. We agreed we need to ask the user explicitly about some things on first startup. This is not my idea - I would have been fine with some default choices. But we had super-long discussions and arguments about the default UI which seem to have reached a wide agreement on doing this. As for the dark/light mode - that's more debatable, although many apps ask about this on startup. > We should NOT pester people with this kind of nonsense But we already pester people with nonsense on startup - with tip of the day. I have to apologize though, I wrote tooltip and meant to say tip of the day. > The UI picker as evolved was sufficient, it hinted that the MUFFIN > assemblages were available as alternatives. Beyond that we WANT people to > read the manual and spend time on forum, maillist, even ASK on how to > use/configure LibreOffice. If we decide the only thing to ask on startup is for a choice of UI mode, we could have the startup screen only contain that. > We don't need to do hand-holding to walk folks through it--that's just > insulting to even the average user. I don't believe that UI mode selection is insulting hand-holding. Other ideas, like choosing whether or not to show the sidebar, are silly hand-holding and I would agree with you on that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #2 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #1) > Why? ... we should > provide functional defaults that let them get on with using the application. > > But we should not FORCE it on them, there are other documentation > avenues/getting started help that is more appropriate than an "in-your-face" > do this before you can start doing anything. We agreed we need to ask the user explicitly about some things on first startup. This is not my idea - I would have been fine with some default choices. But we had super-long discussions and arguments about the default UI which seem to have reached a wide agreement on doing this. As for the dark/light mode - that's more debatable, although many apps ask about this on startup. > We should NOT pester people with this kind of nonsense But we already pester people with nonsense on startup - with tip of the day. I have to apologize though, I wrote tooltip and meant to say tip of the day. > The UI picker as evolved was sufficient, it hinted that the MUFFIN > assemblages were available as alternatives. Beyond that we WANT people to > read the manual and spend time on forum, maillist, even ASK on how to > use/configure LibreOffice. If we decide the only thing to ask on startup is for a choice of UI mode, we could have the startup screen only contain that. > We don't need to do hand-holding to walk folks through it--that's just > insulting to even the average user. I don't believe that UI mode selection is insulting hand-holding. Other ideas, like choosing whether or not to show the sidebar, are silly hand-holding and I would agree with you on that. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #1 from V Stuart Foote --- Why? We should NOT pester people with this kind of nonsense, we should provide functional defaults that let them get on with using the application. If they choose to poke around with customization and personalization--fine! Bet we should not FORCE it on them, there are other documentation avenues/getting started help that is more appropriate than an "in-your-face" do this before you can start doing anything. The UI picker as evolved was sufficient, it hinted that the MUFFIN assemblages were available as alternatives. Beyond that we WANT people to read the manual and spend time on forum, maillist, even ASK on how to use/configure LibreOffice. We don't need to do hand-holding to walk folks through it--that's just insulting to even the average user. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 --- Comment #1 from V Stuart Foote --- Why? We should NOT pester people with this kind of nonsense, we should provide functional defaults that let them get on with using the application. If they choose to poke around with customization and personalization--fine! Bet we should not FORCE it on them, there are other documentation avenues/getting started help that is more appropriate than an "in-your-face" do this before you can start doing anything. The UI picker as evolved was sufficient, it hinted that the MUFFIN assemblages were available as alternatives. Beyond that we WANT people to read the manual and spend time on forum, maillist, even ASK on how to use/configure LibreOffice. We don't need to do hand-holding to walk folks through it--that's just insulting to even the average user. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #26 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #22) Agree with John's comment about this. Also, let's move the discussion about possible welcome-dialog items other than UI selection to bug 154593. Stuart, remember that bringing up the UI selection dialog on first startup is the compromise we seem to have reached in the heated argument regarding the default choice of UI. Please let's not re-tread this again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #26 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #22) Agree with John's comment about this. Also, let's move the discussion about possible welcome-dialog items other than UI selection to bug 154593. Stuart, remember that bringing up the UI selection dialog on first startup is the compromise we seem to have reached in the heated argument regarding the default choice of UI. Please let's not re-tread this again. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151971] Crash in: rtl_uString_alloc when using some Sounds Like (Japanese)" settings (steps in comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=151971 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected Version|7.2.7.2 release |7.3.0.0.alpha1+ CC||sberg...@redhat.com --- Comment #8 from Stéphane Guillou (stragu) --- Bibisected in linux-64-7.3 repo to first bad commit 889b8ec958910846789e960b4ca30e8a79464092 which points to core commit: commit 04af4e4f55f3ef319a78edd4d0109e2e7eba90b6 author Stephan Bergmann Mon Sep 06 16:53:29 2021 +0200 committer Stephan Bergmann Thu Oct 14 19:50:30 2021 +0200 [API CHANGE] Fix all bad UNOIDL identifiers across offapi Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121725 Stephan, can you please have a look? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154572] Scroll by mouse wheel not correctly when rows are fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=154572
--- Comment #2 from stefan_lange...@t-online.de
---
I have tried by Git/bisect to find the commit causing the bug but I didn't
succeed to reproduce the behavior with the builds created by git: Also with the
most new ("Master") the behavior was still OK.
Therefore I have looked for the first build the bug can be reproduced with.
It is the build with the BuildId 676602a1a4e53e88d9f4664579497d534f6ae9c2
(published 2023-03-23).
With the previous build (BuildId b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41,
published 2023-03-19) the behavior was still OK.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #25 from Eyal Rozenberg --- (In reply to haevalencia from comment #20) > create a welcome screen dialog that includes relevant options to customize > on first use. (In reply to andreas_k from comment #21) > have the font stuff at a welcome wizard so the import of docx > files will be improved if Arial or some other fonts are selected. Andreas, Ha-Valencia - I've opened bug 154593 about a welcome screen/dialog, please continue the discussion about what should or should not appear on a welcome dialog over there. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #25 from Eyal Rozenberg --- (In reply to haevalencia from comment #20) > create a welcome screen dialog that includes relevant options to customize > on first use. (In reply to andreas_k from comment #21) > have the font stuff at a welcome wizard so the import of docx > files will be improved if Arial or some other fonts are selected. Andreas, Ha-Valencia - I've opened bug 154593 about a welcome screen/dialog, please continue the discussion about what should or should not appear on a welcome dialog over there. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #24 from John Mills --- I disagree with this part STuart: "Even the concept of "first startup" is a misnomer for the vast count of installations. Many distributions would never allow it to launch, and for folks doing their own installation--they'd blow through it on launch after install and NEVER see it again (even with the TOTD)." Linux users are very much in the minority of LO users, and how can you say with certainty Linux distros would stop this? If users have to make a choice then they can't "blow through it" as you say, especially with Windows and MacOS where this would be part of the installation essentially. Moving a first run "wizard" to a sub-selection of a user menu completely undermines the purposes of this request. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #24 from John Mills --- I disagree with this part STuart: "Even the concept of "first startup" is a misnomer for the vast count of installations. Many distributions would never allow it to launch, and for folks doing their own installation--they'd blow through it on launch after install and NEVER see it again (even with the TOTD)." Linux users are very much in the minority of LO users, and how can you say with certainty Linux distros would stop this? If users have to make a choice then they can't "blow through it" as you say, especially with Windows and MacOS where this would be part of the installation essentially. Moving a first run "wizard" to a sub-selection of a user menu completely undermines the purposes of this request. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 113195] [META] Japanese language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113195 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151971 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151971 [Bug 151971] Crash in: rtl_uString_alloc when using some Sounds Like (Japanese)" settings (steps in comment 7) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151971] Crash in: rtl_uString_alloc when using some Sounds Like (Japanese)" settings (steps in comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=151971 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Summary|Crash in: rtl_uString_alloc |Crash in: rtl_uString_alloc ||when using some Sounds Like ||(Japanese)" settings (steps ||in comment 7) Severity|normal |critical Status|UNCONFIRMED |NEW Keywords||bibisectRequest, regression Version|7.4.2.3 release |7.2.7.2 release Blocks||113195 Crash report or|["rtl_uString_alloc"] |["rtl_uString_alloc","libc. crash signature||so.6"] OS|Windows (All) |All --- Comment #7 from Stéphane Guillou (stragu) --- Crash reproduced with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d36145d7cf6ca4d6072d4ab0a709bb8fe866336c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded and: Version: 7.3.7.2 / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded But not in: Version: 7.2.7.2 / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded So it's a regression in 7.3. Steps to reproduce: After installing the ja langpack and running LO with the environment variable LC_ALL="ja_JP": 1. Open Calc 2. Open Find and Replace dialog 3. Tick "Sounds like (Japanese)" 4. Click on "Sounds" to open dialog. Tick an extra setting highlighted in red in Amber's PDF, for example "Ignore > Punctuation character", click OK. 5. Type "test" in search box, click "Find next" Results: Crash. Next time the "Sounds" dialog is opened, all options are ticked. Crash report: https://crashreport.libreoffice.org/stats/crash_details/16eacbb9-4588-48f8-b8bf-d224514a1a79 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113195 [Bug 113195] [META] Japanese language-specific CJK issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4593 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4593 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154593] Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 Eyal Rozenberg changed: What|Removed |Added CC||haevalen...@gmail.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7931 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154593] New: Show a "Welcome Screen" on first startup with appropriate info and choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154593 Bug ID: 154593 Summary: Show a "Welcome Screen" on first startup with appropriate info and choices Product: LibreOffice Version: 7.5.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com At the moment, when loading LibreOffice for the first time (or an LO module for the first time), we show a tooltip, just like on any other startup. That's not what we should do. We should have a welcome screen/dialog, for making some of the choices which new users should be forced to make explicitly. These include: * Selecting the default UI mode (see bug 137931; personally I don't think this is necessary, but the choice is a reasonable compromise in the long debate the debate regarding menus-vs-tabbed UI). * Choosing between Light Mode, Dark Mode and follow-the-desktop-environment's Light/Dark choice and may include other choices. This welcome screen might be module-specific or appear once for all of LO, I'm not sure which is the better idea. Also, it might have multiple screens to navigate, if we want the user to make multiple choices. A tooltip should appear on the second (or later?) and subsequent startup of each module. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=125823 John Mills changed: What|Removed |Added Depends on|137931 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137931 [Bug 137931] Show the UI selection dialog on first start-up -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 John Mills changed: What|Removed |Added Blocks|125823 | Keywords|needsUXEval | --- Comment #23 from John Mills --- There certainly is some growing momentum for this time "user wizard" which really would be very beneficial for end users of LibreOffice. As I wrote previously I would see this having the UI selection, something on light and dark mode, the fonts is a fantastic idea too and aid in interoperability. This is sorely what is needed with LibreOffice, in a world where Microsoft has >90% of the Office space this is a way to draw more users to FLOSS software. This first-run dialog could also be a way to steer users to where they can find online help, make donations, join forums and participate in the project. The key being that every user would see this. It only has to be a few choices that would be completed in under one minute. This could be the "angle" that marketers are looking for in a potential version 8. TDF could sell this as "LibreOffice is the world's most versatile Office suite and we are empowering our users to create something that works best for them, something the commercial competitors can't." Or something to that effect, the key being the user has the choice to customise LibreOffice to their own expectations. I can not see how those advocates of FLOSS software do not want to empower users by presenting to them some of the wonderful features that LibreOffice has to offer. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125823 [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 John Mills changed: What|Removed |Added Blocks|125823 | Keywords|needsUXEval | --- Comment #23 from John Mills --- There certainly is some growing momentum for this time "user wizard" which really would be very beneficial for end users of LibreOffice. As I wrote previously I would see this having the UI selection, something on light and dark mode, the fonts is a fantastic idea too and aid in interoperability. This is sorely what is needed with LibreOffice, in a world where Microsoft has >90% of the Office space this is a way to draw more users to FLOSS software. This first-run dialog could also be a way to steer users to where they can find online help, make donations, join forums and participate in the project. The key being that every user would see this. It only has to be a few choices that would be completed in under one minute. This could be the "angle" that marketers are looking for in a potential version 8. TDF could sell this as "LibreOffice is the world's most versatile Office suite and we are empowering our users to create something that works best for them, something the commercial competitors can't." Or something to that effect, the key being the user has the choice to customise LibreOffice to their own expectations. I can not see how those advocates of FLOSS software do not want to empower users by presenting to them some of the wonderful features that LibreOffice has to offer. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125823 [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 125217] Replace Mozilla themes with a proprietary tool reusing the existing
https://bugs.documentfoundation.org/show_bug.cgi?id=125217 --- Comment #18 from Eyal Rozenberg --- I don't understand what this bug is about: 1. LO is a FOSS project; why do we need proprietary tools? 2. What Mozilla themes? We use Mozilla themes? Perhaps you mean Mozilla-like theming? 3. "reuse the existing" - existing what? themes? dialog? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125217] Replace Mozilla themes with a proprietary tool reusing the existing
https://bugs.documentfoundation.org/show_bug.cgi?id=125217 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7931 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=125823 V Stuart Foote changed: What|Removed |Added Depends on||137931 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137931 [Bug 137931] Show the UI selection dialog on first start-up -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||5217 CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Blocks||125823 --- Comment #22 from V Stuart Foote --- Many of these additional UI theming ideas, including "first startup" would be more suitable to place on a substantially reworked Tools -> Options -> 'Personalization' panel--where dumping the old Mozilla theme crap, bug 125217, is long overdue. Much less so as changes to the the View -> 'User Interface...' dialog and the current UI picker. Even the concept of "first startup" is a misnomer for the vast count of installations. Many distributions would never allow it to launch, and for folks doing their own installation--they'd blow through it on launch after install and NEVER see it again (even with the TOTD). So, since it is in need of refactoring to dump the old Mozilla style UI theming, let's plan to do something useful with the 'Personalization' panel and assemble the useful UI controls there. Then the 'Personalize' dialog could then be linked from the View toolbar directly, or even linked from the 'User Interface...' dialog. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125823 [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||5217 CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Blocks||125823 --- Comment #22 from V Stuart Foote --- Many of these additional UI theming ideas, including "first startup" would be more suitable to place on a substantially reworked Tools -> Options -> 'Personalization' panel--where dumping the old Mozilla theme crap, bug 125217, is long overdue. Much less so as changes to the the View -> 'User Interface...' dialog and the current UI picker. Even the concept of "first startup" is a misnomer for the vast count of installations. Many distributions would never allow it to launch, and for folks doing their own installation--they'd blow through it on launch after install and NEVER see it again (even with the TOTD). So, since it is in need of refactoring to dump the old Mozilla style UI theming, let's plan to do something useful with the 'Personalization' panel and assemble the useful UI controls there. Then the 'Personalize' dialog could then be linked from the View toolbar directly, or even linked from the 'User Interface...' dialog. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125823 [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154270] Colours reset to defaults
https://bugs.documentfoundation.org/show_bug.cgi?id=154270 ady changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154270] Colours reset to defaults
https://bugs.documentfoundation.org/show_bug.cgi?id=154270 ady changed: What|Removed |Added Whiteboard|| --- Comment #2 from ady --- (In reply to maison from comment #1) > “Whiteboard: QA:needsComment” > What other comment is needed from the reporter? I can’t find an explanation > in the Whiteboard page. The steps are explained. The bug rather needs > someone to fix it. QA:needsComment is for QA, not for the reporter. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sw/source
sw/source/core/crsr/contentcontrolbutton.cxx |2 ++
1 file changed, 2 insertions(+)
New commits:
commit 3bf0727bb03f1b330e9c43f9f5d7eb3bced08e2e
Author: Caolán McNamara
AuthorDate: Mon Apr 3 17:08:42 2023 +0100
Commit: Adolfo Jayme Barrientos
CommitDate: Mon Apr 3 23:14:51 2023 +0200
tdf#152257 popup already launched, don't relaunch
Change-Id: I2503803b756fed179f6aa62cee2c549b6bc7c3c8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149974
Reviewed-by: Adolfo Jayme Barrientos
Tested-by: Jenkins
diff --git a/sw/source/core/crsr/contentcontrolbutton.cxx
b/sw/source/core/crsr/contentcontrolbutton.cxx
index 908d5f1bff01..0d805cb492c3 100644
--- a/sw/source/core/crsr/contentcontrolbutton.cxx
+++ b/sw/source/core/crsr/contentcontrolbutton.cxx
@@ -88,6 +88,8 @@ void SwContentControlButton::MouseButtonDown(const
MouseEvent&) { StartPopup();
void SwContentControlButton::StartPopup()
{
+if (m_xPopup) // tdf#152257 already launched, don't relaunch
+return;
LaunchPopup();
Invalidate();
}
[Libreoffice-bugs] [Bug 133560] FILEOPEN DOCX Direct font name/formatting not read from docx file for empty paragraph (last paragraph only) (fine for DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=133560
--- Comment #13 from Justin L ---
A total hack to is first add
+ xTextAppend->insertString(xCursor, OUString('\x200B')/*CHAR_ZWSP*/, false);
But of course unit tests fail all over the place when you do that.
You can't just delete the entire paragraph, because then you lose frames
anchored to it, like tdf112287, although why they are anchored to a paragraph
that is going to be deleted is beyond me.
I tried a bunch of random stuff, like trying to Exchange() the cursor, but all
to no effect.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154584] LibreOffice Writer frequently crashes when using LibreOfficeMath
https://bugs.documentfoundation.org/show_bug.cgi?id=154584 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Stéphane Guillou (stragu) --- If you get a crash reporter message afterwards or when restarting, please submit it and share the link it gives you. That would help a lot in pinpointing the issue. Please also check if the issue is reproducible while in Safe Mode (Help > Restart in Safe Mode > Continue in safe mode). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137931] Show the UI selection dialog on first start-up
https://bugs.documentfoundation.org/show_bug.cgi?id=137931 --- Comment #21 from andreas_k --- Big +1 for have the font stuff at a welcome wizard so the import of docx files will be improved if Arial or some other fonts are selected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135859] [META] Formula-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=135859 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||132112 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132112 [Bug 132112] UI broken, Writer unusable when formula is wider than the page (gtk3, gen) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151089] Formula with underbrace blocks slide display (when the formula contains more than 17 characters) (Cairo & FreeType?)
https://bugs.documentfoundation.org/show_bug.cgi?id=151089 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||2112 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132112] UI broken, Writer unusable when formula is wider than the page (gtk3, gen)
https://bugs.documentfoundation.org/show_bug.cgi?id=132112
Stéphane Guillou (stragu) changed:
What|Removed |Added
CC||caol...@redhat.com,
||stephane.guillou@libreoffic
||e.org
Blocks||135859
See Also||https://bugs.documentfounda
||tion.org/show_bug.cgi?id=15
||1089
Severity|normal |major
Summary|Maths Formula on|UI broken, Writer unusable
|Libreoffice writer |when formula is wider than
||the page (gtk3, gen)
Version|6.4.2.2 release |6.2.0.3 release
--- Comment #4 from Stéphane Guillou (stragu)
---
I could reproduce the issue with creating a formula that overflows the page
width:
Steps:
1. Open Writer
2. Insert > Object > Formula
3. Paste in formula editor:
{}
underbrace {vec v_e}
Result: Formula area is a grey block, many parts of the UI disappear. Even
though parts of the UI still can be interacted with, Writer is unusable.
This happens with gtk3 VCL.
With the gen VCL, the UI is completely unresponsive.
No issue with gtk2 nor with kf5 VCLs.
Console warnings for gtk3 (unique lines):
warn:vcl.gdi:77103:77103:vcl/source/outdev/font.cxx:1083: Font fallback to the
same font, but has missing codes
warn:legacy.osl:77103:77103:starmath/source/rect.cxx:81: GetTextBoundRect
failed
warn:starmath:77103:77103:starmath/source/rect.cxx:226: Ooops... (Font
missing?)
warn:vcl:77103:77103:vcl/unx/generic/gdi/cairotextrender.cxx:394: rendering
text failed with stretch ratio of: 428, error occurred in libfreetype
warn:vcl:77103:77103:vcl/unx/generic/gdi/cairotextrender.cxx:394: rendering
text failed with stretch ratio of: 10, error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'GtkDrawingArea': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'ImmobilizedViewport': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'GtkScrolledWindow': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'GtkBox': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'GtkGrid': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'GtkViewport': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'OOoFixed': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'GtkEventBox': error occurred in libfreetype
(soffice:77103): Gtk-WARNING **: 22:36:24.573: drawing failure for widget
'GtkWindow': error occurred in libfreetype
Console warnings for gen (unique lines):
warn:vcl.layout:77307:77307:vcl/source/window/layout.cxx:2172: desired border
at paint 3 is larger than expected 2
warn:vcl.gdi:77307:77307:vcl/source/outdev/font.cxx:1083: Font fallback to the
same font, but has missing codes
warn:legacy.osl:77307:77307:starmath/source/rect.cxx:81: GetTextBoundRect
failed
warn:starmath:77307:77307:starmath/source/rect.cxx:226: Ooops... (Font
missing?)
warn:vcl:77307:77307:vcl/unx/generic/gdi/cairotextrender.cxx:394: rendering
text failed with stretch ratio of: 428, error occurred in libfreetype
warn:vcl:77307:77307:vcl/unx/generic/gdi/cairotextrender.cxx:394: rendering
text failed with stretch ratio of: 10, error occurred in libfreetype
warn:legacy.osl:77307:77307:xmloff/source/core/SettingsExportHelper.cxx:176:
this type is not implemented now
warn:legacy.osl:77307:77307:xmloff/source/text/txtparae.cxx:387: hyperlink
without a URL --> no export to ODF
warn:vcl:77307:77307:vcl/unx/generic/gdi/cairotextrender.cxx:394: rendering
text failed with stretch ratio of: 426, error occurred in libfreetype
The warnings that are not seen with kf5 are the Gtk-WARNINGs and
cairotextrender.cxx / libfreetypes ones, making it look similar to bug 151089.
Tested with:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d36145d7cf6ca4d6072d4ab0a709bb8fe866336c
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Caolán, thought you might be interested.
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=135859
[Libreoffice-bugs] [Bug 154577] Calc assumes blank cell has value of 1 instead of zero
https://bugs.documentfoundation.org/show_bug.cgi?id=154577 --- Comment #6 from ady --- This seems to be a matter of clear language and specific details. @BugMagnet, this is probably not what you expect from this function. I indeed understand, but... Let's assume cell A2 is empty or has text. This cell would then be "ignored" by this function means... =PRODUCT(A1,A2) would be equivalent to =PRODUCT(A1) which would be equivalent to cell A1 by itself. A cell without an explicit number (or an equivalent to an explicit number) being "ignored" implies that for a cell to be considered as having a zero, the cell needs to actually be zero or result in zero, not just empty. I do understand that, in terms of "common" arithmetic, this doesn't make much sense. Unfortunately, this is how this function is "defined" (although, possibly additional details in ODF might be welcome). This is the reason for this report to be set as NAB. FWIW, other spreadsheet tools work in the same way with this function. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154551] Cutting a caption from a frame results in crash
https://bugs.documentfoundation.org/show_bug.cgi?id=154551 --- Comment #5 from sdc.bla...@youmail.dk --- (In reply to Telesto from comment #4) > however I got a crash in same area Thanks. New (simpler) STR (also in Safe Mode). 1. Insert - Frame 2. (with frame still selected) Insert - Caption (add caption text and finish dialog). 3. (with frame still selected) Ctrl+X Crash. Additional information: 1. Does not crash if step 2 is skipped. 2. Not exactly the same STR as the OP, because now the frame is being deleted, not the caption. 3. Have also tested now with: 1. Insert - Image 2. Add caption 3. enter frame with image and caption, and select caption 4. Ctrl+X, Crash. (does not crash if image is deleted without deleting caption) 4. I thought this effect might be related to the recent patch (bug 154040) for not being able to make interactive frames, but my version of LO is prior to that patch, while your version is after. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 12ea66f132ae3894f336444ddf30a8f2579be503 Author: Adolfo Jayme Barrientos AuthorDate: Mon Apr 3 14:56:29 2023 -0600 Commit: Gerrit Code Review CommitDate: Mon Apr 3 22:56:29 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 1964fcaee6441a576976a8730287ebd955f9128e - Proofread and add missing markup Change-Id: I1269d775307dcc5ad022d5d99f640bfb778386fa Reviewed-on: https://gerrit.libreoffice.org/c/help/+/150001 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index 5041e95a2e38..1964fcaee644 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 5041e95a2e3804ded772be4b6d6a3d6d7f9e5039 +Subproject commit 1964fcaee6441a576976a8730287ebd955f9128e
[Libreoffice-commits] help.git: source/text
source/text/sdatabase/dabawiz02firebird.xhp | 36 +- source/text/simpress/01/bulletandposition.xhp |2 - source/text/swriter/01/05060900.xhp |2 - 3 files changed, 20 insertions(+), 20 deletions(-) New commits: commit 1964fcaee6441a576976a8730287ebd955f9128e Author: Adolfo Jayme Barrientos AuthorDate: Mon Apr 3 13:53:56 2023 -0600 Commit: Adolfo Jayme Barrientos CommitDate: Mon Apr 3 22:56:29 2023 +0200 Proofread and add missing markup Change-Id: I1269d775307dcc5ad022d5d99f640bfb778386fa Reviewed-on: https://gerrit.libreoffice.org/c/help/+/150001 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/source/text/sdatabase/dabawiz02firebird.xhp b/source/text/sdatabase/dabawiz02firebird.xhp index b2206ef395..bc1bb4a82f 100644 --- a/source/text/sdatabase/dabawiz02firebird.xhp +++ b/source/text/sdatabase/dabawiz02firebird.xhp @@ -30,58 +30,58 @@ Creating a new Firebird database file -Choose File - New - Database and select Connect to an existing database. Click on Next. +Choose File - New - Database and select Connect to an existing database. Click Next. -Click on Create. The Save as dialog opens. Enter a suitable name and location for the database file, and click on Save. The path of the new file is displayed in the wizard text box. Click Next. +Click Create. The Save As dialog opens. Enter a suitable name and location for the database file, and click Save. The path of the new file is displayed in the wizard’s text box. Click Next. -Optionally, enter your username and password. Click on Next. +Optionally, enter your username and password. Click Next. -Decide your preferred options about registered database and what to do with database once saved, and click Finish. Proceed entering a name to the new %PRODUCTNAME Base file. +Decide your preferred options about registered database and what to do with the database once saved, and click Finish. Proceed to enter a name for the new %PRODUCTNAME Base file. This name is the name of the new Firebird database file (*.fdb), not the name of the %PRODUCTNAME Base (*.odb) file. Connect to an existing Firebird database file -Choose File - New - Database and select Connect to an existing database. Click on Next +Choose File - New - Database and select Connect to an existing database. Click Next. -Click on Browse and navigate to select the Firebird file (*.fdb). Click on Open button, the complete URL to the database file is displayed in the text box. Click on Next. +Click Browse and select the Firebird file (*.fdb). Click the Open button; the full URL to the database file is displayed in the text box. Click Next. -Optionally, enter your username and password. Click on Next. +Optionally, enter your username and password. Click Next. -Decide your preferred options about database registration and what to do with database once saved, and click Finish. Proceed entering a name to the new %PRODUCTNAME Base file. +Decide your preferred options about database registration and what to do with database once saved, and click Finish. Proceed to enter a name for the new %PRODUCTNAME Base file. Connect directly to a Firebird server In addition to connections via JDBC and ODBC, you can connect to a Firebird server via the internal Firebird driver: -Choose File - New - Database and select Connect to an existing database. Click on Next +Choose File - New - Database and select Connect to an existing database. Click Next. -Manually enter the database connection URL in the text box. The pattern is servername/port:path_to_the_database, for example: -server1/3050:C:/data/mydatabase.fdb (note the “/” although it is a Windows path) -server1:C:/data/mydatabase.fdb (default port, Windows path) -localhost:/data/mydatabase.fdb (localhost server, default port, Linux path) -server1:mydata (default port, registered database) +Manually enter the database connection URL in the text box. The pattern is servername/port:path_to_the_database, for example: +server1/3050:C:/data/mydatabase.fdb (note the “/” although it is a Windows path) +server1:C:/data/mydatabase.fdb (default port, Windows path) +localhost:/data/mydatabase.fdb (localhost server, default port, Linux path) +server1:mydata (default port, registered database) -Click on Next. +Click Next. -Provide a suitable username and password required for the server connection. Test the connection (recommended) and fix the issues, if any. Click Next. +Provide a suitable username and password
[Libreoffice-commits] core.git: cui/uiconfig
cui/uiconfig/ui/bulletandposition.ui |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit c74117e400578348187113bcf191ccfd6deb2cce Author: Adolfo Jayme Barrientos AuthorDate: Sun Apr 2 19:32:59 2023 -0600 Commit: Adolfo Jayme Barrientos CommitDate: Mon Apr 3 22:53:47 2023 +0200 Hyphenate this compound adjective Change-Id: I7e19c90fd0106f59398205579d7b5d60cbf4a07e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149945 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/cui/uiconfig/ui/bulletandposition.ui b/cui/uiconfig/ui/bulletandposition.ui index 573babf76084..1dc7393ea531 100644 --- a/cui/uiconfig/ui/bulletandposition.ui +++ b/cui/uiconfig/ui/bulletandposition.ui @@ -699,7 +699,7 @@ True -Check this box to preserve the height to width ratio of the graphic bullet. +Check this box to preserve the height-to-width ratio of the graphic bullet.
[Libreoffice-bugs] [Bug 148321] FILEOPEN PPTX: text on top of circular object misplaced
https://bugs.documentfoundation.org/show_bug.cgi?id=148321 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2633 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109530] [META] File opening issues
https://bugs.documentfoundation.org/show_bug.cgi?id=109530 Bug 109530 depends on bug 152633, which changed state. Bug 152633 Summary: colleagues using MSO 365 can not open my .docx file https://bugs.documentfoundation.org/show_bug.cgi?id=152633 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150966] FILESAVE Editing this MSO file in LO Writer causes the header and footer contents to be corrupted
https://bugs.documentfoundation.org/show_bug.cgi?id=150966 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||tom1will...@yandex.com --- Comment #16 from Gabor Kelemen (allotropia) --- *** Bug 152633 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 152633] colleagues using MSO 365 can not open my .docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=152633 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com Status|NEW |RESOLVED See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8321 Resolution|--- |DUPLICATE --- Comment #14 from Gabor Kelemen (allotropia) --- bibisected in 7.3-win to: https://git.libreoffice.org/core/+/5319087ab75a01793462c8c41cebfa1996cc688a author Tomaž Vajngerl Mon Jun 06 22:53:23 2022 +0200 committer Miklos Vajna Fri Jun 10 13:10:36 2022 +0200 treebcd5374bde2e2d76f80bdaed2ff5ec9e52dc296e parent 054c248127c78521b4a4e7aacd8936bd54259996 [diff] tdf148321: convert OOXML inset values to text distance values But this affects only the 7.3 stable branch, not in 7.4.0 stable. This seems to have been solved in bug 150966 which is mentioned as followup in bug 148321. *** This bug has been marked as a duplicate of bug 150966 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Rafael Lima changed: What|Removed |Added Depends on||154592 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154592 [Bug 154592] When using multiple monitors, the hamburger menu popup opens on a different screen -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154592] When using multiple monitors, the hamburger menu popup opens on a different screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154592 Rafael Lima changed: What|Removed |Added Blocks||107237 --- Comment #2 from Rafael Lima --- I guess this bug only affects the tabbed UI. I believe a fix is possible, since the hamburger menu in the sidebar works fine in multi monitor setups. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153985] Horrible performance scrolling up with PgUp
https://bugs.documentfoundation.org/show_bug.cgi?id=153985 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6940 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146940] Libreoffice became increadibly slow on using emoticons
https://bugs.documentfoundation.org/show_bug.cgi?id=146940 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3985 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154269] FindReplaceRembemberdSearches not always used
https://bugs.documentfoundation.org/show_bug.cgi?id=154269 --- Comment #1 from maison --- “Whiteboard: QA:needsComment” What other comment is needed from the reporter? I can’t find an explanation in the Whiteboard page. The steps are explained. The bug rather needs someone to fix it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154270] Colours reset to defaults
https://bugs.documentfoundation.org/show_bug.cgi?id=154270 maison changed: What|Removed |Added Whiteboard| QA:needsComment| --- Comment #1 from maison --- “Whiteboard: QA:needsComment” What other comment is needed from the reporter? I can’t find an explanation in the Whiteboard page. The steps are explained. The bug rather needs someone to fix it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154551] Cutting a caption from a frame results in crash
https://bugs.documentfoundation.org/show_bug.cgi?id=154551 --- Comment #4 from Telesto --- (In reply to sdc.blanco from comment #3) Hmm. Still not able to repro the exact steps, however I got a crash in same area 1. Insert a shape. 2. Select shape, right-click, choose "Insert Caption" 3. Press with the caption frame selected CTRL+X (or select the caption within the frame) 4. Press CTRL+F4 or Red Close LibreOffice button 5. Don't save on warning -> Crash -- You are receiving this mail because: You are the assignee for the bug.
