[Libreoffice-bugs] [Bug 150902] (LibreOffice-Flatpak) "total editing time" is always 00:00:00
https://bugs.documentfoundation.org/show_bug.cgi?id=150902 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org --- Comment #7 from Stéphane Guillou (stragu) --- Can't reproduce with: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Flatpak Calc: threaded Installed it from Flathub: flatpak install flathub org.libreoffice.LibreOffice Ran it: flatpak run org.libreoffice.LibreOffice Edited for a few seconds, saved, Checked File > Properties, could see the editing time of a few seconds. Please test with the latest version and provide precise steps if you can still reproduce, along with the information in Help > About LibreOffice. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 65138] [META] Sidebar feature related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=65138 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||144813 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144813 [Bug 144813] Tabbed UI (drop down box) and sidebar options - rapid blinking/flashing when GTK_IM_MODULE=xim -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144813] Tabbed UI (drop down box) and sidebar options - rapid blinking/flashing when GTK_IM_MODULE=xim
https://bugs.documentfoundation.org/show_bug.cgi?id=144813 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||65138 Ever confirmed|0 |1 Summary|Tabbed UI (drop down box) |Tabbed UI (drop down box) |and sidebar options - rapid |and sidebar options - rapid |blinking/flashing. |blinking/flashing when ||GTK_IM_MODULE=xim Status|UNCONFIRMED |NEW Hardware|x86 (IA32) |All Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=65138 [Bug 65138] [META] Sidebar feature related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Fahad Al-Saidi changed: What|Removed |Added Depends on||151757 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151757 [Bug 151757] Changing the spacing of RTL tables messes up the spacing of the entire table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151757] Changing the spacing of RTL tables messes up the spacing of the entire table
https://bugs.documentfoundation.org/show_bug.cgi?id=151757 Fahad Al-Saidi changed: What|Removed |Added Blocks||43808 --- Comment #4 from Fahad Al-Saidi --- I confirm this bug. I am using Version: 7.4.3.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: ar-OM (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.4.3~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded As workaround set table direction to LTR do your format then set it back to RTL. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43808 [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 113afb4bc76acf93aec3f9c5917a67ececa43430 Author: Stanislav Horacek AuthorDate: Sun Jan 8 05:24:51 2023 +0100 Commit: Gerrit Code Review CommitDate: Sun Jan 8 04:24:51 2023 + Update git submodules * Update helpcontent2 from branch 'libreoffice-7-5' to 406cdee110dc4966fb2942f5319af3cb464df311 - do not localize source code Change-Id: I00c8b6014be077f78485e43cbe0f86f2c2f29c6c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145173 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos (cherry picked from commit 34e1fdb87700f1541ca5b15e3e3cfcd0dc5c2e98) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145126 diff --git a/helpcontent2 b/helpcontent2 index 989e68607954..406cdee110dc 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 989e6860795416236219c038f3708573054b5626 +Subproject commit 406cdee110dc4966fb2942f5319af3cb464df311
[Libreoffice-commits] help.git: Branch 'libreoffice-7-5' - source/text
source/text/sbasic/shared/03/sf_dialogcontrol.xhp | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
New commits:
commit 406cdee110dc4966fb2942f5319af3cb464df311
Author: Stanislav Horacek
AuthorDate: Sat Jan 7 20:47:23 2023 +0100
Commit: Adolfo Jayme Barrientos
CommitDate: Sun Jan 8 04:24:50 2023 +
do not localize source code
Change-Id: I00c8b6014be077f78485e43cbe0f86f2c2f29c6c
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145173
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
(cherry picked from commit 34e1fdb87700f1541ca5b15e3e3cfcd0dc5c2e98)
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145126
diff --git a/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
b/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
index 642acfeaa8..8ccd4e4218 100644
--- a/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
+++ b/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
@@ -86,13 +86,13 @@
Call SF_Exception.Clear
if you do not want the error to propagate after the dialog execution
ended.
In Python use native
try/except blocks for exception handling as shown
below:
-def
on_button_clicked(event=None):
-try:
-oControl =
CreateScriptService("DialogEvent", event)
+def
on_button_clicked(event=None):
+
try:
+
oControl = CreateScriptService("DialogEvent", event)
# Process the
event
-except Exception
as e:
+
except Exception as e:
# The object
"bas" below is an instance of the Basic service
-
bas.MsgBox(str(e))
+
bas.MsgBox(str(e))
Control types
The
DialogControl service is available for these control
types:
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 9b5c342121e8cc2d05569f7339bd32e9c8133938 Author: Stanislav Horacek AuthorDate: Sun Jan 8 05:23:48 2023 +0100 Commit: Gerrit Code Review CommitDate: Sun Jan 8 04:23:48 2023 + Update git submodules * Update helpcontent2 from branch 'master' to 34e1fdb87700f1541ca5b15e3e3cfcd0dc5c2e98 - do not localize source code Change-Id: I00c8b6014be077f78485e43cbe0f86f2c2f29c6c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145173 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index 2154d8b47552..34e1fdb87700 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 2154d8b47552c60c458e78f806a241dce721cbc5 +Subproject commit 34e1fdb87700f1541ca5b15e3e3cfcd0dc5c2e98
[Libreoffice-commits] help.git: source/text
source/text/sbasic/shared/03/sf_dialogcontrol.xhp | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
New commits:
commit 34e1fdb87700f1541ca5b15e3e3cfcd0dc5c2e98
Author: Stanislav Horacek
AuthorDate: Sat Jan 7 20:47:23 2023 +0100
Commit: Adolfo Jayme Barrientos
CommitDate: Sun Jan 8 04:23:47 2023 +
do not localize source code
Change-Id: I00c8b6014be077f78485e43cbe0f86f2c2f29c6c
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/145173
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
b/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
index d2045aa855..94bc90c3be 100644
--- a/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
+++ b/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
@@ -86,13 +86,13 @@
Call SF_Exception.Clear
if you do not want the error to propagate after the dialog execution
ended.
In Python use native
try/except blocks for exception handling as shown
below:
-def
on_button_clicked(event=None):
-try:
-oControl =
CreateScriptService("DialogEvent", event)
+def
on_button_clicked(event=None):
+
try:
+
oControl = CreateScriptService("DialogEvent", event)
# Process the
event
-except Exception
as e:
+
except Exception as e:
# The object
"bas" below is an instance of the Basic service
-
bas.MsgBox(str(e))
+
bas.MsgBox(str(e))
Control types
The
DialogControl service is available for these control
types:
[Libreoffice-bugs] [Bug 152655] Introduce a Slide/Page style category in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152655 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 152665] Fill cells (e.g. Fill down) not working on single-column/single-row selection discontinuous ranges of cells such as e.g. after applying autofilter (filtered cells)
https://bugs.documentfoundation.org/show_bug.cgi?id=152665 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152655] Introduce a Slide/Page style category in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152655 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152667] Wrong text encoding for file names and clip board under KDE x11
https://bugs.documentfoundation.org/show_bug.cgi?id=152667 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 152456] When deleting a character style that is in use to give user option to decide which style to apply to instances that use it
https://bugs.documentfoundation.org/show_bug.cgi?id=152456 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149763] Lots of Spaces get suppressed, when a Paragraph mark is added after this Sample
https://bugs.documentfoundation.org/show_bug.cgi?id=149763 --- Comment #12 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95940] Word sub-numbered sections (having the same style as first numbered sections..) lacks numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=95940 --- Comment #13 from QA Administrators --- Dear Tomáš Chvátal, 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 149907] Condition on the Standard Filter can not be Updated once added
https://bugs.documentfoundation.org/show_bug.cgi?id=149907 --- Comment #5 from QA Administrators --- Dear bugfree, 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 94504] Editing: strikethrough 'with X' on a bullet list make corrupted characters to appear
https://bugs.documentfoundation.org/show_bug.cgi?id=94504 --- Comment #17 from QA Administrators --- Dear palmierivinc.ent, 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 133558] Tracking changes storage isn't purged after rejecting changes
https://bugs.documentfoundation.org/show_bug.cgi?id=133558 --- 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 133554] Tracking changes pasting to multiple columns generates uses > 5 GB ram (without undo steps) and takes far to long
https://bugs.documentfoundation.org/show_bug.cgi?id=133554 --- 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 40270] Header border showing on PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=40270 --- Comment #18 from QA Administrators --- Dear Jonathan, 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 125687] Extreme memory usage opening/saving a large ODS with tracking changed enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=125687 --- 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 125792] Cutting a whole (empty) sheet while Tracking Changes takes a long time
https://bugs.documentfoundation.org/show_bug.cgi?id=125792 --- Comment #4 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 122802] Check-box is missing from opening menus of For Paragraph, For All Text.
https://bugs.documentfoundation.org/show_bug.cgi?id=122802 --- Comment #6 from QA Administrators --- Dear ricky.tigg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118118] external file links still chased even if entry containing them deleted (change tracking enabled)
https://bugs.documentfoundation.org/show_bug.cgi?id=118118 --- Comment #4 from QA Administrators --- Dear Ted Lee, 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 120917] Tab key at the beginning of heading has strange and inconsistent effects
https://bugs.documentfoundation.org/show_bug.cgi?id=120917 --- Comment #8 from QA Administrators --- Dear Kenneth Hanson, 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 122756] Unable to clone currency and other cell Number format in a Writer table
https://bugs.documentfoundation.org/show_bug.cgi?id=122756 --- Comment #3 from QA Administrators --- Dear Marina Latini (SUSE), 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 108933] Crash if I connect to a computer in the WiFi tab (android 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=108933 --- Comment #7 from QA Administrators --- Dear bug.reporter, 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 152655] Introduce a Slide/Page style category in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152655 --- Comment #2 from Eyal Rozenberg --- (In reply to Cor Nouws from comment #1) > Hi Eyal, > > How would your idea interfere with the possibilities offered by the existing > feature Master Slides? This is a fair question. In some senses, yes, but I believe we can think of it as "overlap" with the feature of Master Slides. Let me try and elaborate. I would say the master slide view is a lot like a way to edit slide styles by modifying a concrete slide. So, imagine instead of the dialog for character style dialog we had a box with a single character, and that we could use direct-formatting on that character - and the change would apply to every character associated somehow with that "master character". The analogy is not perfect, mostly because you can do other things on a master slide: * You can introduce drawing objects which are static on the slides with a chosen master. * You can position and format modifiable objects on the slide (e.g. the title area and content area), affecting default positions on the slides - that's not part of what I would consider the "slide style" but there are also things you can't do: * You can't have masters inherit from each other * Not all changes on the master slide apply to the slides using this master, and not just due to DF on those slides. (Although this non-application may be a bug; or it may only be limited to styling of the modifiable slide elements rather than styling of the slide itself) * Some changes you make to the master actually apply to all slides, e.g. slide dimensions Now, back to my suggestion that this could be an "overlap" rather than a clash - we could, for example, have the changes to the slide master automatically apply to a generated/induced slide style; and when setting a slide to have a certain master, have that master's slide style constitute the non-master slide's default slide style, to which it starts out as being set. One could of course go in the other direction, of having slide styles representing different masters, or limiting the scope of what you can do in masters with DF of the slide etc. - but I'm not sure what I think about that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152655] Introduce a Slide/Page style category in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152655 --- Comment #2 from Eyal Rozenberg --- (In reply to Cor Nouws from comment #1) > Hi Eyal, > > How would your idea interfere with the possibilities offered by the existing > feature Master Slides? This is a fair question. In some senses, yes, but I believe we can think of it as "overlap" with the feature of Master Slides. Let me try and elaborate. I would say the master slide view is a lot like a way to edit slide styles by modifying a concrete slide. So, imagine instead of the dialog for character style dialog we had a box with a single character, and that we could use direct-formatting on that character - and the change would apply to every character associated somehow with that "master character". The analogy is not perfect, mostly because you can do other things on a master slide: * You can introduce drawing objects which are static on the slides with a chosen master. * You can position and format modifiable objects on the slide (e.g. the title area and content area), affecting default positions on the slides - that's not part of what I would consider the "slide style" but there are also things you can't do: * You can't have masters inherit from each other * Not all changes on the master slide apply to the slides using this master, and not just due to DF on those slides. (Although this non-application may be a bug; or it may only be limited to styling of the modifiable slide elements rather than styling of the slide itself) * Some changes you make to the master actually apply to all slides, e.g. slide dimensions Now, back to my suggestion that this could be an "overlap" rather than a clash - we could, for example, have the changes to the slide master automatically apply to a generated/induced slide style; and when setting a slide to have a certain master, have that master's slide style constitute the non-master slide's default slide style, to which it starts out as being set. One could of course go in the other direction, of having slide styles representing different masters, or limiting the scope of what you can do in masters with DF of the slide etc. - but I'm not sure what I think about that. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152920] LO Writer: User Input fields in header or footer not visible in freshly opened documents
https://bugs.documentfoundation.org/show_bug.cgi?id=152920 Detlef Girke changed: What|Removed |Added CC||m...@dgirke.de --- Comment #1 from Detlef Girke --- Created attachment 184521 --> https://bugs.documentfoundation.org/attachment.cgi?id=184521=edit Bug Description with Screenshots. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148306] ToC column layout doesn't respect the page style's direction in a document imported from MS Word
https://bugs.documentfoundation.org/show_bug.cgi?id=148306 Eyal Rozenberg changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #8 from Eyal Rozenberg --- (In reply to Dieter from comment #7) > In a new document PS Contents 1 and Contents 2 have text direction "Use > superordinate object settings". So, if you change page direction to LTR, > direction of paragraphs also changes. This bug is not about the direction of paragraphs in the ToC, it's about the order of columns within the ToC. I think I made this clear in the subject and the description. Also, I do not know how to reproduce this, particularly not from scratch - but I reported this bug explicitly about documents imported from MS-Word. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147132] Flatten Basic function implementations
https://bugs.documentfoundation.org/show_bug.cgi?id=147132 Commit Notification changed: What|Removed |Added Whiteboard|target:7.4.0 target:7.5.0 |target:7.4.0 target:7.5.0 |reviewed:2022 target:7.6.0 |reviewed:2022 target:7.6.0 ||target:7.5.0.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147132] Flatten Basic function implementations
https://bugs.documentfoundation.org/show_bug.cgi?id=147132 --- Comment #11 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/fd5a4de7c39dc43b9668e77046622894cdd2051a Resolves: tdf#152917 Add ConvertFromUrl() put result back, tdf#147132 follow-up It will be available in 7.5.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - basic/source
basic/source/runtime/methods1.cxx |1 +
1 file changed, 1 insertion(+)
New commits:
commit fd5a4de7c39dc43b9668e77046622894cdd2051a
Author: Eike Rathke
AuthorDate: Sat Jan 7 20:29:38 2023 +0100
Commit: Eike Rathke
CommitDate: Sat Jan 7 22:42:38 2023 +
Resolves: tdf#152917 Add ConvertFromUrl() put result back, tdf#147132
follow-up
Regression from
commit 6b3e66cd7a355061bf1dec76bbc4f389b6b60f2d
CommitDate: Mon Sep 5 16:04:25 2022 +0200
tdf147132 basic : flaten some functions
Change-Id: I20e6b00ed613b98a5e58623a010d894b1bcb4c6f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145172
Reviewed-by: Eike Rathke
Tested-by: Jenkins
(cherry picked from commit e06198e1544f33419be4ce303458da8b5160bc1a)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145125
diff --git a/basic/source/runtime/methods1.cxx
b/basic/source/runtime/methods1.cxx
index 9e5356a6327b..b4f7dfb5fd9a 100644
--- a/basic/source/runtime/methods1.cxx
+++ b/basic/source/runtime/methods1.cxx
@@ -1419,6 +1419,7 @@ void SbRtl_ConvertFromUrl(StarBASIC *, SbxArray & rPar,
bool)
{
aSysPath = aStr;
}
+rPar.Get(0)->PutString(aSysPath);
}
[Libreoffice-bugs] [Bug 148306] ToC column layout doesn't respect the page style's direction in a document imported from MS Word
https://bugs.documentfoundation.org/show_bug.cgi?id=148306 Eyal Rozenberg changed: What|Removed |Added Summary|ToC column layout doesn't |ToC column layout doesn't |the page style's direction |respect the page style's |in a document imported from |direction in a document |MS Word |imported from MS Word -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152916] Error on Mendeley Citation
https://bugs.documentfoundation.org/show_bug.cgi?id=152916 V Stuart Foote changed: What|Removed |Added Component|Writer |Extensions Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- This cite-write .oxt extension from Medeley Desktop is Elsevier maintained. Check with them. IMHO => NOB -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152921] New: Sidebar deck is shown as open when closing with grey cross
https://bugs.documentfoundation.org/show_bug.cgi?id=152921 Bug ID: 152921 Summary: Sidebar deck is shown as open when closing with grey cross Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lob...@web.de Created attachment 184520 --> https://bugs.documentfoundation.org/attachment.cgi?id=184520=edit Sidebar deck shown open when closing The deck in the sidebar is shown as open when closing it with the grey cross. This happens every second time. Steps to Reproduce: 1. Open a Writer document 2. Click on any deck button for example navigator 3. Close the deck with the grey cross 4. Open the same deck with the deck button 5. Repeat step 4 and 5 (See attached video) This occurs in all LO applications. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 44355a90b3450111ad87ad4b6607a564e41d7b54 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152915] unwanted upper by lower case replacement
https://bugs.documentfoundation.org/show_bug.cgi?id=152915 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from V Stuart Foote --- Believe this is already provided via the AutoCorrect Options dialog (Tools -> AutoCorrect -> AutoCorrect Options, and on the "Exceptions" tab you'll see an element "Words with TWo INitial CApitals or sMALL iNITIAL" Please try that dialog to add an exception for your "HSt-STUMPF" string, help is available [1]. =-Ref-= [1] https://help.libreoffice.org/7.4/en-US/text/shared/01/06040300.html?=SHARED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152656] "Drawing Style" should be renamed "Drawing Object Style"
https://bugs.documentfoundation.org/show_bug.cgi?id=152656 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #2) > I never read "Drawing Style" as > something else but related to an object. A "drawing style" is a style of drawing. Just search for it and you'll see: https://duckduckgo.com/?t=ffab=%22drawing+style > Do we really need to change it? The world won't collapse if we don't, but that's not the question. The question is would it be better to change it than to keep the current term, and I claim that it would... I'll even make an AI-based argument! These days, if you tell an app to change the "drawing style", the association may be that you expect something to be re-rendered as impressionist, or cubist, or surrealist etc. :-P > The first item is "Default Drawing Style" and renaming it to "Default > Drawing Object Style" sounds wrong. That stems from the fact that these are styles of entities whose names have two words. Suppose we had styles for "self-sealing stem bolts". Then, the default style might be "Default self-sealing stem bolt style" - yes, a bit awkward, but that's what it would be. Now, as for this awkwardness - I can think of several ways to resolve this: 1. Call the default style "Default Object Style". The fact that it's a _Drawing_ object style would be understood from the context. 1. (More radical) Call the default style of every category of styles just "Default Style" or "(Default Style)". That would be more consistent, but might theoretically cause some kind of name clash problem. (Or not? I don't know.) 3. Call the default style "Default Drawing-Object Style". And similarly, "Default self-sealing-stem-bolt style" if we had styles for those. This guides the pronunciation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152656] "Drawing Style" should be renamed "Drawing Object Style"
https://bugs.documentfoundation.org/show_bug.cgi?id=152656 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #2) > I never read "Drawing Style" as > something else but related to an object. A "drawing style" is a style of drawing. Just search for it and you'll see: https://duckduckgo.com/?t=ffab=%22drawing+style > Do we really need to change it? The world won't collapse if we don't, but that's not the question. The question is would it be better to change it than to keep the current term, and I claim that it would... I'll even make an AI-based argument! These days, if you tell an app to change the "drawing style", the association may be that you expect something to be re-rendered as impressionist, or cubist, or surrealist etc. :-P > The first item is "Default Drawing Style" and renaming it to "Default > Drawing Object Style" sounds wrong. That stems from the fact that these are styles of entities whose names have two words. Suppose we had styles for "self-sealing stem bolts". Then, the default style might be "Default self-sealing stem bolt style" - yes, a bit awkward, but that's what it would be. Now, as for this awkwardness - I can think of several ways to resolve this: 1. Call the default style "Default Object Style". The fact that it's a _Drawing_ object style would be understood from the context. 1. (More radical) Call the default style of every category of styles just "Default Style" or "(Default Style)". That would be more consistent, but might theoretically cause some kind of name clash problem. (Or not? I don't know.) 3. Call the default style "Default Drawing-Object Style". And similarly, "Default self-sealing-stem-bolt style" if we had styles for those. This guides the pronunciation. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152920] New: LO Writer: User Input fields in header or footer not visible in freshly opened documents
https://bugs.documentfoundation.org/show_bug.cgi?id=152920 Bug ID: 152920 Summary: LO Writer: User Input fields in header or footer not visible in freshly opened documents Product: LibreOffice Version: 7.3.0.0.alpha1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@dgirke.de Description: Relates to bug 152919 (https://bugs.documentfoundation.org/show_bug.cgi?id=152919) After inserting User Input fields into header or footer the content of these fields isn´t visible when a document is freshly opened. F9 needs to be pressed to make them visible again. Steps to Reproduce: 1. Go to "Insert - Field - More Fields" or simply press CTRL+F2. 2. Select the Tab "Variables". 3. Select "User Field" on the left (box with the heading "Type"). 4. Fill out "Name" and "Value" afterwards. Then click on the green checkmark behind to save the new User field. 5. Select "Input field" under "Type". 6. Now you can insert the selected User field as an Input field into the document. You can do this as many times as you want. 7. Choose Insert - Header and Footer - Header 8. Insert the same User field as an Input field as described above. 9. Save an close the document. 10. Open the document. Actual Results: The User Input field in the header does not appear after the document was freshly opened. F9 needs to be pressed to make it appear again. Expected Results: All User Input fields are visible (and automatically update when they are edited as described in bug 152919) like in all Versions of LO until 7.2. Reproducible: Always User Profile Reset: Yes Additional Info: Affects to all versions of LO Writer since 7.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 152605] Change "outline level" to "heading level" in UI and help pages for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152605 --- Comment #8 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #5) > Yes, abbreviated "Chapter Numbering" label change of bug 107573 was a poor > decision, "Chapter and Outline Numbering" would have been better replacement > for "Outline Numbering" I disagree. I mean, it would have been a slight improvement, but adding the word "Chapters" is not the way to go: * "Heading and Outline Numbering" is the most, shall we say, explanatory and easy-to-understand - but rather long; * "Outline Numbering" and "Heading Numbering" each have their benefits, and none of them is perfect IMHO. I would be willing to live with any of them, so I'm ok with the change suggested here. * "Chapter Numbering" is entirely inappropriate, confusing and even silly, see my explanation in bug 141452. ... and the above goes for "XXX level" just as it does for "XXX numbering". sdc.blanco, please note that while bug 141452 asked for going back "Outline Numbering", that was only because that had been the previous name. I said I wouldn't mind it being "Heading Numbers" in bug 141452c26, at the bottom. So I would encourage you (and others) to reopen that bug and support it (perhaps changing the title to say Heading/Outline numbering). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152605] Change "outline level" to "heading level" in UI and help pages for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152605 --- Comment #8 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #5) > Yes, abbreviated "Chapter Numbering" label change of bug 107573 was a poor > decision, "Chapter and Outline Numbering" would have been better replacement > for "Outline Numbering" I disagree. I mean, it would have been a slight improvement, but adding the word "Chapters" is not the way to go: * "Heading and Outline Numbering" is the most, shall we say, explanatory and easy-to-understand - but rather long; * "Outline Numbering" and "Heading Numbering" each have their benefits, and none of them is perfect IMHO. I would be willing to live with any of them, so I'm ok with the change suggested here. * "Chapter Numbering" is entirely inappropriate, confusing and even silly, see my explanation in bug 141452. ... and the above goes for "XXX level" just as it does for "XXX numbering". sdc.blanco, please note that while bug 141452 asked for going back "Outline Numbering", that was only because that had been the previous name. I said I wouldn't mind it being "Heading Numbers" in bug 141452c26, at the bottom. So I would encourage you (and others) to reopen that bug and support it (perhaps changing the title to say Heading/Outline numbering). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152919] New: LO Writer: user input fields not updating automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=152919 Bug ID: 152919 Summary: LO Writer: user input fields not updating automatically Product: LibreOffice Version: 7.3.0.0.alpha1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@dgirke.de Description: I have a huge problem with LibreOffice 7.3 and above, which makes it unusable for me. I am working a lot with user input fields. The advantage is, that I can use them at as many positions inside the document as I like and they all update automatically when I change one of them. This worked until LibreOffice 7.2. Since LibreOffice 7.3 it´s broken. I have lots of documents using about 100 different user fields without problems until LibreOffice 7.2. Since LibreOffice 7.3 I need to press F9 to update them. Steps to Reproduce: 1. Go to "Insert - Field - More Fields" or simply press CTRL+F2. 2. Select the Tab "Variables". 3. Select "User Field" on the left (box with the heading "Type"). 4. Fill out "Name" and "Value" afterwards. Then click on the green checkmark behind to save the new User field. 5. Select "Input field" under "Type". 6. Now you can insert the selected User field as an Input field into the document. You can do this as many times as you want. Actual Results: Since LO 7.3 I need to press F9 to update them. This is annoying because I often forget it an my documents sometimes keep the wrong content when exporting them to PDF for example. Expected Results: Until LO 7.2, User fields inserted as Input fields with the same name were all updated automatically by editing one of them. Reproducible: Always User Profile Reset: Yes Additional Info: Affects all Versions of LO Writer since 7.3. -- You are receiving this mail because: You are the assignee for the bug.
problem with vml-shape-types file
Hi all, The vml-shape-types file is used, when a shape is exported to VML. If I understand it correctly, then this file is generated from presetShapeDefinitions.xml and presetTextWarpDefinitions.xml respectively by preset-definitions-to-shape-types.pl script. The file itself is located in /share/filter, not in repository (Why?). This file does not work for handles in Fontwork shapes. The problem is the position attribute of a handle: (A) The reference to the adjustment value is made by a reference to a formula (@), but it needs to be a reference to the adjustment value itself (#). (B) The positions left, right, top, bottom, center are written with numbers 0, 10800 and 21600. But it need to be topLeft, center, bottomRight. VML is needed for export of Fontwork shapes with fill other than solid or gradient, because such fill cannot be expressed with Words "abc Transform". Therefore I need a way to get correct VML shapetype markup for Fontwork shapes. There exist 40 types of Fontwork shapes in presetTextWarpDefinitions.xml. All of them have handles. There are 8 binary WordArt shapes, where the relationship to the shapes in presetTextWarpDefinitions.xml is unclear. I could manually make a file for the markup of the WordArt shapetypes and use that. I'm not familiar with Perl scripts. Better ideas or suggestions? BTW, Word uses VML WordArt, when it opens a doc file with binary WordArt or opens an odt file with custom-shape with textpath on. And it keeps it as VML, when converting the file to docx, even if it would be possible to use "abc Transform". But that is a -not jet fixed- import problem and not effected by the above mentioned file. Kine regards, Regina
[Libreoffice-bugs] [Bug 140657] LibreOffice Impress cannot page down or up, affects Zoom windows
https://bugs.documentfoundation.org/show_bug.cgi?id=140657 --- Comment #3 from Tammy --- I was unable to reproduce the following versions. I was unable to locate 7.0.1.3. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ec2f1d73936c9d8cee83c0887170e9ecb8f044ba CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.0.1.2 (x64) Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Verified by 1. Running a Zoom meeting. The Zoom version is 5.12.9 2. I Opened a PowerPoint with Libre Office on a couple of versions. 3. Navigate slides using the page up or down while in presentation mode and non-presentation mode while using the screen share in Zoom. 4. The keyboard controls display the zoom participant windows with no issues. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147132] Flatten Basic function implementations
https://bugs.documentfoundation.org/show_bug.cgi?id=147132 --- Comment #10 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e06198e1544f33419be4ce303458da8b5160bc1a Resolves: tdf#152917 Add ConvertFromUrl() put result back, tdf#147132 follow-up It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147132] Flatten Basic function implementations
https://bugs.documentfoundation.org/show_bug.cgi?id=147132 Commit Notification changed: What|Removed |Added Whiteboard|target:7.4.0 target:7.5.0 |target:7.4.0 target:7.5.0 |reviewed:2022 |reviewed:2022 target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: basic/source
basic/source/runtime/methods1.cxx |1 +
1 file changed, 1 insertion(+)
New commits:
commit e06198e1544f33419be4ce303458da8b5160bc1a
Author: Eike Rathke
AuthorDate: Sat Jan 7 20:29:38 2023 +0100
Commit: Eike Rathke
CommitDate: Sat Jan 7 20:28:55 2023 +
Resolves: tdf#152917 Add ConvertFromUrl() put result back, tdf#147132
follow-up
Regression from
commit 6b3e66cd7a355061bf1dec76bbc4f389b6b60f2d
CommitDate: Mon Sep 5 16:04:25 2022 +0200
tdf147132 basic : flaten some functions
Change-Id: I20e6b00ed613b98a5e58623a010d894b1bcb4c6f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145172
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/basic/source/runtime/methods1.cxx
b/basic/source/runtime/methods1.cxx
index 9e5356a6327b..b4f7dfb5fd9a 100644
--- a/basic/source/runtime/methods1.cxx
+++ b/basic/source/runtime/methods1.cxx
@@ -1419,6 +1419,7 @@ void SbRtl_ConvertFromUrl(StarBASIC *, SbxArray & rPar,
bool)
{
aSysPath = aStr;
}
+rPar.Get(0)->PutString(aSysPath);
}
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 Buovjaga changed: What|Removed |Added Assignee|tenanc...@gmail.com |libreoffice-b...@lists.free ||desktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 Anne changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |tenanc...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 --- Comment #14 from Alex Thurgood --- (In reply to Daniele from comment #13) > @Alex, sorry I copied from a previous message hastily and wrote it wrongly. > This is the path it was installed to: Macintosh > HD/Library/Java/JavaVirtualMachines > I am also attaching a screenshot of the details @Daniele, thanks for the update! Very strange that LO doesn't recognize the JDK there. That's exactly where all of mine are. The only other thing I can think of would be a permissions problem, possibly due to a recent macOS update? Sorry I can't be of more help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/uiwriter/data/cursor_position_after_undo.odt |binary
sw/qa/extras/uiwriter/uiwriter8.cxx | 41 ++
sw/source/core/edit/edundo.cxx|4 -
sw/source/uibase/inc/wrtsh.hxx| 12 +++-
sw/source/uibase/shells/basesh.cxx|2
5 files changed, 53 insertions(+), 6 deletions(-)
New commits:
commit 156fd06dbca2fcca3246dba964a58a7ef698cf21
Author: Jim Raykowski
AuthorDate: Tue Dec 27 10:00:01 2022 -0900
Commit: Jim Raykowski
CommitDate: Sat Jan 7 19:46:42 2023 +
Outline folding: Fix cursor position after undo redo
This patch makes the cursor position to be the same after undo redo as
when outline folding is not active.
Change-Id: I9e1f827455afb2675f3085c1560b1e2a246f4524
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144873
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sw/qa/extras/uiwriter/data/cursor_position_after_undo.odt
b/sw/qa/extras/uiwriter/data/cursor_position_after_undo.odt
new file mode 100644
index ..d6c300be61c0
Binary files /dev/null and
b/sw/qa/extras/uiwriter/data/cursor_position_after_undo.odt differ
diff --git a/sw/qa/extras/uiwriter/uiwriter8.cxx
b/sw/qa/extras/uiwriter/uiwriter8.cxx
index a5f41319c65f..42eaad1fb53a 100644
--- a/sw/qa/extras/uiwriter/uiwriter8.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter8.cxx
@@ -2547,6 +2547,47 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest8, testTdf151801)
CPPUNIT_ASSERT_EQUAL(sReplaced, getParagraph(1)->getString());
}
+CPPUNIT_TEST_FIXTURE(SwUiWriterTest8, testCursorPositionAfterUndo)
+{
+createSwDoc("cursor_position_after_undo.odt");
+SwDoc* pDoc = getSwDoc();
+SwWrtShell* pWrtShell = pDoc->GetDocShell()->GetWrtShell();
+
+// switch on "Outline Folding" mode
+dispatchCommand(mxComponent, ".uno:ShowOutlineContentVisibilityButton",
{});
+
CPPUNIT_ASSERT(pWrtShell->GetViewOptions()->IsShowOutlineContentVisibilityButton());
+
+// move the cursor to the beginning of the 3rd word in the 3rd paragraph,
"tincidunt"
+pWrtShell->FwdPara();
+pWrtShell->FwdPara();
+pWrtShell->Right(SwCursorSkipMode::Chars, /*bSelect=*/false, 16,
/*bBasicCall=*/false);
+
+// select the word
+dispatchCommand(mxComponent, ".uno:SelectWord", {});
+
+// check the word is select
+SwShellCursor* pShellCursor = pWrtShell->getShellCursor(false);
+CPPUNIT_ASSERT_EQUAL(OUString("tincidunt"), pShellCursor->GetText());
+
+// remember the cursor position for comparsion
+SwPosition aCursorPos(*pWrtShell->GetCursor()->GetPoint());
+
+// delete the selected word
+pWrtShell->Delete();
+
+// undo delete
+dispatchCommand(mxComponent, ".uno:Undo", {});
+
+// without the fix in place, the cursor would have been set to the start
of the outline node
+// - Expected: SwPosition (node 11, offset 25)
+// - Actual : SwPosition (node 9, offset 0)
+CPPUNIT_ASSERT_EQUAL(aCursorPos, *pWrtShell->GetCursor()->GetPoint());
+
+// switch off "Outline Folding" mode
+dispatchCommand(mxComponent, ".uno:ShowOutlineContentVisibilityButton",
{});
+
CPPUNIT_ASSERT(!pWrtShell->GetViewOptions()->IsShowOutlineContentVisibilityButton());
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/core/edit/edundo.cxx b/sw/source/core/edit/edundo.cxx
index 9516488cbc61..576b092214df 100644
--- a/sw/source/core/edit/edundo.cxx
+++ b/sw/source/core/edit/edundo.cxx
@@ -104,7 +104,7 @@ void
SwEditShell::HandleUndoRedoContext(::sw::UndoRedoContext & rContext)
void SwEditShell::Undo(sal_uInt16 const nCount, sal_uInt16 nOffset)
{
-MakeAllOutlineContentTemporarilyVisible a(GetDoc());
+MakeAllOutlineContentTemporarilyVisible a(GetDoc(), true);
CurrShell aCurr( this );
@@ -161,7 +161,7 @@ void SwEditShell::Undo(sal_uInt16 const nCount, sal_uInt16
nOffset)
void SwEditShell::Redo(sal_uInt16 const nCount)
{
-MakeAllOutlineContentTemporarilyVisible a(GetDoc());
+MakeAllOutlineContentTemporarilyVisible a(GetDoc(), true);
CurrShell aCurr( this );
diff --git a/sw/source/uibase/inc/wrtsh.hxx b/sw/source/uibase/inc/wrtsh.hxx
index 98b3d9038204..801e52bef7ab 100644
--- a/sw/source/uibase/inc/wrtsh.hxx
+++ b/sw/source/uibase/inc/wrtsh.hxx
@@ -681,9 +681,10 @@ class MakeAllOutlineContentTemporarilyVisible
private:
SwWrtShell* m_pWrtSh = nullptr;
bool m_bDone = false;
+bool m_bScrollToCursor = false;
public:
static sal_uInt32 nLock;
-MakeAllOutlineContentTemporarilyVisible(SwDoc* pDoc)
+MakeAllOutlineContentTemporarilyVisible(SwDoc* pDoc, bool bScrollToCursor
= false)
{
++nLock;
if (nLock > 1)
@@ -692,8 +693,10 @@ public:
if ((m_pWrtSh = pDocSh->GetWrtShell()) &&
m_pWrtSh->GetViewOptions() &&
[Libreoffice-bugs] [Bug 147132] Flatten Basic function implementations
https://bugs.documentfoundation.org/show_bug.cgi?id=147132 Eike Rathke changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2917 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152917] Regression: ConvertFromUrl() returns an empty string in LibreOffice 7.5.0.1
https://bugs.documentfoundation.org/show_bug.cgi?id=152917 Eike Rathke changed: What|Removed |Added Keywords||bibisectNotNeeded, ||regression Version|unspecified |7.5.0.0 alpha0+ OS|Linux (All) |All Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Eike Rathke --- Regression from https://git.libreoffice.org/core/commit/6b3e66cd7a355061bf1dec76bbc4f389b6b60f2d -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152918] New: Disable Gutter position
https://bugs.documentfoundation.org/show_bug.cgi?id=152918 Bug ID: 152918 Summary: Disable Gutter position Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: afs...@libreoffice.ir Created attachment 184519 --> https://bugs.documentfoundation.org/attachment.cgi?id=184519=edit Gutter on right side of page Hello. Since each book has only one gutter, I think that when the user ticks the "Gutter on right side of page" option, the "Gutter position" options should be disabled (greyed out). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125595] FORMATTING: Validity cell range with invisible characters (e.g. newline) stripped
https://bugs.documentfoundation.org/show_bug.cgi?id=125595 --- Comment #9 from Teraslilja --- Recently I have upgraded my Ubuntu to 22.04 LTS and I tested with Calc version 7.3.7.2. Now everything seems to be working correctly. I propose that this ticket is closed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 --- Comment #13 from Daniele --- @Alex, sorry I copied from a previous message hastily and wrote it wrongly. This is the path it was installed to: Macintosh HD/Library/Java/JavaVirtualMachines I am also attaching a screenshot of the details -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 --- Comment #12 from Daniele --- Created attachment 184518 --> https://bugs.documentfoundation.org/attachment.cgi?id=184518=edit Location of java on disk -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152917] New: Regression: ConvertFromUrl() returns an empty string in LibreOffice 7.5.0.1
https://bugs.documentfoundation.org/show_bug.cgi?id=152917 Bug ID: 152917 Summary: Regression: ConvertFromUrl() returns an empty string in LibreOffice 7.5.0.1 Product: LibreOffice Version: unspecified Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rolan...@free.fr In LibreOffice 7.5.0.1, the ConvertFromUrl() function returns an empty string instead of doing the conversion from URL to path. This breaks the TexMaths extension. To reproduce, run the following macro: REM * BASIC * Sub Main Dim str1 as String Dim str2 as String str1 = "file:///home/roland/test.txt" msgbox str1 str2 = ConvertFromURL(str1) msgbox str2 End Sub In LibreOffice 7.4.2.3, string str2 is equal to "/home/roland/test.txt", as expected. In LibreOffice 7.5.0.1, string str2 is empty. LibreOffice 7.4.2.3 Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 2; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu package version: 1:7.4.2~rc3-0ubuntu1 Calc: threaded LibreOffice 7.5.0.1 === Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 2; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded System == Ubuntu 22.10 64 bits (running in A VM, fresh install, fresh LibreOffice profile) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152781] Format - Character: too many warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152781 --- Comment #19 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/aa445da4c0cfc1491ceac80126ec6503677c672b Related: tdf#152781 Pin some known on-the-fly langtags to user-defined LCIDs It will be available in 7.5.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - i18nlangtag/source include/i18nlangtag
i18nlangtag/source/isolang/isolang.cxx |7 ++-
include/i18nlangtag/lang.h |6 ++
2 files changed, 12 insertions(+), 1 deletion(-)
New commits:
commit aa445da4c0cfc1491ceac80126ec6503677c672b
Author: Eike Rathke
AuthorDate: Fri Jan 6 18:53:11 2023 +0100
Commit: Eike Rathke
CommitDate: Sat Jan 7 18:00:00 2023 +
Related: tdf#152781 Pin some known on-the-fly langtags to user-defined LCIDs
These are pulled in by either our own bundled extension
dictionaries (es-*, ca-*), or hunspell dictionary (en-AG), but
have no language listbox entry (and don't need one until someone
insists) thus are generated.
So if selected and in case stored in binary MS file formats ensure
a stable back-and-forth conversion. The on-the-fly 0x7e1, 0x7e2,
... are generated arbitrarily in order as encountered.
Change-Id: I0dc72bf1301b26d5b82e1b271c58fc77c82eea0f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145161
Reviewed-by: Eike Rathke
Tested-by: Jenkins
(cherry picked from commit 54d25b36c0bf3dcc715f2098ad658bb113e868ec)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145124
diff --git a/i18nlangtag/source/isolang/isolang.cxx
b/i18nlangtag/source/isolang/isolang.cxx
index 2bd6b5e5e229..d64b00f0694a 100644
--- a/i18nlangtag/source/isolang/isolang.cxx
+++ b/i18nlangtag/source/isolang/isolang.cxx
@@ -343,7 +343,9 @@ IsoLanguageCountryEntry const aImplIsoLangEntries[] =
{ LANGUAGE_SINDHI, "sd", "IN", kSAME },//
Devanagari script
{ LANGUAGE_BELARUSIAN, "be", "BY", k0},
{ LANGUAGE_CATALAN, "ca", "ES", k0},// Spain
(default)
-{ LANGUAGE_CATALAN, "ca", "AD", k0},// Andorra
+{ LANGUAGE_USER_CATALAN_ANDORRA,"ca", "AD", k0},
+{ LANGUAGE_USER_CATALAN_FRANCE, "ca", "FR", k0},
+{ LANGUAGE_USER_CATALAN_ITALY, "ca", "IT", k0},
//LANGUAGE_CATALAN_VALENCIAN ca-ES-valencia Bcp47CountryEntry takes
precedence
{ LANGUAGE_CATALAN_VALENCIAN, "ca", "XV", kSAME },// XV: ISO
3166 user-assigned; old workaround for UI localization only, in case it escaped
to document content
{ LANGUAGE_CATALAN_VALENCIAN, "qcv", "ES", kSAME },// qcv:
ISO 639-3 reserved-for-local-use; old UI localization quirk only, in case it
escaped to document content
@@ -674,6 +676,9 @@ IsoLanguageCountryEntry const aImplIsoLangEntries[] =
{ LANGUAGE_USER_ENGLISH_ISRAEL, "en", "IL", k0},
{ LANGUAGE_USER_PENNSYLVANIA_DUTCH,"pdc", "US", k0},
{ LANGUAGE_USER_PORTUGUESE_MOZAMBIQUE, "pt", "MZ", k0},
+{ LANGUAGE_USER_SPANISH_EQUATORIAL_GUINEA, "es", "GQ", k0},
+{ LANGUAGE_USER_SPANISH_PHILIPPINES,"es", "PH", k0},
+{ LANGUAGE_USER_ENGLISH_ANTIGUA_BARBUDA,"en", "AG", k0},
// Add new languages ^^^ there.
{ LANGUAGE_MULTIPLE, "mul", "" , k0},//
multiple languages, many languages are used
{ LANGUAGE_UNDETERMINED, "und", "" , k0},//
undetermined language, language cannot be identified
diff --git a/include/i18nlangtag/lang.h b/include/i18nlangtag/lang.h
index 59e20669cddd..55be18878209 100644
--- a/include/i18nlangtag/lang.h
+++ b/include/i18nlangtag/lang.h
@@ -776,6 +776,12 @@ namespace o3tl
#define LANGUAGE_USER_INTERSLAVIC_CYRILLIC LanguageType(0x06AE)
#define LANGUAGE_USER_PENNSYLVANIA_DUTCHLanguageType(0x06AF)
#define LANGUAGE_USER_PORTUGUESE_MOZAMBIQUE LanguageType(0x8416) /*
makeLangID( 0x21, getPrimaryLanguage( LANGUAGE_PORTUGUESE)) */
+#define LANGUAGE_USER_SPANISH_EQUATORIAL_GUINEA LanguageType(0x840A) /*
makeLangID( 0x21, getPrimaryLanguage( LANGUAGE_SPANISH)) */
+#define LANGUAGE_USER_SPANISH_PHILIPPINES LanguageType(0x880A) /*
makeLangID( 0x22, getPrimaryLanguage( LANGUAGE_SPANISH)) */
+#define LANGUAGE_USER_CATALAN_ANDORRA LanguageType(0x8403) /*
makeLangID( 0x21, getPrimaryLanguage( LANGUAGE_CATALAN)) */
+#define LANGUAGE_USER_CATALAN_FRANCELanguageType(0x8803) /*
makeLangID( 0x22, getPrimaryLanguage( LANGUAGE_CATALAN)) */
+#define LANGUAGE_USER_CATALAN_ITALY LanguageType(0x8C03) /*
makeLangID( 0x23, getPrimaryLanguage( LANGUAGE_CATALAN)) */
+#define LANGUAGE_USER_ENGLISH_ANTIGUA_BARBUDA LanguageType(0xB809) /*
makeLangID( 0x2E, getPrimaryLanguage( LANGUAGE_ENGLISH_UK)) */
/* XXX Add new user defined LCIDs ^^^ there.
[Libreoffice-bugs] [Bug 149676] Can not switch off Auto Correction replace of 3 dots ("...") with the typographical single character "…" Ellipsis
https://bugs.documentfoundation.org/show_bug.cgi?id=149676 Adolfo Jayme Barrientos changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152916] New: Error on Mendeley Citation
https://bugs.documentfoundation.org/show_bug.cgi?id=152916 Bug ID: 152916 Summary: Error on Mendeley Citation Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: brianderbyshir...@gmail.com Description: Error: Argument is not optional. Additional information: Type: com.sun.star.beans.UnknownPropertyException Message: Mendeley Citation Style_2 At line: 1058 Steps to Reproduce: 1.Open Mendeley Desktop 2.Select Insert Citation 3.Choose citation and click OK Actual Results: Error: Argument is not optional. Additional information: Type: com.sun.star.beans.UnknownPropertyException Message: Mendeley Citation Style_2 At line: 1058 Expected Results: Inserted the Citation and Bibliography Reproducible: Always User Profile Reset: No Additional Info: Version 7.4.3.2 (x64) Build 1048a8393ae2eeec98dff31b5c133c5f1d08b890 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152176] Calc data entry and cell move slowdown
https://bugs.documentfoundation.org/show_bug.cgi?id=152176 --- Comment #16 from Malte S --- Hi, i will get myself familiar with the Bibisecting procedure and will let you know about the results. Just be a bit pacient as i'am sometimes quite busy in my day job but i will post results here once done. i'am glad to help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152915] New: unwanted upper by lower case replacement
https://bugs.documentfoundation.org/show_bug.cgi?id=152915 Bug ID: 152915 Summary: unwanted upper by lower case replacement Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gmild...@t-online.de Description: I hate it when a program patronises me. It (calc) always replaces "HSt-STUMPF" BY "Hst-STUMPF". I found no way to stop this. Steps to Reproduce: 1.see above 2. 3. Actual Results: see above Expected Results: xö Reproducible: Always User Profile Reset: No Additional Info: x -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148306] ToC column layout doesn't the page style's direction in a document imported from MS Word
https://bugs.documentfoundation.org/show_bug.cgi?id=148306 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148306] ToC column layout doesn't the page style's direction in a document imported from MS Word
https://bugs.documentfoundation.org/show_bug.cgi?id=148306 --- Comment #7 from Dieter --- In a new document PS Contents 1 and Contents 2 have text direction "Use superordinate object settings". So, if you change page direction to LTR, direction of paragraphs also changes. In original document PS Contents 1 and Contents 2 have text direction RTL. So it's expected, that text direction doesn't change, if you change it in page style. If you change text direction of PS to "Use superordinate object settings" and change text direction of page style I would expect, that text direction of paragraphs should change also, but it doesn't. But this might be document specific as the copy and paste example shows. So for me question is: Is it possible for you to reproduce bug from scratch? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152914] Writer reports ALL .odt files as corrupt, even newly saved ones.
https://bugs.documentfoundation.org/show_bug.cgi?id=152914 --- Comment #1 from Stirling Westrup --- Okay, I've found the cause of this bug. OpenSuse recently changed its use of /tmp to tmpfs and now /tmp regularly fills to 100%. When this happens many things break, including LibreOffice's loading of files. It would be helpful if it could detect that /tmp was out of space rather than just report corrupt files. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146445] Change behaviour of anchor to character in an empty paragraph (see comment 15)
https://bugs.documentfoundation.org/show_bug.cgi?id=146445 --- Comment #36 from Dieter --- (In reply to Telesto from comment #35) > B) Mimic the behavior, as if a comment comment box where present in the > empty paragraph. In that case you really need to press arrow left to go > beginning. This should be limited to case of empty paragraph. This would > solve the issue in the majority of the cases. I still agree to Telesto and think it might be a solution, if technically possible (although it might be seen as an easter egg) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 146445] Change behaviour of anchor to character in an empty paragraph (see comment 15)
https://bugs.documentfoundation.org/show_bug.cgi?id=146445 --- Comment #36 from Dieter --- (In reply to Telesto from comment #35) > B) Mimic the behavior, as if a comment comment box where present in the > empty paragraph. In that case you really need to press arrow left to go > beginning. This should be limited to case of empty paragraph. This would > solve the issue in the majority of the cases. I still agree to Telesto and think it might be a solution, if technically possible (although it might be seen as an easter egg) -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 --- Comment #11 from Alex Thurgood --- (In reply to Daniele from comment #10) Hi @Daniele, > Macintosh > > HD/Users/USERA/Library/Java/JavaVirtualMachines/temurin-18.jdk > > > but got the same error message. > Ah, pretty certain that that's the wrong place to put your JDK in. It needs to go in the system /Library/ folder (and not the user Library folder) under the corresponding /JavaVirtualMachines/ directory. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138169] EDITING: Copying an image with a name should also copy the name
https://bugs.documentfoundation.org/show_bug.cgi?id=138169 --- Comment #5 from Dieter --- (In reply to Stéphane Guillou (stragu) from comment #4) > Can't find the fixing commit or corresponding bug just yet so marking as > "works for me". What about the correspondig bug 151828? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137343] Dropcaps can produce Text outside of Text-Borders
https://bugs.documentfoundation.org/show_bug.cgi?id=137343 Dieter changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137343] Dropcaps can produce Text outside of Text-Borders
https://bugs.documentfoundation.org/show_bug.cgi?id=137343 --- Comment #4 from Dieter --- Created attachment 184517 --> https://bugs.documentfoundation.org/attachment.cgi?id=184517=edit test file I could no longe reproduce the problem with attached test file. Clarc, is it possible for you? If this is the case, please provide a sample file. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152914] New: Writer reports ALL .odt files as corrupt, even newly saved ones.
https://bugs.documentfoundation.org/show_bug.cgi?id=152914 Bug ID: 152914 Summary: Writer reports ALL .odt files as corrupt, even newly saved ones. Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: swest...@gmail.com Description: LibreOffice refuses to open any .odt files, saying they are corrupt. It offers the choice of fixing them, which never succeeds. Steps to Reproduce: 1. Save a trivial test file from Writer 2. Close Writer 3. Attempt to open file. Its reported Corrupt Actual Results: File is reported corrupt. Even zero-length files. After an attempted repair, the zero length file was 4.2 KB, and was still reported corrupt. Expected Results: Saved files should be loadable. Reproducible: Always User Profile Reset: Yes Additional Info: I'm not sure when this bug showed up but I suspect its very new. I hadn't noticed it before yesterday's software update (I'm running OpenSUSE Tumbleweed 20230105) but I know the bug was NOT present in 7.4.1.2 Version: 7.4.3.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-CA (en_CA.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152788] When inserting a Formula object in Writer, one particular subscript is not shown whereas other similar ones are
https://bugs.documentfoundation.org/show_bug.cgi?id=152788 csyu@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from csyu@gmail.com --- Reproducible in stable and unstable builds Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152800] Edits to default style in default template do not persist
https://bugs.documentfoundation.org/show_bug.cgi?id=152800 csyu@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||csyu@gmail.com Ever confirmed|0 |1 --- Comment #1 from csyu@gmail.com --- Reproducible in stable and unstable builds Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49881] VML Autoshapes created in MS Office not imported at all in LO 3.5.3, FILEOPEN, FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=49881 --- Comment #15 from Regina Henschel --- Tested with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 12e8d57e791bb1befc0716d4d02af7d1d1ccb4ae CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 --- Comment #10 from Daniele --- Hi @Alex, thank you for your detailed answers also on the history of Java. I installed temurin-18.jdk, and from LO preferences advanced pointed to Macintosh > HD/Users/USERA/Library/Java/JavaVirtualMachines/temurin-18.jdk but got the same error message. The previous version of LO found it without any issue, but somehow now that it is higher up in the file system it won't fetch it. I am also happy to use any other java version that works. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49881] VML Autoshapes created in MS Office not imported at all in LO 3.5.3, FILEOPEN, FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=49881 --- Comment #14 from Regina Henschel --- The import is still incorrect. The shapes themselves are better now, only shadow is missing. But the size and position of the text is wrong and some arrows are missing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - sw/inc sw/qa sw/source
sw/inc/strings.hrc |1
sw/qa/extras/ooxmlexport/data/tdf125338.docm |binary
sw/qa/extras/ooxmlexport/ooxmlexport9.cxx| 10 ++-
sw/source/filter/ww8/docxexport.cxx |3 +-
sw/source/filter/ww8/docxexportfilter.cxx| 35 +++
5 files changed, 43 insertions(+), 6 deletions(-)
New commits:
commit 39a09050d309de7ebcf4630cc12cdffa2ca4a654
Author: offtkp
AuthorDate: Wed Dec 14 22:21:34 2022 +0200
Commit: Tomaž Vajngerl
CommitDate: Sat Jan 7 16:05:58 2023 +
tdf#125338 Do not export macros when saving as .docx
Docx files that have macros should be saved as .docm. Now displays a
warning that macros won't be saved if exporting a .docm as a .docx and
doesn't export them.
Change-Id: I178855baa6c0a7d32fd9b00c83a817230b33a1a1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144197
Tested-by: Jenkins
Reviewed-by: Justin Luth
(cherry picked from commit cbca5617387aaa39c9ee86272166bb3df7874b25)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144811
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Tomaž Vajngerl
diff --git a/sw/inc/strings.hrc b/sw/inc/strings.hrc
index b4b03968a1eb..59fe112fecba 100644
--- a/sw/inc/strings.hrc
+++ b/sw/inc/strings.hrc
@@ -331,6 +331,7 @@
#define STR_SOUTH NC_("STR_SOUTH", "South")
#define STR_SUM NC_("STR_SUM", "Sum")
#define STR_INVALID_AUTOFORMAT_NAME
NC_("STR_INVALID_AUTOFORMAT_NAME", "You have entered an invalid name.\nThe
desired AutoFormat could not be created. \nTry again using a different name.")
+#define STR_CANT_SAVE_MACROSNC_("STR_CANT_SAVE_MACROS",
"This document has macros, but macros will not be saved in this file format.")
#define STR_NUMERIC NC_("STR_NUMERIC", "Numeric")
#define STR_ROW NC_("STR_ROW", "Rows")
#define STR_COL NC_("STR_COL", "Column")
diff --git a/sw/qa/extras/ooxmlexport/data/tdf125338.docm
b/sw/qa/extras/ooxmlexport/data/tdf125338.docm
new file mode 100644
index ..44e943531d30
Binary files /dev/null and b/sw/qa/extras/ooxmlexport/data/tdf125338.docm differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport9.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport9.cxx
index 99d4b0112a60..1b97e846f1ef 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport9.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport9.cxx
@@ -139,7 +139,7 @@ DECLARE_OOXMLEXPORT_TEST(testTdf109063, "tdf109063.docx")
CPPUNIT_ASSERT_EQUAL(0, getShapes());
}
-CPPUNIT_TEST_FIXTURE(Test, testTdf108269)
+CPPUNIT_TEST_FIXTURE(DocmTest, testTdf108269)
{
loadAndReload("tdf108269.docm");
uno::Reference xNameAccess =
packages::zip::ZipFileAccess::createWithURL(comphelper::getComponentContext(m_xSFactory),
maTempFile.GetURL());
@@ -149,6 +149,14 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf108269)
CPPUNIT_ASSERT(xNameAccess->hasByName("word/vbaData.xml"));
}
+CPPUNIT_TEST_FIXTURE(Test, testTdf125338)
+{
+loadAndSave("tdf125338.docm");
+uno::Reference xNameAccess =
packages::zip::ZipFileAccess::createWithURL(comphelper::getComponentContext(m_xSFactory),
maTempFile.GetURL());
+// docm files should not retain macros when saved as docx
+CPPUNIT_ASSERT(!xNameAccess->hasByName("word/vbaProject.bin"));
+}
+
DECLARE_OOXMLEXPORT_TEST(testTdf92045, "tdf92045.docx")
{
// This was true, resulted in setting the
blinking font effect.
diff --git a/sw/source/filter/ww8/docxexport.cxx
b/sw/source/filter/ww8/docxexport.cxx
index 74d081baf244..d5bc243d5c2e 100644
--- a/sw/source/filter/ww8/docxexport.cxx
+++ b/sw/source/filter/ww8/docxexport.cxx
@@ -538,7 +538,8 @@ ErrCode DocxExport::ExportDocument_Impl()
WriteEmbeddings();
-WriteVBA();
+if (m_bDocm)
+WriteVBA();
m_aLinkedTextboxesHelper.clear(); //final cleanup
m_pStyles.reset();
diff --git a/sw/source/filter/ww8/docxexportfilter.cxx
b/sw/source/filter/ww8/docxexportfilter.cxx
index 08308ca9398c..5ffd32f4c25b 100644
--- a/sw/source/filter/ww8/docxexportfilter.cxx
+++ b/sw/source/filter/ww8/docxexportfilter.cxx
@@ -63,6 +63,37 @@ bool DocxExportFilter::exportDocument()
pViewShell->GetPostItMgr()->UpdateDataOnActiveSidebarWin();
}
+OUString aFilterName;
+auto& rMediaDescriptor = getMediaDescriptor();
+rMediaDescriptor[utl::MediaDescriptor::PROP_FILTERNAME] >>= aFilterName;
+bool bDocm = aFilterName.endsWith("VBA");
+
+if (!bDocm)
+{
+// Check whether application is in headless mode
+if (!Application::IsHeadlessModeEnabled())
+{
+uno::Reference
xStorageBasedDocument(
+pDoc->GetDocShell()->GetBaseModel(), uno::UNO_QUERY);
+if (xStorageBasedDocument.is())
+{
+uno::Reference xDocumentStorage =
+
[Libreoffice-commits] core.git: Branch 'libreoffice-7-4' - dbaccess/source
dbaccess/source/ui/misc/WCPage.cxx |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit f2d3658697f22090ee138cebda4d10c3ede21230 Author: Julien Nabet AuthorDate: Fri Jan 6 17:11:47 2023 +0100 Commit: Caolán McNamara CommitDate: Sat Jan 7 16:03:32 2023 + tdf#152900: "Create new field as primary key" disabled... when pasting data as new table Regression from 3f8e50f9b2fb35db190ce0204981f3f02d1d5ae6 (05/2021) "merge handlers into single toggle handler" Change-Id: I05376f288c1687978225bd98da21a5e21810292a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145120 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/dbaccess/source/ui/misc/WCPage.cxx b/dbaccess/source/ui/misc/WCPage.cxx index 738c85124708..602edd2d6e24 100644 --- a/dbaccess/source/ui/misc/WCPage.cxx +++ b/dbaccess/source/ui/misc/WCPage.cxx @@ -106,8 +106,8 @@ IMPL_LINK(OCopyTable, RadioChangeHdl, weld::Toggleable&, rButton, void) SetAppendDataRadio(); return; } -m_pParent->EnableNextButton(m_xRB_View->get_active()); -bool bKey = m_bPKeyAllowed && m_xRB_View->get_active(); +m_pParent->EnableNextButton(!m_xRB_View->get_active()); +bool bKey = m_bPKeyAllowed && !m_xRB_View->get_active(); m_xFT_KeyName->set_sensitive(bKey && m_xCB_PrimaryColumn->get_active()); m_xEdKeyName->set_sensitive(bKey && m_xCB_PrimaryColumn->get_active()); m_xCB_PrimaryColumn->set_sensitive(bKey);
[Libreoffice-commits] core.git: include/svx
include/svx/ColorSets.hxx |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
New commits:
commit 34791b203fdf5f571189f82510fd4a2d02008bd4
Author: Caolán McNamara
AuthorDate: Sat Jan 7 11:01:20 2023 +
Commit: Caolán McNamara
CommitDate: Sat Jan 7 16:03:21 2023 +
cid#1518911 Uninitialized scalar variable
Change-Id: Ieef6bf8cd20907531301ab8cf6d81d2dcd5397a4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145171
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/include/svx/ColorSets.hxx b/include/svx/ColorSets.hxx
index 3d345b20c1b3..115b7448a8a0 100644
--- a/include/svx/ColorSets.hxx
+++ b/include/svx/ColorSets.hxx
@@ -113,9 +113,9 @@ struct SVXCORE_DLLPUBLIC ThemeFont
{
OUString maTypeface;
OUString maPanose;
-sal_Int16 maPitch;
-sal_Int16 maFamily;
-sal_Int32 maCharset;
+sal_Int16 maPitch = 0;
+sal_Int16 maFamily = 0;
+sal_Int32 maCharset = 0;
sal_Int16 getPitchFamily() const
{
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - dbaccess/source
dbaccess/source/ui/misc/WCPage.cxx |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit 4288b9a2cc5f70cebf6124db0b47277a4581e305 Author: Julien Nabet AuthorDate: Fri Jan 6 17:11:47 2023 +0100 Commit: Caolán McNamara CommitDate: Sat Jan 7 16:03:10 2023 + tdf#152900: "Create new field as primary key" disabled... when pasting data as new table Regression from 3f8e50f9b2fb35db190ce0204981f3f02d1d5ae6 (05/2021) "merge handlers into single toggle handler" Change-Id: I05376f288c1687978225bd98da21a5e21810292a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145119 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/dbaccess/source/ui/misc/WCPage.cxx b/dbaccess/source/ui/misc/WCPage.cxx index 738c85124708..602edd2d6e24 100644 --- a/dbaccess/source/ui/misc/WCPage.cxx +++ b/dbaccess/source/ui/misc/WCPage.cxx @@ -106,8 +106,8 @@ IMPL_LINK(OCopyTable, RadioChangeHdl, weld::Toggleable&, rButton, void) SetAppendDataRadio(); return; } -m_pParent->EnableNextButton(m_xRB_View->get_active()); -bool bKey = m_bPKeyAllowed && m_xRB_View->get_active(); +m_pParent->EnableNextButton(!m_xRB_View->get_active()); +bool bKey = m_bPKeyAllowed && !m_xRB_View->get_active(); m_xFT_KeyName->set_sensitive(bKey && m_xCB_PrimaryColumn->get_active()); m_xEdKeyName->set_sensitive(bKey && m_xCB_PrimaryColumn->get_active()); m_xCB_PrimaryColumn->set_sensitive(bKey);
[Libreoffice-bugs] [Bug 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 Alex Thurgood 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 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 --- Comment #9 from Alex Thurgood --- (In reply to Daniele from comment #7) > Hi @Sierk Bornemann, > > thank you for following up. > > My Java VM are in Macintosh HD/Library/Java/JavaVirtualMachines/ > > got the same error message. > > Went manually to (tried both clicking on add and class path) > /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/ > Why aren't you using temurin-18.jdk? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152644] Java path not found nor selectable after upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=152644 --- Comment #8 from Alex Thurgood --- (In reply to Daniele from comment #7) > Hi @Sierk Bornemann, > > thank you for following up. > > My Java VM are in Macintosh HD/Library/Java/JavaVirtualMachines/ > > I think that they previously were in Macintosh > HD/Users/USERA/Library/Java/JavaVirtualMachines/ > > because it took me a long time to find them, but I cannot be sure. Do not > know either when/how they were moved (not by me at any rate). Maybe when I > moved to Monterey? > > as to your second question: "And: do you have set the environment > variable... etc." I am really not familiar with these things. All I do is go > to https://adoptium.net/temurin/releases/ > > > choose the right release and then install it. But as > > @Alex Thurgood pointed out, I might have chosen the wrong one. So I am > choosing now the aarch64. Downloaded and installed it. Deleted the other two. > > I closed LO and re-opened it. > > Got the same error message. > > Went manually to (tried both clicking on add and class path) > /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/ > Theoretically, you shouldn't need to point it to the /bin directory, just the /temurin-17.jdk/ folder. However, it might well be that temurin-17.jdk isn't recognized. As I said, not all versions are recognized. > I do not know if this is possible: but it would be great if LO worked "out > of the box": the average user (who will at the most download and install LO > without going to Preferences) would highly benefit from it! Maybe an error > message from LO pointing to a java download page (and instructions on what > to do)? Thanks! I would love for this to be possible, but the whole sorry Java recognition business has been a long standing debacle due to the fact that Apple and Oracle fell out, and the LO project has been trying to play keep up for functionality that it has wanted to make entirely optional and not yet succeeded without losing key functionality, well, because people actually still use Java on a day-to-day basis with their office productivity suite. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - external/hunspell
external/hunspell/0001-Resolves-rhbz-2158548-allow-longer-words-for-hunspel.patch
| 77 ++
external/hunspell/UnpackedTarball_hunspell.mk
|1
2 files changed, 78 insertions(+)
New commits:
commit a682ae47029f751ec7354ac8ebf12426210a1bd7
Author: Caolán McNamara
AuthorDate: Fri Jan 6 16:28:03 2023 +
Commit: Adolfo Jayme Barrientos
CommitDate: Sat Jan 7 15:50:17 2023 +
Related: rhbz#2158548 allow longer words for hunspell-ko
https://github.com/hunspell/hunspell/issues/903
A problem since the sanity check added in:
commit 05e44e069e4cfaa9ce1264bf13f23fc9abd7ed05
Author: Caolán McNamara
Date: Thu Sep 1 13:46:40 2022 +0100
Check word limit (#813)
* check against hentry blen max
Change-Id: Iab2c062584da076260c3262537690435eae7f396
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145121
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git
a/external/hunspell/0001-Resolves-rhbz-2158548-allow-longer-words-for-hunspel.patch
b/external/hunspell/0001-Resolves-rhbz-2158548-allow-longer-words-for-hunspel.patch
new file mode 100644
index ..c0225fbd70a4
--- /dev/null
+++
b/external/hunspell/0001-Resolves-rhbz-2158548-allow-longer-words-for-hunspel.patch
@@ -0,0 +1,77 @@
+From e2fe9f86e1769b440972971240e9b8fb1cd53b97 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Caol=C3=A1n=20McNamara?=
+Date: Fri, 6 Jan 2023 16:20:45 +
+Subject: [PATCH] Resolves: rhbz#2158548 allow longer words for hunspell-ko
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+https://github.com/hunspell/hunspell/issues/903
+
+A problem since the sanity check added in:
+
+commit 05e44e069e4cfaa9ce1264bf13f23fc9abd7ed05
+Author: Caolán McNamara
+Date: Thu Sep 1 13:46:40 2022 +0100
+
+Check word limit (#813)
+
+* check against hentry blen max
+---
+ src/hunspell/hashmgr.cxx | 6 +++---
+ src/hunspell/htypes.hxx | 4 ++--
+ tests/korean.dic | 3 ++-
+ 3 files changed, 7 insertions(+), 6 deletions(-)
+
+diff --git a/src/hunspell/hashmgr.cxx b/src/hunspell/hashmgr.cxx
+index 100916d..14201e9 100644
+--- a/src/hunspell/hashmgr.cxx
b/src/hunspell/hashmgr.cxx
+@@ -209,7 +209,7 @@ int HashMgr::add_word(const std::string& in_word,
+ }
+
+ // limit of hp->blen
+- if (word->size() > std::numeric_limits::max()) {
++ if (word->size() > std::numeric_limits::max()) {
+ HUNSPELL_WARNING(stderr, "error: word len %ld is over max limit\n",
word->size());
+ delete desc_copy;
+ delete word_copy;
+@@ -235,8 +235,8 @@ int HashMgr::add_word(const std::string& in_word,
+
+ int i = hash(hpw, word->size());
+
+- hp->blen = (unsigned char)word->size();
+- hp->clen = (unsigned char)wcl;
++ hp->blen = (unsigned short)word->size();
++ hp->clen = (unsigned short)wcl;
+ hp->alen = (short)al;
+ hp->astr = aff;
+ hp->next = NULL;
+diff --git a/src/hunspell/htypes.hxx b/src/hunspell/htypes.hxx
+index 44366b1..2b896fb 100644
+--- a/src/hunspell/htypes.hxx
b/src/hunspell/htypes.hxx
+@@ -62,8 +62,8 @@
+ #endif
+
+ struct hentry {
+- unsigned char blen;// word length in bytes
+- unsigned char clen;// word length in characters (different for UTF-8
enc.)
++ unsigned short blen; // word length in bytes
++ unsigned short clen; // word length in characters (different for UTF-8
enc.)
+ short alen;// length of affix flag vector
+ unsigned short* astr; // affix flag vector
+ struct hentry* next; // next word with same hash code
+diff --git a/tests/korean.dic b/tests/korean.dic
+index 95cb450..d76ea05 100644
+--- a/tests/korean.dic
b/tests/korean.dic
+@@ -1,3 +1,4 @@
+-2
++3
+ 들어오세요
+ 안녕하세요
++김수한무거북이와두루미삼천갑자동방삭치치카포사리사리세ᅡ워리워리세브리캉무드셀ᅡ구름위허ᅵ케ᅵᆫᅦ담벼락서생원에ᄀ양
+--
+2.38.1
+
diff --git a/external/hunspell/UnpackedTarball_hunspell.mk
b/external/hunspell/UnpackedTarball_hunspell.mk
index 2b8823021998..4667a3642bcc 100644
--- a/external/hunspell/UnpackedTarball_hunspell.mk
+++ b/external/hunspell/UnpackedTarball_hunspell.mk
@@ -23,6 +23,7 @@ $(eval $(call gb_UnpackedTarball_set_patchlevel,hunspell,1))
$(eval $(call gb_UnpackedTarball_add_patches,hunspell, \
external/hunspell/0001-fix-LibreOffice-build-problem-with-basic_string-appe.patch
\
+
external/hunspell/0001-Resolves-rhbz-2158548-allow-longer-words-for-hunspel.patch
\
))
# vim: set noet sw=4 ts=4:
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - cui/uiconfig
cui/uiconfig/ui/gradientpage.ui |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 19d11c7d7f6bccc9bc10ab599721dc7c8e69646b Author: Adolfo Jayme Barrientos AuthorDate: Fri Jan 6 21:32:43 2023 + Commit: Adolfo Jayme Barrientos CommitDate: Sat Jan 7 15:49:06 2023 + Revert "tdf#101731 Rename gradient border label to midpoint" This reverts commit 5e7663b792ee1d56838d7a5082e5c29867f839f2. Reason for revert: Change based on a misunderstanding Change-Id: I6187b89e86652fe3a2d0ccb82c1c93922064c3d4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145123 Reviewed-by: Adolfo Jayme Barrientos Tested-by: Jenkins diff --git a/cui/uiconfig/ui/gradientpage.ui b/cui/uiconfig/ui/gradientpage.ui index e2ec661b3b7d..6a66dad09597 100644 --- a/cui/uiconfig/ui/gradientpage.ui +++ b/cui/uiconfig/ui/gradientpage.ui @@ -390,7 +390,7 @@ True False -Mid_point: +_Border: True bordermtr 0
[Libreoffice-bugs] [Bug 152913] New: FILESAVE DOCX handles of Fontwork shape wrong in VML
https://bugs.documentfoundation.org/show_bug.cgi?id=152913 Bug ID: 152913 Summary: FILESAVE DOCX handles of Fontwork shape wrong in VML Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Blocks: 136406 Created attachment 184516 --> https://bugs.documentfoundation.org/attachment.cgi?id=184516=edit File with "Slant Up" Fontwork shape. Open attached document and save it to docx format. Open the saved file in Word. Notice that the handle is at a wrong position and is not moveable in Word. To see how it should work, switch to a different shape type in the "WordArt" menu in Word and then back to type "Slant-Up". Examining the docx file you will see, that the fontwork shape is exported as VML shape. The produced VML markup has these errors: (1) The y value in the position attribute of the handle uses a reference to a formula (@) instead of a reference to an adjustment value (#). Referencing a formula is no syntactical error, but it determines that the handle is fix in that direction. Only the reference to an adjust value gives a moveable handle. https://learn.microsoft.com/en-us/windows/win32/vml/position-attribute--h--vml (2) The x value in the position attribute of the handle uses the constant 0. That is not evaluated in Word but treated as "center". Instead the key "topLeft" has to be used. (3) The element misses the adj attribute, which determines via the # reference the position of the handle. The fact, that this shape is not exported as DrawingML but to VML, is an additional, but different error. In case a Fontwork shape has a bitmap fill, it has to be exported to VML anyway, because in current Word the "abc Transformation" is not able to use bitmap fill. So the problem will be still relevant after this special shape will be correctly exported as DrawingML. The erroneous export to VML has its root in the HasTextBoxContent method in https://opengrok.libreoffice.org/xref/core/filter/source/msfilter/util.cxx?r=6b252b6a#1220 and its use. The VML export is mixed with the export to binary format. I have currently no idea where the errors come in. Tips are appreciated. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136406 [Bug 136406] [META] OOXML VML shape related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136406] [META] OOXML VML shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136406 Regina Henschel changed: What|Removed |Added Depends on||152913 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152913 [Bug 152913] FILESAVE DOCX handles of Fontwork shape wrong in VML -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152894] random crashes in Writer (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=152894 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||vsfo...@libreoffice.org Summary|Below please find the event |random crashes in Writer |log in connection with a|(Windows) |crash of Writer. I think| |this has happened several | |times since I recently | |started using this | |computer, an Acer Spin 5| |with an I-5 8th gen | |processor | --- Comment #1 from V Stuart Foote --- Thanks for filing and sorry you're having an issue. Unfortunately not enough detail in the posted Windows event log to do anything for this issue. For starters we'd like you to copy and post the LibreOffice Help -> About details and the Windows system details from msinfo32.exe (core panel, and the components -> display panel). Also, for many "crash" scenarios LibreOffice will trigger a minidump using Breakpad and on restart offer to upload the report--are you seeing that on restart of LibreOffice? Otherwise getting more detail of your issue [1] requires you to install the WinDbg module of the Windows Development Kit and downloading the build symbols libraries. Then attaching the soffice.bin process to the debugger and capturing the moment that LibreOffice crashes on your system. Being able to isolate the part of the program causing your issues. Many of the issues with older CPU/GPU configurations like yours have been display driver related. Check for updates (from Acer or Intel). And also see if LO is stable setting Tools -> Options -> View, so both Skia rendering checkboxes are unchecked and restart. =-ref-= [1] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152912] The Installation program says it can't remove the "old" version. I searched the registry - it completes without finding any reference to 'libre'!
https://bugs.documentfoundation.org/show_bug.cgi?id=152912 Jim Willis changed: What|Removed |Added CC||willis0...@gmail.com --- Comment #1 from Jim Willis --- Created attachment 184515 --> https://bugs.documentfoundation.org/attachment.cgi?id=184515=edit A 'screen shot' (actually a 'snip') Here's a snip of what I encounter. I get this every time I try to install. I've also done a registry search for 'libre' and it doesn't "find" anything! Help! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152912] New: The Installation program says it can't remove the "old" version. I searched the registry - it completes without finding any reference to 'libre'!
https://bugs.documentfoundation.org/show_bug.cgi?id=152912 Bug ID: 152912 Summary: The Installation program says it can't remove the "old" version. I searched the registry - it completes without finding any reference to 'libre'! Product: LibreOffice Version: 7.4.3.2 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: willis0...@gmail.com Description: The Installation program says it can't remove the "old" version. I searched the registry - it completes without finding any reference to 'libre'! What's going on? Please send instructions on "how to attach a file or photo." Steps to Reproduce: 1.Double-click on the *.msi file 2.follow the 'on-screen' prompts 3. Actual Results: No Installation! Expected Results: Installation! Reproducible: Always User Profile Reset: No Additional Info: There is no other information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152911] New: VIEWING - High CPU and lag when scrolling on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=152911 Bug ID: 152911 Summary: VIEWING - High CPU and lag when scrolling on Wayland Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: b...@irreversibly.org Description: When using KDE Wayland on a laptop with an AMD integrated GPU, I get some high CPU spikes and massive lag when i scroll through a document. Large documents (tens of thousands of words, zero images) are near-unusable, but this is noticeable even on an empty one-page document. On an X11 session, scrolling is perfectly smooth. Steps to Reproduce: 1. Start a KDE Wayland session 2. Open LibreOffice Writer 3. Scroll Actual Results: Choppy scrolling and high CPU usage Expected Results: Smooth scrolling, like in X11 Reproducible: Always User Profile Reset: No Additional Info: This is on LO 7.4.3.2, kf5 (cairo+wayland) Linux 6.0 (Fedora 37). I have smooth scrolling disabled and hardware acceleration enabled (toggling any of these settings makes no difference). I do use fractional scaling on Wayland, but then again it doesn't make a difference, the only factor that makes it not lag seems to be not using Wayland at all. Starting LO in Safe Mode does not make a difference either. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104719] Include archive with help images with helppacks on all platforms
https://bugs.documentfoundation.org/show_bug.cgi?id=104719 Buovjaga changed: What|Removed |Added CC||mr.fro...@gmail.com --- Comment #3 from Buovjaga --- (In reply to Kaan Güler from comment #2) > Is this bug fixed right now? This is not a bug, but a request to release engineering (on hindsight Bugzilla is not even the best place for this). If I may ask, why are you interested in this? Also, what is behind your message in bug 84838 comment 28? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104719] Include archive with help images with helppacks on all platforms
https://bugs.documentfoundation.org/show_bug.cgi?id=104719 --- Comment #2 from Kaan Güler --- Is this bug fixed right now? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149763] Lots of Spaces get suppressed, when a Paragraph mark is added after this Sample
https://bugs.documentfoundation.org/show_bug.cgi?id=149763 Adalbert Hanßen changed: What|Removed |Added Attachment #181008|0 |1 is obsolete|| --- Comment #11 from Adalbert Hanßen --- Created attachment 184514 --> https://bugs.documentfoundation.org/attachment.cgi?id=184514=edit Example of the bug with screenshot. Can be reproduced in 6.4.4.2 Fortunately this bug did not show up any longer with my example in the current development version: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: da3dd48eaf9086f8ab28d6a6655f9a638e51433a CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Unfortunately in the example given originally, the bug could not be observed because it already had happened when I stored the example. Unfortunately I don’t have the development version at hand, with which I first observed the bug. But I was able to reproduce it in the older Version: 6.4.4.2 Build-ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff CPU-Threads: 4; BS: Linux 5.4; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded If somebody wants to reproduce it, attached is an example in which the bug shows up with 6.4.4.2. It also contains a screenshot of the situation before and after the bug has happened. -- You are receiving this mail because: You are the assignee for the bug.
