[Libreoffice-bugs] [Bug 151059] Can't type "^" character with AltGr+3 using Slovenian keyboard, opening Gallery instead
https://bugs.documentfoundation.org/show_bug.cgi?id=151059 --- Comment #3 from grofaty --- I can confirm @Tex2002ans work-around fixes the problem. Excellent. This was really really really annoying, specially in LibreOffice Calc where "^" character is used for "exponent". Now I have to fix this in all of the my computers and coworkers etc. I assume (I may be wrong) this shortcut was added at some point to LibreOffice. Can someone search for the commit and revert it properly for all users. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: sl-SI (en_SI); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155399] New: Writer shows incorrect colors on fillable form elements when system UI is set to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155399 Bug ID: 155399 Summary: Writer shows incorrect colors on fillable form elements when system UI is set to dark mode Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: andrew.hak...@gmail.com Description: I'm running Libre Office in Linux under KDE. I have the system theme set to Breeze Dark. Opening a previously created writer document that has form elements in it, with the KDE theme set to dark mode, ALL of the form text boxes have a dark grey background and light gray text, even though the main part of the document is normal (black text on a white background). There are really 4 bugs here: 1) I can't select ALL of the form elements and change them at once. I can only select one form element at a time, and have to change them individually. This is REALLY painful. 2) Why does the background color and font color of form elements default to some color from the system color scheme when the non-form parts of the document work normally? 3) To fix the background, I can simply change the color and pick "white" instead of "default", but to fix the font color, it's actually set to "black" the first time I open the font dialog, but the text is picking a different color from the UI color scheme. To actually change it to be black, I have to change it to a color other than black, press OK, then re-open the font dialog a second time, and set it back to "black" again - then it actually changes. 4) The border colors of the form elements also got changed from black to a lighter color from the color scheme too. Form elements shouldn't default to random colors from the UI theme when the rest of the document doesn't do that. Form elements should be multi-selectible and be able to mass edit common parameters of them (such as colors, appearance, fonts, etc.) all at one time. There's also a long-standing bug with form elements that are set to "centered" text. When I open a saved file, the text is not centered, but way off to the right of the form box. If I type an extra space at the end of the text, then the text centers properly. It will remain centered until I save, and re-open the document in a new session - then it's back to not being centered correctly again. All of these bugs (form element colors, and text alignment) affects the final rendering of the document - if I export a PDF, I get the incorrect colors and alignments as well until I manually fix all of them. Steps to Reproduce: 1.Create a document with forms with the color scheme set normally - put some text in the forms and set them to "centered" - save the document, and close Writer 2.Change the system UI to dark mode and re-open the saved document Actual Results: Form fields have incorrect colors and text alignment Expected Results: Form fields maintain colors consistent with the rest of the document regardless of UI color schemes. Text alignment of text fields set to "centered" is actually centered. Reproducible: Always User Profile Reset: No Additional Info: Please add more unit tests to form fields in writer - there have been a number of weird issues with forms in the last number of versions, so clearly there isn't enough testing being done to ensure forms are working properly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142444] Hyperlink not added to the with Ctrl-A selected text in cell
https://bugs.documentfoundation.org/show_bug.cgi?id=142444 BogdanB changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #5 from BogdanB --- Feel free to reopen if it's not working for you with a newer version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108252] [META] Cell-related bugs and enhancements (including formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=108252 BogdanB changed: What|Removed |Added Depends on||119423 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=119423 [Bug 119423] CTRL+D leads to invalid merged cells that are not selectable and are not saved -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119423] CTRL+D leads to invalid merged cells that are not selectable and are not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=119423 BogdanB changed: What|Removed |Added Blocks||108252 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108252 [Bug 108252] [META] Cell-related bugs and enhancements (including formatting) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155384] Fixed width paste does not sample enough input data
https://bugs.documentfoundation.org/show_bug.cgi?id=155384 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 155384] Fixed width paste does not sample enough input data
https://bugs.documentfoundation.org/show_bug.cgi?id=155384 --- 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 155353] unable to export as PDF in 7.5
https://bugs.documentfoundation.org/show_bug.cgi?id=155353 --- 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 145149] Unable to open spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=145149 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137272] Superscripted font is cut off and line spacing increased when smaller block quoted text has footnote or endnote in it, due to use of one font size for all footnotes in
https://bugs.documentfoundation.org/show_bug.cgi?id=137272 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145149] Unable to open spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=145149 --- Comment #6 from QA Administrators --- Dear Richard BARRAS, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137272] Superscripted font is cut off and line spacing increased when smaller block quoted text has footnote or endnote in it, due to use of one font size for all footnotes in
https://bugs.documentfoundation.org/show_bug.cgi?id=137272 --- Comment #14 from QA Administrators --- Dear TH, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89069] FILESAVE: HTML output removes bold/italic from open-quote characters
https://bugs.documentfoundation.org/show_bug.cgi?id=89069 --- Comment #13 from QA Administrators --- Dear Rev. Bob, 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 66299] FILESAVE: Shapes not exported to XHTML
https://bugs.documentfoundation.org/show_bug.cgi?id=66299 --- Comment #10 from QA Administrators --- Dear callow.mark, 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 64067] HTML document conversion and viewing text justification issue with Microsoft Word HTML document
https://bugs.documentfoundation.org/show_bug.cgi?id=64067 --- Comment #12 from QA Administrators --- Dear grave_123, 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 52586] Mail Merge doesn't seem to respect a standard data sources filter - steps in Comment 4 (workaround: use filter in address list)
https://bugs.documentfoundation.org/show_bug.cgi?id=52586 --- Comment #20 from QA Administrators --- Dear Joshua, 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 142343] VIEWING Chart with calculated floating values displays broken data labels
https://bugs.documentfoundation.org/show_bug.cgi?id=142343 --- Comment #6 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 142112] Calc : routine Msgbox(Application.Name) returns "Microsoft Excel" in place of "LibreOffice Calc"
https://bugs.documentfoundation.org/show_bug.cgi?id=142112 --- Comment #5 from QA Administrators --- Dear Laurent Louvet, 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 141302] PARAGRAPH: Thin lines between paragraphs after filling area with a colour
https://bugs.documentfoundation.org/show_bug.cgi?id=141302 --- Comment #6 from QA Administrators --- Dear Panos Stokas, 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 155398] Writer file error
https://bugs.documentfoundation.org/show_bug.cgi?id=155398 --- Comment #1 from david chen --- Created attachment 187389 --> https://bugs.documentfoundation.org/attachment.cgi?id=187389=edit object has error , and unrecoverable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155398] New: Writer file error
https://bugs.documentfoundation.org/show_bug.cgi?id=155398 Bug ID: 155398 Summary: Writer file error Product: LibreOffice Version: 7.5.1.2 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d...@ms31.hinet.net Description: show error message then no response Steps to Reproduce: 1.open file 2.click upper icon 3.shown error Actual Results: liberoffice no response , need close this program Expected Results: it's wrong Reproducible: Always User Profile Reset: No Additional Info: I can send you file , my e-mail d...@ms31.hinet.net -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153034] Three wrong Greek characters in WordPerfect 5 import
https://bugs.documentfoundation.org/show_bug.cgi?id=153034 --- Comment #9 from e...@columbia.edu --- Just to repeat what I wrote on SourceForge: the latest commit leaves one character incorrect. I've posted the details in libwpd on SourceForge. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155397] New: Urgent: Libreoffice crashes frequently on iMac M1 CPU
https://bugs.documentfoundation.org/show_bug.cgi?id=155397 Bug ID: 155397 Summary: Urgent: Libreoffice crashes frequently on iMac M1 CPU Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ezyl...@gmail.com Description: I cannot use Libreoffice 7.4.6.2 at all. Each time I run it, it crashes on my newly bought Apple iMac with M1 CPU and latest Vetura op system. Please fix the bug as soon as possible. I copy and past some crash report for your information. Steps to Reproduce: 1.fix the bug to make the sw work on iMac 2. 3. Actual Results: need to fix the bug as soon as possible Expected Results: Fix the bug. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no The copy of part of error report is as follows: Translated Report (Full Report Below) - Process: soffice [1715] Path: /Applications/LibreOffice.app/Contents/MacOS/soffice Identifier:org.documentfoundation.libreoffice Version: 7.4.6002 (7.4.6002) App Item ID: 1630474372 App External ID: 855383657 Code Type: ARM-64 (Native) Parent Process:launchd [1] User ID: 501 Date/Time: 2023-05-19 11:00:33.0857 +1000 OS Version:macOS 13.4 (22F66) Report Version:12 Anonymous UUID:2A2ECC49-598B-0138-979D-4974FD7C3F67 Time Awake Since Boot: 740 seconds System Integrity Protection: enabled Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x1a5c64724 __pthread_kill + 8 1 libsystem_pthread.dylib0x1a5c9bc28 pthread_kill + 288 2 libsystem_c.dylib 0x1a5ba9ae8 abort + 180 3 libuno_sal.dylib.3 0x1030404c8 (anonymous namespace)::signalHandlerFunction(int, __siginfo*, void*) (.cold.1) + 32 4 libuno_sal.dylib.3 0x103033c98 (anonymous namespace)::signalHandlerFunction(int, __siginfo*, void*) + 1060 5 libsystem_platform.dylib 0x1a5ccaa24 _sigtramp + 56 6 libsystem_pthread.dylib0x1a5c9bc28 pthread_kill + 288 7 libsystem_c.dylib 0x1a5ba9ae8 abort + 180 8 libsystem_malloc.dylib 0x1a5acae28 malloc_vreport + 908 9 libsystem_malloc.dylib 0x1a5ace6e8 malloc_report + 64 10 libsystem_malloc.dylib 0x1a5adaf20 find_zone_and_free + 308 11 libuno_sal.dylib.3 0x10301f71c rtl_uString_release + 52 12 libuno_cppu.dylib.30x103259bb4 cppu::idestructElements(void*, _typelib_TypeDescriptionReference*, int, int, void (*)(void*)) + 268 13 libuno_cppu.dylib.30x103259a5c cppu::idestroySequence(_sal_Sequence*, _typelib_TypeDescriptionReference*, _typelib_TypeDescription*, void (*)(void*)) + 184 14 libuno_cppu.dylib.30x10326435c uno_type_sequence_destroy + 20 15 libvclplug_osxlo.dylib 0x107088cdc +[AquaA11yTextAttributesWrapper createAttributedStringForElement:inOrigRange:] + 1000 16 AppKit 0x1a94e9bbc -[NSAccessibilityAttributeAccessorInfo getParameterizedAttributeValue:forObject:withParameter:] + 72 17 AppKit 0x1a94eb6b4 ___NSAccessibilityEntryPointValueForAttributeWithParameter_block_invoke.777 + 408 18 AppKit 0x1a94e6a84 NSAccessibilityPerformEntryPointObject + 44 19 AppKit 0x1a94e8684 NSAccessibilityEntryPointValueForAttributeWithParameter + 232 20 AppKit 0x1a92ea2d4 CopyParameterizedAttributeValue + 504 21 HIServices 0x1ab512678 _AXXMIGCopyParameterizedAttributeValue + 464 22 HIServices 0x1ab5399ac _XCopyParameterizedAttributeValue + 540 23 HIServices 0x1ab4f152c mshMIGPerform + 204 24 CoreFoundation 0x1a5d7abcc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 60 25 CoreFoundation 0x1a5d7aaec __CFRunLoopDoSource1 + 520 26 CoreFoundation 0x1a5d794cc
[Libreoffice-bugs] [Bug 155384] Fixed width paste does not sample enough input data
https://bugs.documentfoundation.org/show_bug.cgi?id=155384 --- Comment #5 from Pierre Fortin --- Created attachment 187388 --> https://bugs.documentfoundation.org/attachment.cgi?id=187388=edit sample file 2 I have no idea how that file got selected... Here's another try at the file I thought was attached... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120283] connector view changes when duplicating slide
https://bugs.documentfoundation.org/show_bug.cgi?id=120283 --- Comment #10 from Dave Gilbert --- I'm chasing this backwards from the XML output, the points come from SdrEdgeObj::ImpCalcEdgeTrack and it's called very differently in the good and bad cases; I'll follow it back to see why. In the good case we see (with a bunch of debug): SdrEdgeObj::ImpCalcEdgeTrack entry: 0x2637f20 eKind: 3 Angles:27000 / 9000 Points:14829,2381 / 16086,3766 BoundRects: 2758x921@(13450,1462) / 3223x1039@(14475,3765) BewareRects: 3758x1921@(12950,962) / 4223x2039@(13975,3265) bezier>2 case(Z / 4) Pts: 14829,2381 / 14829,3074 / 16086,3074 / 16086,3766 d1: 0 / 693 d2: 0 / -692 in the bad case it tries a whole bunch of different configurations, 5 point, 4 point Z, 3 point and finally a 4 point U; in all cases the bound and beware rects fro the destination is screwy compared to the original: SdrEdgeObj::ImpCalcEdgeTrack entry: 0x42daf20 eKind: 3 Angles:27000 / 0 Points:14829,2381 / 16086,3766 BoundRects: 2758x921@(13450,1462) / 1x1@(16086,3766) BewareRects: 3758x1921@(12950,962) / 1x1@(16086,3766) bezier>2 case(? / 5) Pts: 14829,2381 / 14829,3324 / 16086,3766 / 16086,3766 d1: 0 / 943 d2: 0 / 0 SdrEdgeObj::ImpCalcEdgeTrack entry: 0x42daf20 eKind: 3 Angles:27000 / 9000 Points:14829,2381 / 16086,3766 BoundRects: 2758x921@(13450,1462) / 1x1@(16086,3766) BewareRects: 3758x1921@(12950,962) / 1x1@(16086,3766) bezier>2 case(Z / 4) Pts: 14829,2381 / 14829,3324 / 16086,3324 / 16086,3766 d1: 0 / 943 d2: 0 / -442 SdrEdgeObj::ImpCalcEdgeTrack entry: 0x42daf20 eKind: 3 Angles:27000 / 18000 Points:14829,2381 / 16086,3766 BoundRects: 2758x921@(13450,1462) / 1x1@(16086,3766) BewareRects: 3758x1921@(12950,962) / 1x1@(16086,3766) bezier>2 case(L / 3) Pts: 14829,2381 / 14829,3766 / 14829,3766 / 16086,3766 d1: 0 / 1385 d2: -1257 / 0 SdrEdgeObj::ImpCalcEdgeTrack entry: 0x42daf20 eKind: 3 Angles:27000 / 27000 Points:14829,2381 / 16086,3766 BoundRects: 2758x921@(13450,1462) / 1x1@(16086,3766) BewareRects: 3758x1921@(12950,962) / 1x1@(16086,3766) bezier>2 case(U / 4) Pts: 14829,2381 / 14829,3766 / 16086,3766 / 16086,3766 d1: 0 / 1385 d2: 0 / 0 I'll chase that back. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #5 from m.a.riosv --- Please test with a clean profile, Menu/Help/Restart in Safe Mode If it doesn't work, you can test with a prerelease 7.6.a1 https://qa.blog.documentfoundation.org/2023/05/17/libreoffice-7-6-alpha1-is-available-for-testing/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153527] LibreOffice 7.5 Calc: unable to apply formatting to all cells in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=153527
TBeholder changed:
What|Removed |Added
CC||turbobehol...@mail.ru
--- Comment #19 from TBeholder ---
(In reply to defector from comment #0)
> Then you want
> to format all the cells. Select all cells and press Ctrl + 1 and format the
> cells:
Obviously it’s a bug, but… I know some people try to paint on spreadsheets
manually like this, but you know there are editable styles, right?
(In reply to ady from comment #11)
> other complains), the response would also be about a UX decision, with a
> relevant comment about workarounds ("modify the default cell style").
It’s not a workaround, it’s the primary tool for this purpose. I mean, is it
not obvious that ability to apply the same formatting to many elements is the
main reason for having styles to begin with?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155388] Context menu in SlideShow mode temporarily disables SlideShow mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155388 --- Comment #4 from m.a.riosv --- With a clean profile, v76? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155388] Context menu in SlideShow mode temporarily disables SlideShow mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155388 --- Comment #3 from m.a.riosv --- Ok, I see, but I can't reproduce it, even with the same template. v7600a1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 haxel...@pm.me changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #4 from haxel...@pm.me --- (In reply to m.a.riosv from comment #2) > Have you selected > Menu/Tools/Options/Application colors - Scheme - LibreOffice dark Added an attachment, where it's selected and unmodified. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 --- Comment #3 from haxel...@pm.me --- Created attachment 187387 --> https://bugs.documentfoundation.org/attachment.cgi?id=187387=edit Selected Application Colors Yes, it's selected here and unmodified. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155389] MCGR FILESAVE PPTX fill style is erroneously set to NONE
https://bugs.documentfoundation.org/show_bug.cgi?id=155389 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from m.a.riosv --- Who does, may have mistakes, but I'm sure I win. Reproducible. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b3c88dc039d447322b8c8c564ab6e2f0ce9c5b90 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded BTW, v753 shows the whole shape blank. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155396] New: Click on 'Size' field in status bar should open Position dialog in Calc too
https://bugs.documentfoundation.org/show_bug.cgi?id=155396 Bug ID: 155396 Summary: Click on 'Size' field in status bar should open Position dialog in Calc too Product: LibreOffice Version: 7.6.0.0 alpha1+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de When a shape is selected and you click on the 'Size' field in the status bar, then the Position dialog opens if the module is Writer, Impress or Draw. But if you do the same in Calc, nothing happens. Request: If you click in Calc on the 'Size' field of the status bar while a shape is selected, then the Position dialog should open, same as in the other modules. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145702] Bad cint() behaviour for languages using comma as separator before the decimal point
https://bugs.documentfoundation.org/show_bug.cgi?id=145702
--- Comment #3 from Kai Struck ---
I can confirm a (mysterious) change in behaviour of the cint command in the 7er
versions.
with English local language setting:
In all previous versions (and OpenOffice) something like
cint("1,a") gave 1
cint("1,e") gave 1
cint("1,e2") gave 1
In LO7 all above give 0
In German local setting the "e" is suddenly treated as exponent:
In all previous versions (and OpenOffice) something like
cint("1,a") gave 1
cint("1,e") gave 1
cint("1,e1") gave 1
cint("1,e2") gave 1
In LO7:
cint("1,a") still gives 1
cint("1,e") gives 0
cint("1,e1") gives 10
cint("1,e2") gives 100
I don't know what's going on but report it here. Tested on Windows 10 and
LinuxMint17 and 21.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155384] Fixed width paste does not sample enough input data
https://bugs.documentfoundation.org/show_bug.cgi?id=155384 --- Comment #4 from m.a.riosv --- Created attachment 187386 --> https://bugs.documentfoundation.org/attachment.cgi?id=187386=edit Screenshot opening csv sample file I think sample file, it's not the same you have reported. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153527] LibreOffice 7.5 Calc: unable to apply formatting to all cells in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=153527 m.a.riosv changed: What|Removed |Added CC||rob...@prino.org --- Comment #18 from m.a.riosv --- *** Bug 155395 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155395] Calc - Change font of whole sheet does not work and has side effects
https://bugs.documentfoundation.org/show_bug.cgi?id=155395 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 153527 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155394] Inserting an animated gif crash LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155394 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- No problem here Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #2 from m.a.riosv --- Have you selected Menu/Tools/Options/Application colors - Scheme - LibreOffice dark -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155390] "Growing Liberty" Impress template has a slide of unclear (suspicious for advertizing) nature in the end
https://bugs.documentfoundation.org/show_bug.cgi?id=155390 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Right, although the link is not clickable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155379] Libre Office 7.5.3 fails to launch
https://bugs.documentfoundation.org/show_bug.cgi?id=155379 Julien Nabet changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Julien Nabet --- Thank you for the feedback, let’s put this one to WFM then! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155379] Libre Office 7.5.3 fails to launch
https://bugs.documentfoundation.org/show_bug.cgi?id=155379 --- Comment #2 from steve.rawlinso...@outlook.com --- I finally fixed this bug by uninstalling and re-installing Libre Office. What may have happened, is that Libre Office had to re-start to finish its installation. During that time, I think that it got caught up with a Windows Update and God only knows what could have happened. I re-installed and everything seems OK. I have had problems with Windows Updates in the past with the CAMERA application with it not coming up immediately after an update. Thanks for your help. Steve Rawlinson. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155395] Calc - Change font of whole sheet does not work and has side effects
https://bugs.documentfoundation.org/show_bug.cgi?id=155395 rob...@prino.org changed: What|Removed |Added CC||rob...@prino.org --- Comment #1 from rob...@prino.org --- Created attachment 187385 --> https://bugs.documentfoundation.org/attachment.cgi?id=187385=edit ODS file exhibiting the problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155395] New: Calc - Change font of whole sheet does not work and has side effects
https://bugs.documentfoundation.org/show_bug.cgi?id=155395 Bug ID: 155395 Summary: Calc - Change font of whole sheet does not work and has side effects Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@prino.org Description: When changing the font of one of the sheets of the attached "lift & v100+.ods", in casu the "Waiting info" one, the first six characters in cell J7 will not be changed, but remain Segoe UI. Also, once the font is changed to "Source Code Pro Light", licking a single cell and bolding it will bold every cell of the sheet. Steps to Reproduce: 1. Open the attached "lift & v100+.ods" 2. Select the "Waiting info" sheet 3. Select the entire sheet, Ctrl-A 4. Select the new font, "Source Code Pro Light" (or for that matter, "Courier New" or "Arial", the result is the same) 5. Put the pointer on cell J7 and see that the first six characters are still "Segoe UI" 6. Select any single cell in this sheet, and click on "B(old)" (or "I(talic)" or U(nderline)" and every cell will change Additional: On two occasions, also changing other sheets to use "Source Code Pro Light", Bolding, Italicizing, and Underlining completely stopped working, but I cannot reproduce this behaviour again. Actual Results: The font in cell J7 is only partially changed Expected Results: Cell J7 should change in its entirety, bolding a single selected cell should not affect the whole sheet Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: CL threaded Starting in Safe Mode does not correct the problem! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113829] FILEOPEN: DOC: Incorrect position of table - on top instead of 5 cm vertical relative to page
https://bugs.documentfoundation.org/show_bug.cgi?id=113829 Justin L changed: What|Removed |Added CC||vmik...@collabora.com --- Comment #7 from Justin L --- fixed in LO 7.6 by commit 61be351ac83acec75788d2f79a9038486163160f Author: Miklos Vajna on Thu Apr 20 08:13:12 2023 +0200 sw floattable: import floating tables from DOC as split flys by default -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155393] Crash in SfxShell::GetViewShell()
https://bugs.documentfoundation.org/show_bug.cgi?id=155393 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 Keywords||haveBacktrace Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155393] Crash in SfxShell::GetViewShell()
https://bugs.documentfoundation.org/show_bug.cgi?id=155393 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- Created attachment 187384 --> https://bugs.documentfoundation.org/attachment.cgi?id=187384=edit bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153828] Lagging with GTK
https://bugs.documentfoundation.org/show_bug.cgi?id=153828 --- Comment #4 from jake.m.knep...@gmail.com --- (In reply to Telesto from comment #3) > I guess bug 153007 being related to this. Source of the problem is likely > the 4K monitor I guess a temporary solution would be not to use LibreOffice at high resolutions like 4k on Linux. I wonder if this problem effects Windows, too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154602] Scrolling using keyboard very slow (GTK3) with 4K monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=154602 --- Comment #10 from jake.m.knep...@gmail.com --- Played with LibreOffice (writer) at 4k on Xorg and i3wm. Same thing seems to happen. CPU usages spikes to 50% plus on a single thread/core for some reason. Scrolling other applications like Firefox at 4k for example doesn't seem to push any particular CPU thread drastic usage levels. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152657] Slower graphical performance and laggy behavior on data entry with large window (GTK)
https://bugs.documentfoundation.org/show_bug.cgi?id=152657 --- Comment #24 from jake.m.knep...@gmail.com --- Would like to add I notice a single thread/core will jump to 50% or so usage when scrolling on Fedora 38 at 4k. When running Debian with i3wm, the same thing happens. It seems to happen regardless of Xorg or Wayland. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134204] SW UI: inheriting styles not updated (until reload) when fontsize+some other attribute are changed in paragraph style dialog (autostyle related?).
https://bugs.documentfoundation.org/show_bug.cgi?id=134204 Justin L changed: What|Removed |Added Summary|Area colour not properly|SW UI: inheriting styles |removed (not properly |not updated (until reload) |repainted) after changing |when fontsize+some other |style settings |attribute are changed in ||paragraph style dialog ||(autostyle related?). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134204] Area colour not properly removed (not properly repainted) after changing style settings
https://bugs.documentfoundation.org/show_bug.cgi?id=134204 --- Comment #8 from Justin L --- repro 7.6+ (In reply to Justin L from comment #6) > 134204_red.odt: example document that doesn't use highlight. Steps to reproduce: 1.) open comment 6's attachment 170679 2.) Go to the default paragraph style dialog, Font Effects tab and change the red font color to something else. Then go to the font tab and change the font size. (the order doesn't matter - can change the font size first) --> result is that Heading 1 style text and the footnote text don't change. Doing them one at a time (instead of as a combination) has no problem. Using italic or bold along with font color has no problem. It seems to be specific to the font size in combination with one or more other attributes. I was easily able to reproduce this in a new document with just two paragraphs. One was with a Title paragraph style, and the other was default paragraph style. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Aron Budea changed: What|Removed |Added URL|https://www.prism-me.com/ar | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155292] FILESAVE: Undoing all changes made in a comment leaves the document marked as needing saving
https://bugs.documentfoundation.org/show_bug.cgi?id=155292 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com Blocks||116625 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=116625 [Bug 116625] [META] Bugs where document modification status is wrong -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116625] [META] Bugs where document modification status is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=116625 Aron Budea changed: What|Removed |Added Depends on||155292 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155292 [Bug 155292] FILESAVE: Undoing all changes made in a comment leaves the document marked as needing saving -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80717] FILEOPEN: DOC DOCX file has incorrect vertical position relative to 'page' of floating table
https://bugs.documentfoundation.org/show_bug.cgi?id=80717 --- Comment #28 from Justin L --- Probably each of the duplicates here will need to be re-assessed one by one. comment 11's GE Bilokin Nadia-fixed.doc had the first table hidden by 7.6's commit 61be351ac83acec75788d2f79a9038486163160f Author: Miklos Vajna on Thu Apr 20 08:13:12 2023 +0200 sw floattable: import floating tables from DOC as split flys by default And hidden paragraph's are likely related to the spacing difference between the tables as well. If I turn on Tools - Options - Writer - Formatting Aids - Hidden Characters, and remove the hidden paragraph, then it looks right. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155394] Inserting an animated gif crash LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155394 Alhay94 changed: What|Removed |Added CC||agrang...@yahoo.fr --- Comment #1 from Alhay94 --- Created attachment 187383 --> https://bugs.documentfoundation.org/attachment.cgi?id=187383=edit The attachment inserted in Writer, crashes Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155394] New: Inserting an animated gif crash LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155394 Bug ID: 155394 Summary: Inserting an animated gif crash LibreOffice Writer Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: agrang...@yahoo.fr Description: I open a new Documentwriter, I click on "Insert Menu" then "Picture" and choose the animated gif : "gif-esempio.gif" found on Internet. After Insertion, I click into Writer but outside of the "gif" and LibreOffice crashes. Steps to Reproduce: 1.open Writer 2.insert picture "gif-esempio.gif" 3.click after the "gif" in wwiter Actual Results: Crash of LibreOffice Writer Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: crash I Will attach the "gif" to the report -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103314] [META] Templates bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103314 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||155390 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155390 [Bug 155390] "Growing Liberty" Impress template has a slide of unclear (suspicious for advertizing) nature in the end -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155390] "Growing Liberty" Impress template has a slide of unclear (suspicious for advertizing) nature in the end
https://bugs.documentfoundation.org/show_bug.cgi?id=155390 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Blocks||103314 Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103314 [Bug 103314] [META] Templates bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Component|LibreOffice |UI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150915] [META] Windows Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=150915 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||155392 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155392 [Bug 155392] Not readable menu items in Windows 11 dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||150915 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150915 [Bug 150915] [META] Windows Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||155393 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155393 [Bug 155393] Crash in SfxShell::GetViewShell() -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155393] Crash in SfxShell::GetViewShell()
https://bugs.documentfoundation.org/show_bug.cgi?id=155393 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||133092 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155373] Feature request impress: editing slides and notes at the same time
https://bugs.documentfoundation.org/show_bug.cgi?id=155373 --- Comment #1 from Shu Zhang <122092...@qq.com> --- How about we add one more function so that the user can input the text in that field, and it will appear on both sides and notes after the user can have the ability to export the text into writer or text? I’m trying to get the idea of this function into a mockup. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154198] [Writer] The second and the before-final vertical lines are hidden in RTL documents.
https://bugs.documentfoundation.org/show_bug.cgi?id=154198 --- Comment #6 from Mahmoud Alnaanah --- I missed step in previous comment. You need step 3 in this new comment. To produce the bug. 1- Open new writer document. 2- From: Tools>options>Language Settings> Languages>Enable complex text layout and set to Arabic Jordan. 3- From: Format>Page style> Change text direction to right-to-left. 4- Create 5x5 table. 5- Save the file as docx format. 6- Close the file. 7- Reopen the file. 8- Notice that the second and the before final vertical lines are hidden. Regards, -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154198] [Writer] The second and the before-final vertical lines are hidden in RTL documents.
https://bugs.documentfoundation.org/show_bug.cgi?id=154198 Mahmoud Alnaanah changed: What|Removed |Added Resolution|WORKSFORME |WONTFIX Status|RESOLVED|VERIFIED --- Comment #5 from Mahmoud Alnaanah --- Status update: Sorry for reporting that the bug is resolved, in fact it is not. The bug exists since version 7.2 in files saved as docx format. To produce the bug. 1- Open new writer document. 2- From: Tools>options>Language Settings> Languages>Enable complex text layout and set to Arabic Jordan. 3- Create 5x5 table. 4- Save the file as docx format. 5- Close the file. 6- Reopen the file. 7- Notice that the second and the before final vertical lines are hidden. Regards, -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=143344 Bug 143344 depends on bug 144587, which changed state. Bug 144587 Summary: Tree item is inconsistent with dark theme https://bugs.documentfoundation.org/show_bug.cgi?id=144587 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 144587, which changed state. Bug 144587 Summary: Tree item is inconsistent with dark theme https://bugs.documentfoundation.org/show_bug.cgi?id=144587 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137075] Accessibility Statusline is not announced
https://bugs.documentfoundation.org/show_bug.cgi?id=137075
--- Comment #9 from Michael Weghorn ---
(In reply to Ken Scott from comment #7)
> I did find and install LibreOffice 7.5.2. This installer did place a
> LibreOffice7.5 shortcut on the desktop using the standard option in the
> installer. No desktop shortcut for LibreOffice seems to be created when
> using the LibreOffice7.5.3 installer. There also seems to be no choice
> about a standard or custom install option when using a screen reader with
> LibreOffice7.5.3 installer.
If I understand correctly, this is about the second aspect described in
tdf#155236 ("First, The installer in version 7.5.3.2 did not exposed the check
box to add a desktop icon/shortcut.") and unrelated to the issue described in
this bug report here.
Please create a separate bug report for that, which allows to keep focus (and
avoids things getting "lost").
> I was able to open LibreOffice7.5.2’s Writer application. When, the NVDA
> insert + end key combination is pressed the result is no status Bar
> information. The anticipated result is the announcement of the status bar
> information like page number and word count and so on in a word processor
> application such as LibreOffice Writer.
This is the issue actually handled here.
This described anticipated result is what I get with the mentioned suggested
NVDA change in place:
https://github.com/nvaccess/nvda/pull/14933
So if that change is accepted and integrated into NVDA, it will work with a
future version of NVDA, without requiring any changes on LibreOffice side.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149258] FILESAVE DOCX Dots appear IN MS WORD for custom numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=149258 Justin L changed: What|Removed |Added Summary|FILESAVE DOCX Dots appear |FILESAVE DOCX Dots appear |in Word for custom |IN MS WORD for custom |numbering |numbering --- Comment #5 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155393] Crash in SfxShell::GetViewShell()
https://bugs.documentfoundation.org/show_bug.cgi?id=155393 Xisco Faulí changed: What|Removed |Added CC||caolan.mcnamara@collabora.c ||om --- Comment #1 from Xisco Faulí --- @Caolán, I thought you might be interested in this issue -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155393] Crash in SfxShell::GetViewShell()
https://bugs.documentfoundation.org/show_bug.cgi?id=155393 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org Crash report or||["SfxShell::GetViewShell()" crash signature||] -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155393] New: Crash in SfxShell::GetViewShell()
https://bugs.documentfoundation.org/show_bug.cgi?id=155393 Bug ID: 155393 Summary: Crash in SfxShell::GetViewShell() Product: LibreOffice Version: 7.6.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xiscofa...@libreoffice.org Created attachment 187382 --> https://bugs.documentfoundation.org/attachment.cgi?id=187382=edit screencast Steps to reproduce: 1. Open Impress 2. Open the navigator -> Slide 1 is selected 3. View - Notes 4. Once Slide 1 gets deselected in the navigator click many times on Shape 1 -> Crash. See screencast Reproduced in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 343f1910d40f6d89658cf6e30b9b8f4af51deb43 CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: x11 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119423] CTRL+D leads to invalid merged cells that are not selectable and are not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=119423 --- Comment #9 from Aron Budea --- (In reply to BogdanB from comment #8) > What Ctrl+D is doing? I assume what is described in the first sentence of the description. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108770] [META] DOCX (OOXML) bullet and numbering list-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108770 Bug 108770 depends on bug 135716, which changed state. Bug 135716 Summary: FILESAVE DOCX Numbering highlight is not saved to DOCX https://bugs.documentfoundation.org/show_bug.cgi?id=135716 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135716] FILESAVE DOCX Numbering highlight is not saved to DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=135716 Justin L changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #9 from Justin L --- (In reply to NISZ LibreOffice Team from comment #0) > Steps to Reproduce: > 4. The numbering loses its yellow highlight, but does not get the new. > Numbering has no highlight color in Word. > Reopening the file in Writer sets the new highlight color on the numbering. As stated in comment 6, Not since 7.2 commit 873df086db969cadc66087a5abdb1ff33f2c99f1 > Expected Results: > Numbering should have the highlight color that is set on the UI. Above indicated that the UI doesn't set any highlight color. And that is precisely what we see in the round-trip in both Word and Writer. So, fixed, not NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 --- Comment #1 from haxel...@pm.me --- Created attachment 187381 --> https://bugs.documentfoundation.org/attachment.cgi?id=187381=edit Bug visuals -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155392] New: Not readable menu items in Windows 11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155392 Bug ID: 155392 Summary: Not readable menu items in Windows 11 dark mode Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: haxel...@pm.me Description: Toggleable menu items in any view is barely readable in dark mode on Windows 11 22H2. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 24; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded ^ It says I run windows 10, but it's wrong. Steps to Reproduce: 1. Install latest LibreOffice in Windows 11 in dark mode. 2. Run LibreOffice Writer or any other. 3. Observe the bug when you select toggleable menu item. Actual Results: Hard-readable menu items. White text on white background. Expected Results: Readable menu items. Reproducible: Always User Profile Reset: No Additional Info: No other info. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120201] [META] Update or add link to help page
https://bugs.documentfoundation.org/show_bug.cgi?id=120201 Bug 120201 depends on bug 155309, which changed state. Bug 155309 Summary: Help not found: Base forms - dialog Record Search. https://bugs.documentfoundation.org/show_bug.cgi?id=155309 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155391] Two consecutive days, two completely identical catastrophic crashes. Good average eh ?
https://bugs.documentfoundation.org/show_bug.cgi?id=155391 Julien Nabet changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Julien Nabet --- If you just wanted to complain and nothing else, no need to waste time here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137075] Accessibility Statusline is not announced
https://bugs.documentfoundation.org/show_bug.cgi?id=137075 --- Comment #8 from V Stuart Foote --- (In reply to Ken Scott from comment #6) > Since I did not get a clarifying message, I will restate my observations... https://github.com/nvaccess/nvda/pull/14933 (In reply to Ken Scott from comment #7) > I did find and install LibreOffice 7.5.2. This installer ... This is resolved *NOT* a LibreOffice issue to be resolved with patch and update of NVDA. See: https://github.com/nvaccess/nvda/issues/11698 with patch of NVDA in as pull request: https://github.com/nvaccess/nvda/pull/14933 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137075] Accessibility Statusline is not announced
https://bugs.documentfoundation.org/show_bug.cgi?id=137075 --- Comment #7 from Ken Scott --- I did find and install LibreOffice 7.5.2. This installer did place a LibreOffice7.5 shortcut on the desktop using the standard option in the installer. No desktop shortcut for LibreOffice seems to be created when using the LibreOffice7.5.3 installer. There also seems to be no choice about a standard or custom install option when using a screen reader with LibreOffice7.5.3 installer. I was able to open LibreOffice7.5.2’s Writer application. When, the NVDA insert + end key combination is pressed the result is no status Bar information. The anticipated result is the announcement of the status bar information like page number and word count and so on in a word processor application such as LibreOffice Writer. As a double check, I use the Windows F6 keyboard function to rotate through the various sections of the LibreOffice7.5.2 Writer screen. The following was announced: File submenu “f” – based on prior experience I know that is a menu bar. Standard toolbar Formatting toolbar property option pane – close sidebar… Untitled 1 LibreOffice writer… Normally the content of status bar if any would be announced when using the F6 keyboard screen review function. This did not happen. In fact, the F6 key stroke went from the last listed item to the first item without any kind of an announcement related to the status bar. Based on my experience with screen readers, I am guessing that there is a problem with the accessibility API used by LibreOffice in the case of the status bar. I also tested with Microsoft’s Narrator which is a much less capable screen reader. The design and philosophy of Narrator and NVDA are quite different. I also use Narrator a lot less so am less comfortable with testing results. The Narrator results to me also suggest an accessibility API problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85964] Bullet size changes when saving LO created document as doc/docx
https://bugs.documentfoundation.org/show_bug.cgi?id=85964 --- Comment #15 from Justin L --- (In reply to Telesto from comment #14) > When moving the cursor to the bullet symbol, in ODT the font name is > "OpenSymbol;Arial Unicode MS" while in DOCX it is "Liberation Serif". And this is likely the heart of the discussion. repro OpenSymbol in 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150408] "Legal numbering style" is not applied to list levels with tag
https://bugs.documentfoundation.org/show_bug.cgi?id=150408 --- Comment #5 from Justin L --- Please note that my "discussion examples" are not based on isLgl-2.docx. Both are separate (although they do highlight the same principles). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150408] "Legal numbering style" is not applied to list levels with tag
https://bugs.documentfoundation.org/show_bug.cgi?id=150408 Justin L changed: What|Removed |Added Priority|medium |low Severity|normal |enhancement Version|6.0.7.3 release |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155235] Draw crashes on close: SIGSEGV in SalInstance:GetYieldMutex()
https://bugs.documentfoundation.org/show_bug.cgi?id=155235 --- Comment #7 from Dave Gilbert --- I'm still seeing a crash on exit here, but it's moved to a different accessibility object, perhaps they need hitting with the same hammer: #0 SalInstance::GetYieldMutex() (this=0x0) at /usr/include/c++/13/bits/unique_ptr.h:199 #1 0x7f97f78ae176 in Application::GetSolarMutex() () at /discs/fast/core/vcl/source/app/svapp.cxx:481 #2 0x7f97e40e8b3e in SolarMutexGuard::SolarMutexGuard() (this=) at /discs/fast/core/include/vcl/svapp.hxx:1365 #3 atk_object_wrapper_finalize(GObject*) (obj=0x3d947c0) at /discs/fast/core/vcl/unx/gtk3/a11y/atkwrapper.cxx:662 #4 0x7f97f407ca53 in g_object_unref (_object=0x3d947c0) at ../gobject/gobject.c:3938 #5 g_object_unref (_object=0x3d947c0) at ../gobject/gobject.c:3802 #6 0x7f97e40d97cb in AtkListener::~AtkListener() (this=0x3d8d180, __in_chrg=) at /discs/fast/core/vcl/unx/gtk3/a11y/atklistener.cxx:57 #7 0x7f97e40d9839 in AtkListener::~AtkListener() (this=0x3d8d180, __in_chrg=) at /discs/fast/core/vcl/unx/gtk3/a11y/atklistener.cxx:58 #8 0x7f97fb0cb40e in com::sun::star::uno::Reference::~Reference() (this=0x3e5bf48, __in_chrg=) at /discs/fast/core/include/com/sun/star/uno/Reference.hxx:114 #9 std::_Destroy >(com::sun::star::uno::Reference*) (__pointer=0x3e5bf48) at /usr/include/c++/13/bits/stl_construct.h:151 #10 std::_Destroy_aux::__destroy*>(com::sun::star::uno::Reference*, com::sun::star::uno::Reference*) (__last=0x3e5bf50, __first=0x3e5bf48) at /usr/include/c++/13/bits/stl_construct.h:163 #11 std::_Destroy*>(com::sun::star::uno::Reference*, com::sun::star::uno::Reference*) (__last=0x3e5bf50, __first=) at /usr/include/c++/13/bits/stl_construct.h:196 #12 std::_Destroy*, com::sun::star::uno::Reference >(com::sun::star::uno::Reference*, com::sun::star::uno::Reference*, std::allocator >&) (__last=0x3e5bf50, __first=) at /usr/include/c++/13/bits/alloc_traits.h:947 #13 std::vector, std::allocator > >::~vector() (this=0x4e35f60, __in_chrg=) at /usr/include/c++/13/bits/stl_vector.h:732 #14 o3tl::cow_wrapper, std::allocator > >, o3tl::ThreadSafeRefCountingPolicy>::impl_t::~impl_t() (this=0x4e35f60, __in_chrg=) at /discs/fast/core/include/o3tl/cow_wrapper.hxx:176 #15 o3tl::cow_wrapper, std::allocator > >, o3tl::ThreadSafeRefCountingPolicy>::release() (this=0x27802d0) at /discs/fast/core/include/o3tl/cow_wrapper.hxx:207 #16 o3tl::cow_wrapper, std::allocator > >, o3tl::ThreadSafeRefCountingPolicy>::release() (this=0x27802d0) at /discs/fast/core/include/o3tl/cow_wrapper.hxx:203 --Type for more, q to quit, c to continue without paging-- #17 o3tl::cow_wrapper, std::allocator > >, o3tl::ThreadSafeRefCountingPolicy>::~cow_wrapper() (this=0x27802d0, __in_chrg=) at /discs/fast/core/include/o3tl/cow_wrapper.hxx:271 #18 comphelper::OInterfaceContainerHelper4::~OInterfaceContainerHelper4() (this=0x27802d0, __in_chrg=) at /discs/fast/core/include/comphelper/interfacecontainer4.hxx:126 #19 std::pair >::~pair() (this=0x27802c8, __in_chrg=) at /usr/include/c++/13/bits/stl_pair.h:187 #20 std::__new_allocator >, false> >::destroy > >(std::pair >*) (__p=0x27802c8, this=0x7f97fb203520 <(anonymous namespace)::gaClients>) at /usr/include/c++/13/bits/new_allocator.h:194 #21 std::allocator_traits >, false> > >::destroy > >(std::allocator >, false> >&, std::pair >*) (__p=0x27802c8, __a=...) at /usr/include/c++/13/bits/alloc_traits.h:557 #22 std::__detail::_Hashtable_alloc >, false> > >::_M_deallocate_node(std::__detail::_Hash_node >, false>*) (this=0x7f97fb203520 <(anonymous namespace)::gaClients>, __n=0x27802c0) at /usr/include/c++/13/bits/hashtable_policy.h:2020 #23 std::__detail::_Hashtable_alloc >, false> > >::_M_deallocate_nodes(std::__detail::_Hash_node >, false>*) (__n=0x31eaac0, this=0x7f97fb203520 <(anonymous namespace)::gaClients>) at /usr/include/c++/13/bits/hashtable_policy.h:2042 #24 std::_Hashtable >, std::allocator > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::clear() (this=0x7f97fb203520 <(anonymous namespace)::gaClients>) at /usr/include/c++/13/bits/hashtable.h:2509 #25 std::_Hashtable >, std::allocator > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::~_Hashtable() (this=0x7f97fb203520 <(anonymous namespace)::gaClients>, __in_chrg=) at /usr/include/c++/13/bits/hashtable.h:1593 #26 std::unordered_map, std::hash, std::equal_to, std::allocator > > >::~unordered_map() (this=0x7f97fb203520 <(anonymous namespace)::gaClients>, __in_chrg=) at /usr/include/c++/13/bits/unordered_map.h:109 #27 0x7f97fbc89bfd in __cxa_finalize (d=0x7f97fb1f2840) at cxa_finalize.c:82 #28 0x7f97fb097c77 in __do_global_dtors_aux ()
[Libreoffice-bugs] [Bug 150408] "Legal numbering style" is not applied to list levels with tag
https://bugs.documentfoundation.org/show_bug.cgi?id=150408 --- Comment #4 from Justin L --- Created attachment 187380 --> https://bugs.documentfoundation.org/attachment.cgi?id=187380=edit isLgl-2.docx: the source demo file - highlighting feature and caveats There were two caveats mentioned in the "short documentation". A) it applies to all levels (not just previous levels) A.One becomes 1.1, not 1.One. B) it does not apply to NONE levels _.One becomes 1, not 1.1 Notice that it does not affect prior (or future) levels themselves. A) remains A) and doesn't become 1) 1.1) is the only level with isLgl, so it is the only level affected. A.One.1) does not becomes 1.1.1) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124891] [META] Basic IDE bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=124891 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||155381 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155381 [Bug 155381] Basic IDE should remember status of visible UI components -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155381] Basic IDE should remember status of visible UI components
https://bugs.documentfoundation.org/show_bug.cgi?id=155381 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||124891 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=124891 [Bug 124891] [META] Basic IDE bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150408] "Legal numbering style" is not applied to list levels with tag
https://bugs.documentfoundation.org/show_bug.cgi?id=150408 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #3 from Justin L --- Created attachment 187379 --> https://bugs.documentfoundation.org/attachment.cgi?id=187379=edit isLgl-2.pdf: demonstrating the purpose of isLgl That was an excellent bug report. THANK-YOU. However, the example document wasn't the best, because it did not display the intention of IsLegal, nor the caveat conditions. This is something that MUST be handled at display time - and it is a capability that LO currently does not have. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155391] New: Two consecutive days, two completely identical catastrophic crashes. Good average eh ?
https://bugs.documentfoundation.org/show_bug.cgi?id=155391 Bug ID: 155391 Summary: Two consecutive days, two completely identical catastrophic crashes. Good average eh ? Product: LibreOffice Version: 7.4.2.3 release Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: peter.find...@gmail.com Editing a CALC file, it's a file I edit most days. Yesterday (17-May) while updating the file I had got through about two thirds of my work when your software crashed my Mac! It crashed so totally that a FORCE QUIT showed that NOTHING was responding, not even FINDER ! I've never seen a Mac crashed so totally ! Today, exactly the same thing happened, a total crash. Despite you trying to pull the wool over my eyes by saying that the file was recovered on both days - IT WASN'T ! On both occasions I was back to the file in the state it was in before I started to edit it ! What a complete waste of time ! I used to use OpenOffice, but that was so SLOW, it was rather like watching paint dry, watching that spinning beach ball for hours on end, but at least it didn't crash ! Eventually I got so fed up of watching the spinning beach ball that I thought I'd try LibreOffice. BAD MOVE ! Two days of using it and two total crashes ! Failure rate of 100%. I will probably just have to bite the bullet, kick your rubbish software into the long grass and get my hands on MS Office, maybe (hopefully) that will function without making a complete bollocks of my system ! No need to reply ! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155088] FRAME: Hyperlinks have line break inserted before them
https://bugs.documentfoundation.org/show_bug.cgi?id=155088 --- Comment #6 from dolez...@cvut.cz --- No, you're misunderstanding. The way it *currently* works is that it breaks the line when there is a hyphen in the link, not (as far as I am aware) in any other case. For example https://example.com/items/item-one/picture-three.png might get broken as: words words words https://example.com/items/item-one/picture- three.png words I don't see any real issue with breaking on hyphen, however in many cases the link would better fit broken up like this: words words words https://example.com/ items/item-one/picture-three.png words This, however doesn't happen naturally, and *that* is my issue. Even worse, it is not uncommon to see something as hideous as this: words words words https://example.com/items/itemone/ picturethree.png words -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155088] FRAME: Hyperlinks have line break inserted before them
https://bugs.documentfoundation.org/show_bug.cgi?id=155088 --- Comment #5 from Dieter --- (In reply to dolezvo1 from comment #3) > If I am not mistaken, according to this > (https://www.unicode.org/reports/tr14/), solidus should be break opportunity > in URLs. However it seems to me the only break opportunity that is currently > ever used in URLs is the hyphen (possibly because breaking algorithm might > not be differentiating URLs from text). Hyphen is definitley not a coud idea, because it could be misinterpreted as part of the hyperlink. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149827] It's possible to add text in write-protected sections immediately before (but outside) of input fields
https://bugs.documentfoundation.org/show_bug.cgi?id=149827 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4808 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154808] Writer - protected section - allow to insert content into fields
https://bugs.documentfoundation.org/show_bug.cgi?id=154808 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9827 --- Comment #5 from Dieter --- (In reply to kabilo from comment #4) > Hi Dieter, user fields are e.g. address data in contracts that you want to > repeat multiple times. Text box is not a suitable solution for this. Thanks Could you please attach a short sample document with a protected section and user field? Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155390] New: "Growing Liberty" Impress template has a slide of unclear (suspicious for advertizing) nature in the end
https://bugs.documentfoundation.org/show_bug.cgi?id=155390 Bug ID: 155390 Summary: "Growing Liberty" Impress template has a slide of unclear (suspicious for advertizing) nature in the end Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com The "Growing Liberty" Impress template has a normal "Thank you!" slide #12, with a "Growing Liberty by Budi Aryo @tokofoss" acknowledgement at the bottom. But after that, there is a "Fully Editable Icon Sets / by Garik Barseghyan from Pixabay" slide #13, with an URL at the bottom; overall, this last slide looks inappropriate here, either forgotten during preparation, or some kind of "advertising"/"promotion" of an unrelated product. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Dieter changed: What|Removed |Added Depends on||155158 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155158 [Bug 155158] Cursor dissapears when switching from chinese layout (windows 10) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155158] Cursor dissapears when switching from chinese layout (windows 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=155158 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Blocks||83066 CC||dgp-m...@gmx.de Ever confirmed|0 |1 --- Comment #1 from Dieter --- Thank you for reporting the bug. Does it also happen in SafeMode (Help -> Restart in SafeMode)? => NEEDINFO Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83066 [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues -- You are receiving this mail because: You are the assignee for the bug.
