[Libreoffice-bugs] [Bug 151828] Table name should be retained, if table is cutted & pasted
https://bugs.documentfoundation.org/show_bug.cgi?id=151828 --- Comment #4 from Jim Raykowski --- Here is a proposed patch to retain the table name on cut and paste: https://gerrit.libreoffice.org/c/core/+/142984 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151828] Table name should be retained, if table is cutted & pasted
https://bugs.documentfoundation.org/show_bug.cgi?id=151828 --- Comment #3 from Jim Raykowski --- (In reply to Heiko Tietze from comment #2) > Same is also true for other objects such as shapes and in fact the name is > kept but added by a number. Like "Foo" becomes "Foo 1". With subsequent > cut/paste operations it remains "Foo 1". => needsDevAdvice Here is a fix for this: https://gerrit.libreoffice.org/c/core/+/142983 I searched but didn't find a bug report specific to shape names changing when cut/paste so I've listed it under this bug report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152135] New: Crash when Firefox add-on: Digital Eye Strain Prevention Tool activates while editing LibreOffice spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=152135 Bug ID: 152135 Summary: Crash when Firefox add-on: Digital Eye Strain Prevention Tool activates while editing LibreOffice spreadsheet Product: LibreOffice Version: 7.4.2.3 release Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sears.cameronp...@att.net Description: The crash report was successfully uploaded. You can soon find the report at: https://crashreport.libreoffice.org/stats/crash_details/fdcdb5d0-3519-4cbd-9150-5479a49ebf85 Steps to Reproduce: 1.Open Firefox with add-on: Digital Eye Strain Prevention Tool Ver 2.3 installed 2.Open LibreOffice spreadsheet with 2 columns data. 3.Create XY Scatter Chart 4.When Editing chart, under View menu select Toolbars - Drawing. 5.Pick an drawing tool from the Drawing toolbar at the bottom of the screen. 6.While actively using the drawing tool, when the Firefox Digital Eye Strain Prevention add-on activates, LibreOffice spreadsheet crashes Digital Eye Strain Prevention Tool will activate every 20 minutes LibreOffice local Help is now displayed in default browser - Firefox. LibreOffice spreadsheet does NOT crash when XY Scatter Chart is open to edit and NO drawing tool is in use and Digital Eye Strain Prevention Tool activates. Actual Results: Immediate crash and close. Expected Results: Immediate crash and close. Has happened multiple times. Reproducible: Always User Profile Reset: No Additional Info: LibreOffice info: 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 Computer info: Processor 11th Gen Intel(R) Core(TM) i5-1155G7 @ 2.50GHz 2.50 GHz Installed RAM 12.0 GB (11.7 GB usable) Product ID 00342-21919-63734-AAOEM System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display Firefox 107.0 (64-bit) Add-on (extension) Digital Eye Strain Prevention Tool Ver 2.3 Last Updated November 4, 2021 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V4..(same sheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 --- Comment #1 from wzpd...@gmail.com --- Function appears to add but when closed the sheet undergoes recovery every time and the attempted change is lost. No such fail on Windows8.1 and have used that system and function several years w/o issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V4..(same sheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 wzpd...@gmail.com changed: What|Removed |Added Version|unspecified |7.4.2.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] New: assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V4..(same sheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 Bug ID: 152134 Summary: assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V4..(same sheet) Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wzpd...@gmail.com Cannot assign macro on Windows11 LO v7.4.2.3 x64 but can on Windows8.1 LO v4. once macro assigned on Windows8.1 system sheet Tools menu with macro functions on either system. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148370] In Calc, Autocomplete places black marks in cell where letters should be, instead of previously used characters
https://bugs.documentfoundation.org/show_bug.cgi?id=148370 BogdanB changed: What|Removed |Added Resolution|FIXED |WORKSFORME CC||buzea.bog...@libreoffice.or ||g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151220] LibreOffice Window Appears Extremely Small When Opened
https://bugs.documentfoundation.org/show_bug.cgi?id=151220 Lucas J changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #7 from Lucas J --- If that is the case, then we can reopen it. I just changed the status to REOPENED. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151660] application window problem
https://bugs.documentfoundation.org/show_bug.cgi?id=151660 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 151005] With "Option VBASupport 1" arguments should be treated as ByValue by default (not as ByRef)
https://bugs.documentfoundation.org/show_bug.cgi?id=151005 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 147951] API returns wrong user path on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=147951 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 151925] With q5 VCL, cursor disappears in some paragraphs in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151925 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 151916] Not working if I choose Mongolian Cyrillic
https://bugs.documentfoundation.org/show_bug.cgi?id=151916 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 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=152098 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=152098 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152017] footnotes move onto the next page as I add paragraphs to my document
https://bugs.documentfoundation.org/show_bug.cgi?id=152017 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152017] footnotes move onto the next page as I add paragraphs to my document
https://bugs.documentfoundation.org/show_bug.cgi?id=152017 --- 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 149210] Libre Office crashes unexpectedly
https://bugs.documentfoundation.org/show_bug.cgi?id=149210 --- Comment #3 from QA Administrators --- Dear jan.feliksiak1, 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 149104] Fails to paste images into Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=149104 --- Comment #4 from QA Administrators --- Dear Ian Jarvis, 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 149103] libre office writer, delete image or image frame causes freeze & crash
https://bugs.documentfoundation.org/show_bug.cgi?id=149103 --- Comment #6 from QA Administrators --- Dear Jerry, 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 148862] Tools Options UI cannot be resized and is too wide
https://bugs.documentfoundation.org/show_bug.cgi?id=148862 --- Comment #3 from QA Administrators --- Dear bryce.a.carson, 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 147597] File crashed when using "Toggle Print Preview"
https://bugs.documentfoundation.org/show_bug.cgi?id=147597 --- Comment #3 from QA Administrators --- Dear Sion, 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 147249] cannot change fonts, colors, paragraph, etc etc. the drop down menu doesn't load
https://bugs.documentfoundation.org/show_bug.cgi?id=147249 --- Comment #6 from QA Administrators --- Dear 11afepa6o6, 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 138117] Custom toolbar icons rendered small even on option Large and not at all on option Small
https://bugs.documentfoundation.org/show_bug.cgi?id=138117 --- Comment #6 from QA Administrators --- Dear david mccracken, 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 144705] LibreOffice Writer and/or Calc show High CPU and "not responding" in Windows 10 Task Manager
https://bugs.documentfoundation.org/show_bug.cgi?id=144705 --- Comment #3 from QA Administrators --- Dear Ayjaycee, 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 137536] Animation for object in presentation mode flashes after finishing Skia (not GDI)
https://bugs.documentfoundation.org/show_bug.cgi?id=137536 --- 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 126034] FILEOPEN DOCX Paragraph border in rotated text box is not rotated with text
https://bugs.documentfoundation.org/show_bug.cgi?id=126034 --- Comment #5 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122710] PRINT DIALOG: For "Pages to print" field interpret space as separator for a list of distinct pages to print
https://bugs.documentfoundation.org/show_bug.cgi?id=122710 --- Comment #18 from QA Administrators --- Dear Ulf Zibis, 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 113912] UI Leaving dialog open prevents docking sidebar in another window
https://bugs.documentfoundation.org/show_bug.cgi?id=113912 --- Comment #6 from QA Administrators --- Dear Emil Tanev, 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 152133] New: Stack Protection is not provided for BASIC call to DLL using declare - lib
https://bugs.documentfoundation.org/show_bug.cgi?id=152133 Bug ID: 152133 Summary: Stack Protection is not provided for BASIC call to DLL using declare - lib Product: LibreOffice Version: 7.4.2.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tanhda...@gmail.com Description: When a call is made to a function provided by a declaration with a bad signature: Public Declare Function WSAStartup Lib "ws2_32.dll" (ByVal wVersionRequested As Integer, lpWSAData As wsaData) As Long -- LibreOffice Calc just crashes. In a similar situation, MS Excel does not crash, because VBA checks and corrects the stack. Steps to Reproduce: 1.Type wsaData wVersion As Integer wHighVersion As Integer szDescription As String * WSA_DescriptionSize szSystemStatus As String * WSA_SysStatusSize iMaxSockets As Integer iMaxUdpDg As Integer lpVendorInfo As String * 200 End Type Public Declare Function WSAStartup Lib "ws2_32.dll" (ByVal wVersionRequested As Integer, lpWSAData As wsaData) As Long Sub Test() Dim errCode As Integer Const wsVer22 = 514 Dim SockInfo As wsaData errCode = WSAStartup(wsVer22, SockInfo) Exit Sub 2.Call the sub Actual Results: LibreOffice crashes and closes. Expected Results: Libre Office does not crash. Reproducible: Always User Profile Reset: Yes Additional Info: There's not much you can do if the stack is corrupted by a call to an external DLL. But LO should wrap calls to DLL's declared in BASIC, so that LO itself doesn't crash. Stack faults in this situation should either be ignored, or cause an orderly shutdown. The stack protection provided by MS VBA makes calls slower, and requires the use of LastDLLError (because the wrapper code will lose GetLastError), but that has not been a cause of complaint. Version: 7.4.2.3 (x86) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145069] The return value of a Basic function is not initialized
https://bugs.documentfoundation.org/show_bug.cgi?id=145069 --- Comment #6 from tanh --- (In reply to Andreas Heinisch from comment #2) > From > https://docs.microsoft.com/en-us/office/vba/language/reference/user- > interface-help/function-statement > > "If Static isn't used, the value of local variables is not preserved between > calls." > > So I thought that the value should be cleared. How about recursions? I've not seen VBA documentation that makes it clear that the name of a function is a "local" variable. But all versions of VBA treat it that way. The name of a function is a local variable of that function, and is initialised at every call of that function. Regarding recursion 'static' is not normally used with recursive VBA functions -- it kind of defeats the purpose in common cases. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147951] API returns wrong user path on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=147951
--- Comment #2 from tanh ---
The obvious way to get %USERPROFILE%
is
sTemp=Environ ("USERPROFILE")
I agree that use of Environment variables is bad practice with known security
weekness: for security, LO should provide an object that provides direct access
to the WinAPI or ShellAPI path requests. Does it?
But I'm leery about changing a feature of OO that has been around since V1 just
because some other feature is needed.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151005] With "Option VBASupport 1" arguments should be treated as ByValue by default (not as ByRef)
https://bugs.documentfoundation.org/show_bug.cgi?id=151005 --- Comment #2 from tanh --- In LO, the statement DummySub (a) Does NOT create and discard a reference. Rather, it acts the same way as the CALL syntax LibreOffice: DummySub(a) is the same as Call DummySub(a). MS VBA: DummySub (a) is NOT the same as Call DummySub(a) LibreOffice: DummySub2(a,b) is NOT a syntax error. MS VBA: DummySub2(a,b) IS a syntax error. MS VBA: Call DummySub2(a,b) is NOT a syntax error. LibreOffice: Call DummySub2( (a), b) is the same as Call DummySub2( a,b) MS VBA: Call DummySub2( (a), b) is NOT the same as Call DummySub2( a,b) == sub Test() Dim a As String,b a = "X" call DummySub2((a),b) MsgBox (a) End Sub Sub DummySub2(val As String,b) val = "Y" End Sub == -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151005] With "Option VBASupport 1" arguments should be treated as ByValue by default (not as ByRef)
https://bugs.documentfoundation.org/show_bug.cgi?id=151005 --- Comment #1 from tanh --- In MS VBA, arguments are passed BYREF as default. (Documentation claims that VB.NET is different). In MS VBA the test case shown creates a temporary reference by using an expression DummySub (a) The expression (a) is created, referenced, updated to 'Y', and discarded. Subsequent use of the variable a is not affected by the discarded (expression) To demonstrate the same behavior using Call syntax: Call DummySub( (a) ) Wrapping a variable in () creates an expression. The CALL syntax requires call brackets, which are not expression brackets. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152132] New: Hash Mark Lines (#define) treated as comments in Libre Office Basic
https://bugs.documentfoundation.org/show_bug.cgi?id=152132
Bug ID: 152132
Summary: Hash Mark Lines (#define) treated as comments in Libre
Office Basic
Product: LibreOffice
Version: 7.4.2.3 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: BASIC
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: tanhda...@gmail.com
Description:
#if fred
Is treated as a comment.
It should always be treated as an error.
Steps to Reproduce:
Create new Basic subroutine:
sub Mysub
#if fred
dim a as int
#else
dim a as int
#endif
end sub
Run the sub.
1.Import VBA module containing #if, #else, #endif
2.Run any function in the module
3.
Actual Results:
BASIC syntax error. Variable a already defined.
Expected Results:
Lines starting with # are errors
Reproducible: Always
User Profile Reset: Yes
Additional Info:
It would be really nice if BASIC handled #if, #else the same way VBA 6 or 7 do:
as conditional compilation meta commands. Some older OO versions handled this
differently, the initial syntax check handled #if as if: for declaration
outside of a function I got "If outside of function or sub is not allowed"
But the present implementation is even worse: #if and #else are silently
ignored when inside a function, so both branches are included.
In VBA back to Office 97, #if allows you to include different branches for
different #defines. There are predefined values ('Win32' etc), and two
different ways of defining values. #if is commonly used to allow different
branches for VBA7 and OSX: it may also be used generally, as for debug builds.
When VBA code is imported into LO, the idiosyncratic treatment of # meta
commands is confusing and unexpected: the lack of documentation contributes to
the problem.
Implementing the feature correctly would be good: implementing the feature in a
minimal way with a clear error message would be good enough.
Version: 7.4.2.3 (x86) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: en-AU (en_AU); UI: en-US
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101631] VBA function parameter is passed by reference by default
https://bugs.documentfoundation.org/show_bug.cgi?id=101631 --- Comment #11 from tanh --- (In reply to Aron Budea from comment #1) > The direct reason for the self-modifying behavior is that function > "stableford" modifies the "score" parameter, which is apparently passed by > reference. > > I can't tell if it's the correct behavior or not, got confused by different > VB-related MS resources that state contradicting things: > https://msdn.microsoft.com/en-us/library/aa263527(v=vs.60).aspx "Passing by > reference is the default in Visual Basic." > https://msdn.microsoft.com/en-us/library/ddck1z30.aspx "The default in > Visual Basic is to pass arguments by value." > They're for different VB versions, and not VBA, either, but it's still weird. > > Until this is clarified, as a workaround you can copy the parameter to a > local variable, and modify that. Just for note, the 'Visual Basic" referred to in the .NET MS resource "The default in Visual Basic is to pass arguments by value", is VB.Net VB.net is to VBA as c# is to c, only less so. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145532] Sheet copy from doc1 to doc2 breaks "Defined Range" linkage
https://bugs.documentfoundation.org/show_bug.cgi?id=145532 dev...@realcom.co.uk 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 145532] Sheet copy from doc1 to doc2 breaks "Defined Range" linkage
https://bugs.documentfoundation.org/show_bug.cgi?id=145532 dev...@realcom.co.uk changed: What|Removed |Added CC||dev...@realcom.co.uk --- Comment #3 from dev...@realcom.co.uk --- Created attachment 183684 --> https://bugs.documentfoundation.org/attachment.cgi?id=183684=edit small ods with sample Defined Range use and route to failure Attached is a sample ods file, as requested. The file contains comments to identify 'path to failure' to recreate the fault. In essence, any change to the sheet population (copy, move, delete but not rename) results in the (inter-sheet) Defined Range(s) relationships becoming corrupt. Probably stems from the internal sheet identity being inadequately robust/independent. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152131] New: Dragging document from window header bar to another location copies wrong document version
https://bugs.documentfoundation.org/show_bug.cgi?id=152131 Bug ID: 152131 Summary: Dragging document from window header bar to another location copies wrong document version Product: LibreOffice Version: unspecified Hardware: x86 (IA32) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: andrewjsk...@gmail.com If you use the MacOS feature to drag the document icon in the Window title bar to another location (such as a folder or an email), if the same document was loaded under a particular filename and then saved using Save As... to a different filename, the unamended document under the original filename gets dragged, as oppposed to the most recent version. To reproduce this bug: 1. Create a new text document in LibreOffice Writer. Type "this is the original document" into the document. 2. Save it under the name "Test.odt". 3. Type "And this is an amendment" into the document. 4. Save it under the name "Test001.odt". 5. Drag the document icon from the title bar of the window to another location (such as the desktop). You will find that the dragged document is "Test.odt" and not "Test001.odt". If you open the dragged file, you will see that it does not contain the words "And this is an amendment". The correct behaviour would be for the dragged document to be Test001.odt, and for it to contain the words "And this is an amendment". Thanks Andrew -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152130] New: user defined calc chart names not reflected in e.g. BASIC macros
https://bugs.documentfoundation.org/show_bug.cgi?id=152130
Bug ID: 152130
Summary: user defined calc chart names not reflected in e.g.
BASIC macros
Product: LibreOffice
Version: 7.4.2.3 release
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: trowelandmatt...@yahoo.co.uk
Description:
if a chart name is changed from defaults the default name is retained 'in
background' of API and the chart can not be accsed by the new user name:
e.g.
for single chart (Object 1) renamed in Calc GUI to (Chart1)
:
getByIndex(0) > gets the chart
[getByIndex(0)] .Name > gets the original default name (Object 1)
and getByName("Object 1") also works to get the chart
but
getByName("Chart1") fails ('Chart1 not found')
Steps to Reproduce:
1.see above
2.
3.
Actual Results:
new user/GUI defined name for chart not found e.g. with basic macro
Expected Results:
user defined chart names should be find-able with e.g. getByName , and the old
default names should not remain 'in background' being used by the API
also; getByIndex can be awkward because index positions of new vs copied charts
is not intuitive
Reproducible: Always
User Profile Reset: No
Additional Info:
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47679] Copy + Paste changes "OpenSymbol" font to "StarSymbol"
https://bugs.documentfoundation.org/show_bug.cgi?id=47679 --- Comment #16 from V Stuart Foote --- > or a fully Open Office PUA string s/Open Office/OpenSymbol -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47679] Copy + Paste changes "OpenSymbol" font to "StarSymbol"
https://bugs.documentfoundation.org/show_bug.cgi?id=47679 --- Comment #15 from V Stuart Foote --- Testing attachment 163496 with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded For string U+20AC U+2021 U+2020 U+00BB or a fully Open Office PUA string, e.g. U+e11aU+e691U+e690U+e593U+e594 Confirm handling of the copy/paste and copy/paste special (unformatted or RTF) is now consistent. But I do see that the handling of PUA glyph fallback around OpenSymbol is doing some odd things with the sample document prepared with 7.0.0 Seems font "selection" has changed considerably (between 7.0.0 and 7.5.0) on Windows for fallback mapping U+f080 U+f087 U+f086 U+f0bb PUA -- but I think that is to be expected as those specific codepoints are not (never were?) present in OpenSymbol PUA space and got StarSymbol/StarBat mappings, and the test document as structured is no longer applicable for testing OpenSymbol PUA. Better OpenSymbol specific PUA string (no StarBat, StarSymbol lookups) might be: U+e11aU+e691U+e690U+e593U+e594 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=152116 --- Comment #4 from V Stuart Foote --- (In reply to Eyal Rozenberg from comment #3) > (In reply to R. Green from comment #0) > I can't reproduce this with a 7.5 build: Note: "Close then reopen" not just collapse the SB deck, please recheck. No issue if the SB deck is only collapsed and expanded. Only with a full close / open of the SB -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151846] LibreOffice 7.4 missing several imports in com.sun.star.chart2 namespace
https://bugs.documentfoundation.org/show_bug.cgi?id=151846 --- Comment #9 from flywire --- (In reply to Commit Notification from comment #8) > Noel Grandin committed a patch related to this issue. > It has been pushed to "master": Doesn't look like a Resolved Fix to me. Seems a commit unintentionally broke functionality and dev is only restoring code required for a specific example. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152129] New: Cannot move shape to left or upper adjacent position using (some) base points
https://bugs.documentfoundation.org/show_bug.cgi?id=152129 Bug ID: 152129 Summary: Cannot move shape to left or upper adjacent position using (some) base points Product: LibreOffice Version: 6.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: luk_dha...@yahoo.co.uk Description: Moving a shape to one of its adjacent positions can normally be done by copying the X- or Y-coordinate to itself after selecting another base point. For example, to move the shape to its right, you can select the top right base point, copy the X-coordinate, then select the top left base point, then paste the new X value. Now, this trick doesn't work anymore when moving to the left or upper direction. It does still work however for the right and lower directions. Steps to Reproduce: 1. Place any shape, e.g. a rectangle. 2. Select RMB > "Position and Size...". 3. Notice the default base point is top left. 4. Copy the X-coordinate. 5. Select the top right base point (position). 6. Paste the value into the X-coordinate. 7. Click OK. Actual Results: The shape does not move. Expected Results: The shape should have moved to the left. Reproducible: Always User Profile Reset: No Additional Info: It does work when selecting the middle or lower left base point instead. So there's an easy workaround. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152128] New: backspace key does not work when creating a new address block in mail merge
https://bugs.documentfoundation.org/show_bug.cgi?id=152128 Bug ID: 152128 Summary: backspace key does not work when creating a new address block in mail merge Product: LibreOffice Version: 7.3.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ch...@chriscurvey.com Description: 1. Start the Mail Merge Wizard 2. Make it a "letter" 3. Choose a spreadsheet of addresses 4. Under "address block" choose "more" 5. Create a new address block 6. Type some characters in the text box 7. Try to erase the characters using backspace You will be unable to do so. Steps to Reproduce: see description Actual Results: letters are not deleted when hitting the backspace key Expected Results: letters should be deleted when I hit the backspace key Reproducible: Always User Profile Reset: No Additional Info: filing bugs here is painful I like Jello -- 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 --- Comment #61 from Commit Notification --- Siddharth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9cac01b4f19c8fc3adb1a19a71b2f214a1586d8f tdf#143148 Use pragma once instead of include guards It will be available in 7.5.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 145532] Sheet copy from doc1 to doc2 breaks "Defined Range" linkage
https://bugs.documentfoundation.org/show_bug.cgi?id=145532 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Status|UNCONFIRMED |NEEDINFO Whiteboard| QA:needsComment| Ever confirmed|0 |1 --- Comment #2 from Buovjaga --- (In reply to devMgr from comment #0) > Steps to Reproduce: > 1.Create Doc1 with Defined Range specs and valid formulae that use the D.R.s > 2.Create Doc2 with distinct Defined Range specs and valid formulae that use > the D.R.s Please attach minimal example spreadsheets at this step, so we can quickly reproduce the problem. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the documents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152127] Improve Help Online (/text/shared/01/01010303.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152127 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Assignee|libreoffice-b...@lists.free |buzea.bog...@libreoffice.or |desktop.org |g Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152127] New: Improve Help Online (/text/shared/01/01010303.xhp)
https://bugs.documentfoundation.org/show_bug.cgi?id=152127 Bug ID: 152127 Summary: Improve Help Online (/text/shared/01/01010303.xhp) Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: buzea.bog...@libreoffice.org CC: olivier.hal...@libreoffice.org Description: After I enter my data into Tools - Options - LibreOfficeDev - User Data, in the File - New - Business Card - Private tab I get "Country/state:" and 2 input for this fields. In Writer the order is right, first the country, than the state. On help page they are reverse and if you fill the data based on Help, you can consider that first is the state, than the country. --> Country and State need to change the order in the Help Page https://help.libreoffice.org/7.5/en-US/text/shared/01/01010303.html?=SHARED=UNIX Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152123] Non-correct display of subscript and italic characters when importing .svg-files into libreoffice writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152123 --- Comment #3 from Eyal Rozenberg --- Created attachment 183683 --> https://bugs.documentfoundation.org/attachment.cgi?id=183683=edit Partial reproduction on sample document I can only partially reproduce the bug: * Italicization is ok. * Getting regular size instead of subscript * Subscript horizontal placement is a little off: Too much space before the `t` on the middle line of the example. Build info: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Calc: threaded (build is from earlier today) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152119] Dropdown content control for RTL fields no longer selectable by mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=152119 --- Comment #2 from Eyal Rozenberg --- (In reply to Hossein from comment #0) Can't reproduce with: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bcf09f9a9bde21aac1302cbead2b23822458 CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Build timestamp: 2022-11-19_05.43.41 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150657] CALC Chart elements disappear when the data columns are hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150657 --- Comment #8 from Colin --- (In reply to Colin from comment #7) > (In reply to Stéphane Guillou (stragu) from comment #6) > > Thanks Colin. > > > > > I am finding it hard to test the issue you are describing. > > Could you please: > > > > - Describe the simplest series of precise steps to reproduce the issue, > > starting with which attachment to use > > Hi Stéphane > Oops, forgot to mention that you may wish to focus row 4 by clicking any cell in row 3 and then a down arrow My bad -- 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 Eyal Rozenberg changed: What|Removed |Added Depends on||152119 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152119 [Bug 152119] Dropdown content control for RTL fields no longer selectable by mouse -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152119] Dropdown content control for RTL fields no longer selectable by mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=152119 Eyal Rozenberg changed: What|Removed |Added Blocks||43808 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-bugs] [Bug 150657] CALC Chart elements disappear when the data columns are hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150657 Colin changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #7 from Colin --- (In reply to Stéphane Guillou (stragu) from comment #6) > Thanks Colin. > > I am finding it hard to test the issue you are describing. > Could you please: > > - Describe the simplest series of precise steps to reproduce the issue, > starting with which attachment to use Hi Stéphane With the file Chart Error Ensure group G is unhidden Double click the chart to activate the chart editing ribbon Select Data Range for editing Edit the two range values so that they both commence on row 5 as opposed to row 4 Hide Group G The chart elements should now have disappeared Now the image of the two edit panes should help you to realise that the data series parameter (Right click one of the data elements in the chart) to hide or include the hidden cells is being corrupted by the edit process - It presents on screen as checked to include hidden cells but ignores the parameter. changing the flag, saving, accessing the flag changing it back again will force it to behave as expected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152116] Navigator: State of outline headings is lost when navigator is closed then reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=152116 --- Comment #3 from Eyal Rozenberg --- (In reply to R. Green from comment #0) I can't reproduce this with a 7.5 build: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2486d99c6053af1414117faac2c0db18c0d344c4 CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Also, for those trying to reproduce: Increase the maximum heading level represented in the Navigator to 4, otherwise you won't see any subheadings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152083] Ligatures are incorrectly reversed opening RTL PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=152083 Kevin Suo changed: What|Removed |Added Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152083] Ligatures are incorrectly reversed opening RTL PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=152083 --- Comment #2 from Kevin Suo --- The below change on gerrit could fix this issue: https://gerrit.libreoffice.org/c/core/+/142978 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103239] [META] Toolbars bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103239 Bug 103239 depends on bug 114505, which changed state. Bug 114505 Summary: Changing icon theme while in RTL mode causes flipped icons in toolbar to misbehave https://bugs.documentfoundation.org/show_bug.cgi?id=114505 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Bug 129661 depends on bug 114505, which changed state. Bug 114505 Summary: Changing icon theme while in RTL mode causes flipped icons in toolbar to misbehave https://bugs.documentfoundation.org/show_bug.cgi?id=114505 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114505] Changing icon theme while in RTL mode causes flipped icons in toolbar to misbehave
https://bugs.documentfoundation.org/show_bug.cgi?id=114505 Maxim Monastirsky changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Maxim Monastirsky --- *** This bug has been marked as a duplicate of bug 149956 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152126] New: selecting a line and changing line style affects half of lines, which are not selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152126 Bug ID: 152126 Summary: selecting a line and changing line style affects half of lines, which are not selected Product: LibreOffice Version: 7.3.6.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: g.statk...@gmail.com Created attachment 183682 --> https://bugs.documentfoundation.org/attachment.cgi?id=183682=edit selecting a line and changing line style affects half of lines, which are not selected, part belongs to different group In Libre Office, selecting a line and changing line style affects half of lines, which are not selected. I need to use 5 different line styles, but i can use only two of them. For some reason line styles are grouped into two groups, and n wierd manner, because chaging the curve style affects part of the box style, which are different figures, were drawn separately, box the first, and all box lines were joined. Do not know why any curved line style affects some of the box lines, which are joined, and why selected any curve style affects other curves styles? How to fix it. it is a fresh installation of Linux Mint 21 Cinnamon v5.4.8, but i updated it mny times, after installing various packages. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117710] [META] UNO API issues
https://bugs.documentfoundation.org/show_bug.cgi?id=117710 Bug 117710 depends on bug 151846, which changed state. Bug 151846 Summary: LibreOffice 7.4 missing several imports in com.sun.star.chart2 namespace https://bugs.documentfoundation.org/show_bug.cgi?id=151846 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151846] LibreOffice 7.4 missing several imports in com.sun.star.chart2 namespace
https://bugs.documentfoundation.org/show_bug.cgi?id=151846 Noel Grandin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151846] LibreOffice 7.4 missing several imports in com.sun.star.chart2 namespace
https://bugs.documentfoundation.org/show_bug.cgi?id=151846 --- Comment #8 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ec6502a1f61fcbd4bf05b62f172650fe442c3a1d tdf#151846 Restore XChartTypeTemplate It will be available in 7.5.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 151846] LibreOffice 7.4 missing several imports in com.sun.star.chart2 namespace
https://bugs.documentfoundation.org/show_bug.cgi?id=151846 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152125] New: Ease use of Unicode control characters for bidirectionality, e.g. RLI and PDI
https://bugs.documentfoundation.org/show_bug.cgi?id=152125 Bug ID: 152125 Summary: Ease use of Unicode control characters for bidirectionality, e.g. RLI and PDI Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Keywords: needsUXEval Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de CC: libreoffice-ux-adv...@lists.freedesktop.org Created attachment 183681 --> https://bugs.documentfoundation.org/attachment.cgi?id=183681=edit Examples with RTL in LTR If you have a text run with strong RTL characters in a paragraph with base direction left-to-right, the implementation of the BiDi-Algorithm in LibreOffice works well. But there are situations where bidirectional text is not rendered as necessary if only using the BiDi-Algorithm. Since ODF has no attribute to set the base direction on a portion of text, but only on the paragraph, such situations need to be solved by inserting Unicode control characters. Such are: (1) LRI, RLI, FSI, PDI (U+2066..U+2069) (2) LRE, RLE, LRO, RLO, PDF (U+202A..U202E) (3) LRM, RLM (U+200E, U+200F) Problem A You cannot see, which one is used and where it is inserted because all this characters are hidden and have zero width. That is a problem when you need to edit the text. Using control characters (2) is problematic, but if you do not see them it is hard to remove such, for example. Problem B LibreOffice supports to enter the control characters (3). That is in Insert > Formatting Mark > Left-to-Right Mark and Right-to-Left Mark. But there exists no tool for the control characters (1) and (2). Entering them directly into the text via U+ and Alt+x is very problematic, because character order might change while entering them. A solution for A could be, to show the illustration glyphs (that with the dotted border in the Unicode chart files) when "Show Formatting Marks" is ON. I have no idea for a good tool to enter these controls. You should use the attachment and try to bring the sentence which has no control character into the correct word order. Then you will notice the problems for the user. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152017] footnotes move onto the next page as I add paragraphs to my document
https://bugs.documentfoundation.org/show_bug.cgi?id=152017 --- Comment #3 from Sarah --- Hi Stephanie. Apologies for my delay in replying. I did downgrade back to: Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 16; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: CL That did resolve the issue, but it has now started again. As my document is a genealogy course assignment, it states family member's names and dates of birth / death, I don't want to upload it here. I shall e-mail the document to you now. Sarah -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86174] logic error with mod() and int() function
https://bugs.documentfoundation.org/show_bug.cgi?id=86174 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #6 from Roman Kuznetsov <79045_79...@mail.ru> --- Still repro in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ddb8a1a282aae74c1cee3a5e1f446abd0c00b116 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133796] [EDITING] Scroll Lock mode fails for horizontal cursor keys, when there are frozen rows and columns
https://bugs.documentfoundation.org/show_bug.cgi?id=133796 --- Comment #6 from zzz --- Problem still reproduces in Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: en-US Calc: CL on Windows 10 Professional -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107701] [META] Table border bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107701 Bug 107701 depends on bug 120530, which changed state. Bug 120530 Summary: Table border isn't redrawn until some movement https://bugs.documentfoundation.org/show_bug.cgi?id=120530 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120530] Table border isn't redrawn until some movement
https://bugs.documentfoundation.org/show_bug.cgi?id=120530 Gabor Kelemen (allotropia) changed: What|Removed |Added Resolution|--- |FIXED CC||kelem...@ubuntu.com, ||vmik...@collabora.com Status|NEW |RESOLVED --- Comment #5 from Gabor Kelemen (allotropia) --- This seems to have been fixed in 6.3 with https://git.libreoffice.org/core/+/d5b50e74ee822e1c8402e3044e14799e47907ff8 author Miklos Vajna Mon Sep 16 21:15:28 2019 +0200 committer Mike Kaganski Tue Sep 17 18:57:09 2019 +0200 tdf#105330 sw: fix lost cursor on undoing nested table insert -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107701] [META] Table border bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107701 Bug 107701 depends on bug 119520, which changed state. Bug 119520 Summary: The table borders/content shifting when saving with selected content (and afterwards when deselecting) https://bugs.documentfoundation.org/show_bug.cgi?id=119520 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119520] The table borders/content shifting when saving with selected content (and afterwards when deselecting)
https://bugs.documentfoundation.org/show_bug.cgi?id=119520 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|NEW |RESOLVED CC||kelem...@ubuntu.com, ||michael.st...@allotropia.de Resolution|--- |FIXED --- Comment #10 from Gabor Kelemen (allotropia) --- This seems to be fixed in 7.3 with https://git.libreoffice.org/core/+/dadaf930d14283f96cc06741d2eec6d846e59f7f author Michael Stahl Mon Jul 11 19:20:33 2022 +0200 committer Miklos Vajna Thu Jul 14 16:49:07 2022 +0200 sw: fix spurious layout invalidation from ~SwCallLink() Thanks Michael! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152075] Writer: TOC for chapter should start at current level+1, not current level
https://bugs.documentfoundation.org/show_bug.cgi?id=152075 --- Comment #8 from Mike Kaganski --- (In reply to Peter Roelofsen from comment #7) Having the described layout (Chapter ToC prior to the chapter itself) would possibly best be implemented by the third element in the "For:" drop-down (next to "Entire document" and "Chapter"), like "Specified chapter", giving a choice similar to what "Cross-reference"->"Headings" field allows. That is a separate issue, that needs an own proposal. This is off-topic here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152075] Writer: TOC for chapter should start at current level+1, not current level
https://bugs.documentfoundation.org/show_bug.cgi?id=152075 Peter Roelofsen changed: What|Removed |Added CC||floris...@gmail.com --- Comment #7 from Peter Roelofsen --- Having a TOC right below a chapter title with the chapter title included seems redundant to me. But there are books where a new chapter starts on a right page, and the TOC for that chapter sits on the opposite (left) page. In that case, including the chapter title in the TOC would make perfect sense. Unfortunately, you wouldn't be able to include a chapter TOC just before the start of a chapter in the present implementation. I played a bit with inserting the content of a single chapter in a section, wondering if you can make a TOC for just a section of a document. It turns out that you can't, but maybe it's an idea to allow TOCs for sections. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152075] Writer: TOC for chapter should start at current level+1, not current level
https://bugs.documentfoundation.org/show_bug.cgi?id=152075 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||0318 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=152098 --- Comment #5 from JohnHa --- I (OP) cannot reproduce today. I was doing testing by saving with the cursor in various positions in the file and it was reproduceable so I am wondering if it is cursor position dependent and/or related to the cursor location problem bug 141586. When testing this morning on the first occasion it opened OK and I could scroll, but it then locked up. I had minimised its window and I could not re-open the window. CPU was at 26%. On the second, third and fourth tests it opened within a few seconds and did not lock up. My PC is minimal with few startup programs which could interfere. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152075] Writer: TOC for chapter should start at current level+1, not current level
https://bugs.documentfoundation.org/show_bug.cgi?id=152075 --- Comment #6 from Mike Kaganski --- (In reply to Mike Kaganski from comment #5) > 1. The "Chapter" element must mean "current section" Sorry for the use of misleading "section" word there - it is meant "current part of the document outline". I have no good proposal for the UI term - but I feel "chapter" term, still used in the "For:" dropdown in the dialog, to be inadequate for the newly implemented "current level" behavior. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152075] Writer: TOC for chapter should start at current level+1, not current level
https://bugs.documentfoundation.org/show_bug.cgi?id=152075 --- Comment #5 from Mike Kaganski --- There are two ~orthogonal aspects: 1. Creation of a ToC *for the current part of the document*; 2. Inclusion of the entry that defines the current path into the ToC. IMO, the "flexible" proposal from comment 1 makes little sense. It is unreasonable to expect both levels higher than current in the local ToC, and also starting from levels lower than the immediate sublevels of the current one. So: when you have a section 2.4.6, and create a ToC under it, you might want to have 2.4.6 in the generated ToC, or you may want to have only 2.4.6.1, 2.4.6.2, ... . But you would not want entry 2 there, nor entry 2.4. In a strange situation when one could want these, one can always create cross-reference fields before the ToC, with specified levels. And one would not want the ToC to only contain 2.4.6.1.1, without 2.4.6.1 itself, in the ToC. All the extra situations are implementable using specific style assignment to the ToC, instead of basing the ToC on outline. One can even implement the layout requested in the mentioned Russian forum topic, using existing tools; bit since the requests to have ToCs for levels below 2, and also to omit the "starting" level, are really common, these *two* specific needs should be addressed in dedicated UI, but not an unlimited flexibility. So IMO: 1. The "Chapter" element must mean "current section" - which is already implemented in master, right? 2. There should be a [] Include current "chapter" into the ToC. The flexible "from level" selector is overkill, and is bad (would result in poor UX). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152124] New: Figure captions for custom captions disappear after reopening the document
https://bugs.documentfoundation.org/show_bug.cgi?id=152124 Bug ID: 152124 Summary: Figure captions for custom captions disappear after reopening the document Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nf_m...@dismail.de Description: Custom figure captions disappear after saving, close and reopening the document. Please see the section "steps to reproduce". Steps to Reproduce: 1. Add a figure to libreoffice 2. Add a caption to this figure, but use a custom-name, like "Bildbeschreibung". 3. If you add a second figure, the new figure will be also labeled with the new custom-name label and the automatic figure counter is set to "2". 4. save and close the document 5. reopen the document (both figures are correctly labeled as "Bildbeschreibung 1" and "Bildbeschreibung 2" 6. add a new figure and try to add the custom-caption. 7. See that the custom label disappeared into the checkbox where you can add labels 8. If you try to add again your custom-label like "Bildbeschreibung", this works, but the figure is not labeled to "Bildbeschreibung 3" but to "Bildbeschreibung 1". Now, there are two "Bildbeschreibung 1"-labeled figures in your document. Actual Results: see steps to reproduce Expected Results: custom figure labels do not disappear when closing and reopening the document. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE 7.3.7-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144853] Sentence case applied around word, not undone when cycling case with Shift + F3
https://bugs.documentfoundation.org/show_bug.cgi?id=144853 --- Comment #12 from Linux --- I confirm in LibreOffice 7.4.2 (Zorin OS 16.2) everything is the same. If you select one word in a sentence, and then switch Shift + F3 works correctly. But if you set the cursor in one word in a sentence, then the switch Shift + F3 does not work correctly! Then all the words in the sentence written in capital letters are changed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152123] Non-correct display of subscript and italic characters when importing .svg-files into libreoffice writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152123 --- Comment #2 from nf_m...@dismail.de --- Created attachment 183680 --> https://bugs.documentfoundation.org/attachment.cgi?id=183680=edit inkscape .svg file to reproduce the bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152123] Non-correct display of subscript and italic characters when importing .svg-files into libreoffice writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152123 --- Comment #1 from nf_m...@dismail.de --- Created attachment 183679 --> https://bugs.documentfoundation.org/attachment.cgi?id=183679=edit output example of italic and subcripted text. See results in inkscape and libreoffice writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152123] New: Non-correct display of subscript and italic characters when importing .svg-files into libreoffice writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152123 Bug ID: 152123 Summary: Non-correct display of subscript and italic characters when importing .svg-files into libreoffice writer Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nf_m...@dismail.de Description: Display of subscripts and italic characters are not correctly displayed into libreoffice writer. See attached files Steps to Reproduce: 1. Draw a .svg graphic (in Inkscape) and use subscript and italic 2. drag and drop the .svg into libreoffice writer 3. see non-correct display of .svg-file inside libreofficwriter Actual Results: See attached screenshot Expected Results: file looks same as in inkscape Reproducible: Always User Profile Reset: Yes Additional Info: libreoffice writer should display .svg-files including subscripts and italic characters correctly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152106] can not open particular DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=152106 László Németh changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2080 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152106] can not open particular DOCX file
https://bugs.documentfoundation.org/show_bug.cgi?id=152106 László Németh changed: What|Removed |Added Status|ASSIGNED|RESOLVED Assignee|nem...@numbertext.org |libreoffice-b...@lists.free ||desktop.org Resolution|--- |FIXED See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||8518 Regression By|Eike Rathke | --- Comment #4 from László Németh --- tdf#152106 sw layout: fix freezing of multicol sections with flys Loading documents with multicol sections with flys could freeze Writer. Add loop control for multicol sections to fix it. Regression from commit 8feac9601cfe35ee0966776bab15d122206f154e "tdf#138518 sw: layout: avoid moving flys forward prematurely". Follow-up to ed12269c42f75f553bb8a8770923406f7824e473 "tdf#142080 sw: layout: fix infinite loop in CalcContent()". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33697] Unable to choose proxy type "system"
https://bugs.documentfoundation.org/show_bug.cgi?id=33697 --- Comment #22 from Laurent Balland --- Confirmed with Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
