[Libreoffice-bugs] [Bug 145371] Global Array of defined user type : values lost
https://bugs.documentfoundation.org/show_bug.cgi?id=145371 Dorange-Pattoret Didier changed: What|Removed |Added CC||ddora...@dmaths.org --- Comment #1 from Dorange-Pattoret Didier --- Created attachment 175982 --> https://bugs.documentfoundation.org/attachment.cgi?id=175982=edit A small extension for tests -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145372] Cross References to Figures Do Not Update
https://bugs.documentfoundation.org/show_bug.cgi?id=145372 --- Comment #1 from a...@norsci.com --- To clarify, when I say "delete the image" I mean delete the frame that contains the image, the caption, and the field. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145372] New: Cross References to Figures Do Not Update
https://bugs.documentfoundation.org/show_bug.cgi?id=145372 Bug ID: 145372 Summary: Cross References to Figures Do Not Update Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: a...@norsci.com Description: When working with a document that contains cross-references to figure numbers, deleting the figures does not result in the references showing the "Error: Reference source not found" text. Instead, the field shows the old number. Using "Update Fields" or pressing F9 does not update them. Steps to Reproduce: 1. Create a blank Writer document. 2. Insert 4 images. 3. Configure each image to be positioned as a character. 4. Add a caption to each image, which also adds a figure number field to each one. 5. At the top of the document use the Insert>Cross-reference tool to insert references to the figure numbers. This simple example just looks like "1 2 3 4" where each number is a field. 6. Pick an image at random and delete it. While the figure numbering for the remaining figures does update, the number for the one I deleted remains the same. So, if I delete figure 2 from the document, the cross references now look like "1 2 2 3". We *know* that the second reference is wrong, and clicking on it goes no where, but it is not updated to show the "Error: Reference source not found" message. 7. Clicking F9 or using the menu to "Update Fields" does not work. Saving the document and opening it again seems to update the fields. Sometimes clicking View>"Show Tracked Changes" is enough to update the missing field, but this doesn't always work. Actual Results: The field text for a deleted field target retains the old value. Expected Results: The field text for a deleted field target should always show the "Error: Reference source not found" message. Reproducible: Always User Profile Reset: No Additional Info: Please fix. This makes working on large documents with lots of cross references to figures particularly painful. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145371] New: Global Array of defined user type : values lost
https://bugs.documentfoundation.org/show_bug.cgi?id=145371 Bug ID: 145371 Summary: Global Array of defined user type : values lost Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ddora...@dmaths.org Description: LO 7.2 : Values of Global Array defined user type are lost at end of runtime. No problem with LO 7.1 or Aoo 4.1 Steps to Reproduce: Use joigned extension 1. Run macro 1 2. Run macro 2 Actual Results: Values of A lost Expected Results: Values of A retained Reproducible: Always User Profile Reset: Yes Additional Info: It works without problem with LO 7.1.2, AOOo 4.1.11 but not with LO 7.2.1 So it's a regression. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145127] LibreOfficeKit macOS?
https://bugs.documentfoundation.org/show_bug.cgi?id=145127 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 145126] It'd be nice if the formula bar in Calc would accept the LibreOffice Dark application color scheme
https://bugs.documentfoundation.org/show_bug.cgi?id=145126 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 145125] EDITING Moving a bulleted paragraph upwards/downwards and rejecting all changes leaves paragraph bulleted
https://bugs.documentfoundation.org/show_bug.cgi?id=145125 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 145124] EDITING Moving down a numbered paragraph with change tracking and rejecting all gets duplicated
https://bugs.documentfoundation.org/show_bug.cgi?id=145124 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 145122] Linux/KDE: Cursor disappears while creating a table in Base, switching between text and styles in Writer …
https://bugs.documentfoundation.org/show_bug.cgi?id=145122 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 145061] Font::identifyFont should also detect Type1C font
https://bugs.documentfoundation.org/show_bug.cgi?id=145061 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 141406] Forms do not work with PDF/DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=141406 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 141406] Forms do not work with PDF/DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=141406 --- Comment #4 from QA Administrators --- Dear LI AR, 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 141353] Upgrading from 7.03 to 7.0.5 Win 10 error 1303
https://bugs.documentfoundation.org/show_bug.cgi?id=141353 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141353] Upgrading from 7.03 to 7.0.5 Win 10 error 1303
https://bugs.documentfoundation.org/show_bug.cgi?id=141353 --- Comment #4 from QA Administrators --- Dear Michael, 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 141325] Problem with Transaction
https://bugs.documentfoundation.org/show_bug.cgi?id=141325 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141325] Problem with Transaction
https://bugs.documentfoundation.org/show_bug.cgi?id=141325 --- Comment #3 from QA Administrators --- Dear Xavier, 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 139476] if you accidently paste something large into a search box LO freezes for a long time
https://bugs.documentfoundation.org/show_bug.cgi?id=139476 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139476] if you accidently paste something large into a search box LO freezes for a long time
https://bugs.documentfoundation.org/show_bug.cgi?id=139476 --- Comment #5 from QA Administrators --- Dear ffs, 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 139223] FILESAVE DOC: Loosing parallel wrap on DOC export
https://bugs.documentfoundation.org/show_bug.cgi?id=139223 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 139223] FILESAVE DOC: Loosing parallel wrap on DOC export
https://bugs.documentfoundation.org/show_bug.cgi?id=139223 --- Comment #7 from QA Administrators --- Dear Telesto, 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 138575] Pasting images makes LibreOffice Writer slow
https://bugs.documentfoundation.org/show_bug.cgi?id=138575 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 138575] Pasting images makes LibreOffice Writer slow
https://bugs.documentfoundation.org/show_bug.cgi?id=138575 --- Comment #9 from QA Administrators --- Dear Alex, 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 136775] Content appears after save & reload (Track & changes involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=136775 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 136775] Content appears after save & reload (Track & changes involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=136775 --- Comment #4 from QA Administrators --- Dear Telesto, 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 136774] Image visible which should probably by hidden (track & changes)
https://bugs.documentfoundation.org/show_bug.cgi?id=136774 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 136774] Image visible which should probably by hidden (track & changes)
https://bugs.documentfoundation.org/show_bug.cgi?id=136774 --- Comment #3 from QA Administrators --- Dear Telesto, 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 136627] Memory usage increases with 200 MB after hovering over file send (java runtime related)
https://bugs.documentfoundation.org/show_bug.cgi?id=136627 --- Comment #4 from QA Administrators --- Dear Telesto, 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 136627] Memory usage increases with 200 MB after hovering over file send (java runtime related)
https://bugs.documentfoundation.org/show_bug.cgi?id=136627 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 136284] Undo steps cut/off broken after RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=136284 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109040] [META] RTF paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109040 Bug 109040 depends on bug 136284, which changed state. Bug 136284 Summary: Undo steps cut/off broken after RTF paste https://bugs.documentfoundation.org/show_bug.cgi?id=136284 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136284] Undo steps cut/off broken after RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=136284 --- Comment #5 from QA Administrators --- Dear Telesto, 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 136178] File opens with different formatting compared to how it was saved (track & changes involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=136178 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 136178] File opens with different formatting compared to how it was saved (track & changes involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=136178 --- Comment #5 from QA Administrators --- Dear Telesto, 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 135751] BUG numéros et nombre de pages
https://bugs.documentfoundation.org/show_bug.cgi?id=135751 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 135751] BUG numéros et nombre de pages
https://bugs.documentfoundation.org/show_bug.cgi?id=135751 --- Comment #3 from QA Administrators --- Dear claude.ol.martin, 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 135678] Draw unable to open file properly after creation/saving
https://bugs.documentfoundation.org/show_bug.cgi?id=135678 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135678] Draw unable to open file properly after creation/saving
https://bugs.documentfoundation.org/show_bug.cgi?id=135678 --- Comment #5 from QA Administrators --- Dear Michael, 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 142015] Tabbed NB 'User Interface...' dialog box is blank
https://bugs.documentfoundation.org/show_bug.cgi?id=142015 --- Comment #3 from QA Administrators --- Dear voncloft, 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 142001] Crash in: igc64.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=142001 --- Comment #2 from QA Administrators --- Dear ernestbarbosa, 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 91664] Form controls in frame in section disappear after hiding
https://bugs.documentfoundation.org/show_bug.cgi?id=91664 --- Comment #9 from QA Administrators --- Dear Graham Horner, 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 84427] FILESAVE: Video files not saved in DOC or DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=84427 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 125934] No application icon on Wayland with the qt5 / kf5 backend
https://bugs.documentfoundation.org/show_bug.cgi?id=125934 --- Comment #14 from QA Administrators --- Dear Jan-Marek Glogowski, 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 124694] Video passing slide boundaries causes weird zoom in or shift (gtk2/gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=124694 --- Comment #19 from QA Administrators --- Dear Saren Tasciyan, 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 124042] Lots of CoreGraphics calls without a valid context
https://bugs.documentfoundation.org/show_bug.cgi?id=124042 --- Comment #9 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 118823] Zooming in or out with blue header toolbar button visible rather slow and lagging (Win-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=118823 --- Comment #7 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 145355] EDITING: CellStyle should allow making text all UPPERCASE or all lowercase
https://bugs.documentfoundation.org/show_bug.cgi?id=145355 --- Comment #2 from Tom Williams --- Thanks for the reply. Yes, I'm aware I can manually change the case of the text but I was looking for a way to do it automatically and conditionally. :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139503] No playing item in presentation mode (GDI)
https://bugs.documentfoundation.org/show_bug.cgi?id=139503 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu --- Comment #12 from Aron Budea --- Telesto, what are your GPU details? Ie. cache\opengl_device.log -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145355] EDITING: CellStyle should allow making text all UPPERCASE or all lowercase
https://bugs.documentfoundation.org/show_bug.cgi?id=145355 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from m.a.riosv --- What you are asking meaning change the cell content. Modify the format never carries a change on the content. I guess you know there is an option to Menu/Format/Text to do it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145353] Editing within a CALC Cell with wordwrap .. does not remove deleted characters from next line in the cell!
https://bugs.documentfoundation.org/show_bug.cgi?id=145353 V.S. Umamaheswaran changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 Assignee|libreoffice-b...@lists.free |bhanudo...@rogers.com |desktop.org | --- Comment #2 from V.S. Umamaheswaran --- Created attachment 175981 --> https://bugs.documentfoundation.org/attachment.cgi?id=175981=edit Contains screen captures showing the problem along with a Readme file. I have attached samples showing (what I think is a) Bug, as requested. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145340] Collabora Android 6.4.13
https://bugs.documentfoundation.org/show_bug.cgi?id=145340 Aron Budea changed: What|Removed |Added Resolution|--- |MOVED Status|UNCONFIRMED |RESOLVED CC||ba...@caesar.elte.hu --- Comment #2 from Aron Budea --- This issue should be fixed now by the following commit: https://github.com/CollaboraOnline/online/commit/c6e67fd7da95ffec0fc5cd2a3170c46f2bc52e41 The data loss is unfortunate, however there is an attempted fix for that as well (it wasn't consistently reproducible), please wait for the next update, or give the latest snapshot a try: https://www.collaboraoffice.com/downloads/Collabora-Office-Android-Snapshot/ If either issue persists, use the following URL to report issues related to the Collabora Office app: https://github.com/CollaboraOnline/online/issues/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122735] objects outside the selected group don't become pale
https://bugs.documentfoundation.org/show_bug.cgi?id=122735 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5359 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145359] Enter group: the other shapes are not dimmed & cannot add a other shape in the group
https://bugs.documentfoundation.org/show_bug.cgi?id=145359 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2735 --- Comment #2 from Regina Henschel --- Your bug reports two independent problems. The problem "are not dimmed" is already reported in bug 122735. So your report should focus on the problem "functionality to add an existing shape to a group is missing". Please change the summary accordingly. That would then be an enhancement request. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139162] Copy Paste in LibreOffice Online documents non-libre>libre and libre>libre (Collabora/Owncloud)
https://bugs.documentfoundation.org/show_bug.cgi?id=139162 Aron Budea changed: What|Removed |Added Whiteboard| QA:needsComment| CC||ba...@caesar.elte.hu Resolution|--- |MOVED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Aron Budea --- Please check again with a fresh CODE/Collabora Online version, if the issue still persists, open an issue at: https://github.com/CollaboraOnline/online/issues/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122735] objects outside the selected group don't become pale
https://bugs.documentfoundation.org/show_bug.cgi?id=122735 Regina Henschel changed: What|Removed |Added CC||alex.pyatt...@gmail.com --- Comment #6 from Regina Henschel --- *** Bug 136882 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 136882] Enter group does not have any visual feedback
https://bugs.documentfoundation.org/show_bug.cgi?id=136882 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from Regina Henschel --- The problem is already tracked in bug 122735. *** This bug has been marked as a duplicate of bug 122735 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134116] LibO Writer 6.4.4 crashes with serial correspondence
https://bugs.documentfoundation.org/show_bug.cgi?id=134116 Aron Budea changed: What|Removed |Added Alias|asdfgh | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144896] problem with SUMIF, SUBTOTAL and AUTO FILTER leaving trace numbers when total should be 0
https://bugs.documentfoundation.org/show_bug.cgi?id=144896 Michael Warner changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134116] LibO Writer 6.4.4 crashes with serial correspondence
https://bugs.documentfoundation.org/show_bug.cgi?id=134116 -- changed: What|Removed |Added Alias||asdfgh -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145370] New: spell checking initiated by F7 doesn't start where you'd expect, and endnotes are also checked
https://bugs.documentfoundation.org/show_bug.cgi?id=145370 Bug ID: 145370 Summary: spell checking initiated by F7 doesn't start where you'd expect, and endnotes are also checked Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@cspv.hu Description: hi, I've been using the appimage 7. for an hour only, and I like it, but when I press f7 to activate spell checking, what happens is not what I'd expect Steps to Reproduce: 1. press f7 2. 3. Actual Results: if I place the cursor at the beginning of the doc, it works okay.. but later on / deeper in the doc, when I press it while having the cursor on or before a word which I'd like to add to the dictionary, the checking doesn't start there... moreover, it goes to the endnotes, too! and when it is not the same language as the body text, every word will be underlined as "wrong" Expected Results: this has worked perfectly for long... I use 6.something, and works perfectly, and I can't remember when I last had a problem with getting a word checked... that is, getting the spell checking start where I wish... Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded - [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145369] lines and spaces occasionally inserted -- (doesn't happen in Writer 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=145369 --- Comment #1 from peter josvai --- Created attachment 175980 --> https://bugs.documentfoundation.org/attachment.cgi?id=175980=edit spaces and lines created by placing the cursor into the body of an empty document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145369] New: lines and spaces occasionally inserted -- (doesn't happen in Writer 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=145369 Bug ID: 145369 Summary: lines and spaces occasionally inserted -- (doesn't happen in Writer 7) Product: LibreOffice Version: 6.4.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@cspv.hu Description: this is a strange behavior.. I'm using version 6.4.7.6 so I downloaded the v7 app image, 7.2.0.4 and it works perfectly.. without this undesired behavior... I'm only reporting this because perhaps nobody has,and this might be helpful some day in the future if(ever) this should show up again :) Steps to Reproduce: 1. you have a document, with nothing typed in it yet 2. place your cursor somewhere, like, in line 15 3. Actual Results: to your surprise, you are able to do this... although nothing has been typed "that far"... you can place your cursor there... moreover, the spaces thus created, on the fly, will remain there... for real.. you can also place the cursor to a nearer spot, like line 5 instead of line 15, and the spaces will magically rearrange.. Expected Results: if you haven't typed, added characters / spaces to your doc, you shouldn't be able to place your cursor Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145368] Comment boxes in LibreOffice Writer are smaller than their text
https://bugs.documentfoundation.org/show_bug.cgi?id=145368 --- Comment #1 from Tohotom --- Created attachment 175979 --> https://bugs.documentfoundation.org/attachment.cgi?id=175979=edit Screenshot of tbe broken comment box -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145368] New: Comment boxes in LibreOffice Writer are smaller than their text
https://bugs.documentfoundation.org/show_bug.cgi?id=145368 Bug ID: 145368 Summary: Comment boxes in LibreOffice Writer are smaller than their text Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: megteheted_toho...@yahoo.com Description: Comment boxes in LibreOffice Writer are one line smaller than the the text entered in them. Boxes will resize with the text, but always cut/hide the last line. Steps to Reproduce: 1.Open LO Writer document 2.Insert comment 3.Enter text in comment box Actual Results: The last line will remain hidden. Expected Results: Last line should be visible. Reproducible: Always User Profile Reset: No Additional Info: Using Kubuntu 20.04, with LO 7.2.2 installed form fresh PPA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144158] MalwareBytes instantly and completely shuts down Libreoffice when clicking Tools / Options / Advanced
https://bugs.documentfoundation.org/show_bug.cgi?id=144158 --- Comment #14 from xordevore...@gmail.com --- Declare it not your bug if you want but it means I'm skipping using parts of LO affected by it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145367] MIN(SUM(), 333) is damaged on edit
https://bugs.documentfoundation.org/show_bug.cgi?id=145367 --- Comment #2 from Dave McKellar --- Created attachment 175978 --> https://bugs.documentfoundation.org/attachment.cgi?id=175978=edit Screenshot: The damanged formula in LibreOffice Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145367] MIN(SUM(), 333) is damaged on edit
https://bugs.documentfoundation.org/show_bug.cgi?id=145367 --- Comment #1 from Dave McKellar --- Created attachment 175977 --> https://bugs.documentfoundation.org/attachment.cgi?id=175977=edit Screenshot of a the RTF file in a text editor showing the codes. The field formula is highlighted -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145367] New: MIN(SUM(), 333) is damaged on edit
https://bugs.documentfoundation.org/show_bug.cgi?id=145367 Bug ID: 145367 Summary: MIN(SUM(),333) is damaged on edit Product: LibreOffice Version: 7.2.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmckel...@gmail.com Created attachment 175976 --> https://bugs.documentfoundation.org/attachment.cgi?id=175976=edit A RTF doc made with Microsoft Word - load this info LibreOffice Writer 1. Create a RTF document in Microsoft Word with field formula of MIN(SUM(),333) 2. Load that RTF into LibreOffice Writer 3. Right click on the field formula and select "Edit fields" and the value becomes incorrect and the formula has changed to MIN(SUM()|333) which is invalid syntax. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145357] SUM function does not calculate values
https://bugs.documentfoundation.org/show_bug.cgi?id=145357 Timur changed: What|Removed |Added Resolution|FIXED |NOTABUG --- Comment #11 from Timur --- https://bugs.documentfoundation.org/page.cgi?id=fields.html#bug_status -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145351] Please make the visual indicators of breaks more practical
https://bugs.documentfoundation.org/show_bug.cgi?id=145351 --- Comment #3 from phv --- I worry that too much information may overload the interface, especially when the information is following the text. I would prefer that the label only appears when the mouse hovers over the break mark. Today, no symbol clearly indicates that the break is a clickable element. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138347] Link to call Basic script with vnd.sun.star.script: not working in Writer. Same thing working in Calc (also with HYPERLINK()).
https://bugs.documentfoundation.org/show_bug.cgi?id=138347 --- Comment #5 from Wolfgang Jäger --- Created attachment 175975 --> https://bugs.documentfoundation.org/attachment.cgi?id=175975=edit Exemplifying relevant differences by three insetzed hyperlinks (In reply to Andreas Heinisch from comment #4) > I tried to investigate this error. Here are my findings: > > For both Calc and Writer the URL will be open in: > https://opengrok.libreoffice.org/xref/core/sfx2/source/appl/appopen. > cxx?r=5021a10f#1078 > > The only difference is that the target of the URL is "empty" for Calc and > "_blank" for Writer, ... > Imho, this is not a macro problem, but a problem in the target handling in > appopen.cxx and the supported protocols for the "_blank" target. I can't go the same ways, but would doubt the "... but a problem in the target handling..." as the only background. After all ordinary external links assigned to text portions in Writer are working as expected, and for a link made to call a script, I would expect the target frame irrelevant. A new example exemplifying differences I suppose to be part of the bug's backround is attached as "bug_tdf#138347_example2 . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145366] New: writer latency
https://bugs.documentfoundation.org/show_bug.cgi?id=145366 Bug ID: 145366 Summary: writer latency Product: LibreOffice Version: 7.2.1.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jon.nico...@wanadoo.fr Description: When I use libreoffice writer on windows 11 I have latency in typing and with the mouse. Steps to Reproduce: I am using Windows 11 21H2. I am having a latency problem with libreoffice 7.2.2. I am using writer in normal mode, what I type and when I click in different places there is a delay. If I restart the application in safe mode without disabling or other settings the problem goes away. How to fix the problem? Thank you Actual Results: I disabled OpenGL as indicated in your solution but identical result. Expected Results: Problem still present Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: The software should work without latency like when I start it in safe mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145365] Calc UI scrolls sheet tabs after renaming a tab
https://bugs.documentfoundation.org/show_bug.cgi?id=145365 sarp...@aol.com changed: What|Removed |Added Summary|Calc UI scrolls sheet tabs |Calc UI scrolls sheet tabs |after renaming one |after renaming a tab -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145365] New: Calc UI scrolls sheet tabs after renaming one
https://bugs.documentfoundation.org/show_bug.cgi?id=145365 Bug ID: 145365 Summary: Calc UI scrolls sheet tabs after renaming one Product: LibreOffice Version: 7.2.0.4 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sarp...@aol.com Description: I create a bunch of empty tabs, and start renaming them to the appropriate names. So I scroll the first unnamed one to the left, so I can see which names I've done as I work across the page and through the tabs. I hope. But when I rename one, Calc scrolls my view so that the newly renamed tab is all the way to the right, and I can't see the next one needing renaming. It's possible this is regarded as desired behavior for some. For me there are two problems. The first is that it moves something I'm working on, without my permission or command, and requires me to quit working and scroll my work back to where I put it. I have scroll bars to move the tabs with. There's no need for the software to move them in this situation. The second is that not only does it move my work, it actively hides it from me, in a way that I can't really picture a use for. It would be one thing if this were an incomplete feature, but this behavior seems intentional. Is it possible there's an option to turn this behavior off that I haven't found? Steps to Reproduce: 1. Create enough new tabs to overflow the tab bar. 2. Rename enough tabs to overflow tab bar 3. Scroll the first default-named tab to the left 4. Select and rename the first default-named tab Actual Results: After step 4, the renamed tab moves all the way to the right, if there are enough tabs before it, and the next tab after it is scrolled partially or completely off the screen. Tabs renamed in the middle of the screen seem to move around more or less at random, sometimes depending on the length of the previous name. Expected Results: After step 4, the tabs stay scrolled where I left them, unless there is some other reason to move them. But even if my new name is too long to display, I'd still expect the tabs to remain where I had left them. i.e. if the newly renamed tab is in the visible portion of the tab bar, don't scroll the tabs at all. If the new name is too long for the visible portion, I'd still prefer that the beginning stay visible (i.e. no scrolling) than scrolling to the end of the name, or to the next tab. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145351] Please make the visual indicators of breaks more practical
https://bugs.documentfoundation.org/show_bug.cgi?id=145351 --- Comment #2 from Adriano --- Yes, when formatting marks are enabled, the user should see clear marks for all break types at the place of the break and should easily identify the break type from those marks. This will make breaks easier to work with, including deleting them. Implementing this will improve the work with text in Writer. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145364] New: calc problem with header
https://bugs.documentfoundation.org/show_bug.cgi?id=145364 Bug ID: 145364 Summary: calc problem with header Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: paolo...@gmail.com Description: chiedo scusa ma non parlo inglese. Riporto la traduzione con google. Versione calc 7.2.2.2 su Kubuntu 18.04 non è possibile inserire testo nell'intestazione "area a sinistra". E' come se nonm fosse attiva I apologize but I don't speak English. I report the translation with google. Calc version 7.2.2.2 on Kubuntu 18.04 it is not possible to insert text in the "left area" header. It is as if nonm were active Actual Results: formato stile di pagina intestazione attiva riga di intestazione modifica area a sinistra (non attiva!) Expected Results: non è possibile scrivere nell'area a sinistra Reproducible: Always User Profile Reset: No Additional Info: permettere di scrivere -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118734] FILEOPEN: Only one bookmark displayed in navigator instead of 2
https://bugs.documentfoundation.org/show_bug.cgi?id=118734 --- Comment #8 from Dave Lovelace --- I tested this again, as requested. If the comment starts at the same point as the bookmark, the comment still vanishes. However, IF the bookmark was INSIDE the selected text that the comment applies to, then the bookmark remains. Am I really the only one who uses both bookmarks and comments a lot? It's really hard for me to believe that fixing this has such low priority. For me, it's a MAJOR pain. I need to be able to comment on things in my text, and also to bookmark places so I can find them (and see them in sequence). Version info: Version: 7.1.6.2 (x64) / LibreOffice Community Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL (There are many more deficiencies with bookmarks, some of which other people have certainly complained about, BTW. Whoever implemented them must not be someone who actually uses them.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145351] Please make the visual indicators of breaks more practical
https://bugs.documentfoundation.org/show_bug.cgi?id=145351 --- Comment #1 from Tomaz Vajngerl --- I agree - the break aren't that easy to spot how we currently implement them. Maybe we don't need to change the dotted line for the page/column break - just add an additional break marker at the place of the break when formatting marks are enabled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145363] KDE Plasma: Enters loop when editing bullet style
https://bugs.documentfoundation.org/show_bug.cgi?id=145363 David changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from David --- 7.x, 6.x, 7.3 alpha. Appimages earlier than 6.x work, but the issue may have only began though after upgrading to latest Debian Stable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144625] Regression: a macro stopped working with upgrade of LO.
https://bugs.documentfoundation.org/show_bug.cgi?id=144625 --- Comment #7 from Michael Warner --- You will need to reduce your test case down to the smallest possible thing that demonstrates the issue. It can't be reliant on the existence of other paths or system configuration that doesn't contribute to testing this specific issue at hand. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145357] SUM function does not calculate values
https://bugs.documentfoundation.org/show_bug.cgi?id=145357 Leon changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Leon --- (In reply to Regina Henschel from comment #9) > If you use View > Value Highlighting, then text is black, numbers are blue > and formulas are green. In that mode you see, that cell content in E3:E10 > and G3:G10 is text. > > Changes in cell format on existing content cannot be used for changes > between data type text and data type number. > > To change existing 'text with decimal point' to 'number with comma > separator', you can do these steps: > 1. cut the text to clipboard > 2. Format the (still marked) cells to "General". That is in Format > Cells > > Tab numbers. Make sure the field 'language' in that tab is correct. > 3. (cells still marked) Use the item "Unformated text (TSV-Calc)" from the > drop-down list of the 'Paste' button in the toolbar. You get the "Text > Import" dialog. > 4. In that dialog click on column header (shows "Standard" as default) in > the section 'Fields' and then select item "US English" in field 'Column > type'. OK. > > To change the display of the formula result in cell E11 to "number with > comma separator", go to Format > Cell > Tab numbers. Change the language to > -in your case- "English (South Africa)". > > Do all your tries on a copy of the document! > > For more assistance in formatting and data type handling in Calc please use > user mailing list or Ask. > > For me this is not a bug. thanks. I basically simply do a mass replace of period to comma. I am unable to find the place where it is set as a dot. It did not used to exhibit this behaviour so I am not sure where this chnaged in the locale settings. Will close because it basically is a formatting issue where commas must be used, and not periods as decimal separator. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145357] SUM function does not calculate values
https://bugs.documentfoundation.org/show_bug.cgi?id=145357 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #9 from Regina Henschel --- If you use View > Value Highlighting, then text is black, numbers are blue and formulas are green. In that mode you see, that cell content in E3:E10 and G3:G10 is text. Changes in cell format on existing content cannot be used for changes between data type text and data type number. To change existing 'text with decimal point' to 'number with comma separator', you can do these steps: 1. cut the text to clipboard 2. Format the (still marked) cells to "General". That is in Format > Cells > Tab numbers. Make sure the field 'language' in that tab is correct. 3. (cells still marked) Use the item "Unformated text (TSV-Calc)" from the drop-down list of the 'Paste' button in the toolbar. You get the "Text Import" dialog. 4. In that dialog click on column header (shows "Standard" as default) in the section 'Fields' and then select item "US English" in field 'Column type'. OK. To change the display of the formula result in cell E11 to "number with comma separator", go to Format > Cell > Tab numbers. Change the language to -in your case- "English (South Africa)". Do all your tries on a copy of the document! For more assistance in formatting and data type handling in Calc please use user mailing list or Ask. For me this is not a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145285] Cannot export: Exporting Drawing Crashes EVERY time on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=145285 steve changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #11 from steve --- No trouble exporting with 7.3 nightly build. Retested 7.2.2.2 with sample file: - open Export crashes trying to export the 3rd page as JPEG - select page 3 - select file > export - switch `File type` to jpeg and press enter to save - confirm default export options no trouble at all, jpg exported as expected. Do you have access to a second mac at a friends or neighbours? Would be curious if it works there, but it does not seem to be a general problem in LibreOffice or your file, as export here works fine in both versions of LO. So it is something profile or machine specific with your setup. Lets wait how the nightly behaves for you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145363] KDE Plasma: Enters loop when editing bullet style
https://bugs.documentfoundation.org/show_bug.cgi?id=145363 BogdanB 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 145363] KDE Plasma: Enters loop when editing bullet style
https://bugs.documentfoundation.org/show_bug.cgi?id=145363 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #2 from BogdanB --- What version of LibreOffice? Go to Help - About -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144625] Regression: a macro stopped working with upgrade of LO.
https://bugs.documentfoundation.org/show_bug.cgi?id=144625 --- Comment #6 from Aaron Gerber --- What does a person have to do to get their bug confirmed? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 --- Comment #16 from Buovjaga --- (In reply to Alex Thurgood from comment #15) > No repro for me already with : > > Version: 7.2.1.2 / LibreOffice Community > Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 > CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR > Calc: threaded Then it must be some other fix than bug 144564 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 --- Comment #15 from Alex Thurgood --- No repro for me already with : Version: 7.2.1.2 / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145354] Wrong slide to page layout in Print dialog preview
https://bugs.documentfoundation.org/show_bug.cgi?id=145354 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=99 ||183 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99183] Changing slide orientation in print options not OK in virtual printers (per comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=99183 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5354 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145357] SUM function does not calculate values
https://bugs.documentfoundation.org/show_bug.cgi?id=145357 --- Comment #8 from Leon --- PS. I also tried changing the decimal separator key, but thus far it did not have an effect on the outcome. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145361] Cannot convert to XHTML document containing list with line break
https://bugs.documentfoundation.org/show_bug.cgi?id=145361 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org Keywords||bibisected, bisected, ||regression --- Comment #4 from Xisco Faulí --- Reproduced in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 97583efeb2e2d21b501b52ba6be2442e955bdec3 CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded marking as regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 Xisco Faulí changed: What|Removed |Added CC||l...@ptoye.com --- Comment #14 from Xisco Faulí --- *** Bug 145362 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 145362] Crash in: WinSalFrame::SetPointer(PointerStyle)
https://bugs.documentfoundation.org/show_bug.cgi?id=145362 Xisco Faulí changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #5 from Xisco Faulí --- anyway, it seems a duplicate of bug 144072 *** This bug has been marked as a duplicate of bug 144072 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 --- Comment #13 from Buovjaga --- No crash for me at least, hopefully others can verify as well Arch Linux 64-bit Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 6678b8123c9952c80a637d3a7f4e27511122009e CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 27 October 2021 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145354] Wrong slide to page layout in Print dialog preview
https://bugs.documentfoundation.org/show_bug.cgi?id=145354 --- Comment #4 from Telesto --- The same issue as reported here - as dedicated report - is actually also mentioned in: bug 99183 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145354] Wrong slide to page layout in Print dialog preview
https://bugs.documentfoundation.org/show_bug.cgi?id=145354 Telesto changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Telesto --- Repro Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 93115d2c54d645bcf2f80fde325e3ede39dee4d5 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145362] Crash in: WinSalFrame::SetPointer(PointerStyle)
https://bugs.documentfoundation.org/show_bug.cgi?id=145362 Peter Toye changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145362] Crash in: WinSalFrame::SetPointer(PointerStyle)
https://bugs.documentfoundation.org/show_bug.cgi?id=145362 --- Comment #4 from Peter Toye --- I don't have a copy of version 7.2.2 - and I'm under the impression that if I install it, it's then difficult to get back to the 7.1.6 stable version. Is that still true? The other issue is that I have no idea exactly what I did to cause the crash. I was editing a report in the Report Builder (which seems to have a lot of bugs) when suddenly it died. So even trying to reproduce it isn't going to be possible. Very sorry. I realise that this isn't much help (I was a programmer for too many years...) but can't see how I could reproduce the crash on version 7.1.4, let alone 7.2.2. If you've any ideas, I'd like to hear them and will try to help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 Xisco Faulí changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #12 from Xisco Faulí --- Hi all, I'm wondering whether it was fixed by the fix for bug 144564. Could you please try again with LibreOffice 7.2.2.2? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145362] Crash in: WinSalFrame::SetPointer(PointerStyle)
https://bugs.documentfoundation.org/show_bug.cgi?id=145362 Xisco Faulí changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #3 from Xisco Faulí --- I'm wondering whether it was fixed by the fix for bug 144564. Could you please try again with LibreOffice 7.2.2.2? -- You are receiving this mail because: You are the assignee for the bug.
