[Libreoffice-bugs] [Bug 151488] page line-spacing: lines don't seem to be in level
https://bugs.documentfoundation.org/show_bug.cgi?id=151488 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 155280] Allow adjusting height of text box when setting columns
https://bugs.documentfoundation.org/show_bug.cgi?id=155280 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 155277] Feature request: Tab key alternative behavior - de-select and jump to next cell instead of jumping around inside selection
https://bugs.documentfoundation.org/show_bug.cgi?id=155277 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 152255] Crash in: ImpEditView::dragDropEnd(com::sun::star::datatransfer::dnd::DragSourceDropEvent const &)
https://bugs.documentfoundation.org/show_bug.cgi?id=152255 --- Comment #2 from QA Administrators --- Dear Colin Zimmermann, 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 151487] page line-spacing: active page line-spacing cannot be set "OFF" in template
https://bugs.documentfoundation.org/show_bug.cgi?id=151487 --- Comment #3 from QA Administrators --- Dear peter josvai, 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 151487] page line-spacing: active page line-spacing cannot be set "OFF" in template
https://bugs.documentfoundation.org/show_bug.cgi?id=151487 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 151488] page line-spacing: lines don't seem to be in level
https://bugs.documentfoundation.org/show_bug.cgi?id=151488 --- Comment #6 from QA Administrators --- Dear peter josvai, 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 152130] user defined calc chart names not reflected in e.g. BASIC macros
https://bugs.documentfoundation.org/show_bug.cgi?id=152130 --- Comment #2 from QA Administrators --- Dear trowelandmattock, 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 138806] Drag and drop in Impress stop working after a few minutes
https://bugs.documentfoundation.org/show_bug.cgi?id=138806 --- Comment #4 from QA Administrators --- Dear bjo, 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 50893] Error moving cursor through sign "-" at end of string
https://bugs.documentfoundation.org/show_bug.cgi?id=50893 --- Comment #9 from QA Administrators --- Dear sotnikov123, 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 146249] Spell Checker not remebering new words
https://bugs.documentfoundation.org/show_bug.cgi?id=146249 --- Comment #2 from QA Administrators --- Dear Tim, 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 61649] PRINTING: Printing Selected Frame doesn't print frame contents
https://bugs.documentfoundation.org/show_bug.cgi?id=61649 --- Comment #10 from QA Administrators --- Dear Matt Needles, 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 124950] On-screen keyboard pops up much too eagerly
https://bugs.documentfoundation.org/show_bug.cgi?id=124950 --- Comment #8 from QA Administrators --- Dear Tor Lillqvist, 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 138580] Anchor to character constantly jumping to left column when moving an image (if they table is the first thing on the page)
https://bugs.documentfoundation.org/show_bug.cgi?id=138580 --- 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 124870] Up key does not move to line ended by hyphen
https://bugs.documentfoundation.org/show_bug.cgi?id=124870 --- Comment #9 from QA Administrators --- Dear Dávid Horváth, 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 105777] Pasting image in Calc: wrong placement when there's previous image overlapping currently selected cell
https://bugs.documentfoundation.org/show_bug.cgi?id=105777 --- Comment #7 from QA Administrators --- Dear andy-scull, 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 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 --- Comment #21 from Jim Raykowski --- (In reply to sdc.blanco from comment #20) > 1. There are probably good use cases for both variations (because it depends > on the content of document, including its conceptual relations, which can > change during the text production phase, which is why one wants to move > sections) ==> will be hard to justify one version over another, if there is > only going to be one form of behavior. > 2. As a user, it is useful to know what to expect (no matter which > functionality is chosen) -- which also implies clear documentation. > 3. If only one functionality is chosen, then make it the simplest one (e.g., > move heading and text to above/below the next heading, no matter what > outline level). > Reason: easy to predict what will happen. > 4. If only one section is moved, then just click multiple times to get > desired result. (not so hard) > 5. (With outline folding, I believe it is possible to move larger chunks of > text). > 6. Most important is symmetry (i.e., up and down have the same effect. In > this way, if you move something up (or down) (and do not like the result), > then you can use down (or up) to undo. > Effort to restore chapter move behavior to what it was before the patch committed to fix bug 154212 and keep comment 19 behavior from master: https://gerrit.libreoffice.org/c/core/+/152347 > More ambitious comments > 7. In the modern interface, what about drag and drop in the Navigator? That > is, instead of move up/down, you can select one or more headings, and then > drag them to where you want in the outline structure. That would be ideal > (and would make move up and down irrelevant, i.e, could be removed). Chapters can be moved by drag and drop when the Navigator is in Headings Content Navigation View. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152534] Win11 dark theme support--Active selections on Notebook Bar and Sidebar UI have light blue background which makes the white icon almost invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=152534 --- Comment #16 from Michael FA --- I confirm, the error is still in version 7.5.3 and 7.6.0.0.alpha1 of libreoffice in Windows 11, I don't know if the same error is present in other operating systems. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36711] FILOPEN .DOC Wrap around frame positions wrong, horizontal relative to Page, vertical relative to Paragraph (MSO opens wrong self saved DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=36711 --- Comment #21 from Justin L --- Created attachment 187552 --> https://bugs.documentfoundation.org/attachment.cgi?id=187552=edit 133504_dump.doc:doc_dumper sprm details of the internal guts There must be some kind of default value that is wrong here. When I created a DOCX of this file, I get Margin3 (based on Heading3): Heading 3 (based on Heading2): Heading 2: In DOCX, these would all inherit the defined w:vAnchor from Heading 2, but in DOC it looks different. Margin3: specifies nothing - inherits everything from Heading 3 Heading 3: specifies 1000 = H:Entire Page, V:Page Margin So, I'm not sure why MS Word would treat that as paragraph, unless it is because sprmPDyaAbs == 0 as a corner case? Ah, yes, that is likely because 0 has a special meaning of inline. "Inline (in line with text): Specifies that the parent object shall be vertically aligned in line with the surrounding text (i.e. shall not allow any text wrapping around it when positioned in the document." -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129369] Function suggestion while editing end of text content in cell
https://bugs.documentfoundation.org/show_bug.cgi?id=129369 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||1638 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116261] CALC FORMATTING editing in-cell attributed content (rich text) in the Input Line removes attribution from cell content
https://bugs.documentfoundation.org/show_bug.cgi?id=116261 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||1638 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132026] Entering "-" in a cell formatted as text puts Calc into formula-entering mode
https://bugs.documentfoundation.org/show_bug.cgi?id=132026 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||1638 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152534] Win11 dark theme support--Active selections on Notebook Bar and Sidebar UI have light blue background which makes the white icon almost invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=152534 V Stuart Foote changed: What|Removed |Added Summary|Windows 11 dark theme |Win11 dark theme |support--Active selections |support--Active selections |on Notebook Bar and Sidebar |on Notebook Bar and Sidebar |UI have light blue |UI have light blue |background which makes the |background which makes the |white icon almost invisible |white icon almost invisible -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85811] [META] Main menu bar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85811 Bug 85811 depends on bug 147482, which changed state. Bug 147482 Summary: Suboptimal Menubar's Highlighted Text Color with Windows 11 https://bugs.documentfoundation.org/show_bug.cgi?id=147482 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147482] Suboptimal Menubar's Highlighted Text Color with Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=147482 Rizal Muttaqin changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #5 from Rizal Muttaqin --- (In reply to V Stuart Foote from comment #4) > Rizal, still an issue in Win11 light theme mode? I can confirm Ilmari's statement in #c3. Let me close this bug report -- 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 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5528 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155515] CRASH: clicking on sheet (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=155515 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5528 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145593] [META] Exit LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=145593 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155528 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155528 [Bug 155528] crash with SIGSEGV in SalInstance::GetYieldMutex() on exit after inserting image -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155528] New: crash with SIGSEGV in SalInstance::GetYieldMutex() on exit after inserting image
https://bugs.documentfoundation.org/show_bug.cgi?id=155528 Bug ID: 155528 Summary: crash with SIGSEGV in SalInstance::GetYieldMutex() on exit after inserting image Product: LibreOffice Version: 7.6.0.0 alpha1+ Master Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org CC: noelgran...@gmail.com Blocks: 133092, 145593 Created attachment 187551 --> https://bugs.documentfoundation.org/attachment.cgi?id=187551=edit Backtrace unpacked from Apport crash file Steps to reproduce: 1. Open Calc 2. Insert an image 3. Close Calc without saving 4. Open Calc Result: Crash reporter shows. Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 2b3b4026a5c6a1b92c0b29b94dd62a4c3c7b9fad CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs https://bugs.documentfoundation.org/show_bug.cgi?id=145593 [Bug 145593] [META] Exit LibreOffice -- 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 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155528 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155528 [Bug 155528] crash with SIGSEGV in SalInstance::GetYieldMutex() on exit after inserting image -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155452] When pasting image from Firefox in Calc, pasted image is not visible (only paste frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=155452 --- Comment #10 from Julien Nabet --- Created attachment 187550 --> https://bugs.documentfoundation.org/attachment.cgi?id=187550=edit bt Sorry, I hadn't thought the copy-paste of the bt directly in the comment would be so badly formatted. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155452] When pasting image from Firefox in Calc, pasted image is not visible (only paste frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=155452 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #9 from Julien Nabet --- On Win10 with master sources updated today, I could reproduce this. Noticing this line: warn:svtools:13036:14080:svtools/source/svhtml/parhtml.cxx:1480: GetOption: unknown HTML option 'decoding' I took a bt from here with Visual Studio: svtlo.dll!HTMLParser::GetOptions(const HtmlOptionId * pNoConvertToken) Ligne 1478 C++ scfiltlo.dll!ScHTMLLayoutParser::Image(HtmlImportInfo * pInfo) Ligne 1270 C++ scfiltlo.dll!ScHTMLLayoutParser::ProcToken(HtmlImportInfo * pInfo) Ligne 1548 C++ scfiltlo.dll!ScHTMLLayoutParser::HTMLImportHdl(HtmlImportInfo & rInfo) Ligne 864C++ scfiltlo.dll!ScHTMLLayoutParser::LinkStubHTMLImportHdl(void * instance, HtmlImportInfo & data) Ligne 858C++ editenglo.dll!Link::Call(HtmlImportInfo & data) Ligne 111C++ editenglo.dll!EditEngine::CallHtmlImportHandler(HtmlImportInfo & rInfo) Ligne 2853 C++ editenglo.dll!EditHTMLParser::NextToken(HtmlTokenId nToken) Ligne 491 C++ svtlo.dll!HTMLParser::Continue(HtmlTokenId nToken) Ligne 298C++ svtlo.dll!HTMLParser::CallParser() Ligne 282C++ editenglo.dll!EditHTMLParser::CallParser(EditEngine * pEE, const EditPaM & rPaM) Ligne 84 C++ editenglo.dll!ImpEditEngine::ReadHTML(SvStream & rInput, const rtl::OUString & rBaseURL, EditSelection aSel, SvKeyValueIterator * pHTTPHeaderAttrs) Ligne 168 C++ editenglo.dll!ImpEditEngine::Read(SvStream & rInput, const rtl::OUString & rBaseURL, EETextFormat eFormat, const EditSelection & rSel, SvKeyValueIterator * pHTTPHeaderAttrs) Ligne 97 C++ editenglo.dll!EditEngine::Read(SvStream & rInput, const rtl::OUString & rBaseURL, EETextFormat eFormat, SvKeyValueIterator * pHTTPHeaderAttrs) Ligne 1506 C++ scfiltlo.dll!ScHTMLLayoutParser::Read(SvStream & rStream, const rtl::OUString & rBaseURL) Ligne 280 C++ scfiltlo.dll!ScEEImport::Read(SvStream & rStream, const rtl::OUString & rBaseURL) Ligne 84 C++ sclo.dll!ScImportExport::HTML2Doc(SvStream & rStrm, const rtl::OUString & rBaseURL) Ligne 2634 C++ > sclo.dll!ScImportExport::ImportStream(SvStream & rStrm, const > rtl::OUString & rBaseURL, SotClipboardFormatId nFmt) Ligne 426C++ sclo.dll!ScViewFunc::PasteDataFormat(SotClipboardFormatId nFormatId, const com::sun::star::uno::Reference & rxTransferable, short nPosX, long nPosY, const Point * pLogicPos, bool bLink, bool bAllowDialogs) Ligne 382C++ sclo.dll!ScViewFunc::PasteFromSystem(SotClipboardFormatId nFormatId, bool bApi) Ligne 745 C++ sclo.dll!ScViewFunc::PasteFromSystem() Ligne 601C++ sclo.dll!ScClipUtil::PasteFromClipboard(ScViewData & rViewData, ScTabViewShell * pTabViewShell, bool bShowDialog) Ligne 87 C++ sclo.dll!ScCellShell::ExecuteEdit(SfxRequest & rReq) Ligne 1391 C++ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155525] the page area of a Draw OLE document inside a Writer page doesn't keep "none" property
https://bugs.documentfoundation.org/show_bug.cgi?id=155525 --- Comment #5 from m.a.riosv --- Sorry. More than a bug, it looks like an enhancement request, adding the option to Draw. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155525] the page area of a Draw OLE document inside a Writer page doesn't keep "none" property
https://bugs.documentfoundation.org/show_bug.cgi?id=155525 m.a.riosv changed: What|Removed |Added Status|RESOLVED|NEW Ever confirmed|0 |1 Resolution|NOTABUG |--- --- Comment #4 from m.a.riosv --- Sorry my mistake. The issue is that Draw, even alone, has no option to disable print background. Mas que un bug, parace una solicitud de mejora, añadiendo la opción en Draw. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153517] CALC - wrong time value when using the autofill function and minutes are entered (not for 00 min)
https://bugs.documentfoundation.org/show_bug.cgi?id=153517 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131638] Text cell prompting about incorect formula
https://bugs.documentfoundation.org/show_bug.cgi?id=131638 Baole Fang changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #5 from Baole Fang --- start working on this -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155525] the page area of a Draw OLE document inside a Writer page doesn't keep "none" property
https://bugs.documentfoundation.org/show_bug.cgi?id=155525 m.a.riosv changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- Menu/Tools/Options/LibreOffice Writer/Print – Contents – Page background -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155527] Nothing happen on table row's mouse selecting if it's splitted differently
https://bugs.documentfoundation.org/show_bug.cgi?id=155527 --- Comment #3 from Alexander Kurakin --- Possibly related: bug #155517. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155517] Can't select row if it's splitted differently
https://bugs.documentfoundation.org/show_bug.cgi?id=155517 --- Comment #2 from Alexander Kurakin --- Possibly related: bug #155527. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155517] Can't select row if it's splitted differently
https://bugs.documentfoundation.org/show_bug.cgi?id=155517 --- Comment #1 from Alexander Kurakin --- Created attachment 187549 --> https://bugs.documentfoundation.org/attachment.cgi?id=187549=edit Test case file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36711] FILOPEN .DOC Wrap around frame positions wrong, horizontal relative to Page, vertical relative to Paragraph (MSO opens wrong self saved DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=36711 --- Comment #20 from Justin L --- Created attachment 187548 --> https://bugs.documentfoundation.org/attachment.cgi?id=187548=edit winsig34_Min.doc: three frames - two (with styles Margin/Heading3) are wrongly positioned -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155527] Nothing happen on table row's mouse selecting if it's splitted differently
https://bugs.documentfoundation.org/show_bug.cgi?id=155527 --- Comment #2 from Alexander Kurakin --- Reproduced in: Version: 7.4.6.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: ru-RU Gentoo official package Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155527] Nothing happen on table row's mouse selecting if it's splitted differently
https://bugs.documentfoundation.org/show_bug.cgi?id=155527 --- Comment #1 from Alexander Kurakin --- Created attachment 187547 --> https://bugs.documentfoundation.org/attachment.cgi?id=187547=edit Test case file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155527] New: Nothing happen on table row's mouse selecting if it's splitted differently
https://bugs.documentfoundation.org/show_bug.cgi?id=155527 Bug ID: 155527 Summary: Nothing happen on table row's mouse selecting if it's splitted differently Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kuraga...@mail.ru CC: kuraga...@mail.ru 1. Open the Writer. 2. Create a 2-rows 3-columns table. 3. Split the 2nd column of the 2nd row into 2 rows. 4. Result: - | | | | - | | | | | - | | | | | - 5. Try to select "the 2nd row" using the mouse. Nothing happened. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155513] screen artefacts with LibreCalc 7.5.3.2 and Kubuntu 23.04 - EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=155513 --- Comment #4 from redmoon1...@protonmail.com --- Fonts used are ALL Liberation Sans -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155513] screen artefacts with LibreCalc 7.5.3.2 and Kubuntu 23.04 - EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=155513 --- Comment #3 from redmoon1...@protonmail.com --- Created attachment 187546 --> https://bugs.documentfoundation.org/attachment.cgi?id=187546=edit Closer view to font pixel shifting -- 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 Bug 133092 depends on bug 145756, which changed state. Bug 145756 Summary: Impress crashes in presentation mode with fractional scaling enabled under Gnome 41 + Wayland https://bugs.documentfoundation.org/show_bug.cgi?id=145756 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Bug 103182 depends on bug 145756, which changed state. Bug 145756 Summary: Impress crashes in presentation mode with fractional scaling enabled under Gnome 41 + Wayland https://bugs.documentfoundation.org/show_bug.cgi?id=145756 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Bug 100156 depends on bug 145756, which changed state. Bug 145756 Summary: Impress crashes in presentation mode with fractional scaling enabled under Gnome 41 + Wayland https://bugs.documentfoundation.org/show_bug.cgi?id=145756 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145756] Impress crashes in presentation mode with fractional scaling enabled under Gnome 41 + Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=145756 Caolán McNamara changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED See Also||https://gitlab.freedesktop. ||org/cairo/cairo/-/issues/43 ||7 --- Comment #9 from Caolán McNamara --- This looks the same as https://gitlab.freedesktop.org/cairo/cairo/-/issues/437 which was an issue in cairo with just the type of scenario described by the reporter here -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152336] Improve CSV field separator detection/behavior when several separators are selected on import
https://bugs.documentfoundation.org/show_bug.cgi?id=152336 BogdanB changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||buzea.bog...@libreoffice.or ||g --- Comment #5 from BogdanB --- Changed to New based on +1 from Stuart, and duplicates. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155521] Resolution metadata not stored when exporting PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=155521 Julien Nabet changed: What|Removed |Added Summary|Resolution metada not |Resolution metadata not |stored when exporting PNG |stored when exporting PNG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36711] FILOPEN .DOC Wrap around frame positions wrong, horizontal relative to Page, vertical relative to Paragraph (MSO opens wrong self saved DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=36711 Justin L changed: What|Removed |Added CC||jl...@mail.com Status|RESOLVED|NEW Resolution|FIXED |--- --- Comment #19 from Justin L --- Whoo boy - let me qualify that statement. It was fixed for DOCX (comment 17). It is not fully fixed for DOC format. It was partially fixed in 7.6 with https://gerrit.libreoffice.org/c/core/+/152331. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112698] [META] DOC (binary) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112698 Bug 112698 depends on bug 36711, which changed state. Bug 36711 Summary: FILOPEN .DOC Wrap around frame positions wrong, horizontal relative to Page, vertical relative to Paragraph (MSO opens wrong self saved DOCX) https://bugs.documentfoundation.org/show_bug.cgi?id=36711 What|Removed |Added Status|RESOLVED|NEW Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112698] [META] DOC (binary) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112698 Bug 112698 depends on bug 36711, which changed state. Bug 36711 Summary: FILOPEN .DOC Wrap around frame positions wrong, horizontal relative to Page, vertical relative to Paragraph (MSO opens wrong self saved DOCX) https://bugs.documentfoundation.org/show_bug.cgi?id=36711 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36711] FILOPEN .DOC Wrap around frame positions wrong, horizontal relative to Page, vertical relative to Paragraph (MSO opens wrong self saved DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=36711 Justin L changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #18 from Justin L --- The described problem has basically been fixed in LO 7.6 with commit 630732bfd8ed531e9d412a36a083f33763def054 Author: Justin Luth on Sat Mar 11 13:16:56 2023 -0500 tdf#112287 tdf#154129 writerfilter framePr: fix vAnchor default -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112786] [META] DOC (binary) textbox-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112786 Bug 112786 depends on bug 76092, which changed state. Bug 76092 Summary: FORMATTING: Writer shows separate textboxes with text incorrectly formatted https://bugs.documentfoundation.org/show_bug.cgi?id=76092 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76092] FORMATTING: Writer shows separate textboxes with text incorrectly formatted
https://bugs.documentfoundation.org/show_bug.cgi?id=76092 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Justin L --- fixed in 7.6 by https://gerrit.libreoffice.org/c/core/+/152331 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 --- Comment #12 from Attila Szűcs --- sorry for the typo, the 3. ticket was tdf#120715 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 --- Comment #11 from Attila Szűcs --- I think this bug report should be rethinked.. and maybe some smaller feature request could be enought for you.. But it is a complex situation and many ideas could be problem for someone else... because this whole situation is a bit controversiar ... we want to be able to hit more spaces, but we want to see as there would be no spaces there .. some cases we want to be able to move into it.. some cases we don't.. we dont want to break line because of them.. but if you put 1 letter in the middle, then suddenly show the spoaces at next line, and change its behaviour... there was 3 related ticket on bugzilla about this: tdf#43100 tdf#104683 tdf#12071 however... some could say... it is a rare case when someone want to put 10+ space at the end of the line... (even i dont know when/why someone want it, sure some will do, just like i when i tested it :) ) The original problem (what i fixed) was a more common problem, that you was not able to see how many spaces are at the end of the line... because sometimes we mistakenly type 2 spaces. For example at justified case, it does not even show 1 space .. because letters was until the margo... and nothing was displayed after margo... For some peoples, it was a critical bug, as they used 3. party tool, that was made errors if there was extra spaces on the line end... They had to open it in MS word to even check where are the errors... and we don't want to suggest peoples to use MS word just because of this.. :) So it had to be fixed... and it was not so simple to fix.. as the extra spaces was not stored like other spaces.. you can check my gerrit, and see what is SwHolePortion, and i had to make sure the layout will not change by this. Once i diplayed the hidden spaces .. when you tried to delete some.. it was very confusing that the cursor was not worked as in the middle of the line... it moved differently and showed false position .. So i made the cursor to work just like in the middle of the line. Just like MS Word do. i did not handled every special cases.. maybe we should crop cursor position at the page end.. but we could think about columns end.. and other cases like.. when there are a hole portion in the middle of the line... (if there is an image that cut a hole into some lines.. ) maybe the "writing a number in then end of the line" could be good too.. but that is again a complex feature (not so easy to implement).. how to display it, so you will not confuse it with real text?.. where to put, when text is centered? at the margin, or right next to text?.. and what about the cursor... if someone want to cut 4 space to the next line from the 10... should he be able to do it.. or should we say, no.. you will have to delete the 4 from here, and insert the 4 space there... Some peoples even suggested to not have any spaces after the margin, but at justified mode, the spaces at the end of the line, must be after the margin... as letters are paced from left to right margins... the space between the last word of the 1. line, and the first word of the 2. line... must be outside of the margins.. I think this kind of ideas should be designed deeply, and carefully. So in short: I would suggest for you to ask fix only for what annoy you now.. for example to not show cursor after the page end... or crop cursor visible position to the page end... or someting like that... i dont promise to fix that.. as i have other things to do now.. but who knows.. :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68765] Requested clipboard format not available when right click on video
https://bugs.documentfoundation.org/show_bug.cgi?id=68765 --- Comment #9 from Mike --- OK, it turned out that the bug I get is since I switched to Wayland. On Xorg, all works fine. Since text is in the clipboard, possible to paste on other applications or works in Xorg, it means, that something is wrong on the Libre Office'es side on Wayland. Since this is Wayland issue, should I create a new case, because surely the original issue is not the same. The results are the same thou. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155526] New: Moving average trend line equation on chart does not show period and R^2
https://bugs.documentfoundation.org/show_bug.cgi?id=155526 Bug ID: 155526 Summary: Moving average trend line equation on chart does not show period and R^2 Product: LibreOffice Version: 7.6.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vladislav.taraka...@bk.ru Description: If click "Insert R^2 and Trend Line Equation" after plotting the moving average for the chart, then the lines "Moving Average trend line with period = %PERIOD" and "R^2 = NaN" will be obtained, which does not look like the expected behavior Steps to Reproduce: 1. Write arbitrary numbers in any column 2. Select the numbers written and click "Insert Chart" on the toolbar 3. Choose any type of chart and build a chart 4. Select data series and in the context menu click "Insert Trend Line..." 5. Select "Moving Average" type and click "ok" 6. Select trend line and in the context menu click "Insert R^2 and Trend Line Equation" Actual Results: The strings "Moving Average trend line with period = %PERIOD" and "R^2 = NaN" are displayed Expected Results: Display strings like "Moving Average trend line with period = 2" Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: efcbd2306f0310809f2d6f1db086b839055c77f6 CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76092] FORMATTING: Writer shows separate textboxes with text incorrectly formatted
https://bugs.documentfoundation.org/show_bug.cgi?id=76092 Justin L changed: What|Removed |Added Hardware|Other |All CC||jl...@mail.com Summary|FORMATTING: Writer shows|FORMATTING: Writer shows |nested textboxes with text |separate textboxes with |incorrectly formatted |text incorrectly formatted OS|Windows (All) |All Version|4.2.1.1 release |3.4.2 release --- Comment #7 from Justin L --- repro 7.6+ It looks pretty fine if I save it as DOCX. The framePr (single textbox) was fine in OOo 3.3, but it already had that FirstParagraph-only wrap enabled. The single textbox broke in 3.4.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155523] Color Palette Drop List Empty
https://bugs.documentfoundation.org/show_bug.cgi?id=155523 Rainer Bielefeld Retired changed: What|Removed |Added CC||LibreOffice@bielefeldundbus ||s.de --- Comment #2 from Rainer Bielefeld Retired --- NOT reproducible with Server Installation of Version: 7.6.0.0.alpha0+ (X86_64) Build ID: 3bc7cc14706f47d740dfc5715970054922ca470c CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: Arabic (Saudi Arabia); Theme: Automatic (Colibre) Calc: CL threaded – Special new User Profile for testing @reporter: of course we will need information concerning your system, OS, Theme, ... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 BogdanB changed: What|Removed |Added Depends on||128412 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128412 [Bug 128412] UNDO is ignored after Lower case word is forced into Upper case by Autocorrect -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128412] UNDO is ignored after Lower case word is forced into Upper case by Autocorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=128412 BogdanB changed: What|Removed |Added Blocks||105948 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105948 [Bug 105948] [META] Undo/Redo bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61995] FORMATTING: Tables layout problems with negative indents and continuous section break
https://bugs.documentfoundation.org/show_bug.cgi?id=61995 --- Comment #14 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135891] Background of Calc tables pasted as OLE objects in Impress not rendering fill colors as expected
https://bugs.documentfoundation.org/show_bug.cgi?id=135891 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5525 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155525] the page area of a Draw OLE document inside a Writer page doesn't keep "none" property
https://bugs.documentfoundation.org/show_bug.cgi?id=155525 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||5891 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155525] the page area of a Draw OLE document inside a Writer page doesn't keep "none" property
https://bugs.documentfoundation.org/show_bug.cgi?id=155525 --- Comment #2 from Jérôme --- Created attachment 187545 --> https://bugs.documentfoundation.org/attachment.cgi?id=187545=edit PDF export -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155525] the page area of a Draw OLE document inside a Writer page doesn't keep "none" property
https://bugs.documentfoundation.org/show_bug.cgi?id=155525 --- Comment #1 from Jérôme --- Created attachment 187544 --> https://bugs.documentfoundation.org/attachment.cgi?id=187544=edit Writer document with Draw OLE object inserted -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45089] FILELOAD: Table formatting damaged loading file from .doc
https://bugs.documentfoundation.org/show_bug.cgi?id=45089 --- Comment #17 from Justin L --- repro point 33 on 7.6+ All the settings look fine. The font sizes are the same, and the row height is exactly 0.7cm. The text just doesn't fix inside the box in LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155525] New: the page area of a Draw OLE document inside a Writer page doesn't keep "none" property
https://bugs.documentfoundation.org/show_bug.cgi?id=155525 Bug ID: 155525 Summary: the page area of a Draw OLE document inside a Writer page doesn't keep "none" property Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jerome.bo...@laposte.net Here's how to reproduce the bug. 1. create an empty Writer document et check that the background of the page is area is set to "None". 2. insert an OLE object by creating a new Draw object and check that its page property has "background" set to "None". 3. export the Writer document as pdf The pdf shows that the background of the OLE object is grey. The problem is the same when printing as when exporting to pdf. Note that I changed the application colours in the LibreOffice options : I set document background to grey instead of white. I though that the application colour shouldn't change the way a document is rendered for printing or pdf. I just want to alter the colour when editing. When printing, the printer could set a different paper colour (and let the automatic font colour be chosen when printing). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120466] [META] DOCX (OOXML) anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120466 Bug 120466 depends on bug 107628, which changed state. Bug 107628 Summary: Filesave: Table position wrong on RT (filesave and fileopen) in LO, behind chart in DOC and overlapping chart in DOCX (anchor changed?) - position OK in MSO https://bugs.documentfoundation.org/show_bug.cgi?id=107628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120468] [META] DOC (binary) anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120468 Bug 120468 depends on bug 107628, which changed state. Bug 107628 Summary: Filesave: Table position wrong on RT (filesave and fileopen) in LO, behind chart in DOC and overlapping chart in DOCX (anchor changed?) - position OK in MSO https://bugs.documentfoundation.org/show_bug.cgi?id=107628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112700] [META] DOC (binary) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112700 Bug 112700 depends on bug 107628, which changed state. Bug 107628 Summary: Filesave: Table position wrong on RT (filesave and fileopen) in LO, behind chart in DOC and overlapping chart in DOCX (anchor changed?) - position OK in MSO https://bugs.documentfoundation.org/show_bug.cgi?id=107628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116112] [META] Regressions introduced by alg_writerframes
https://bugs.documentfoundation.org/show_bug.cgi?id=116112 Bug 116112 depends on bug 107628, which changed state. Bug 107628 Summary: Filesave: Table position wrong on RT (filesave and fileopen) in LO, behind chart in DOC and overlapping chart in DOCX (anchor changed?) - position OK in MSO https://bugs.documentfoundation.org/show_bug.cgi?id=107628 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107628] Filesave: Table position wrong on RT (filesave and fileopen) in LO, behind chart in DOC and overlapping chart in DOCX (anchor changed?) - position OK in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=107628 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #13 from Justin L --- *** This bug has been marked as a duplicate of bug 76022 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013)
https://bugs.documentfoundation.org/show_bug.cgi?id=76022 --- Comment #36 from Justin L --- *** Bug 107628 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 155521] Resolution metada not stored when exporting PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=155521 raal changed: What|Removed |Added Blocks||109323 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109323 [Bug 109323] [META] Graphic export bugs and enhancements (jpg, png, eps, tiff, gif ...) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109323] [META] Graphic export bugs and enhancements (jpg, png, eps, tiff, gif ...)
https://bugs.documentfoundation.org/show_bug.cgi?id=109323 raal changed: What|Removed |Added Depends on||155521 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155521 [Bug 155521] Resolution metada not stored when exporting PNG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112724] [META] Options dialog's Load/Save settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112724 Bug 112724 depends on bug 148756, which changed state. Bug 148756 Summary: Document Type in Options dialog should correspond to the application that opened the dialog https://bugs.documentfoundation.org/show_bug.cgi?id=148756 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155521] Resolution metada not stored when exporting PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=155521 raal changed: What|Removed |Added Version|7.5.3.2 release |4.2.0.4 release Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||r...@post.cz --- Comment #1 from raal --- Confirm with Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 578758835e700b38b167753ccda9527f3a8cc43b CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Version: 4.1.0.0.alpha1+ Build ID: a2c9d4f8bbde97f175bae4df771273a61251f40 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62613] Unwanted spacing in DOC, table imported on another page (9 pages in MSO, 12 pages in LO) but wrong even in MSO if saved as DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=62613 --- Comment #20 from Justin L --- repro 7.6+ I think the main problem is that the very large/tall row wants to keep together on the same page in LO. IIUC, if this is saved in compat15 DOCX, then MSO will also look like this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101717] FORMATTING: Superscript raise percent too small (automatic unchecked) when pasting from Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=101717 --- Comment #7 from Buovjaga --- Yes, it's fine Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 6.3; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154168] FILESAVE: Export selection to .PNG without transparency fails
https://bugs.documentfoundation.org/show_bug.cgi?id=154168 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #8 from raal --- *** Bug 155524 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 155524] Export to PNG, file has zero size
https://bugs.documentfoundation.org/show_bug.cgi?id=155524 raal changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from raal --- *** This bug has been marked as a duplicate of bug 154168 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81257] FILEOPEN DOC: wrong image layout with square wrap - pictures that should be right aligned, appear at top of page (OK if DOC resaved in MSO as DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=81257 Justin L changed: What|Removed |Added Hardware|Other |All --- Comment #13 from Justin L --- I think ww8par is reading the image data instead of configuration data and just getting random matches for if(maShapeRecords.SeekToContent( rSt, DFF_msofbtUDefProp, SEEK_FROM_CURRENT_AND_RESTART ) && maShapeRecords.Current()->nRecLen ) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155524] Export to PNG, file has zero size
https://bugs.documentfoundation.org/show_bug.cgi?id=155524 raal changed: What|Removed |Added Keywords||bibisected, bisected, ||regression CC||parisop...@gmail.com, ||r...@post.cz Regression By||Paris Oplopoios --- Comment #1 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-7.5. Adding Cc: to Paris Oplopoios ; Could you possibly take a look at this one? Thanks 47b810ff80dca560f10916888f8ecbf3574ee357 is the first bad commit commit 47b810ff80dca560f10916888f8ecbf3574ee357 Author: Jenkins Build User Date: Tue Jul 19 13:15:25 2022 +0200 source sha:1d548a2bc70e0b38e32ccae8b15b04bda84f3576 137132: Replace old png writer in graphicfilter.cxx | https://gerrit.libreoffice.org/c/core/+/137132 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155524] New: Export to PNG, file has zero size
https://bugs.documentfoundation.org/show_bug.cgi?id=155524 Bug ID: 155524 Summary: Export to PNG, file has zero size Product: LibreOffice Version: 7.6.0.0 alpha1+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: r...@post.cz Description: Export to PNG produce file with zero size. Steps to Reproduce: 1. open writer 2. File - Export 3. Select file type PNG 4. Export with default options Actual Results: File is zero size Expected Results: png file Reproducible: Always User Profile Reset: No Additional Info: . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152534] Windows 11 dark theme support--Active selections on Notebook Bar and Sidebar UI have light blue background which makes the white icon almost invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=152534 V Stuart Foote changed: What|Removed |Added Summary|Dark Mode on Windows 11 |Windows 11 dark theme |Active selections from the |support--Active selections |tabbed menu bar have light |on Notebook Bar and Sidebar |blue background which makes |UI have light blue |the white icon almost |background which makes the |invisible |white icon almost invisible Keywords|accessibility | --- Comment #15 from V Stuart Foote --- The Notebook Bar UIs were tweaked for bug 152454 for Win11 to not use Buttons for the tabs [1] and set better colors [2]. To support Win11 dark theme, something similar may be needed to render selected toggles for button widgets bcz MSSTYLES handling at Win11 muddles fg and bg assignment. =-ref-= [1] https://gerrit.libreoffice.org/c/core/+/144046 [2] https://gerrit.libreoffice.org/c/core/+/144045 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81257] FILEOPEN DOC: wrong image layout with square wrap - pictures that should be right aligned, appear at top of page (OK if DOC resaved in MSO as DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=81257 --- Comment #12 from Justin L --- The problem is that filter/source/msfilter is reading an nYRelTo that has an invalid value - so sw/source/filter/ww8/ww8graf.cxx sets to Entire Page sal_uInt32 nYAlign = nCntYAlign > rRecord.nYAlign ? rRecord.nYAlign : 1; -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147482] Suboptimal Menubar's Highlighted Text Color with Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=147482 --- Comment #4 from V Stuart Foote --- Rizal, still an issue in Win11 light theme mode? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147482] Suboptimal Menubar's Highlighted Text Color with Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=147482 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Status|NEW |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155499] Button widget "selected" status not well rendered light fg on blue bg (Win11 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=155499 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||vsfo...@libreoffice.org Version|7.6.0.0 alpha1+ Master |7.5.0.3 release Summary|improvements for dark mode |Button widget "selected" ||status not well rendered ||light fg on blue bg (Win11 ||only) --- Comment #5 from V Stuart Foote --- This is Windows 11 specific. Clips only show button widgets affected. Are button widgets on standard toolbars, and toggles on menu items affected as well on Windows 11 in os/DE dark theme? And is this for all button widgets or just the ones shown in the screen clips? Please comment on dupe. *** This bug has been marked as a duplicate of bug 152534 *** -- 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 Bug 150915 depends on bug 155499, which changed state. Bug 155499 Summary: Button widget "selected" status not well rendered light fg on blue bg (Win11 only) https://bugs.documentfoundation.org/show_bug.cgi?id=155499 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152534] Dark Mode on Windows 11 Active selections from the tabbed menu bar have light blue background which makes the white icon almost invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=152534 V Stuart Foote changed: What|Removed |Added CC||maicoleduardofigueroa@gmail ||.com --- Comment #14 from V Stuart Foote --- *** Bug 155499 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 140091] Suggestion: burger menu for sheets in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=140091 --- Comment #12 from ady --- (In reply to Leandro Martín Drudi from comment #11) > I think what you suggest is an excellent solution considering that currently > it only says that it is used to add a new sheet. See comment 10. > It might say "Add new sheet (right click to see all sheets)" As already mentioned, it is currently not showing _all_ worksheets, but non-hidden worksheets only. There are pros and cons for this behavior. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155500] can not change order of commands in notebookbar (omnibarra)
https://bugs.documentfoundation.org/show_bug.cgi?id=155500 ady changed: What|Removed |Added OS|Linux (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101769] LibreOffice Calc does not save language style of xslx file
https://bugs.documentfoundation.org/show_bug.cgi?id=101769 ady changed: What|Removed |Added OS|Linux (All) |All Keywords||filter:xls, filter:xlsx --- Comment #9 from ady --- FWIW: * cell's direct formatting is not the same as modifying the style. * [CTRL]+[1] > "Numbers" tab has a "Language" selection; * [CTRL]+[1] > "Font" tab has a "Language" selection. * Menu Tools > Options > Language Settings > Languages > Formats area has a "Language" selection; * Menu Tools > Options > Language Settings > Languages > Defaults Languages for Documents area has a "Language" selection. I am not sure which of all these "Language" selections are actually supported by Excel in its own xls and/or xlsx formats. This should be verified before reporting the fail to save/export any of these attributes from Calc to xls(x). -- You are receiving this mail because: You are the assignee for the bug.
