[Libreoffice-bugs] [Bug 140265] Emoji selector takes too long to load and respond
https://bugs.documentfoundation.org/show_bug.cgi?id=140265 خالد حسني changed: What|Removed |Added CC||kha...@aliftype.com OS|All |Linux (All) --- Comment #10 from خالد حسني --- It seems that most of the time is spent in glyph fallback, which matches my experience that the font the emoji widget sets is unused and the default font is used and then glyph fallback is used to select fonts with emoji and this seems to be extremely slow on Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140265] Emoji selector takes too long to load and respond
https://bugs.documentfoundation.org/show_bug.cgi?id=140265 خالد حسني changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #9 from خالد حسني --- *** Bug 136922 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 136922] Emoji selector is slow
https://bugs.documentfoundation.org/show_bug.cgi?id=136922 خالد حسني changed: What|Removed |Added Resolution|--- |DUPLICATE CC||kha...@aliftype.com Status|NEW |RESOLVED --- Comment #9 from خالد حسني --- *** This bug has been marked as a duplicate of bug 140265 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150922] Default Arabic style names have a gratuitous definite article marker
https://bugs.documentfoundation.org/show_bug.cgi?id=150922 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 150916] Bibliography entry creation does not update type if selected from dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=150916 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 147672] Crash in: SwContentNode::GetAttr(SfxItemSet &) fails during Spell-Check Editing
https://bugs.documentfoundation.org/show_bug.cgi?id=147672 --- Comment #3 from QA Administrators --- Dear agencelivre, 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 150907] Capitalize not working after tamil content.
https://bugs.documentfoundation.org/show_bug.cgi?id=150907 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150907] Capitalize not working after tamil content.
https://bugs.documentfoundation.org/show_bug.cgi?id=150907 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147672] Crash in: SwContentNode::GetAttr(SfxItemSet &) fails during Spell-Check Editing
https://bugs.documentfoundation.org/show_bug.cgi?id=147672 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 140507] embedded pictures disappear when name changed
https://bugs.documentfoundation.org/show_bug.cgi?id=140507 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 140650] And easy the select a collection of shapes for grouping
https://bugs.documentfoundation.org/show_bug.cgi?id=140650 --- Comment #7 from QA Administrators --- Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140650] And easy the select a collection of shapes for grouping
https://bugs.documentfoundation.org/show_bug.cgi?id=140650 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 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Bug 103152 depends on bug 140507, which changed state. Bug 140507 Summary: embedded pictures disappear when name changed https://bugs.documentfoundation.org/show_bug.cgi?id=140507 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140507] embedded pictures disappear when name changed
https://bugs.documentfoundation.org/show_bug.cgi?id=140507 --- Comment #10 from QA Administrators --- Dear Dr. Matthias Weisser, 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 147773] FILEOPEN: Draw imports images with wrong size
https://bugs.documentfoundation.org/show_bug.cgi?id=147773 --- Comment #2 from QA Administrators --- Dear sekret, 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 96387] deadlock in HSQLDB
https://bugs.documentfoundation.org/show_bug.cgi?id=96387 --- Comment #4 from QA Administrators --- Dear Michael Stahl (CIB), 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 98491] Split hsqldb Base application will not start under OSX10.11.x causes LO to freeze requiring force kill
https://bugs.documentfoundation.org/show_bug.cgi?id=98491 --- Comment #17 from QA Administrators --- Dear jay Arr, 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 95191] Forms and dialogs opened via macros on ODB file open no longer work
https://bugs.documentfoundation.org/show_bug.cgi?id=95191 --- Comment #35 from QA Administrators --- Dear antonio, 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 88239] Impress: Wrong icon in new presentantions for changed default slide master in the slidemaster's pane in the sidebar.
https://bugs.documentfoundation.org/show_bug.cgi?id=88239 --- Comment #8 from QA Administrators --- Dear aprekates, 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 54930] EDITING Report builder: mouse-resize control allows to move top of control to out of section
https://bugs.documentfoundation.org/show_bug.cgi?id=54930 --- Comment #11 from QA Administrators --- Dear Lionel Elie Mamane, 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 87737] EDITING: Date-parameter in HSQLDB-queries don't work in UI-language, if parameter is only in subquery
https://bugs.documentfoundation.org/show_bug.cgi?id=87737 --- Comment #13 from QA Administrators --- Dear Robert Großkopf, 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 91814] Problem when copying large table with floating-point values from Calc to Base (HSQLDB)
https://bugs.documentfoundation.org/show_bug.cgi?id=91814 --- Comment #14 from QA Administrators --- Dear christian_kuhn, 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 36546] Internal HSQLDB 1.8 fails to cascade updates through multiple paths and deletions through some cyclic structures
https://bugs.documentfoundation.org/show_bug.cgi?id=36546 --- Comment #27 from QA Administrators --- Dear R.D.Nielsen, 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 53473] Embedded HSQLDB calls flush (CHECKPOINT) too often
https://bugs.documentfoundation.org/show_bug.cgi?id=53473 --- Comment #18 from QA Administrators --- Dear Lionel Elie Mamane, 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 136993] Unwanted scroll after pressing undo for moving frame in header
https://bugs.documentfoundation.org/show_bug.cgi?id=136993 --- Comment #2 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136540] Unwanted scroll when deleting all comments by an author
https://bugs.documentfoundation.org/show_bug.cgi?id=136540 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136131] FORMCONTROLS: Numerical & Formatted Field Form Controls Value Limits Don't Save User Inputs & Returns To Default +/- 1000000
https://bugs.documentfoundation.org/show_bug.cgi?id=136131 --- Comment #6 from QA Administrators --- Dear sims.316, 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 132888] Inconsistency with drag and drop and adding spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=132888 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132879] UI: The dialog always showing the "To frame" option, even when not applicable (see comment 1)
https://bugs.documentfoundation.org/show_bug.cgi?id=132879 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112628] Disable 'Header and Footer' when in master slide mode
https://bugs.documentfoundation.org/show_bug.cgi?id=112628 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 106336] EDITING: Copying column or row to another one with different width doesn't reposition image correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=106336 --- Comment #8 from QA Administrators --- Dear Thomas Lendo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100940] Clicking the right mouse button scrolls a page
https://bugs.documentfoundation.org/show_bug.cgi?id=100940 --- Comment #9 from QA Administrators --- Dear fiftyigfuci_f_mi, 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 151196] FORMATTING "MM/DD/YYYY HH:MM" won't wrap (wrapping uses pre-formatted data?)
https://bugs.documentfoundation.org/show_bug.cgi?id=151196 --- Comment #1 from Jim Avera --- Created attachment 182692 --> https://bugs.documentfoundation.org/attachment.cgi?id=182692=edit Small demo spreadsheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151196] New: FORMATTING "MM/DD/YYYY HH:MM" won't wrap (wrapping uses pre-formatted data?)
https://bugs.documentfoundation.org/show_bug.cgi?id=151196 Bug ID: 151196 Summary: FORMATTING "MM/DD/ HH:MM" won't wrap (wrapping uses pre-formatted data?) Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com Description: If a Calc cell has Alignment set to "wrap", a formatted date with time which contains a space should wrap at the space. But it does not wrap. Instead "###" appears. It is as if the text-wrapping machine works on the cell value before applying formatting, which in this case introduces a space where wrapping can occur. If that is true, then I think wrapping should use the post-formatted value. Steps to Reproduce: (Demo spreadsheet will be attached to this bug) 1. Format a cell with with the Number Format set to a Date form which introduces a space, for example format code MM/DD/YY HH:MM AM/PM (note space between date and time). 2. Set the "Alignment" format to "Wrap" 3. Increase the height of the cell to allow several lines to be visible. 4. Store a value in the cell, for example 9/10/11 12:13:14 4. Adjust the column width to be slightly too narrow for the entire date & time Actual Results: "###" appears in the cell Expected Results: Value should be wrapped, e.g. 09/10/11 12:13:14 Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.8.0.0+ Build ID: 71a3f015f2ac45ad4a2625a3b6398f5d75feed40 CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-6-4, Time: 2020-10-01_08:33:37 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151195] does not recognize characters
https://bugs.documentfoundation.org/show_bug.cgi?id=151195 --- Comment #1 from alphasquadsni...@gmail.com --- Created attachment 182691 --> https://bugs.documentfoundation.org/attachment.cgi?id=182691=edit picture of smashed minimization -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151195] New: does not recognize characters
https://bugs.documentfoundation.org/show_bug.cgi?id=151195 Bug ID: 151195 Summary: does not recognize characters Product: LibreOffice Version: 7.3.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alphasquadsni...@gmail.com Description: when highlighting columns, placing the cursor in between columns and double clicking to minimize them to character size. it doesn't recognize some of the characters and shrinks too far. Actual Results: when highlighting columns, placing the cursor in between columns and double clicking to minimize them to character size. it doesn't recognize some of the characters and shrinks too far. Expected Results: shrunk columns down so the information was just a "#" Reproducible: Always User Profile Reset: No Additional Info: Removed extra empty space after the information -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37967] VIEWING: Option like "MS WORD's normal view" needed
https://bugs.documentfoundation.org/show_bug.cgi?id=37967
--- Comment #23 from ero...@aol.com ---
How is Bug 121107 ("hide whitespace" not persistent) a duplicate of this bug?
Bug 121107 an independent bug of its own, whether on not one considers "hide
whitespace" to be a reasonable and adequate resolution of this bug 37967 -
'Option like "MS WORD's normal view" needed'
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109362] [META] Custom/object animation bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109362 Rafael Lima changed: What|Removed |Added Depends on||151173 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151173 [Bug 151173] Shadow appears before object entrance animation is scheduled -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151173] Shadow appears before object entrance animation is scheduled
https://bugs.documentfoundation.org/show_bug.cgi?id=151173 Rafael Lima changed: What|Removed |Added Blocks||109362 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109362 [Bug 109362] [META] Custom/object animation bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151173] Shadow appears before object entrance animation is scheduled
https://bugs.documentfoundation.org/show_bug.cgi?id=151173 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Rafael Lima --- Repro with Version: 7.2.6.2 / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: threaded And with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 8b5a989dcdcf4edd50c9fdb092d4180432ce4b6a CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded The red shadow is visible when you start the presentation (it should not be visible). Then the black text appears on click. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=61914 Rafael Lima changed: What|Removed |Added Depends on||151159 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151159 [Bug 151159] StartCenter: Document Filter: rename from `All Applications` to `All Documents` -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151159] StartCenter: Document Filter: rename from `All Applications` to `All Documents`
https://bugs.documentfoundation.org/show_bug.cgi?id=151159 Rafael Lima changed: What|Removed |Added Blocks||61914 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=61914 [Bug 61914] [META] Start Center bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151159] StartCenter: Document Filter: rename from `All Applications` to `All Documents`
https://bugs.documentfoundation.org/show_bug.cgi?id=151159 Rafael Lima changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #3 from Rafael Lima --- Let's hear the opinion of the UX team. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134941] Start screen is bigger than desktop resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=134941 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1194 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151194] VIEWING: Cannot maximize LO start center window when using low resolution screen
https://bugs.documentfoundation.org/show_bug.cgi?id=151194 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||4941 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151194] VIEWING: Cannot maximize LO start center window when using low resolution screen
https://bugs.documentfoundation.org/show_bug.cgi?id=151194 --- Comment #2 from Rafael Lima --- Created attachment 182690 --> https://bugs.documentfoundation.org/attachment.cgi?id=182690=edit Screenshot of Start Center on 1366 x 768 (with panel) I could NOT reproduce this with Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1 Calc: threaded I tested with a 1366 x 768 display on Kubuntu. The Start Center window maximized as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151156] Accessing Help - LibreOffice Help results in "File not found" error
https://bugs.documentfoundation.org/show_bug.cgi?id=151156 Rafael Lima changed: What|Removed |Added Summary|File not found |Accessing Help - ||LibreOffice Help results in ||"File not found" error -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151152] Autofilter checkbox status is wrong when I deselect one item, click OK, then click on the dropdown again (2nd case)
https://bugs.documentfoundation.org/show_bug.cgi?id=151152 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Rafael Lima --- Repro with Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1 Calc: threaded Also repro with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 8b5a989dcdcf4edd50c9fdb092d4180432ce4b6a CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded It does filter correctly though. But the "2020-01-4" entry remains checked in the AutoFilter even after unchecking it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151188] Area-Fill color in Sidebar is not selected on click on the 1st element
https://bugs.documentfoundation.org/show_bug.cgi?id=151188 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||0802 --- Comment #2 from Rafael Lima --- Isn't this related to bug 150802 ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151188] Area-Fill color in Sidebar is not selected on click on the 1st element
https://bugs.documentfoundation.org/show_bug.cgi?id=151188 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com Keywords||bibisectRequest Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Rafael Lima --- Repro with Version: 7.4.0.3 / LibreOffice Community Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: threaded Not repro with Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151194] VIEWING: Cannot maximize LO start center window when using low resolution screen
https://bugs.documentfoundation.org/show_bug.cgi?id=151194
tr_mail_...@t-online.de changed:
What|Removed |Added
Attachment #182689|Bottom part of main window |Bottom part of main window
description|hidden behind task bar |("help" and "extensions"
||buttons) hidden behind task
||bar
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151194] VIEWING: Cannot maximize LO start center window when using low resolution screen
https://bugs.documentfoundation.org/show_bug.cgi?id=151194 --- Comment #1 from tr_mail_...@t-online.de --- Created attachment 182689 --> https://bugs.documentfoundation.org/attachment.cgi?id=182689=edit Bottom part of main window hidden behind task bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151194] New: VIEWING: Cannot maximize LO start center window when using low resolution screen
https://bugs.documentfoundation.org/show_bug.cgi?id=151194 Bug ID: 151194 Summary: VIEWING: Cannot maximize LO start center window when using low resolution screen Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tr_mail_...@t-online.de Description: When starting LO 7.3 start center / main window (the window that shows the recently used documents) I cannot maximize this very window as apparently its minimum height is larger than the available size on my 1366x768 laptop screen. The lowest part of the window gets hidden behind my DEs task bar (see attached screenshot). The window is about ~38px too tall although there is plenty of free vertical space within the window. While this itself is a minor problem, the non-maximized state is taken over by every opened document such that, e.g., in a Calc document the status bar and sheets tabs will then as well be hidden behind the task bar. I always have to manually maximize the window after opening a document from start center. First observed this behavior after updating from version 7.2.7.5 to 7.3.6.2. Looks like the start center has been slightly rearranged in 7.3. See also this old thread, same problem with different version and even smaller resolution: https://ask.libreoffice.org/t/screen-too-small-for-libreoffice/18381 Operating system: - ArchLinux Desktop environment: - XFCE Steps to Reproduce: 1. Use screen with low resolution such as 1366x768 2. Start LibreOffice main window / start center Actual Results: Window does not start maximized and cannot be maximized Expected Results: Minimum window height should be smaller / window should be maximizable Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE 7.3.6-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 67544] FILESAVE: Slide transistion sound(other sound) is not included in presentation file
https://bugs.documentfoundation.org/show_bug.cgi?id=67544 YuNoH changed: What|Removed |Added CC||marsupilami...@gmail.com --- Comment #24 from YuNoH --- I had the same issue on LibreOffice Impress 7.3.6.2, custom transition sounds are only linked, and when sending the odp file to someone else (on another computer), the sound is gone. This is especially a big problem if you need to make a soundtrack to the slides, for a work you need to send to someone else. At least, it should be stated somewhere that files are only linked, to warn the user that the sound is not included in the .odp ... Because otherwise the user just notices the problem at the end of the work, which might cause him big troubles and annoyances. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151193] New: Couldn't establish data source connection when Java 18 is installed.
https://bugs.documentfoundation.org/show_bug.cgi?id=151193 Bug ID: 151193 Summary: Couldn't establish data source connection when Java 18 is installed. Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: other Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rajasekara...@gmail.com Created attachment 182688 --> https://bugs.documentfoundation.org/attachment.cgi?id=182688=edit Dialog box asking 32 -bit Java installation. Couldn't establish connection to the existing database file because LibreOffice Base asks 32-bit version of Java installation. But I already installed latest version(Java 18) 64-bit on my laptop. When I try to open the data base file,I get the following dialog box: "The connection to the data source "Test" couldn't be established. No Java installation could be found.Please check your installation." -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134408] Character transparency don't work properly in Writer and Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=134408 Leandro Martín Drudi changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #16 from Leandro Martín Drudi --- In the case of Writer: 7.4.1: Transparency with color Automatic, applies white font color. In Calc's case: 7.4.1: Transparency is not applied at all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134294] Chapter numbering not updated when heading added in between (until heading applied again or reload )
https://bugs.documentfoundation.org/show_bug.cgi?id=134294 Björn Michaelsen changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #14 from Björn Michaelsen --- (In reply to Timur from comment #13) > I set New again, as original steps from Description are reproduced for me in > 7.5+. > Test Build ID: bb47ffbc9d36e83695aa0d01767d3f83533c04e0, VCL: gtk3 ... which is not the current master at the time of my comment. That is older. This might be relevant as the fix for https://bugs.documentfoundation.org/show_bug.cgi?id=144939 came in after that and might also have fixed this one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147371] save icon misleading
https://bugs.documentfoundation.org/show_bug.cgi?id=147371 Adolfo Jayme Barrientos changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #9 from Adolfo Jayme Barrientos --- We already show the icon in a different way to signal when the document has unsaved changes; we just don’t do it by disabling the icon. You can see commit 22328a224df4619218b88205838307f70612207e for the rationale, but basically, we want to allow you to save the document whenever you want. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53976] XLS FILESAVE: File loses it's VBA functionality after saving in latest version(after 3.4)
https://bugs.documentfoundation.org/show_bug.cgi?id=53976 Justin L changed: What|Removed |Added Summary|Calc FILESAVE: File loses |XLS FILESAVE: File loses |it's VBA functionality |it's VBA functionality |after saving in latest |after saving in latest |version(after 3.4) |version(after 3.4) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100366] [META] Impress/Draw table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=100366 Rafael Lima changed: What|Removed |Added Depends on||151185 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151185 [Bug 151185] Impress: Table design icon without function -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151185] Impress: Table design icon without function
https://bugs.documentfoundation.org/show_bug.cgi?id=151185 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com Blocks||100366 --- Comment #2 from Rafael Lima --- This isn't a bug per se. The "Table Design" command simply opens the Table Design sidebar. If it is already open, then nothing happens. (In reply to Timur from comment #1) > But let's hear UX on changing this icon to dropdown with table designs. I'm not sure this would be the way to go, because the current implementation of Table Design needs a deeper rework. Basically, the available set of table styles is hardcoded (see bug 34391, bug 38213 and bug 74142). There's also bug 101802 that requests an integration of Table Design across Writer / Draw / Impress, which seems the better approach. So I believe that when these enhancements have been made, this bug report will be automatically fixed. The main question is whether any dev will take on these huge tasks. I am an avid user of Impress Tables and I can tell that table support in Impress/Draw is very lacking and buggy. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100366 [Bug 100366] [META] Impress/Draw table bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151192] Print Dialog Print Preview: Orientation of page changes after switching paper size to something different and back
https://bugs.documentfoundation.org/show_bug.cgi?id=151192 Telesto changed: What|Removed |Added Keywords||bibisectRequest --- Comment #1 from Telesto --- Changing paper size doesn't affect orientation with (with orientation set to automatic) Version: 6.4.0.0.beta1+ (x64) Build ID: e75dd1fc992f168f24d66595265a978071cdd277 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL Impossible to change paper size from LibreOffice Print Dialog Version: 6.2.9.0.0+ (x86) Build ID: 5f01fe15eb2661f1f9ce12d1d99dc2a705b462ee CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151192] New: Print Dialog Print Preview: Orientation of page changes after switching paper size to something different and back
https://bugs.documentfoundation.org/show_bug.cgi?id=151192 Bug ID: 151192 Summary: Print Dialog Print Preview: Orientation of page changes after switching paper size to something different and back Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Print Dialog Print Preview: Orientation of page changes after switching paper size to something different and back Steps to Reproduce: 1. Open Impress (empty sheet or template) 2. CTRL+P -> Preview Landscape (OK) 3. Change the suggested Paper Size from A4 to B5 (or something else) in the Print Dialog 4. Change the Paper Size back to A4 -> Print Preview in Portrait -> Should be Landscape, IMHO Actual Results: Portrait Expected Results: Landscape Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d3050ff4a1355f7ebd3d4e7ddc8fb64f2b8894dd CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151154] Change category "draw" in Template Manager and make it translatable
https://bugs.documentfoundation.org/show_bug.cgi?id=151154 --- Comment #6 from Laurent BP --- (In reply to Rafael Lima from comment #4) > This is exactly what I did. However, for it to take effect you need to be on > a clear user profile. You need to either be on safe mode or apply the "Reset > settings and user interface modifications" option to see the new category > name. You are so right! :-) Thanks, I feel better. I added some comments on your patch. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47295] Default paragraph style should be "Text body" and not "Default"
https://bugs.documentfoundation.org/show_bug.cgi?id=47295 --- Comment #42 from Telesto --- FWIW: I'm not a PS Style expert.. I'm not even sure if the below could be implemented at all (compatibility reasons). Only thinking out loud.. A) I surely grasp inconvenience mentioned in comment 30 comment 36. Where the order of actions has influence on the formatting. Terrible, IMHO B) Default Paragraph Style is actually "Master/Parent Paragraph Style" (like comment 5 points out). It's not a ordinary style, in principle it affects all other Paragraph Styles except if those other paragraphs explicitly define otherwise. Currently the 'Master/Parent Paragraph Style is set to be default too., C) There is the (taste) question: do you like the 'Text Body' formatting to be default.. comment 38 A way out would be to change Next Paragraph Style from headings and such to Default Paragraph Style instead of Text Body. However you likely into the issue at comment 22.. so no go If the current called Default Paragraph Style would be renamed Master Style or Parent Style. And a new Style introduced: a 'dummy' style: which would be an empty style.. so exact copy of Master Style or Parent Style (the current Default Paragraph Style), called yet Default Paragraph Style. And this style would be made default, instead of the Master Style: problem 22 would be gone. If you change Next Style to the 'future' Default Paragraph Style (instead of Text Body), the formatting difference would be gone as mentioned under A If you prefer different look you can modify the Default Paragraph Style (new), without affect all other styles. Sadly it's impossible to say: replace Default Paragraph Style (new) by say Text Body Style. Which would make it easy an existing PS style to something else of desire. Why would I manually configure the default Paragraph Style to match the specifications of Text Body. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151191] New: Libreoffice 7.4 crash on Mac OS M1+ when saving to csv or excel format
https://bugs.documentfoundation.org/show_bug.cgi?id=151191 Bug ID: 151191 Summary: Libreoffice 7.4 crash on Mac OS M1+ when saving to csv or excel format Product: LibreOffice Version: 7.4.1.2 release Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d...@davidroda.es Description: Libreoffice 7.4 crash on Mac OS M1+ when saving to csv or excel format Actual Results: Close the program and open in file recovery mode Expected Results: Close the program and open in file recovery mode Reproducible: Always User Profile Reset: No Additional Info: The csv file even if it closes if it ends up creating them but when it is xlsx it closes and does not create them, it creates a temporary file but does not create the xlsx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100100] Emoji toolbar control
https://bugs.documentfoundation.org/show_bug.cgi?id=100100 V Stuart Foote changed: What|Removed |Added Depends on||144348 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144348 [Bug 144348] Remove bundled emoji font -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151122] Need way to avoid selecting fonts which don't cover the relevant language Unicode range
https://bugs.documentfoundation.org/show_bug.cgi?id=151122 --- Comment #15 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #13) > What bothers is the wish to get some very broad information at > a control that is simply a picker. But if we turn it around I just need to know the font I'm selecting covers my language(s). The title may overstate what's necessary, I've rephrased it. > unicode coverage does not match the paragraph language. There's a language choice underneath the picker - I believe it's better to go with that one. That can also allow the user to require coverage of multiple languages or no language. I haven't made up my mind regarding whether I like italicizing, graying-out or filtering-out better. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151122] Need way to avoid selecting fonts which don't cover the relevant language Unicode range
https://bugs.documentfoundation.org/show_bug.cgi?id=151122 Eyal Rozenberg changed: What|Removed |Added Summary|Need some indication of |Need way to avoid selecting |font (family) coverage |fonts which don't cover the |range when selecting fonts |relevant language Unicode ||range -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151122] Need some indication of font (family) coverage range when selecting fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=151122 --- Comment #14 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #11) > There are already some fabulous programs for doing font > selection based on its Unicode coverage. Point being > these font management features do not belong in an office > product bcz they are handled better either by os/DE > provided apps--eg fontconfig and the fc- utilities or the > ancient xfd or xfontsel, or by any number of GUI based > character map utilities including the GNOME Character Map. You seem to be suggesting LO remove its font selection dialog, or the font selection pane of the font dialog, entirely... Font selection belongs in (almost) any application in which the user needs to select fonts. And while complex font exploration may perhaps be better suited for a different app, it is not a complex or esoteric task to want to choose a font which can be used for the language you want to write in; and my office productivity app must help me avoid choosing fonts (or font families) which don't cover the language I'm making the choice for. > It has *ALL* the features that Eyal is asking for, I asked for just one thing. And I'm not even the one who asks for it; I would argue every user asks for it: Not misdirected into choosing an invalid font for the language I'm writing in. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151170] Need mechanism for re-centering "Slides pane" onto current slide with edit focus
https://bugs.documentfoundation.org/show_bug.cgi?id=151170 --- Comment #8 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #7) > NO it is strictly a feature request for the Slide / Page pane -- which > technically is a list as Heiko notes. Stuart is exactly right. (In reply to Heiko Tietze from comment #3) > Do we talk about what slide is the currently active - which is clearly shown > in the slides bar by highlighting Ah, but it isn't always. That is, the currently active slide is only shown in the slides bar if its scroll position is close enough to the slide's position. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148806] FILEOPEN: Event-Driven Macros don't enable in DOCM, or after round-tripping in DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=148806 --- Comment #11 from Justin L --- Created attachment 182687 --> https://bugs.documentfoundation.org/attachment.cgi?id=182687=edit formfieldMacros.docm: macro on fileOpen, checkbox1 click repro 7.5+ This is a FILEOPEN problem. Round-tripping this file still works fine in Excel. DOC format is a bit better than this. At least on initial file-open the checkbox1 and commandButton macros are working. LO doesn't work on a RT though. DOCX format has never worked in LO. ActiveX support first came in LO 6.0 via bug 50097, but event-macros were never working. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151172] LibODev crashed if Grammalect extension activated
https://bugs.documentfoundation.org/show_bug.cgi?id=151172 Julien Nabet changed: What|Removed |Added CC||momonas...@gmail.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9956 --- Comment #4 from Julien Nabet --- I noticed in bt "ImageOrientationController" and it's new from: dbeb697d62250e9429462c7f61b859893262a651 tdf#149956 Rework toolbar image flipping An unified code, covering both vcl and weld cases. For SidebarToolBox, the controller is created before items are inserted, so we listen for item insert event to set initially correct state. => cc Maxim -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151181] I can't find "Edit Style..." in the keyboard customization functions
https://bugs.documentfoundation.org/show_bug.cgi?id=151181 Nik Gervae changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151181] I can't find "Edit Style..." in the keyboard customization functions
https://bugs.documentfoundation.org/show_bug.cgi?id=151181 --- Comment #3 from Nik Gervae --- Okay, I found Edit and set its keyboard shortcut to command+alt+E, and when I press that, the Extension Manager window appears (see attachment). Setting the shortcut didn't do anything. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151181] I can't find "Edit Style..." in the keyboard customization functions
https://bugs.documentfoundation.org/show_bug.cgi?id=151181 --- Comment #2 from Nik Gervae --- Created attachment 182686 --> https://bugs.documentfoundation.org/attachment.cgi?id=182686=edit Keyboard shortcut set for "Edit" doesn't take -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151172] LibODev crashed if Grammalect extension activated
https://bugs.documentfoundation.org/show_bug.cgi?id=151172 Julien Nabet changed: What|Removed |Added Summary|LibODev crashed if |LibODev crashed if |gramalect extension |Grammalect extension |activated |activated -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151190] content control: picking date doesn't replace previous date
https://bugs.documentfoundation.org/show_bug.cgi?id=151190 --- Comment #1 from Justin L --- The example file was created in Excel 2010. I wonder if that tends to cause problems with our import compared to perhaps newer MSO output. Let me just add that a similar problem is seen with the check-boxes. They also duplicate instead of replacing each other. That also started in 7.4, with commit c53d3a1f4b8430507d54f5fac336870df7a700af Author: Miklos Vajna on Fri Apr 29 08:12:25 2022 +0200 sw content controls, checkbox: add DOCX import If these two are unrelated, a separate bug report can be split off to handle this - but I expect they end up being the same bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151172] LibODev crashed if gramalect extension activated
https://bugs.documentfoundation.org/show_bug.cgi?id=151172 Julien Nabet changed: What|Removed |Added CC||caol...@redhat.com Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||haveBacktrace --- Comment #3 from Julien Nabet --- Caolán: thought you might be interested in this crash in vcl part. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151172] LibODev crashed if gramalect extension activated
https://bugs.documentfoundation.org/show_bug.cgi?id=151172 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- Created attachment 182685 --> https://bugs.documentfoundation.org/attachment.cgi?id=182685=edit gdb bt On pc Debian x86-64 with master sources updated today, I got a crash when launching Writer (with tabs user interface) I noticed this log too when installing Grammalecte and afterwards warn:configmgr:110125:110125:configmgr/source/xcuparser.cxx:646: unknown property "Target" in "file:///home/julien/lo/libreoffice/instdir/program/../program/../user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/lu4570h.tmp/addons.xcu" BTW, it's quite strange the website indicates in red the current version is 2.1.1 (see https://grammalecte.net/#download) whereas it's 2.1.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151182] Calc crash when cut-paste and drag cell
https://bugs.documentfoundation.org/show_bug.cgi?id=151182 Julien Nabet changed: What|Removed |Added OS|Windows (All) |All Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||haveBacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151182] Calc crash when cut-paste and drag cell
https://bugs.documentfoundation.org/show_bug.cgi?id=151182 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- Created attachment 182684 --> https://bugs.documentfoundation.org/attachment.cgi?id=182684=edit gdb bt On pc Debian x86-64 with master sources updated today, I could reproduce this. Here's a quicker process to reproduce this: - launch Calc - select any cell - move the cursor at the right bottom of the cell (until seeing a cross instead of a standard mouse pointer) - click on the cell (when it's the cross) - move the mouse pointer without "unclicking" to left cell - unclick when in left cell -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151190] New: content control: picking date doesn't replace previous date
https://bugs.documentfoundation.org/show_bug.cgi?id=151190 Bug ID: 151190 Summary: content control: picking date doesn't replace previous date Product: LibreOffice Version: 7.4.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Keywords: bisected, filter:docx, implementationError Severity: minor Priority: low Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com, vmik...@collabora.com Blocks: 113363 Created attachment 182683 --> https://bugs.documentfoundation.org/attachment.cgi?id=182683=edit contentControlMacros.docm: example of macros modifying content controls The date control doesn't replace the existing contents when a new date is chosen. Broken with 7.4's commit 5ee8670f18cb8b1913a23d04590d6a31ac9730de Author: Miklos Vajna on Mon May 30 09:00:25 2022 +0200 sw content controls, date: add DOCX import This is all fairly new stuff. (Before it was mapped/converted into an activeX control? It worked fairly well, so this looks like a regression.) Marking as ImplementationError since this is work-in-progress. For example, one improvement of being a content control is that the dropdown disappears until the control is clicked on. To reproduce: A.) open contentControlMacros.docm (no need to enable macros) B.) change the date. Notice that "Click here to enter a date." is not replaced. Dates are just added on in front every time a change is made. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113363 [Bug 113363] [META] DOCX (OOXML) content control-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113363] [META] DOCX (OOXML) content control-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113363 Justin L changed: What|Removed |Added Depends on||151190 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151190 [Bug 151190] content control: picking date doesn't replace previous date -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144824] Em space not treated as normal space at end or start of line in justified text
https://bugs.documentfoundation.org/show_bug.cgi?id=144824 Peter Roelofsen 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 151187] Crash when exporting ODS file with Persian text to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151187 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | --- Comment #4 from Caolán McNamara --- its an assert, rather than a crash, so only visible in the NDEBUG dev builds -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144824] Em space not treated as normal space at end or start of line in justified text
https://bugs.documentfoundation.org/show_bug.cgi?id=144824 --- Comment #6 from Peter Roelofsen --- Created attachment 182682 --> https://bugs.documentfoundation.org/attachment.cgi?id=182682=edit New sample file with em space a the end of a line Edited sample file with em space at the end of a line. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144824] Em space not treated as normal space at end or start of line in justified text
https://bugs.documentfoundation.org/show_bug.cgi?id=144824 --- Comment #5 from Peter Roelofsen --- @Dieter: All em spaces appear in the middle of lines, where they don't do any harm. If you will copy & paste a few words to force an em space to the end of a line, you will see the problem is still there, even in version 7.4.1.2 Snap. Will upload a new sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151183] DATE spreadsheet function gives unexpected results for small year values, different from Excel
https://bugs.documentfoundation.org/show_bug.cgi?id=151183 --- Comment #6 from Eike Rathke --- (In reply to Mike Kaganski from comment #1) > OTOH, what Excel gives is also confusing: why "year 0" must mean 1900? If at > all, DATE(6;1;1) should give 0006-01-01 That's not confusing, Excel simply does not handle dates before its null-date 1900-01-01, at all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151183] DATE spreadsheet function gives unexpected results for small year values, different from Excel
https://bugs.documentfoundation.org/show_bug.cgi?id=151183 --- Comment #5 from Eike Rathke --- There's not much we can do about this. If we changed the two-digits year input window (for this function only) to 1900-1999 for a hard-wired Excel compatibility then documents that rely on the user's HOST-NULL-YEAR setup would break. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129208] Print to file with multiple copies produces only a single copy
https://bugs.documentfoundation.org/show_bug.cgi?id=129208 --- Comment #8 from Julien Nabet --- (In reply to Heiko Tietze from comment #7) > For sake of simplicity I'd disable the option. Don't see a good use case to > create multiple files. Ok for me but just to be sure here, it's not about creating multiple files but to generate a pdf (not several ones) containing n times (the number of copies) the content of a file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151184] Rendering defects (black horizontal lines) in Arabic/Persian text when exporting ODS to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151184 خالد حسني changed: What|Removed |Added OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151184] Rendering defects (black horizontal lines) in Arabic/Persian text when exporting ODS to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151184 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from خالد حسني --- I can’t reproduce this on master (crash aside, which I prevented temporarily locally), most likely it was fixed when bug 137528 was fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151074] LibreOffice from macOS appstore - can not create connection to mysql database via database creation wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=151074 Alex Thurgood changed: What|Removed |Added CC||cl...@documentfoundation.or ||g, ||heiko.tietze@documentfounda ||tion.org Summary|LibreOffice from macOS |LibreOffice from macOS |appstore - can not create |appstore - can not create |connection to mysql |connection to mysql |database|database via database ||creation wizard --- Comment #2 from Alex Thurgood --- @cloph, @heiko : any idea why the MySQL connection entry might be missing from the Apple AppStore release ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101912] [META] Accessibility (a11y) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101912 Bug 101912 depends on bug 117173, which changed state. Bug 117173 Summary: Search Dialog does not provide search results to Assistive Technology tools at 5.2 and later, results are recorded to GUI without accessible event as text in SetSearchLabel() https://bugs.documentfoundation.org/show_bug.cgi?id=117173 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 Bug 102847 depends on bug 117173, which changed state. Bug 117173 Summary: Search Dialog does not provide search results to Assistive Technology tools at 5.2 and later, results are recorded to GUI without accessible event as text in SetSearchLabel() https://bugs.documentfoundation.org/show_bug.cgi?id=117173 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117173] Search Dialog does not provide search results to Assistive Technology tools at 5.2 and later, results are recorded to GUI without accessible event as text in SetSearchL
https://bugs.documentfoundation.org/show_bug.cgi?id=117173 Michael Weghorn changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #22 from Michael Weghorn --- (In reply to Commit Notification from comment #19) > Jim Raykowski committed a patch related to this issue. > It has been pushed to "master": > > https://git.libreoffice.org/core/commit/ > 947fe0d89dee75ee43515ef7dfb43837d65a45bc > > tdf#119788 tdf#117173 add accessibility NOTIFICATION role That's the main commit, the ones from comment 18, comment 20 and comment 21 are related changes needed for qt6 and Windows in addition. -> Thanks, Jim! Closing as FIXED. (In reply to Samuel Thibault from comment #13) > Jamie, I don't know if the current 6.3 version with static role does get the > feedback spoken? As mentioned in > https://bugs.documentfoundation.org/show_bug.cgi?id=119788 , perhaps another > role would be needed for NVDA to consider speaking the text? At the moment, the ALERT role, together with an extra EVENT_SYSTEM_ALERT is used to make NVDA speak the notification text (which is what I observed was happening for browser alerts in Firefox and Edge), s. the commit from comment 21. If there's a better way to do it, input is welcome. macOS hasn't been tested yet, so any feedback from macOS users would also be welcome. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151187] Crash when exporting ODS file with Persian text to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151187 خالد حسني changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||caol...@redhat.com, ||kha...@aliftype.com Ever confirmed|0 |1 --- Comment #3 from خالد حسني --- Reproduced, you need to install the Vezir font (from bug 151184). CC Caolán, I think he was working on this code lately. Traceback: frame #0: 0x7ff81eed800e libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x7ff81ef0e1ff libsystem_pthread.dylib`pthread_kill + 263 frame #2: 0x7ff81ee59d24 libsystem_c.dylib`abort + 123 frame #3: 0x7ff81ee590cb libsystem_c.dylib`__assert_rtn + 314 * frame #4: 0x0001160c954f libvcllo.dylib`ImplSubPixelToLogic(bCheck=true, n=1661.4015748031495, nDPI=720, nMapNum=1, nMapDenom=2540) at map.cxx:290:5 frame #5: 0x0001160c92fc libvcllo.dylib`OutputDevice::SubPixelToLogic(this=0x00013041e000, rDevicePt=0x000191cd8310, bCheck=true) const at map.cxx:1189:18 frame #6: 0x00011631d53f libvcllo.dylib`vcl::PDFWriterImpl::drawHorizontalGlyphs(this=0x00013041e000, rGlyphs=size=22, rLine=0x7ff7bfef3ab8, rAlignOffset=0x7ff7bfef3880, bFirst=true, fAngle=0, fXScale=1, fSkew=0, nFontHeight=353, nPixelFontHeight=100) at pdfwriter_impl.cxx:6377:23 frame #7: 0x00011631b729 libvcllo.dylib`vcl::PDFWriterImpl::drawLayout(this=0x00013041e000, rLayout=0x63b3da40, rText=0x62776000, bTextLines=true, bCheckSubPixelToLogic=true) at pdfwriter_impl.cxx:6750:17 frame #8: 0x00011631fd40 libvcllo.dylib`vcl::PDFWriterImpl::drawTextArray(this=0x00013041e000, rPos=0x62775ff0, rText=0x62776000, pDXArray=span @ 0x7ff7bfef3bf0, pKashidaArray=(data_ = 0x, size_ = 0), nIndex=0, nLen=22) at pdfwriter_impl.cxx:6962:9 frame #9: 0x0001162c11ff libvcllo.dylib`vcl::PDFWriter::DrawTextArray(this=0x7ff7bfef6438, rStartPt=0x62775ff0, rStr=0x62776000, pDXAry=span @ 0x7ff7bfef3c88, pKashidaAry=(data_ = 0x, size_ = 0), nIndex=0, nLen=22) at pdfwriter.cxx:89:22 frame #10: 0x0001162c75b0 libvcllo.dylib`vcl::PDFWriterImpl::playMetafile(this=0x00013041e000, i_rMtf=0x7ff7bfef56a0, i_pOutDevData=0x7ff7bfef63a8, i_rContext=0x7ff7bfef56f8, pDummyVDev=0x000191cd6060) at pdfwriter_impl2.cxx:816:34 frame #11: 0x0001162c297a libvcllo.dylib`vcl::PDFWriter::PlayMetafile(this=0x7ff7bfef6438, i_rMTF=0x7ff7bfef56a0, i_rPlayContext=0x7ff7bfef56f8, i_pData=0x7ff7bfef63a8) at pdfwriter.cxx:466:22 frame #12: 0x0001a203bc53 libpdffilterlo.dylib`PDFExport::ImplExportPage(this=0x7ff7bfef6ca0, rWriter=0x7ff7bfef6438, rPDFExtOutDevData=0x7ff7bfef63a8, rMtf=0x7ff7bfef5c70) at pdfexport.cxx:1139:13 frame #13: 0x0001a203ae25 libpdffilterlo.dylib`PDFExport::ExportSelection(this=0x7ff7bfef6ca0, rPDFWriter=0x7ff7bfef6438, rRenderable=0x7ff7bfef6580, rSelection=0x7ff7bfef6558, rRangeEnum=0x7ff7bfef65a8, rRenderOptions=0x7ff7bfef63a0, nPageCount=1) at pdfexport.cxx:248:25 frame #14: 0x0001a2040f49 libpdffilterlo.dylib`PDFExport::Export(this=0x7ff7bfef6ca0, rFile=0x7ff7bfef6fc0, rFilterData=0x7ff7bfef6f38) at pdfexport.cxx:994:28 frame #15: 0x0001a20573d3 libpdffilterlo.dylib`PDFFilter::implExport(this=0x6276dd40, rDescriptor=0x7ff7bfef74d0) at pdffilter.cxx:185:24 frame #16: 0x0001a2057f6c libpdffilterlo.dylib`PDFFilter::filter(this=0x6276dd40, rDescriptor=0x7ff7bfef74d0) at pdffilter.cxx:248:23 frame #17: 0x00010936cf0a libsfxlo.dylib`SfxObjectShell::ExportTo(this=0x000191c323a0, rMedium=0x605fb860) at objstor.cxx:2494:25 frame #18: 0x000109368698 libsfxlo.dylib`SfxObjectShell::SaveTo_Impl(this=0x000191c323a0, rMedium=0x605fb860, pSet=0x) at objstor.cxx:1562:19 frame #19: 0x000109375ac9 libsfxlo.dylib`SfxObjectShell::PreDoSaveAs_Impl(this=0x000191c323a0, rFileName=0x7ff7bfef8d20, aFilterName=0x7ff7bfef9138, rItemSet=0x7ff7bfef99c8, rArgs=0x7ff7bfefa370) at objstor.cxx:2981:39 frame #20: 0x000109373ae8 libsfxlo.dylib`SfxObjectShell::CommonSaveAs_Impl(this=0x000191c323a0, aURL=0x7ff7bfef9150, aFilterName=0x7ff7bfef9138, rItemSet=0x7ff7bfef99c8, rArgs=0x7ff7bfefa370) at objstor.cxx:2771:9 frame #21: 0x000109346747 libsfxlo.dylib`SfxObjectShell::APISaveAs_Impl(this=0x000191c323a0, aFileName=(__data = u"file:///Users/khaled/Development/attic/attic/libreoffice/a%20Spressheet%20Test.pdf", __size = 82), rItemSet=0x7ff7bfef99c8, rArgs=0x7ff7bfefa370) at objserv.cxx:318:19 frame #22:
[Libreoffice-bugs] [Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK and GNOME Orca screen reader support
https://bugs.documentfoundation.org/show_bug.cgi?id=36549 Bug 36549 depends on bug 119788, which changed state. Bug 119788 Summary: a11y: Distinguish between role STATIC and new role NOTIFICATION https://bugs.documentfoundation.org/show_bug.cgi?id=119788 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117173] Search Dialog does not provide search results to Assistive Technology tools at 5.2 and later, results are recorded to GUI without accessible event as text in SetSearchL
https://bugs.documentfoundation.org/show_bug.cgi?id=117173 Bug 117173 depends on bug 119788, which changed state. Bug 119788 Summary: a11y: Distinguish between role STATIC and new role NOTIFICATION https://bugs.documentfoundation.org/show_bug.cgi?id=119788 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
