[Libreoffice-bugs] [Bug 120663] No impress remote: Impress incompatible with current bluetooth stack on linux (RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use)
https://bugs.documentfoundation.org/show_bug.cgi?id=120663 --- Comment #18 from Callegar --- Noticed that in the forthcoming LibO 24.2, the "remote" is being given prominence, by moving its settings from the Tools ▸ Options ▸ LibreOffice Impress configuration dialog to the Slide Show ▸ Slide Show Settings menu. IMHO this makes it quite important to have this feature working as intended on all the supported platforms. The remote is meant to work either with a WIFI connection or a Bluetooth one. The current bug is about the Bluetooth connection. Bluetooth Connection As of today, because of the issue at hand, the Bluetooth connection is completely unusable on standard Linux distributions that use Pulseaudio (a detailed discussion why is in the previous comments). Notwithstanding the fact that this but is about the Bluetooth connection, I am providing also a few notes about the Wifi connection to highlight why the Bluetooth connection is so important and should be fixed. WIFI Connection --- Unfortunately, the WIFI option is practically unusable in almost every professional working environment, including universities and conferencing sites. This is because in all these environments the network is completely out of the user control, restricted in any possible way, heavily firewalled, with the wifi framework consisting of multiple access points under the same SSID. In a similar arrangement the possibility of the remote to reach LibO at a non-standard TCP port is erratic if not negligible. The impossibility to use the WIFI connection precisely in those real world environments where the usage of the remote would be most important is the reason why a working Bluetooth connection is needed. Note that in practice the WIFI connection situation could be improved by suggesting the possibility to let the presenter laptop connect to the internet via the mobile phone hotspot. This would need the remote app to try to connect to LibO not just via the phone default interface, but also on the network used for the hotspot. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 --- Comment #5 from Andras Horvath --- Why has this been changed to unconfirmed? You can freely reproduce the bug on a new OS with a fresh snap install. Thx, Andras -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158182] New: Italic formatted text not showing in footnotes in epub format
https://bugs.documentfoundation.org/show_bug.cgi?id=158182 Bug ID: 158182 Summary: Italic formatted text not showing in footnotes in epub format Product: LibreOffice Version: 7.5.7.1 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: peteedwardsph...@gmail.com Description: When I include italic formatted text in footnotes in Writer and export to epub, the text in the footnote is visible but not italic. I am viewing the epub document in Apple Books application. Steps to Reproduce: 1.Create Writer document with a footnote that includes italic formatted text. 2.Export document to epub format. 3.View epub document to see if footnote text includes italic formatting. Actual Results: Footnote text appears in epub document viewed in Apple Books app, but footnote text that was italic in the original Writer document appears as regular text in the epub document. Expected Results: Footnote text to appear as italic in the epub document, just like in the original Writer document. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 4; OS: Mac OS X 11.6; UI render: default; VCL: osx Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158181] (LibreOffice Math) black text in dark background (dark theme) makes text "invisible" in formula editor
https://bugs.documentfoundation.org/show_bug.cgi?id=158181 --- Comment #1 from george --- Created attachment 190793 --> https://bugs.documentfoundation.org/attachment.cgi?id=190793=edit libre math dark text in dark background -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158181] New: (LibreOffice Math) black text in dark background (dark theme) makes text "invisible" in formula editor
https://bugs.documentfoundation.org/show_bug.cgi?id=158181 Bug ID: 158181 Summary: (LibreOffice Math) black text in dark background (dark theme) makes text "invisible" in formula editor Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gd...@yahoo.com Description: While all the UI elemenets in dark theme are white (libre Math, in the formula editor the text is black and the background dark grey. It is very difficult to properly read and type the text there. There is no way to change this attribute in the UI. Steps to Reproduce: 1. insert a formula object in libre writer 2. libre math opens 3. try to type a formula in the editor Actual Results: the text in formula editor (dark theme) is extremeleu difficult to read because it is black in dark background Expected Results: text should be white or something similar, similar to other UI elements for dark theme Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 16; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: el-GR (en_US.UTF-8); UI: en-US Ubuntu package version: 4:7.6.2~rc1-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158160] Libre Writer does not remember default language for documents
https://bugs.documentfoundation.org/show_bug.cgi?id=158160 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158069] Scroll through font selection listbox using arrow keys and preview change on document canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=158069 --- Comment #14 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154534] Can't view the Main menu bar, while choosing the sub design menu.
https://bugs.documentfoundation.org/show_bug.cgi?id=154534 --- Comment #3 from QA Administrators --- Dear Priyanka, 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 97391] [META] OpenCL and "Software Interpreter" issues in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=97391 Bug 97391 depends on bug 154533, which changed state. Bug 154533 Summary: OpenCL: Libreoffice wont start / crash with OpenCL enabled if you have multiple GPUs (Intel+Nvidia) and have dGPU disabled https://bugs.documentfoundation.org/show_bug.cgi?id=154533 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157935] After installation of 7.6.2, first form opening of .odb file freezes LO
https://bugs.documentfoundation.org/show_bug.cgi?id=157935 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 154533, which changed state. Bug 154533 Summary: OpenCL: Libreoffice wont start / crash with OpenCL enabled if you have multiple GPUs (Intel+Nvidia) and have dGPU disabled https://bugs.documentfoundation.org/show_bug.cgi?id=154533 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154533] OpenCL: Libreoffice wont start / crash with OpenCL enabled if you have multiple GPUs (Intel+Nvidia) and have dGPU disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=154533 --- Comment #19 from QA Administrators --- Dear makedir, 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 154497] object clicked and dragged by cursor. cursor visibility size very very small on the drawing page
https://bugs.documentfoundation.org/show_bug.cgi?id=154497 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 154533] OpenCL: Libreoffice wont start / crash with OpenCL enabled if you have multiple GPUs (Intel+Nvidia) and have dGPU disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=154533 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 154497] object clicked and dragged by cursor. cursor visibility size very very small on the drawing page
https://bugs.documentfoundation.org/show_bug.cgi?id=154497 --- Comment #4 from QA Administrators --- Dear Saravanakumar, 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 154436] Drag the outer circle in the circle diagram at Libre office impress-text is going outside of the circle
https://bugs.documentfoundation.org/show_bug.cgi?id=154436 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 154467] Select and right click pop window not showing the delete option.
https://bugs.documentfoundation.org/show_bug.cgi?id=154467 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 154467] Select and right click pop window not showing the delete option.
https://bugs.documentfoundation.org/show_bug.cgi?id=154467 --- Comment #3 from QA Administrators --- Dear Lajeem shah, 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 154436] Drag the outer circle in the circle diagram at Libre office impress-text is going outside of the circle
https://bugs.documentfoundation.org/show_bug.cgi?id=154436 --- Comment #4 from QA Administrators --- Dear Sangeetha, 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 154755] [META] Thunderbird interoperability and integration
https://bugs.documentfoundation.org/show_bug.cgi?id=154755 Bug 154755 depends on bug 153911, which changed state. Bug 153911 Summary: Warning when opening files with other files already open https://bugs.documentfoundation.org/show_bug.cgi?id=153911 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153911] Warning when opening files with other files already open
https://bugs.documentfoundation.org/show_bug.cgi?id=153911 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 153911] Warning when opening files with other files already open
https://bugs.documentfoundation.org/show_bug.cgi?id=153911 --- Comment #11 from QA Administrators --- Dear Nadie Nada Nunca, 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 89130] UI: Better UX for handling layer visibility and locking in the layer bar
https://bugs.documentfoundation.org/show_bug.cgi?id=89130 --- Comment #23 from QA Administrators --- Dear Rodolfo, 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 155302] Table reformatting causes font colour switches or reversions
https://bugs.documentfoundation.org/show_bug.cgi?id=155302 --- Comment #3 from QA Administrators --- Dear glibguide, 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 155331] RTF sections (/sect control word) are not on new pages, which is the default
https://bugs.documentfoundation.org/show_bug.cgi?id=155331 --- Comment #2 from QA Administrators --- Dear coldenjohanson, 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 155224] Libreoffice Writer Freezes and Crashes with multiple windows open and languageTool extension installed
https://bugs.documentfoundation.org/show_bug.cgi?id=155224 --- Comment #11 from QA Administrators --- Dear agapp11, 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 155119] NOTEBOOKBAR: Text format selection is garbled with Hebrew UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155119 --- Comment #5 from QA Administrators --- Dear sh.ya...@gmail.com, 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 155181] clicking anywhere in text area corrupts the line instead of putting the cursor in place
https://bugs.documentfoundation.org/show_bug.cgi?id=155181 --- Comment #2 from QA Administrators --- Dear alignedtraining, 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 98435] dBase accepts invalid column name in select list
https://bugs.documentfoundation.org/show_bug.cgi?id=98435 --- Comment #10 from QA Administrators --- Dear Terrence Enger, 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 126345] Underlining of links is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=126345 --- Comment #9 from QA Administrators --- Dear Matthew Kogan, 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 34850] incorrect positioning when dragging newly-created frame (editing formatting ui)
https://bugs.documentfoundation.org/show_bug.cgi?id=34850 --- Comment #16 from QA Administrators --- Dear Lawrence D'Oliveiro, 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 138225] Menu shortcuts using ALT always use the default keyboard layout, not the selected layout
https://bugs.documentfoundation.org/show_bug.cgi?id=138225 --- Comment #2 from QA Administrators --- Dear harrisonhopkins, 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 139142] Directly applied font is reset from Input List field after saving to DOCX and reloading
https://bugs.documentfoundation.org/show_bug.cgi?id=139142 --- Comment #4 from QA Administrators --- Dear Mike Kaganski, 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 137230] Save a file to network storage trashes the content
https://bugs.documentfoundation.org/show_bug.cgi?id=137230 --- Comment #8 from QA Administrators --- Dear Uwe Altmann, 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 138769] FILEOPEN DOCX WordArt replacement image has incorrect height
https://bugs.documentfoundation.org/show_bug.cgi?id=138769 --- Comment #4 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128713] missing grid pixels ...
https://bugs.documentfoundation.org/show_bug.cgi?id=128713 --- Comment #3 from QA Administrators --- Dear Michael Meeks, 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 107653] LO saves changes after you decline to save upon exiting Relation Design window
https://bugs.documentfoundation.org/show_bug.cgi?id=107653 --- Comment #10 from QA Administrators --- Dear Terrence Enger, 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 158069] Scroll through font selection listbox using arrow keys and preview change on document canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=158069 --- Comment #13 from Bob English --- (In reply to Jean-Francois Nifenecker from comment #12) > In the side bar, select the styles pane... > > This is exactly what you're asking for, IMO. No it's not at all what I want, that method involves even more steps, and the view of the font in the display is too small, and can't be resized. I believe the intended use for the styles pane is much finer control, with the intention on also applying it to the style and anything already using it, not just a single word, line of text... selection, and even saving the style for later use, which you may have no need to do. What I would like, and cannot see why others wouldn't rather have too: 1. Select text in the document; Doesn't have to be a whole paragraph, can be more than one paragraph, and more than one style. 2. Click in the font dropdown in the toolbar: It's always there and out of the way, and It's best use is for quick changes and instant results of very common things one changes, not fine control and a plethora of options. 3. Scroll the mouse wheel or use the up/down arrow keys, and watch the font of the selected text change in the document itself (the font names in the dropdown do not need to be the selected font, but all the same as the rest of the interface). May I even suggest it to also suspend the graphical highlight of the text until the choice is made, so you get the full effect of what it will look like in context if and when applied. Once applied the text Highlight in the document is turned back on for reference and show it's still active to be changed, and until the text is deselected. 4. Only on command should the dropdown lose focus. The commands should be as easy as clicking in any other control to focus it, or in the document window where you want the cursor. Pressing [Enter] also applies it and places the cursor in the document window, just where it was before you changed the font. [Tab] should indeed advance to the next control in the toolbar, because you are already adjusting the font, and it's size and what not matter too, so it's a good feature. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158180] New: T function requires a description When the ERROR Value is an argument
https://bugs.documentfoundation.org/show_bug.cgi?id=158180 Bug ID: 158180 Summary: T function requires a description When the ERROR Value is an argument Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tac...@hotmail.co.jp CC: olivier.hal...@libreoffice.org Description: T function requires a description When the ERROR Value is an argument Steps to Reproduce: 1. Open New Calc 2. Input Cell [ A1 ] "=T(NA())" 3. #N/A 4. Read T Functiuon Help : https://help.libreoffice.org/latest/en-US/text/scalc/01/04060110.html?#t Actual Results: 5. This function returns the target text, or a blank text string if the target is not text. Expected Results: 5. Like the n function, it is necessary to describe the error value is an argument.
[Libreoffice-bugs] [Bug 158139] Writer, Word Completion does not function
https://bugs.documentfoundation.org/show_bug.cgi?id=158139 RGB changed: What|Removed |Added Ever confirmed|0 |1 CC||rgb.m...@gmail.com Status|UNCONFIRMED |NEEDINFO --- Comment #1 from RGB --- Writer does not keep a list of words, it uses the words it finds in open documents, and only if they are of a minimal length (by default, 8 characters). If you only have an empty document, there will be no word completion suggestion because there are no words to use. The system only works if there is text available, either in the current document or in other documents opened at the same time. Can you check if the system works when text is available (and when that text contains long words)? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158175] FILEOPEN does not initialize some formulas/cells correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=158175 --- Comment #1 from nmatravol...@clarabot.com --- Quick update: I've managed to acquire the original MS Office XLSX and I've determined that the original cause of the issue is fixed by "tdf#142905 XLSX import: don't trim leading spaces in formula cell" (7ec4c6df) in the 7.6 branch. The attached file was imported with LibreOffice 7.5, so the XLSX import broke the document in a way that is not fixed automatically at open even in 7.6. This issue can be seen as separate from tdf#142905 to handle such cases, or be closed as a duplicate of tdf#142905 if there is no chance of having a document being fixed at open after it got broken. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158069] Scroll through font selection listbox using arrow keys and preview change on document canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=158069 --- Comment #12 from Jean-Francois Nifenecker --- In the side bar, select the styles pane. There, choose the Paragraph styles category (top toolbar, 1st toolbutton on the left). The current paragraph style is pre-selected, right click it, and select 'Edit'. A new dialogue opens, allowing to change any setting in that paragraph style. Go to the 'Font' tab. There, select a font of interest in the fonts list, then click the 'Apply' button. You see the change immediately applied in the background. This is exactly what you're asking for, IMO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158167] Calc: cannot move selected row (recent 24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=158167 --- Comment #4 from BogdanB --- I build LibreOffice with latest updates from master, and no problem with Calc. Are my steps wrong? (see comment 2) Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 64ccc089c1e6bf82ef10a0dd4768fdff83af55b5 CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158179] New: Layer tab popup menu in Draw shows layer visibility setting of previous selected tab
https://bugs.documentfoundation.org/show_bug.cgi?id=158179 Bug ID: 158179 Summary: Layer tab popup menu in Draw shows layer visibility setting of previous selected tab Product: LibreOffice Version: 7.6.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rayk...@gmail.com Created attachment 190792 --> https://bugs.documentfoundation.org/attachment.cgi?id=190792=edit file for use to repro bug Steps to repro this bug: 1. Open the attached Draw file. 2. Right-click on the Layer5 blue colored text tab. Results: Show Layer (Shift+Click) menu item is checked. Expected Results: Show Layer menu item is not checked because it is set not visible (indicated by the tabs blue text color). 3. With the popup menu still showing, right-click on the Layer4 tab. Results: Popup menu closes as expected. 4. Right-click again on the Layer4 tab. Results: Show Layer menu item is not checked. Expected Results: Show Layer menu item is checked because it is set visible. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e70f5d3db3ad64c3d6a21de998b238bd5d4ac8b5 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded The cause seems to be an issue with how the layer switch command is dispatched in void LayerTabBar::Select()[1]. Changing the dispatcher execute call mode parameter argument from SfxCallMode::ASYNCHRON to SfxCallMode::SYNCHRON produces expected Show Layer menu item results for me. Including Heiko who did the work for enhancement bug 113439 that added the Show Layer menu item. [1] https://opengrok.libreoffice.org/xref/core/sd/source/ui/dlg/LayerTabBar.cxx?r=9b9159aa#137 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158069] Scroll through font selection listbox using arrow keys and preview change on document canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=158069 --- Comment #11 from Bob English --- (In reply to Jean-Francois Nifenecker from comment #10) > Hi, > > here's a suggestion. > > The style edition dialogue might be of great use here. Of course, you're > using styles, aren't you? > > In the (paragraph or character) style edition dialogue (right click on the > style name > Edit), you go to the 'Font' tab. There you may pick any font of > your liking, then click 'Apply'. This updates the text accordingly and you > may check the document changes in the background (note that as the dialogue > is modal, you can't move in the background). If the change doesn't satisfy > you, you pick the formerly selected font and get back. > > Et voilà ;-) You mean in the side bar Styles>Character which should be Styles>Font, for consistency, and well a character isn't a whole font: It does the exact same thing as the font selection dropdown in the toolbar, so no it doesn't change anything but show that both are equally cumbersome, counter productive, and not truly WYSIWYG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131085] SVG cross-hatch pattern appears with spurious mosaic of squares
https://bugs.documentfoundation.org/show_bug.cgi?id=131085 --- Comment #13 from Daniel Neville --- Prompted by the e-mail notice of a version 7.6.2 of LibreOffice to try, I installed that and found the hatch rendering bug persists. (Stéphane Guillou’s super-minimalistic, defs-free test SVG also reveals the bug.) The version information copied from Libre Writer: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-NZ (en_AU.UTF-8); UI: en-US Calc: threaded System: Ubuntu 22.04 LTS on a NUC7i5BNH. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158044] RTF import paragraph style attribute handling wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=158044 Commit Notification changed: What|Removed |Added Whiteboard|target:24.2.0 |target:24.2.0 target:7.6.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158069] Scroll through font selection listbox using arrow keys and preview change on document canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=158069 --- Comment #10 from Jean-Francois Nifenecker --- Hi, here's a suggestion. The style edition dialogue might be of great use here. Of course, you're using styles, aren't you? In the (paragraph or character) style edition dialogue (right click on the style name > Edit), you go to the 'Font' tab. There you may pick any font of your liking, then click 'Apply'. This updates the text accordingly and you may check the document changes in the background (note that as the dialogue is modal, you can't move in the background). If the change doesn't satisfy you, you pick the formerly selected font and get back. Et voilà ;-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154456] TABLE: can't change border settings without also resetting the padding of every cell
https://bugs.documentfoundation.org/show_bug.cgi?id=154456 --- Comment #5 from Szczepan Hołyszewski --- * I confirm that the bug persist in the current version (7.6.2.1). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154456] TABLE: can't change border settings without also resetting the padding of every cell
https://bugs.documentfoundation.org/show_bug.cgi?id=154456 Szczepan Hołyszewski changed: What|Removed |Added Resolution|INSUFFICIENTDATA|--- Ever confirmed|1 |0 Status|RESOLVED|UNCONFIRMED --- Comment #4 from Szczepan Hołyszewski --- Steps to reproduce have been provided by user Dieter in comment #1 back in April, and at that exact moment the "data" became "sufficient". This bug was closed in error. I confirm that the issue persists in the current version (). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158069] Scroll through font selection listbox using arrow keys and preview change on document canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=158069 --- Comment #9 from Bob English --- Sorry for taking this long. Being a user not a developer, there's some stuff in here I don't understand, but this I do: (In reply to V Stuart Foote from comment #7) > Our Design Guideline > > Actions -- > > When the dropdown/combobox is on toolbars or sidebar, changes should not > become effective until the user leaves the control or collapses the open > widget. > > In particular, hoovering over the expanded dropdown or wheeling respectively > navigating with arrow keys the closed control should not apply the selection > on-the-fly. The change is made effective with tab and enter only. Well, it's right, and how it seems to work, but it still makes no sense nor can I see what purpose it serves to work that way. Following it, I first have to select a font in the dropdown which I can both with the up/down arrows, and wheel (So far so good), which works kike this: The combobox font changes, but the highlighted text does not change, so I cannot see my selection applied: Who needs to change the font in the list, but not in their document? What possible purpose does that serve? Even if once applied, you don't like your changes, the undo [Crtrl]+[Z] will fix it right quick. I still have to click, hit [Tab] or [Enter] on a font in the list to apply it, and as soon as I do, the focus is back in the text for click and [Enter], but for [Tab] it moves focuses to the right onto the font size dropdown. Now to see the next font I cannot just continue scrolling, I have to click in the box again, or in the case of having used [Tab] I will be changing the size, again only in the list. Livable if you only have like 10 fonts to choose from, but most of us have a whole lot more. Applying any change via click or [Enter] should not take the focus off of the the control and put it back onto the last cursor position in the document. For tab to move to the next control, does make sense as the next logical step, albeit you still see no changes to the selected text on scrolling until you click or hit [Enter] or [Tab]. All in all, needing to go through all that (Add that I have hundreds of fonts) just to see how font changes will look, exactly where you want to see them (in the actual document) is not in the true spirit of WYSIWYG! What I see change in a control selection I want to get on the selected text! I can scroll through the list and read pretty font names all day without even having anything selected in the document, but if I select something then of course I am doing so in order to do something with or to the selection. Guidelines are great, but only if they serve a real purpose and make sense, and as a user I really don't care what all they do for the developers, if it gives me the user no benefit. I care but what it means to me as to functionality and my workflow, and for that it is counter productive by adding a few unnecessary steps, and compounds them when you want to try many fonts to see which looks best. Seeing only the font name in it's appearance in that list is not sufficient to imagine it in the document itself, and to what is selected: I Want to see what I will get; WYSIWYG, and that totally makes sense, and is of course most likely why GIMP, Inkscape, and most, if not all programs that have selection controls do apply selections within scrolling through them in real time. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158178] New: FILESAVE ODP: Writes wrong start coordinates in svg:d attribute of a connector shape
https://bugs.documentfoundation.org/show_bug.cgi?id=158178 Bug ID: 158178 Summary: FILESAVE ODP: Writes wrong start coordinates in svg:d attribute of a connector shape Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 190791 --> https://bugs.documentfoundation.org/attachment.cgi?id=190791=edit Comparison of curved connector with Bézier curve The attached file has a connector between the two rectangles. This connector was copied and converted to a Bézier curve. Connector and Bézier curve should produce the same svg:viewBox and svg:d attributes in file markup (besides +- rounding differences). But you get for the connector: svg:d="M7000 7000c0-3001 8000-5501 8000 5000" svg:viewBox="0 0 8001 7609" and for the Bézier curve: svg:viewBox="0 0 8000 7608" svg:d="M0 2608c0-3001 8000-5501 8000 5000" The coordinates (0|2608] in the M command of the Bézier curve are correct, the coordinates (7000|7000) in the M command of the connector curve are wrong. Currently it has no large consequences, because LibreOffice recreates the connector curve from the connection points ins svg:x1, svg:y1, svg:x2 and svg:y2. But it will become a problem, if we start to use the svg:d attribute to decide whether the curve form was created to be compatible with the OOXML definitions or follow the LO way. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158158] Saving redline text in doc and docx format
https://bugs.documentfoundation.org/show_bug.cgi?id=158158 raal changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||r...@post.cz Keywords||filter:docx --- Comment #1 from raal --- I can confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 41d9584179ef7b4e18eda47c2c0a955df8c087a5 CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded *** This bug has been marked as a duplicate of bug 147655 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147655] Writer loses some tracked changes when saving as .docx with Deletions/Insertions in Margin
https://bugs.documentfoundation.org/show_bug.cgi?id=147655 raal changed: What|Removed |Added CC||aleksandr.m...@gmail.com --- Comment #9 from raal --- *** Bug 158158 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 158176] Input data is not shown but counted
https://bugs.documentfoundation.org/show_bug.cgi?id=158176 m.a.riosv changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158176] Input data is not shown but counted
https://bugs.documentfoundation.org/show_bug.cgi?id=158176 m.a.riosv changed: What|Removed |Added Resolution|--- |INVALID Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158177] Refresh cart page and it's count should not be cleared
https://bugs.documentfoundation.org/show_bug.cgi?id=158177 m.a.riosv changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158177] Refresh cart page and it's count should not be cleared
https://bugs.documentfoundation.org/show_bug.cgi?id=158177 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |INVALID Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39750] [META] General Math formula editor improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=39750 Bug 39750 depends on bug 90297, which changed state. Bug 90297 Summary: LibreOffice Math dark theme > dark text and background https://bugs.documentfoundation.org/show_bug.cgi?id=90297 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90297] LibreOffice Math dark theme > dark text and background
https://bugs.documentfoundation.org/show_bug.cgi?id=90297 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #16 from Michael Weghorn --- (In reply to george from comment #14) > This bug is still present in > > Version: 7.6.2.1 (X86_64) / LibreOffice Community > Build ID: 60(Build:1) > CPU threads: 16; OS: Linux 6.4; UI render: default; VCL: gtk3 > Locale: el-GR (en_US.UTF-8); UI: en-US > Ubuntu package version: 4:7.6.2~rc1-0ubuntu0.22.04.1~lo1 > Calc: threaded > > > > see attachement screenshot Please create a new bug report. While the problem may seem the same/a similar one, the cause is likely a different one now several years later, and this should therefore be tracked separately. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103184 Bug 103184 depends on bug 90297, which changed state. Bug 90297 Summary: LibreOffice Math dark theme > dark text and background https://bugs.documentfoundation.org/show_bug.cgi?id=90297 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158177] Refresh cart page and it's count should not be cleared
https://bugs.documentfoundation.org/show_bug.cgi?id=158177 mayuri changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158177] New: Refresh cart page and it's count should not be cleared
https://bugs.documentfoundation.org/show_bug.cgi?id=158177 Bug ID: 158177 Summary: Refresh cart page and it's count should not be cleared Product: LibreOffice Version: 7.5.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mayuripadwal1...@gmail.com Description: Refresh in cart page and it's count should not be cleared Actual Results: Refresh cart page and it's count should not be cleared Expected Results: Refresh cart page and it's count should be cleared Reproducible: Always User Profile Reset: No Additional Info: this is test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls/crashes under Windows 11 with Norwegian (Bokmål) locale when opening file dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=157135 --- Comment #44 from Odd Nordland --- (In reply to Odd Nordland from comment #36) > I can confirm that I have no problems using Norwegian Nynorsk under Windows > 10. I just tested LibreOfficePortable version 7.6 under Windows 11 with Nynorsk as language environment. The first attempt stalled (!), but the second try worked. The version I used was: Version: 7.6.2.1 (x86) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: no-NO (nn_NO); UI: nn-NO Calc: threaded Note that LibreOffice reports Windows as being version 10.0 when the correct version should be Windows 11 Home version 23H2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132897] FILEOPEN DOCX: Missing rounded borders in frame
https://bugs.documentfoundation.org/show_bug.cgi?id=132897 --- Comment #11 from Regina Henschel --- It seems the description in https://learn.microsoft.com/en-us/windows/win32/vml/msdn-online-vml-arcsize-attribute: "Defines the rounded corners of a rounded rectangle as a percentage of half the smaller dimension of the length and width of a rectangle. 0% would have square corners, and 100% would form circular corners. A square with an ArcSize value of 1.0 would be a circle. The default value is 0.2 (20%)." does not fit to the reality. When the handle in the shape is dragged to its maximum, creating a circular rounding, then MS Office writes arcsize="0.5". So in reality the reference value is not "half the smaller dimension" but the "smaller of height and width". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158171] Crash when double-clicking DeepL translation dialog OK button
https://bugs.documentfoundation.org/show_bug.cgi?id=158171 Julien Nabet changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | --- Comment #5 from Julien Nabet --- I gave a try with https://gerrit.libreoffice.org/c/core/+/159322 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158171] Crash when double-clicking DeepL translation dialog OK button
https://bugs.documentfoundation.org/show_bug.cgi?id=158171 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||haveBacktrace --- Comment #4 from Julien Nabet --- Now ok it's a crash but it's quite unexpected to double click on a "Ok" button. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158171] Crash when double-clicking DeepL translation dialog OK button
https://bugs.documentfoundation.org/show_bug.cgi?id=158171 --- Comment #3 from Julien Nabet --- Created attachment 190790 --> https://bugs.documentfoundation.org/attachment.cgi?id=190790=edit bt Thank you for the feedback, I could reproduce the crash. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132897] FILEOPEN DOCX: Missing rounded borders in frame
https://bugs.documentfoundation.org/show_bug.cgi?id=132897 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #10 from Regina Henschel --- The problem still exists in Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded The shape is imported as legacy rounded rectangle according to v:roundrect element in the file. But the file has in addition a v:textbox element. Such shape should be imported as drawing object 'text box'. Otherwise the attribute "mso-fit-shape-to-text:t" cannot be translated. The drawing object 'text box' has rounded corners too, so that is not a problem. The radius of the rounding is half as large as it should be. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37093] FILESAVE crash when save as
https://bugs.documentfoundation.org/show_bug.cgi?id=37093 PAUL HOFSETH changed: What|Removed |Added OS|Linux (All) |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37093] FILESAVE crash when save as
https://bugs.documentfoundation.org/show_bug.cgi?id=37093 PAUL HOFSETH changed: What|Removed |Added Version|3.3.2 release |7.6.2.1 release Severity|normal |enhancement Keywords||topicDebug --- Comment #13 from PAUL HOFSETH --- SIRS, i have no experience with reporting bugs, so some leniency is called for, writer goes into a sort of loop whenever I save (even shiorrt text samples) and the restoration option also never finishes. I tried with all other programs off and when looking at memory and CPU- use, no overload was visible. Windows stored fault reports were well hidden, so I cannot provide more info.-Turned the "skia" (whatever that is) off, reinstalled Libre Office in repair modus, same result. This form does not allow me to mark tbhis as a major problem, and below it says reolved, which it is not p. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157935] After installation of 7.6.2, first form opening of .odb file freezes LO
https://bugs.documentfoundation.org/show_bug.cgi?id=157935 --- Comment #3 from w...@sorha-consulting.be --- Created attachment 190789 --> https://bugs.documentfoundation.org/attachment.cgi?id=190789=edit odb file Here is the odb file. Some forms and queries have been deleted (confidential). The remaining form "1. MENU - A lancer en premier" is the one which is to be displayed just after having entered login/password. The bad behavior is : the form remains blank and Libreoffice is stuck the good behavior should be : the form is well displayed (including buttons) and LibreOffice is ready to go on -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90297] LibreOffice Math dark theme > dark text and background
https://bugs.documentfoundation.org/show_bug.cgi?id=90297 george changed: What|Removed |Added CC||gd...@yahoo.com --- Comment #15 from george --- Created attachment 190788 --> https://bugs.documentfoundation.org/attachment.cgi?id=190788=edit dark text in black background in formula editor -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103184 Bug 103184 depends on bug 90297, which changed state. Bug 90297 Summary: LibreOffice Math dark theme > dark text and background https://bugs.documentfoundation.org/show_bug.cgi?id=90297 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39750] [META] General Math formula editor improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=39750 Bug 39750 depends on bug 90297, which changed state. Bug 90297 Summary: LibreOffice Math dark theme > dark text and background https://bugs.documentfoundation.org/show_bug.cgi?id=90297 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90297] LibreOffice Math dark theme > dark text and background
https://bugs.documentfoundation.org/show_bug.cgi?id=90297 george changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #14 from george --- This bug is still present in Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 16; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: el-GR (en_US.UTF-8); UI: en-US Ubuntu package version: 4:7.6.2~rc1-0ubuntu0.22.04.1~lo1 Calc: threaded see attachement screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158176] Input data is not shown but counted
https://bugs.documentfoundation.org/show_bug.cgi?id=158176 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Sorry, what are you talking about? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158173] Draw messes up the formatting of PDFs when trying to edit them
https://bugs.documentfoundation.org/show_bug.cgi?id=158173 --- Comment #3 from V Stuart Foote --- s/Chrome projects/Chromium project's -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158176] New: Input data is not shown but counted
https://bugs.documentfoundation.org/show_bug.cgi?id=158176 Bug ID: 158176 Summary: Input data is not shown but counted Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xsandara0...@gmail.com Description: Upon Student Deployment, the student details are not shown on the list but are counted as I click the deploy button Steps to Reproduce: 1. Navigate to the Deployment Section 2. Verify Student Count 3. Review Code and Configuration Actual Results: The student deployed is not shown on the list, but counted. Expected Results: Student deployed should be shown and counted. Reproducible: Sometimes User Profile Reset: No Additional Info: Student deployed in the chosen grade and section should be shown and counted for the teacher to view all the students enrolled in their handled advisoree. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 V Stuart Foote changed: What|Removed |Added Depends on||158173 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158173 [Bug 158173] Draw messes up the formatting of PDFs when trying to edit them -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158173] Draw messes up the formatting of PDFs when trying to edit them
https://bugs.documentfoundation.org/show_bug.cgi?id=158173 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Blocks||99746 --- Comment #2 from V Stuart Foote --- Aside from providing a specific example needing attention, please note: PDF is a final display/printing publishing format not structured to be editable. LibreOffice is not a PDF editor. Rather it performs a filter "import" (poppler/cairo based) where we parse the PDF content and render as new content on an ODF document canvas (Draw by default, but alternatively to Writer or Impress). During its lossy import each "object" (text run or graphic) from the PDF is parsed and converted into an appropriate LO draw object and placed. The filters do a reasonable job converting the content, but in no sense is the original PDF being edited. And the resulting draw object will probably differ from its source in PDF. There is of course potential to improve fidelity of LO import filter(s) for *some* PDF elements. LO provides an alternative "Insert as image" import filter based on the Chrome projects pdfium libs that will render one PDF page at a time in high-fidelity as a single inserted raster image on ODF document canvas. With this filter path ODF draw objects are not created from the PDF runs. You can also convert your PDF externally from LO, and import PDF pages in a different format, e.g. use pdftocairo -svg (another poppler/cairo based project). Then insert the SVG content to an LO document. That filter path also works (helpful for vector graphics) but can have similar issues with fidelity of draw objects created from the SVG. Bottom line--don't expect to use a PDF published source as an editable document, they aren't. If you can, best to obtain the original document. If you can't, just realize the LO provided PDF import filter(s) will probably loose fidelity to published original during creation of ODF drawing objects. A double whammy as the popple/cairo based PDF export filters are used to convert ODF drawing objects when creating a PDF export from ODF. A "print to PDF" (i.e. gs/ps based) can create a better PDF output. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99746 [Bug 99746] [META] PDF import filter in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158175] New: FILEOPEN does not initialize some formulas/cells correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=158175 Bug ID: 158175 Summary: FILEOPEN does not initialize some formulas/cells correctly Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nmatravol...@clarabot.com Created attachment 190787 --> https://bugs.documentfoundation.org/attachment.cgi?id=190787=edit Erroneous formula values after load. Hi! There are some very finicky circumstances where some formula are not evaluated correctly when opening specific spreadsheets. I'm fairly sure it is a bug, because simply reordering any of the sheets in the workbook will result in the formulas in question to update and display the correct values. History and debugging of the issue 1. First I've received an XLSX file with the issue of some "VLOOKUP" formulas not working. Upon analysis I could discern that the file opened in MS Office works as expected, but not in LibreOffice. Furthermore I noticed that saving the file as ODS and opening that file would work as expected. This lead me to believe there is an MS Office compatibility issue, but was proven wrong later. 2. With the original XLSX is opened, the formula evaluations that were wrong had search values with trailing spaces. Removing the spaces seemed to fix the issue, but after saving and opening the file, the fix would not always "stick". I have not investigated this further, because trailing-spaces or not the formula was valid and should work regardless. 3. The LibreOffice version that originally manifested the issue was Collabora 23.05 master (f64dcce7) while the same issue seemed to not be present in desktop LibreOffice 7.5.1-7.5.7 or 7.6.2.1. So I bisected the sourcetree and found that reverting bb9dcec7 on the master would "fix" the issue on the Collabora branch. All this lead me to believe I've found the issue, so I started to strip the privacy-sensitive information from the spreadsheet to produce a submitable reproduction example. 4. By complete chance I've made just the "right" changes for the issue to manifest even with the commit reverted and also in all of the mainline LibreOffice versions I've mentioned. What is even more interesting, the issue now is present regardless of the file being saved as XLSX or ODS. 5. Further investigation lead me to believe that the erroneous values are wrongly assumed to be correct at FILEOPEN and they are not re-calculated to be correct. The commit bb9dcec7 on the Collabora branch deals with a flag `mbGeneratorKnownGood` set in `WorkbookGlobals::initialize()`. If this flag is not set, the original XLSX is correctly loaded. So finally it seems that at some point the formula results got stored in a way that gets persisted across document saving and loading. Reproduction There are 5 sheets in the document, with the "RH" containing the issue described. The faulty evaluations are in $RH.E45:E74. The cells E45, E47, E52, E55, E61 and E69 of RH fail to evaluate and display "#N/A" while the other cells display "0" instead of being empty. To trigger some evaluation update and see what it should look like, just grab the RH sheet and move it to be the last one for example. Reproduction stability The issue is not CPU/hardware dependent, I've reproduced on two different desktops (AMD64) and an ARM single-board-device as well. Original cause After falling down the rabbit hole, it seems that there could have been a specific operation (maybe the first XLSX opening by LibreOffice) that broke the "stored" value of cells with the formula. I'm not sure if I can find that out. I guess it would be nice if LibreOffice would fix the obvious inconsistency at least when opening the document, even if we can't find out the original source of the issue. I'll try to get a hold of the original XLSX file, before it was ever opened in LibreOffice and see if there is any more information I can gather. Let me know what more information would be useful, if any. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 6; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US 7.6.2-3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157943] LibreOffice 7.6.2.1 - opened files can be modified by someone else without first person's knowledge, even when .lock file exists
https://bugs.documentfoundation.org/show_bug.cgi?id=157943 --- Comment #4 from Mike Kaganski --- (In reply to Stéphane Guillou (stragu) from comment #3) The dialog is just a visual manifestation. The essence is that now, LibreOffice does not use the filesystem locking as it used to do before - so that *another process is able to write into a file opened by LibreOffice*. Previously, Windows filesystem would prevent it physically - no matter what you tried, OS (filesystem driver) would prevent writing into such an open file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157665] Implement a three-way comparison operator to replace ==, <, >, <=, >=
https://bugs.documentfoundation.org/show_bug.cgi?id=157665 Buovjaga changed: What|Removed |Added CC||aswaths...@gmail.com --- Comment #2 from Buovjaga --- (In reply to t.aswath from comment #1) > could you recommend specific files or areas where changes might be > particularly beneficial. One of the tasks in easy hacks is to apply and grow your discovery skills, so can you please tell us how you tried to search for candidates so far? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157665] Implement a three-way comparison operator to replace ==, <, >, <=, >=
https://bugs.documentfoundation.org/show_bug.cgi?id=157665 --- Comment #1 from t.aswath --- could you recommend specific files or areas where changes might be particularly beneficial. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155795] Using divisions in stead of fractions to battle rounding errors
https://bugs.documentfoundation.org/show_bug.cgi?id=155795
--- Comment #4 from Ceaus ---
Wow, that's quite a snappy response. It was just a friendly suggestion...
(In reply to Eike Rathke from comment #2)
> Comment what? All major spreadsheet implementations use IEEE 754 floating
> point double precision to store values, accuracy deficiency and rounding
> errors are inherent and well known, see
> https://help.libreoffice.org/latest/en-GB/text/scalc/01/calculation_accuracy.
> html?DbPAR=CALC and https://wiki.documentfoundation.org/Faq/Calc/Accuracy
>
> Asking to store fractions ("divisions") internally instead of binary
> floating point values doesn't help much as that would already be lost when
> storing the value in any of the commonly used file formats, unless also the
> storage file format is changed. Besides that, processing fractions in
> calculations would come with a performance penalty and would require an
> entire rewrite of the interpreter calculation engine. Something very
> unlikely to happen.
>
> Yes, real accountancy software like GnuCash does not use floating point
> values but fractions, both internally and stored to file, and real
> accountants also don't use spreadsheets to do serious accountancy.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154480] EDITING: Crashes when deleting column in defined range
https://bugs.documentfoundation.org/show_bug.cgi?id=154480 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||7378 --- Comment #6 from Stéphane Guillou (stragu) --- Could be related to bug 107378. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107378] Crash in: rtl_uString_acquire
https://bugs.documentfoundation.org/show_bug.cgi?id=107378 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4480 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120829] Lockfiles can be overridden
https://bugs.documentfoundation.org/show_bug.cgi?id=120829 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7943 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114300] [META] Bugs and enhancements involving lock files or file locking
https://bugs.documentfoundation.org/show_bug.cgi?id=114300 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157943 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157943 [Bug 157943] LibreOffice 7.6.2.1 - opened files can be modified by someone else without first person's knowledge, even when .lock file exists -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131401] Document locking on Linux cifs mount blocking files for MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=131401 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7943 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157943] LibreOffice 7.6.2.1 - opened files can be modified by someone else without first person's knowledge, even when .lock file exists
https://bugs.documentfoundation.org/show_bug.cgi?id=157943 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Version|7.6.2.1 release |7.4.3.2 release CC||stephane.guillou@libreoffic ||e.org Blocks||114300 Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||1401, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||0829 --- Comment #3 from Stéphane Guillou (stragu) --- 2b4cd99d3360ccffb9829a02412824864d045753 made it into 7.2.0.0alpha0+, but I'm setting the earliest version to tsulayaiv's for now. root and tsulayaiv, do you remember how it used to behave before? Would the dialog only offer the two options „Open R/O” and ”Open Copy”? Armin, what do you think? Reading your commit, this is by design, right? I'm all for more consistency between OS, but I can see the issue in making it this easy to do. Is there a corresponding expert configuration that could block from editing when a lock file exists? That would be useful for system admins wanting to have tighter rules. I see we have bug 120829 already. As stated there, we might just need a clearer, strong warning in the dialog about the consequences of opening with an existing lockfile. See the comments in bug 120829, especially the UX/Design team comments. Would you agree with such a solution, root and tsulayaiv? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114300 [Bug 114300] [META] Bugs and enhancements involving lock files or file locking -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157944] Support of common video formats like MP4 / H264 for Impress - ENHANCEMENT - FUNCTIONALITY REQUEST
https://bugs.documentfoundation.org/show_bug.cgi?id=157944 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report. We already have reports for: - Bug 62408 - MP4 videos aren't handled in Windows (without additional codecs) - Bug 142117 - Impress - MP4 H264 video not working Your report is likely a duplicate of one of those, but without information like your OS and version, it's hard to say. Please provide the full version info copied from Help > About LibreOffice (or on macOS LibreOffice > About). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62930] PIVOTTABLE: Add multiple filter criteria to Pivot Table
https://bugs.documentfoundation.org/show_bug.cgi?id=62930 --- Comment #4 from grofaty --- I have reported this feature request 10 years ago, but now in LibreOffice 7.6.2 I have looked into my suggestion again and I think I have much simpler to implement solution. 1. Create pivot table. 2. Right click on pivot table data and select Filter option from pop-up menu. WHAT HAPPENS: Now "Filter" dialog opens. MY SUGGESTION: Instead of opening this "Filter" dialog, just open the dialog from Data | More Filters | Standard Filter dialog. This should be pretty simple to do. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123864] No feedback for screen reader when radio button for underline attribute changes
https://bugs.documentfoundation.org/show_bug.cgi?id=123864 --- Comment #18 from Michael Weghorn --- (In reply to Stéphane Guillou (stragu) from comment #17) > Text read is "Underline push button" without an on/off status. This is the > same as for other split buttons like Font Color and Highlight Color, but it > makes sense for them as they are not on/off toggles like the underline > button is. Bold/italic buttons have role ATSPI_ROLE_TOGGLE_BUTTON, while the underline button has ATSPI_ROLE_PUSH_BUTTON. All of them have a "checked" state set when active, so likely Orca has special handling for toggle buttons here. This will likely need looking into Orca source code and maybe coordination what's the proper way to expose it for Orca to announce it. There's also a "pressed" state that looks like it might be suitable, but it's currently not set. Technically "on/off" is enough to represent the bold/italic state fully, while underline has a wider range of possible values (off, single line, double line,...), but since the button is shown as pressed when any underline is used, screen readers should IMHO also announce it likewise. In any case, pressing Orca_Key+F to have Orca report text formatting makes Orca announce the underlined state when present, so that can be used to find out whether or not it's active for now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95438] SLIDESHOW/VIEWING: Misrendered SVG in presenter console
https://bugs.documentfoundation.org/show_bug.cgi?id=95438 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7068 Resolution|WORKSFORME |FIXED Whiteboard||target:7.1.0 --- Comment #10 from Stéphane Guillou (stragu) --- Fixed by: commit 99f2ae505d2d2dd104842c2133488210c354f731 author Luboš Luňák Thu Nov 19 21:42:16 2020 +0100 committer Luboš Luňák Fri Nov 20 12:29:17 2020 +0100 tools::Polygon::Clip() is broken with bezier curves (tdf#137068) (b3d52624a681c3b28efa6a9218680b68962f6fd2 in linux-64-7.1 bibisect repo) Not marking as duplicate because bug 137068 being Skia-specific would have started later. Thanks Luboš! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137068] Bitmap fill isn't nicely filling within the shape lines in presentation mode (Skia)
https://bugs.documentfoundation.org/show_bug.cgi?id=137068 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=95 ||438 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 158167] Calc: cannot move selected row (recent 24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=158167 --- Comment #3 from Timur --- My build was fresh, like 1 day old, and yesterday bisect was older. So we need 24.2 repo update to see if reproducible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154392] New Automatic Line Adjust row height, takes a lot of time.
https://bugs.documentfoundation.org/show_bug.cgi?id=154392 Buovjaga changed: What|Removed |Added Resolution|INSUFFICIENTDATA|--- Status|RESOLVED|NEW --- Comment #6 from Buovjaga --- Probably this should have been set to NEW per the difference observed in comment 3. -- You are receiving this mail because: You are the assignee for the bug.
