[Libreoffice-bugs] [Bug 151809] UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=151809 --- Comment #5 from Jorg --- I only checked that appearance back to version 6.4.7.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151809] UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=151809
Jorg changed:
What|Removed |Added
CC||inve...@gmx.ch
--- Comment #4 from Jorg ---
The top level menu (e.g. in Writer "File", "Home", "Insert", "Layout",
"References" etc.) is weirdly positioned. See attachment "TabbedToolbar.png".
It's nothing like the preview as in attachment "Select Your Preferred User
Interface.png" probably due to the standard way that macOS handles tabs.
Due to the misalignment of icons on the tabbed toolbar (Bug 133214), those tabs
look particularly out of place.
When the window is resized to a point where the top level menu gets cut off
("ResizedWindow.png") the menu entries to the right can't be selected anymore.
This results in undesired interruptions in workflows as I have resize the
window only to access some of those menu items.
Could the tab bar be at least left aligned so that when the window is resized
in its width all the menu entries can be selected?
Word aligns the menu left too and puts a double chevron to its right if there's
not enough space to place the remaining menu items (see "MSWord Tabbed
Menu.png")
I'd argue if the tabs even have to be all of the same width, saving further
space if they're only as wide as the text on the menu entry.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151809] UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=151809 --- Comment #3 from Jorg --- Created attachment 183320 --> https://bugs.documentfoundation.org/attachment.cgi?id=183320=edit How MS Word aligns the menu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151809] UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=151809 --- Comment #2 from Jorg --- Created attachment 183319 --> https://bugs.documentfoundation.org/attachment.cgi?id=183319=edit Resized Windows with cut off menu bar at top Once a window is resized the top menu bar gets cut off. The "Tools" menu is not visible and selectable anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151809] UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=151809 Jorg changed: What|Removed |Added Attachment #183318|image/jpeg |image/png mime type|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151809] UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=151809 --- Comment #1 from Jorg --- Created attachment 183318 --> https://bugs.documentfoundation.org/attachment.cgi?id=183318=edit Select Your Preferred User Interface in macOS The top level menu (e.g. in Writer "File", "Home", "Insert", "Layout", "References" etc.) is weirdly positioned. See attachment "TabbedToolbar.png". It's nothing like the preview as in attachment "Select Your Preferred User Interface.png" probably due to the standard way that macOS handles tabs. Due to the misalignment of icons on the tabbed toolbar (Bug 133214), those tabs look particularly out of place. Could the tab bar be at least left aligned so that when the window is -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151809] New: UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=151809 Bug ID: 151809 Summary: UI: Top level menu of Tabbed Toolbar isn't positioned well on macOS Product: LibreOffice Version: 6.4 all versions Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: inve...@gmx.ch Created attachment 183317 --> https://bugs.documentfoundation.org/attachment.cgi?id=183317=edit Tabbed Toolbar in macOS The top level menu (e.g. in Writer "File", "Home", "Insert", "Layout", "References" etc.) is weirdly positioned. See attachment "TabbedToolbar.png". It's nothing like the preview as in attachment "Select Your Preferred User Interface.png" probably due to the standard way that macOS handles tabs. Due to the misalignment of icons on the tabbed toolbar (Bug 133214), those tabs look particularly out of place. Could the tab bar be at least left aligned so that when the window is -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151737] Reports recovery of file every time system is shut down
https://bugs.documentfoundation.org/show_bug.cgi?id=151737 --- Comment #2 from Scott franco --- 1. went into safe mode. 2. Opened a document. 3. Tried to exit program (having done nothing at all). 4. It reports "exit with modified document?". I did other experiments. First, it is autosaving regardless of if I actually changed the document. And just as in the safe mode above, I will close the document and get the "exit modified" complaint. Coming back up with libreoffice saying "recover document" happens if I shut down the system and don't first close libreoffice. If I go to it, save the doc, then exit libreoffice before shutting down, then it comes back up without the "recover document". Conclusion: libreoffice does not seem to know when I have not modified the document, or is automatically modifying itself in a way I don't know about (updating the time or something?). It does not seem fatal, I haven't noticed any document damage. Its just disconcerting to see libreoffice state that my document needs recovery, or that it thinks I modified the document when I did nothing. I would expect that libreoffice would not complain about loss of data, or state the document needs recovering if I didn't modify it. I like libreoffice, coming from Microsoft word. Regards, Scott Franco -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151768] table toolbar in Writer on MacOSX appears at the bottom
https://bugs.documentfoundation.org/show_bug.cgi?id=151768 --- Comment #6 from Jorg --- Seems to be the case when user interface "Standard Toolbar" is selected. When "Tabbed Toolbar" is selected, the table toolbar appears at the top. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151533] The effect "change font size", acts as Exit fly-out left effect
https://bugs.documentfoundation.org/show_bug.cgi?id=151533 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 151529] The Play animation button only plays the animation for 2 seconds, even if the animation duration being set to 10 seconds
https://bugs.documentfoundation.org/show_bug.cgi?id=151529 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 151523] Margins shift left in Print, Preview, or Print to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=151523 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 148855] When click to open font list, it isn't open and I had to click many times to open it.
https://bugs.documentfoundation.org/show_bug.cgi?id=148855 --- Comment #2 from QA Administrators --- Dear Leonardo, 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 93084] Fileopen: Text Box with "Resize AutoShape to fit text" from 2007 DOCX shown with wrong size as without option (opens OK if DOCX resaved in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=93084 --- Comment #15 from QA Administrators --- Dear mikhail.v.gavrilov, 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 72239] table cell properties should be saved using style:table-cell-properties element
https://bugs.documentfoundation.org/show_bug.cgi?id=72239 --- Comment #9 from QA Administrators --- Dear David Tardon, 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 137807] Effect Sidebar Section is too wide Glow and Soft Edge spin box controls are truncated
https://bugs.documentfoundation.org/show_bug.cgi?id=137807 --- Comment #2 from QA Administrators --- Dear andreas_k, 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 137612] Table Rows aren't vertically centered; possibly triggered by page break.
https://bugs.documentfoundation.org/show_bug.cgi?id=137612 --- Comment #13 from QA Administrators --- Dear Clarc, 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 133568] After Changing Default Load/Save File Type while Running Calc Reset or Change to Another File Type Failed to Update in Setting Properly
https://bugs.documentfoundation.org/show_bug.cgi?id=133568 --- Comment #5 from QA Administrators --- Dear distantlightning, 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 123068] No Window Transition in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=123068 --- Comment #4 from QA Administrators --- Dear Daniel, 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 119973] OOXML: Signed Signature Line EMF has black background in Windows GDI and Linux GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=119973 --- Comment #9 from QA Administrators --- Dear Samuel Mehrbrodt (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111338] LibO will update the registrymodifications.xcu for every color chosen in the color picker (since LibO 5.3)
https://bugs.documentfoundation.org/show_bug.cgi?id=111338 --- Comment #20 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 113327] UI A vertical line appears in media player timer
https://bugs.documentfoundation.org/show_bug.cgi?id=113327 --- Comment #5 from QA Administrators --- Dear Emil Tanev, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151410] "Please report this incident." is not actionable advice
https://bugs.documentfoundation.org/show_bug.cgi?id=151410 --- Comment #2 from Aron Budea --- Help for Auto-Redact: https://help.libreoffice.org/latest/en-US/text/shared/guide/auto_redact.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125825] [META] (Auto-)Redaction bugs and improvement
https://bugs.documentfoundation.org/show_bug.cgi?id=125825 Aron Budea changed: What|Removed |Added Depends on||151410 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151410 [Bug 151410] "Please report this incident." is not actionable advice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151410] "Please report this incident." is not actionable advice
https://bugs.documentfoundation.org/show_bug.cgi?id=151410 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com Whiteboard| QA:needsComment| Blocks||125825 --- Comment #1 from Aron Budea --- Just collecting some information, this is a string of a message that might be shown in a message box in the Tools -> Auto-Redact dialog. It was first added in the following commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=fe977ec07087b103de8c809597fdaea8dd629837 (and got converted to a translatable string later) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125825 [Bug 125825] [META] (Auto-)Redaction bugs and improvement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151710] Toolbar button for enclosing text in () brackets
https://bugs.documentfoundation.org/show_bug.cgi?id=151710 Aron Budea changed: What|Removed |Added Severity|normal |enhancement CC||aron.bu...@gmail.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Component|General |Writer Summary|A botton () |Toolbar button for ||enclosing text in () ||brackets Keywords||needsUXEval Product|QA Tools|LibreOffice --- Comment #1 from Aron Budea --- Let's ask the UX team's opinion on this feature. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141843] [META] Bugs when file opened in multiple windows
https://bugs.documentfoundation.org/show_bug.cgi?id=141843 Aron Budea changed: What|Removed |Added Depends on||151433 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151433 [Bug 151433] Crash in: SwFrame::FindPageFrame() -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151433] Crash in: SwFrame::FindPageFrame()
https://bugs.documentfoundation.org/show_bug.cgi?id=151433 Aron Budea changed: What|Removed |Added Blocks||141843 CC||aron.bu...@gmail.com Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #4 from Aron Budea --- Let's close as WFM, then. If the bug occurs again, please reopen. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141843 [Bug 141843] [META] Bugs when file opened in multiple windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141843] [META] Bugs when file opened in multiple windows
https://bugs.documentfoundation.org/show_bug.cgi?id=141843 Bug 141843 depends on bug 151433, which changed state. Bug 151433 Summary: Crash in: SwFrame::FindPageFrame() https://bugs.documentfoundation.org/show_bug.cgi?id=151433 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141843] [META] Bugs when file opened in multiple windows
https://bugs.documentfoundation.org/show_bug.cgi?id=141843 Aron Budea changed: What|Removed |Added Summary|[META] Bugs when file open |[META] Bugs when file |in multiple windows |opened in multiple windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151467] FILEOPEN VSD file rendered incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=151467 Aron Budea changed: What|Removed |Added Attachment #182964|application/octet-stream|application/vnd.visio mime type|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127182] [META] MS Visio bugs and Improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=127182 Aron Budea changed: What|Removed |Added Depends on||151467 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151467 [Bug 151467] FILEOPEN VSD file rendered incorrectly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151467] FILEOPEN VSD file rendered incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=151467 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |NEW Blocks||127182 Whiteboard| QA:needsComment| Ever confirmed|0 |1 Keywords||filter:visio Version|3.3.0 release |Inherited From OOo Summary|[RENDERING] Draw - vsd file |FILEOPEN VSD file rendered |rendered incorrectly|incorrectly CC||aron.bu...@gmail.com --- Comment #3 from Aron Budea --- Confirmed in LO 7.5.0.0.alpha0+ (5a1f41a0d3aab15c113651f2edc9d4137ae99063), 3.5.0.3 (3.3.0 doesn't open the file) / Windows. Looks like an import problem, and not a rendering problem, those tab stops mess with text positioning. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127182 [Bug 127182] [META] MS Visio bugs and Improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143050] [META] Track Changes of text formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=143050 Aron Budea changed: What|Removed |Added Depends on||151808 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151808 [Bug 151808] FILEOPEN DOC Tracked formatting change not tracked in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151808] FILEOPEN DOC Tracked formatting change not tracked in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151808 Aron Budea changed: What|Removed |Added Blocks||143050 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143050 [Bug 143050] [META] Track Changes of text formatting -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Aron Budea changed: What|Removed |Added Depends on|150778 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150778 [Bug 150778] DOC Formatting changes remain after pressing Reject All in specific document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143065] [META] DOC Tracking changes-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=143065 Aron Budea changed: What|Removed |Added Depends on||150778 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150778 [Bug 150778] DOC Formatting changes remain after pressing Reject All in specific document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150778] DOC Formatting changes remain after pressing Reject All in specific document
https://bugs.documentfoundation.org/show_bug.cgi?id=150778 Aron Budea changed: What|Removed |Added Version|6.3.6.2 release |Inherited From OOo Blocks|83946 |143065 CC||aron.bu...@gmail.com Summary|Manage Changes dialog |DOC Formatting changes |listing formatting changes |remain after pressing |after pressing Reject All |Reject All in specific ||document --- Comment #6 from Aron Budea --- (In reply to Timur from comment #5) > I prefer it this way, but it's not so in Help, so either needs change. Word removes the italic formatting from Myosotis right away, and leaves no remaining tracked changes after reject all. Considering the behavior was never correct, as pointed out by Timur, I've retitled the bug report, and set oldest as Inherited from OO. Strangely, I checked with a freshly created Word DOC with a formatting change, and the change wasn't imported, opened bug 151808 on that. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83946 [Bug 83946] [META] Tracking changes issues https://bugs.documentfoundation.org/show_bug.cgi?id=143065 [Bug 143065] [META] DOC Tracking changes-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151808] FILEOPEN DOC Tracked formatting change not tracked in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151808 --- Comment #1 from Aron Budea --- Created attachment 183316 --> https://bugs.documentfoundation.org/attachment.cgi?id=183316=edit Screenshot in Word -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38890] Remove hard-coded project URLs
https://bugs.documentfoundation.org/show_bug.cgi?id=38890 Adoche Onaji changed: What|Removed |Added Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143065] [META] DOC Tracking changes-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=143065 Aron Budea changed: What|Removed |Added Depends on||151808 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151808 [Bug 151808] FILEOPEN DOC Tracked formatting change not tracked in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151808] New: FILEOPEN DOC Tracked formatting change not tracked in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151808 Bug ID: 151808 Summary: FILEOPEN DOC Tracked formatting change not tracked in Writer Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aron.bu...@gmail.com Blocks: 143065 Created attachment 183315 --> https://bugs.documentfoundation.org/attachment.cgi?id=183315=edit Sample DOC Open the attached DOC file, created in Word. It has a single tracked formatting change. => Writer shows no tracked changes. Observed in LO 7.5.0.0.alpha0+ (5a1f41a0d3aab15c113651f2edc9d4137ae99063), 3.3.0 / Windows. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143065 [Bug 143065] [META] DOC Tracking changes-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90558] Find & Replace Within Selection
https://bugs.documentfoundation.org/show_bug.cgi?id=90558 --- Comment #12 from Rajasekaran Karunanithi --- Reproducable in LO 7.4.2.3 under LXLE (x64) distro Focal release.Find and replace works only for current selection of text in a table. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 1; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.20.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151806] : Unable to edit function formulas in T-Test statistical function
https://bugs.documentfoundation.org/show_bug.cgi?id=151806 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151806] : Unable to edit function formulas in T-Test statistical function
https://bugs.documentfoundation.org/show_bug.cgi?id=151806
Eike Rathke changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|--- |NOTABUG
--- Comment #1 from Eike Rathke ---
You missed that the formulas for Observed Mean Difference, Variance of the
Differences and df are *array* formulas, as indicated by the leading/trailing
{} braces when viewing them in the Input Line. When modifying them close them
shift Shift+Ctrl+Enter instead of just Enter. Otherwise the ranges passed to
functions that expect scalar values as a parameter are evaluated by their
implicit intersections with the formula cell position.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151794] Validity drop-down shows empty value when 'Allow empty cells' is disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=151794 Justin L changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | --- Comment #12 from Justin L --- I see the problem in both the Calc Allow empty cells - DISABLED.ods file and in Excel.xlsx. (I assume that comment 5 means it works in Excel application, not that it works in Calc.) Proposed fix at http://gerrit.libreoffice.org/c/core/+/142002 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151807] New: Whenever I open a file with LibreOffice a Windows security message immediately pops up
https://bugs.documentfoundation.org/show_bug.cgi?id=151807 Bug ID: 151807 Summary: Whenever I open a file with LibreOffice a Windows security message immediately pops up Product: LibreOffice Version: 7.4.2.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: maidm...@gmail.com Description: Problem started straight after I upgraded to LibreOffice 7.4.2 via PatchMyPC. Every time I open a Writer doc or Calc Spreadsheet I get a Windows Security Virus & Threat Protection message pop up which states: Unauthorised changes blocked. Controlled folder access blocked soffice.bin from making changes. I have run a full Windows Defender security scan on my hard disc. No threats were detected. I am very security conscious and do not want to make changes to my Windows 10 security settings. In simple language (I am not a techie!) what can I do to solve this problem?? Have the files I have opened with LibreOffice 7.4.2 been infected? Please help. Steps to Reproduce: 1.click on document or calc file or LibreOffice 7.4.2 icon 2. 3. Actual Results: File opens, then a couple of seconds later Windows security message pops up but quickly disappears and am able to edit file. Expected Results: Not to get the security message. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: StartModule [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151806] New: : Unable to edit function formulas in T-Test statistical function
https://bugs.documentfoundation.org/show_bug.cgi?id=151806
Bug ID: 151806
Summary: : Unable to edit function formulas in T-Test
statistical function
Product: LibreOffice
Version: 7.4.2.3 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: bertpool...@gmail.com
While trying to edit the automatic formulas produced by running the "built-in"
Paired T-test statistical function, I have found that there are three complex
formulae used within the T-test statistical function that *cannot be edited.*
At all.
T-test is comprised of several sub-values,
for which the formulas CAN be edited by the user.
Those values produced by T-test with zero editing problems are listed here:
Alpha
Hypothesized Mean Difference
Mean
Variance
Observations
Pearson Correlation
t Stat
P (T<=t) one-tail
t Critical one-tail
P (T<=t) two-tail
t Critical two-tail
However, there are three values that use very complicated formulas.
Those three complicated formulas are labelled as:
Observed Mean Difference
Variance of the Differences
df
These three formulas *cannot* be user-edited and continue to work.
If you change *anything* by editing any part of these three formulas,
they will immediately stop producing correct results.
For example, the "Observed Mean Difference formula, used within the T-test
is: =AVERAGE(IF(ISODD(IF(ISNUMBER($Sheet2.$B$2:$B$11), 1, 0) *
IF(ISNUMBER($Sheet2.$C$2:$C$11), 1, 0)), $Sheet2.$B$2:$B$11 -
$Sheet2.$C$2:$C$11, "NA"))
The problem: For example, if you edit the above formula and change the Letter
"V" in the first function AVERAGE to "v", lower case, and press , then
the calculated value immediately changes to a WRONG value!
And if you think the lower case "v" might not work, go ahead try using
a capital "V" if you prefer. The result is the same - the calculated result
changes to a *bad* value.
Attempts to fix: I have updated my copy of Libreoffice to the newest version
7.4.2.3, running under Ubuntu Linux 22.04.1. I even tried testing this
Calc T-test formula editing issue on a different machine running an earlier
version of both Ubuntu and Libreoffice - I find that the attempted system
changes did NOT resolve the problem.
Replicating this problem is super simple.
1) Create a new spreadsheet in Calc
2) Copy the raw data below to cell starting at A1:
Item # DATA 1 DATA 2
1 21251 21251
2 21272 21248
3 21144 21348
4 21301 21150
5 21193 21276
6 21238 21226
7 21240 21034
8 21137 21181
9 21299 21299
10 21040 21247
Row 1 is a header row.
The raw data we will process is in columns B and C, rows 2 thru 11:
3) Using your cursor, highlight the twenty data numbers to be T-tested
(Cells B2:C11)
>From your Calc Menu select "Data", "Statistics", "Paired t-test".
Because you've already highlighted the data to be tested, the first
two required entry fields are already populated; all you have to do
now is:
4) Select the cell where you want the T-test results to go to. Click on cell
E1.
Calc will fill-in the t-test results into your spreadsheet, starting at
Cell E1.
This is what you should see:
Paired t-test
Alpha 0.05
Hypothesized Mean Difference 0
Variable 1Variable 2
Mean21211.5 21226
Variance6918.056 7658.667
Observations1010
Pearson Correlation-0.198090290379547
Observed Mean Difference -14.5
Variance of the Differences 17460.5
df 9
t Stat -0.347008141418145
P (T<=t) one-tail 0.368280585837927
t Critical one-tail 1.83311293265624
P (T<=t) two-tail 0.736561171675855
t Critical two-tail 2.26215716279821
Sorry if this notepad screen changed formatting. But to continue . . .
Pay special attention to Cell F9 ("Observed Mean Difference".
It has a T-test calculated value of -14.5
Now we get to the good part!
Click on cell F9.
Press F2 key to Edit the formula in cell F9.
Remember I said the formula is complex? Here it is again:
=AVERAGE(IF(ISODD(IF(ISNUMBER($Sheet2.$B$2:$B$11), 1, 0) *
IF(ISNUMBER($Sheet2.$C$2:$C$11), 1, 0)), $Sheet2.$B$2:$B$11 -
$Sheet2.$C$2:$C$11, "NA"))
Highlight the left part of the long formula near the beginning, specifically
the word "AVERAGE". Over-type those seven letters (AVERAGE) with exactly
the same letters "AVERAGE". You say "But Bert, I have changed nothing!"
Yes you did.
Press ENTER to save your change. The formula should be identical to what was
[Libreoffice-bugs] [Bug 151804] Sidebar content from WollMux extension disappears when resizing
https://bugs.documentfoundation.org/show_bug.cgi?id=151804 --- Comment #2 from Caolán McNamara --- is this the same as bug 151509 or a separate problem? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura (context switching)
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 --- Comment #10 from Alex Thurgood --- I would add that if you look at comments 8, 13 and 28 of bug 148345, you can see that a commit has been identified as the likely culprit, but nothing has happened since it was bibisected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura (context switching)
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 --- Comment #9 from Alex Thurgood --- (In reply to Matten from comment #8) > Hi Alex, > > a simple context switch is certainly not enough to trigger the issue, it > seems the app must have been in the background for quite a while. I will > create a stacktrace when this happens the next time. Hi Matten, Yes, the traces in the other bug reports appear to show that triggering a redraw of a portion of the LO interface categorised as an idle thread causes a deadlock with other threads. The Visual Class Layer (vcl) is the very old abstraction layer built into LO and inherited from StarOffice onto which the Aqua UI framework (and indeed, all of the other UI frameworks) was bolted to enable the initial macOS port way back in the day before LibreOffice was even a twinkle in the community's eye. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151805] New: Crash in: SkiaSalGraphicsImpl::applyXor()
https://bugs.documentfoundation.org/show_bug.cgi?id=151805 Bug ID: 151805 Summary: Crash in: SkiaSalGraphicsImpl::applyXor() Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: howard.girdlest...@gmail.com This bug was filed from the crash reporting server and is br-b2cee2ef-c870-4952-b6e4-5a33bc882f89. = -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151731] Crash when saving file after manual word wrap in cell (ODS file)
https://bugs.documentfoundation.org/show_bug.cgi?id=151731 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- No repro in windows in current daily build Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 02db1642c9ce4394f4f85755c4a0a831e547e4fb CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded macOS only? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=61914 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||151803 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151803 [Bug 151803] StartCenter: Filter for shown applications - missing Databases and Formula documents -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151803] StartCenter: Filter for shown applications - missing Databases and Formula documents
https://bugs.documentfoundation.org/show_bug.cgi?id=151803 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||implementationError Status|UNCONFIRMED |NEW Severity|normal |enhancement Blocks||61914 Ever confirmed|0 |1 OS|Linux (All) |All CC||79045_79...@mail.ru, ||heiko.tietze@documentfounda ||tion.org --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Indeed Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 02db1642c9ce4394f4f85755c4a0a831e547e4fb CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded Heiko? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=61914 [Bug 61914] [META] Start Center bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123515] Slow zoom with 3D object visible
https://bugs.documentfoundation.org/show_bug.cgi?id=123515 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #6 from Roman Kuznetsov <79045_79...@mail.ru> --- Telesto please retest it yourself, I don't see any delays or some problem when I use zoom in/out Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 02db1642c9ce4394f4f85755c4a0a831e547e4fb CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded and bug 134585 is absolutely the duplicate of this one, IMHO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151804] Sidebar content from WollMux extension disappears when resizing
https://bugs.documentfoundation.org/show_bug.cgi?id=151804 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 183314 --> https://bugs.documentfoundation.org/attachment.cgi?id=183314=edit Empty sidebar after resize -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151804] New: Sidebar content from WollMux extension disappears when resizing
https://bugs.documentfoundation.org/show_bug.cgi?id=151804 Bug ID: 151804 Summary: Sidebar content from WollMux extension disappears when resizing Product: LibreOffice Version: 7.2.0.4 release Hardware: All URL: https://wollmux.org/ OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com CC: caol...@redhat.com, samuel.mehrbr...@allotropia.de Created attachment 183313 --> https://bugs.documentfoundation.org/attachment.cgi?id=183313=edit The sidebar when opening a new document This was observed with the WollMux extension. To set it up: - Get the extension v18.1 from https://github.com/WollMux/WollMux/releases/download/RELEASE_18.2.10/WollMux.oxt and install it in LO - Get the configuration from https://github.com/WollMux/wollmux-config/releases/download/v18.1.0/wollmux-config-18.1.0.tar.gz and extract to ~/.wollmux After a restart you should see 3 new WollMux tabs on the sidebar in Writer. 1, In non-full screen dialog try vertically resizing the Writer dialog so much that the contents of the WollMux tab are not fitting in the area and a scrollbar appears on its right side. 2, Change to another WollMux sidebar tab, then back to the first one. This causes the first tabs content to disappear. Only with GTK3 backend, not gen. Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: f3a82a8ba51195cf31b0f78164735acc7ebbcd2f CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (hu_HU.UTF-8); UI: en-US Calc: threaded Seems to have started in 7.2 with: https://git.libreoffice.org/core/+/d764415977ad65bb4a657ccada7c9b2c19b689e1 author Caolán McNamara Tue Mar 02 16:18:43 2021 + committer Caolán McNamara Thu Mar 11 14:29:54 2021 +0100 tree8f2a84b795e9a4cf5036dae0984c9ed2937933a7 parent feb8164afa67d3e2e5fe27dd01c5101d6d0cb847 [diff] merge panel and panel title Adding CC to: Caolán McNamara -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125674] [META] Document Comparison bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=125674 Bug 125674 depends on bug 125689, which changed state. Bug 125689 Summary: Comparing a large ODS (with an identical file) is extremely slow (Win-only) https://bugs.documentfoundation.org/show_bug.cgi?id=125689 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125689] Comparing a large ODS (with an identical file) is extremely slow (Win-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=125689 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Resolution|--- |WORKSFORME CC||79045_79...@mail.ru Status|NEW |RESOLVED --- Comment #5 from Roman Kuznetsov <79045_79...@mail.ru> --- Around 5 sec in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 02db1642c9ce4394f4f85755c4a0a831e547e4fb CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded Closed as WFM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura (context switching)
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 --- Comment #8 from Matten --- Hi Alex, a simple context switch is certainly not enough to trigger the issue, it seems the app must have been in the background for quite a while. I will create a stacktrace when this happens the next time. -- 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 145266, which changed state. Bug 145266 Summary: Writer crashes when inserting formula object https://bugs.documentfoundation.org/show_bug.cgi?id=145266 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 Buovjaga changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #38 from Buovjaga --- Great to hear :) Let's go ahead and close this, then. 7.5 will be released in February 2023. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 --- Comment #37 from Panos Moisiadis --- (In reply to Buovjaga from comment #36) > Panos: is the crash gone also for you with latest 7.5? Yes I can confirm the crash is gone with 7.5 Thanks everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 --- Comment #36 from Buovjaga --- Panos: is the crash gone also for you with latest 7.5? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151768] table toolbar in Writer on MacOSX appears at the bottom
https://bugs.documentfoundation.org/show_bug.cgi?id=151768 --- Comment #5 from Alex Thurgood --- (In reply to Alex Thurgood from comment #4) > @Nikolay : is there something I'm doing different to what you are doing ? I'm using the standard toolbar display with icons/text labels, and the large Elementary icon theme set. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151768] table toolbar in Writer on MacOSX appears at the bottom
https://bugs.documentfoundation.org/show_bug.cgi?id=151768 --- Comment #4 from Alex Thurgood --- (In reply to m.a.riosv from comment #3) > Please take a look: > https://help.libreoffice.org/latest/en-US/text/shared/guide/floating_toolbar. > html?DbPAR=SHARED#bm_id3152801 At best, that would be a workaround to mitigate the behaviour described. FWIW, I can't reproduce the described behaviour when : 1) Open a blank Writer document 2) Insert a table via the insert table toolbar 3) Switch Writer window to fullscreen (green button on window frame). 4) The table toolbar does appear at the bottom of the window, but the menus unfold from the bottom upwards. @Nikolay : is there something I'm doing different to what you are doing ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151766] Using Java UNO API freezes LibreOffice on M1 MacBook Pro
https://bugs.documentfoundation.org/show_bug.cgi?id=151766 Alex Thurgood changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151766] Using Java UNO API freezes LibreOffice on M1 MacBook Pro
https://bugs.documentfoundation.org/show_bug.cgi?id=151766 --- Comment #3 from Alex Thurgood --- FWIW, the many of the people who do bug triaging within the project are not developers/programmers, and this is almost exclusively so on macOS. There are certainly no paid developers working on macOS specific LO issues, to my knowledge. In order for it to be tested, we would generally need a greater degree of detail on how to reproduce. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151766] Using Java UNO API freezes LibreOffice on M1 MacBook Pro
https://bugs.documentfoundation.org/show_bug.cgi?id=151766 --- Comment #2 from Alex Thurgood --- How is this code supposed to be run ? Do I just download the sample code, add a .java extension to the file name and try and run it from the command line ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151736] Opening Writer document with direct formatting crashes whole LO
https://bugs.documentfoundation.org/show_bug.cgi?id=151736 Robert Großkopf changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #9 from Robert Großkopf --- (In reply to Commit Notification from comment #8) > Noel Grandin committed a patch related to this issue. > It has been pushed to "master": > > https://git.libreoffice.org/core/commit/ > 7d63176bcfbc80fc4045a0f0580c5bf9ccea7a89 > > tdf#151736 writer direct formatting crash > > It will be available in 7.5.0. > Tested in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 876d9d6d333cafc0649abebc757f397faf86fc4d CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Document could be loaded without any problem. Thanks for the fast fix. Could it also be backported to LO 7.4? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura (context switching)
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 Alex Thurgood changed: What|Removed |Added Summary|LO 7.3.6.2 gets stuck on|LO 7.3.6.2 gets stuck on |macOS Ventura |macOS Ventura (context ||switching) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 --- Comment #7 from Alex Thurgood --- (In reply to lupurus from comment #5) > I am using a Mac Silicon too (M2). Thanks ! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hanges on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...)
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1730 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8435 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 --- Comment #6 from Alex Thurgood --- (In reply to Matten from comment #4) > Hi Alex, > > I see the issue on a Apple Silicon based Mac. I do the context switch just > by clicking into the window of another app or via the dock. > > Let me me whether stacktrace would help, I have send several reports to > Apple, but I'm not sure you get these. Hi Matten, thanks for your offer of a stacktrace. It would be useful, if only to see whether it is substantially the same as those produced in other similar bug reports, for example in bug 148435 (spindump), or bug 151726 (Apple stack trace I just uploaded). I am not a developer, just a volunteer QA bug triager, who happens to use LO at work mainly on macOS machines. I certainly don't receive the Apple produced reports that are optionally sent to Apple when an app crashes. I'm not even sure that Apple passes these on to the LO development community. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151726] CMD + Grave Accent causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=151726 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8435 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hanges on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...)
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1726 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151803] StartCenter: Filter for shown applications - missing Databases and Formula documents
https://bugs.documentfoundation.org/show_bug.cgi?id=151803 Robert Großkopf changed: What|Removed |Added Summary|StartCenter: Filter for |StartCenter: Filter for |shown applications -|shown applications - |missing Databases |missing Databases and ||Formula documents -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151803] New: StartCenter: Filter for shown applications - missing Databases
https://bugs.documentfoundation.org/show_bug.cgi?id=151803 Bug ID: 151803 Summary: StartCenter: Filter for shown applications - missing Databases Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de There is a new filter in StartCenter. You could show all documents, Writer, Calc, Impress and Draw - but there is no possibility to show Base-documents or formula-documents without all these other documents. A filter should be able to change between all kind of documents, which could be created. I'm missing a filter for all my databases. Others will need a filter for formula. Seems these documents have been forgotten. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151726] CMD + Grave Accent causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=151726 Alex Thurgood changed: What|Removed |Added Keywords|wantBacktrace | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151726] CMD + Grave Accent causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=151726 --- Comment #6 from Alex Thurgood --- Created attachment 183312 --> https://bugs.documentfoundation.org/attachment.cgi?id=183312=edit Apple stack trace on beachball hang requiring forced kill of soffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151726] CMD + Grave Accent causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=151726 Alex Thurgood changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Alex Thurgood --- Confirming with Version: 7.4.1.2 / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Mac OS X 13.0; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded The spinning beachball freeze is immediate and requires forced kill when using this context switcher with LO7412 aarch64 on macOS Silicon M1. Enclosing Apple stack trace when beachball occurs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151726] CMD + Grave Accent causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=151726 --- Comment #4 from Alex Thurgood --- (In reply to V Stuart Foote from comment #3) > That is +, the glyph is U+0060 GRAVE ACCENT in Unicode. And > internally in LibreOffice the key shortcut is 'QUOTELEFT_MOD1' > > Function on macOS as for bug 116087 or bug 114858, so any crash when > switching between open LibreOffice modules would be a regression, or > possibly something new for a Silicon based Apple. > > But better STR and details of the the crash are needed. > I suspect that this is much more likely to be another manifestation of bug 148435. Context switching appears to give the VCL scheduler a few problems that it fails to handle gracefully. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 --- Comment #5 from lupu...@web.de --- (In reply to Alex Thurgood from comment #3) > Could both of you provide the build architecture version of LibreOffice that > you are using, either x86_64 (Intel version) or aarch64 (Mac Silicon > version) ? I am using a Mac Silicon too (M2). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151791] Calc-UI-Edit drop down menu-Cell protection
https://bugs.documentfoundation.org/show_bug.cgi?id=151791 --- Comment #3 from George Tzan --- The tick mark is actually a prefix NOT a suffix. Sorry! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144167] exported PNG image has wrong size when page has border
https://bugs.documentfoundation.org/show_bug.cgi?id=144167 --- Comment #25 from Valerio Messina --- older version of LO (and current AOO) let select both quantities (size and resolution) at the same time in export dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 --- Comment #35 from tex.ave...@aliceadsl.fr --- Noel Grandin send me also, today, directly the dev of LO: https://dev-builds.libreoffice.org/daily/master/current.html and It works ! We can only hope that version 7.5.0 is released as soon as possible for macOS users… Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143377] FORMATTING and PRINTING: Setting Border with rotated text changes row background color (not with gen VCL backend)
https://bugs.documentfoundation.org/show_bug.cgi?id=143377 Armin Le Grand changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |armin.le.gr...@me.com |desktop.org | --- Comment #11 from Armin Le Grand --- Identified the problem: In Cell::HelperCreateB2DHomMatrixFromB2DRange a Shear/Skew is applied depending on the rotation. It is excluded for zero (IsRotated()) but not for mfOrientation == 3.1415926535897931 which is 180 degree (PI). Thus const double fSkew(aY.getY() * (cos(mfOrientation) / sin(mfOrientation))); is created as -5.5526213800864256e+17 due to sin(mfOrientation) being close to zero (numerical errors, it should be straight zero what would have led to division by zero and a crash). This is HUGE. The rest of the double-precision mechanism creates the correct borders for that Skew, so what you see is the VERY far-stretched geometry of the border polygons. This makes of course no sense, so it needs to be handled for PI/180 deg rotation. The text is drawn at ScOutputData::DrawRotated and use a Skew, too, so we should do the same correction as it has to be there already. Unfortunately it also just works by chance - the eRotMode gets forced to SVX_ROTATE_MODE_STANDARD by if ( nAttrRotate == 18000_deg100 ) eRotMode = SVX_ROTATE_MODE_STANDARD;// no overflow but still wild values for nCos = cos( nRealOrient ); nSin = sin( nRealOrient ); get calculated, nSin (a double :-)) being also wild (1.2246467991473532e-16). All calculations use it, but due to being close to zero, it has no real influence -> nothing bad happens... It *still* only corrects for 18000, not for 17999 nor for 18001, so we are lucky that only single degree values pop in from the UI side (not sure about UNO API or odf import...). But it gives us no good hint how to correct it at Cell::HelperCreateB2DHomMatrixFromB2DRange. Have to think about a good solution... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 --- Comment #34 from tex.ave...@aliceadsl.fr --- I Tried on 7.5.0 !!! There is no bug !!! Yes !!! But it was without Java... Now How can I desinstall everything ??? Regards, -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151726] CMD + Grave Accent causes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=151726 Philip Farris changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132532] FILEOPEN: DOCX: Smartart: Flowchart shows empty boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=132532 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=54 ||095 --- Comment #15 from Regina Henschel --- The "missing" text is covered by bug 54095. In fact it is white text on white background. So this issue should focus on the missing arrows and borders in attachment 166819. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105460] FILEOPEN text color in SmartArt is different than in PP
https://bugs.documentfoundation.org/show_bug.cgi?id=105460 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #7 from Regina Henschel --- Please try a daily build (LO 7.5). I cannot reproduce the problem in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 17dfc9a9da009cc23de3fb4e2cef9c97d581 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded PowerPoint 365 and LO 7.5 show the SmartArt with same colors. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 54095] FILEOPEN: Font color is wrong (white instead of black on white background) in DOCX SmartArt Horizontal Hierarchy (that cannot be edited in LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=54095 Regina Henschel changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151802] Copy/paste on slide pane duplicates the master slide
https://bugs.documentfoundation.org/show_bug.cgi?id=151802 Xisco Faulí changed: What|Removed |Added CC||armin.le.gr...@me.com Version|7.5.0.0 alpha0+ Master |6.1 all versions Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords||bibisected, bisected, ||regression --- Comment #2 from Xisco Faulí --- Regression introduced by: author Armin Le Grand 2018-03-01 15:54:32 +0100 committer Armin Le Grand 2018-04-07 00:28:30 +0200 commit dfefe448c41921f2f1e54d3f69b8b9e89031d055 (patch) tree1aace31054b5740e2faffcbc5de66a791be27f7d parent eba4d5b2b76cefde90cb3d6638c736f435023a45 (diff) SOSAW080: Added first bunch of basic changes to helpers Bisected with: bibisect-linux64-6.1 Adding Cc: to Armin Le Grand -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151802] Copy/paste on slide pane duplicates the master slide
https://bugs.documentfoundation.org/show_bug.cgi?id=151802 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=96 ||708 --- Comment #1 from Xisco Faulí --- Issue found while working on https://gerrit.libreoffice.org/c/core/+/141975 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151802] New: Copy/paste on slide pane duplicates the master slide
https://bugs.documentfoundation.org/show_bug.cgi?id=151802 Bug ID: 151802 Summary: Copy/paste on slide pane duplicates the master slide Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xiscofa...@libreoffice.org Created attachment 183311 --> https://bugs.documentfoundation.org/attachment.cgi?id=183311=edit sample file Steps to reproduce: 1. Open attached document 2. In the slide pane select slide 1, copy and paste -> There are 5 slides 3. Go to View - Master slide -> There are 5 master slides. There should be 4 instead Reproduced in Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: f3a82a8ba51195cf31b0f78164735acc7ebbcd2f CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 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 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 --- Comment #33 from Buovjaga --- (In reply to Alex Thurgood from comment #32) > (In reply to Buovjaga from comment #28) > > (In reply to tex.avery2 from comment #26) > > LODE setup fails on macOS Ventura with error message: > > Unknown kernel version 22.1.0 https://gerrit.libreoffice.org/c/lode/+/141972 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 --- Comment #32 from Alex Thurgood --- (In reply to Buovjaga from comment #28) > (In reply to tex.avery2 from comment #26) LODE setup fails on macOS Ventura with error message: Unknown kernel version 22.1.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151730] LO 7.3.6.2 gets stuck on macOS Ventura
https://bugs.documentfoundation.org/show_bug.cgi?id=151730 Sierk Bornemann changed: What|Removed |Added Blocks||42082 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=42082 [Bug 42082] [META] Make LibreOffice shine and glow on macOS -- You are receiving this mail because: You are the assignee for the bug.
