[Libreoffice-bugs] [Bug 155455] Scroll continues when keyboard key is pressed for long and then released
https://bugs.documentfoundation.org/show_bug.cgi?id=155455 Adam664 changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected Version|7.5.3.2 release |7.5.0.0 alpha0+ CC||caolan.mcnamara@collabora.c ||om --- Comment #8 from Adam664 --- Bisected with linux-64-7.5, shows the following results commit cea5af03761842273c4e14b12d87f40aca7bb782 Author: Jenkins Build User Date: Fri Aug 5 10:03:15 2022 +0200 source sha:7b20a1b0736825c9c934288428e6e581f79971e2 Which points to commit 7b20a1b0736825c9c934288428e6e581f79971e2[log] author Caolán McNamara Thu Aug 04 16:32:10 2022 +0100 committer Caolán McNamara Fri Aug 05 09:52:50 2022 +0200 treec9b534711745499fa31031f201cd8ee320b8cac4 parent 8c4e8818fe9f5ac1f6cdf908299cc109d67f1e50 [diff] Attached a spreadsheet to test with. For me, the bug shows after scrolling through about 300 rows when using gtk-3 Wayland. The bug is not present when using gtk-3 X-11. Changed first affected version to 7.5.0.0.alpha0+ Adding Cc: to -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156242] Writer - Page Style dialog - Footnote - missing preview of separator lines in drop-down list
https://bugs.documentfoundation.org/show_bug.cgi?id=156242 --- Comment #4 from raal --- Created attachment 188391 --> https://bugs.documentfoundation.org/attachment.cgi?id=188391=edit WFM win7 No repro with Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 1; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: threaded Please test in recovery mode Nápověda > Restartovat v nouzovém režimu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144512] Please make timing of auto-save a per-document action
https://bugs.documentfoundation.org/show_bug.cgi?id=144512 --- Comment #16 from Mike Kaganski --- (In reply to Justin L from comment #15) > (In reply to Justin L from comment #14) > > -once they have been autosaved, they won't have impact again unless becoming > > dirty > Wrong! That is only (theoretically) true if UserAutoSave is actually saving > the document itself. Otherwise the modify flag remains unchanged. AFAIK, > there is currently no way that AutoSave can tell if the document has changed > since last AutoSave, so it will run every time (until the user manually > saves the file). The modified flag of the *document* remains unchanged; but the modified flag of IMPL_SfxBaseModel_DataContainer changes. So your comment 14 is correct. (In reply to Justin L from comment #14) > I don't see how separating them would be of any help: > -once they have been autosaved, they won't have impact again unless becoming > dirty - meaning the user is frequently switching between/editing multiple > docs. > -if the save of a non-active document affects the working document (likely > true) > - then having staggered saves would actually be even more disruptive > -while if the save of a non-active document doesn't affect the working > document > - then it is somewhat irrelevant when it auto-saves > > Staggered saves would just mean more frequent (but shorter) interruptions > during idle times. That doesn't sound beneficial to me. Generally I agree with all these facts. I just don't know how shorter (but same-length in total) would affect user psychologically. The just-changed document will not autosave immediately, just because monotonically ticking timer happened to fire now; but it will autosave in 15 minutes; so if user expects less saves, this expectation is wrong. However, I prepare an experiment implementing this. I suppose it won't really help users, but OTOH it won't hurt - if this change is merged, and Luke would download and use a daily with it for some time, and report back, then we may see if the idea worth it, or revert. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155455] Scroll continues when keyboard key is pressed for long and then released
https://bugs.documentfoundation.org/show_bug.cgi?id=155455 --- Comment #7 from Adam664 --- Created attachment 188390 --> https://bugs.documentfoundation.org/attachment.cgi?id=188390=edit one column with 1+ rows of the number 33 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156211] Glitch in the kashida for justified Arabic/Persian text with double quotes
https://bugs.documentfoundation.org/show_bug.cgi?id=156211 خالد حسني changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |kha...@libreoffice.org |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155949] EDITING: Extending selection to next word includes after-word space
https://bugs.documentfoundation.org/show_bug.cgi?id=155949 --- Comment #5 from Jim Raykowski --- The UNO command WordRightSel activated by Ctrl+Shift+Right is labeled 'Select to End of Word'. What actually happens is selection to the start of the next word. I would expect selection to the end of the current word when the cursor is not already at the end of the word or to the end of the next word when the cursor is at the end of a word. Code pointers: WordRightSel UNO is handled here: sw/source/uibase/shells/txtcrsr.cxx SwTextShell::ExecMoveLingu case FN_NEXT_WORD_SEL: One possible approach is to make a function SwWrtShell::SelectToEndOfNextWord() to replace the use of SwWrtShell::NxtWrd( true ) here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33201] UI: Highlight (not select) current row and column in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=33201 Buovjaga changed: What|Removed |Added CC|mentoring@documentfoundatio |angeran...@gmail.com |n.org | --- Comment #67 from Buovjaga --- (In reply to Massimiliano Vessi from comment #66) > I need this feature too. Is possible to fund/pay for this feature? You could ask Andreas: https://blog.documentfoundation.org/blog/2023/04/25/want-new-features-in-libreoffice-help-to-fund-developers/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156274] Table Properties | Table | "Text direction" is confusingly named
https://bugs.documentfoundation.org/show_bug.cgi?id=156274 --- Comment #2 from خالد حسني --- Sounds reasonable, as it indeed changes the layout direction the table cells not the text direction of their contents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147662] data auto filter disappears sporadically
https://bugs.documentfoundation.org/show_bug.cgi?id=147662 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 147662] data auto filter disappears sporadically
https://bugs.documentfoundation.org/show_bug.cgi?id=147662 --- Comment #5 from QA Administrators --- Dear ronrobsil...@gmail.com, 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 147606] Multiple index marks before the terms when updating the index that uses a concordance file
https://bugs.documentfoundation.org/show_bug.cgi?id=147606 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 147606] Multiple index marks before the terms when updating the index that uses a concordance file
https://bugs.documentfoundation.org/show_bug.cgi?id=147606 --- Comment #6 from QA Administrators --- Dear George Acu, 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 152863] Mismatch between ODT and DOCX page layout
https://bugs.documentfoundation.org/show_bug.cgi?id=152863 --- Comment #2 from QA Administrators --- Dear Telesto, 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 153031] Dark mode is too dark
https://bugs.documentfoundation.org/show_bug.cgi?id=153031 --- Comment #3 from QA Administrators --- Dear untenshu, 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 152168] Libre Office crashes every time I try to copy a portion of text using two stroke (ie command x)
https://bugs.documentfoundation.org/show_bug.cgi?id=152168 --- Comment #4 from QA Administrators --- Dear rchene...@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 150210] fileopen docx blank
https://bugs.documentfoundation.org/show_bug.cgi?id=150210 --- Comment #7 from QA Administrators --- Dear jindam, vani, 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 153017] printer chaos
https://bugs.documentfoundation.org/show_bug.cgi?id=153017 --- Comment #3 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 149323] Contents cannot display or blinking when clicking on PPSX file by using Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=149323 --- Comment #2 from QA Administrators --- Dear James Sun, 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 149146] Spurious Err:522
https://bugs.documentfoundation.org/show_bug.cgi?id=149146 --- Comment #7 from QA Administrators --- Dear studog, 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 144413] Crash with copy paste functions (ARM only?)
https://bugs.documentfoundation.org/show_bug.cgi?id=144413 --- Comment #12 from QA Administrators --- Dear Lise, 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 148377] Crashes soon after opening and choosing icon for picture insertion. I am using the Mac Mini Silicone Processor, 16 gigs ram
https://bugs.documentfoundation.org/show_bug.cgi?id=148377 --- Comment #3 from QA Administrators --- Dear Neal Shafto, 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 149134] Black boxes present on document when scrolling through text in writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=149134 --- Comment #3 from QA Administrators --- Dear bjcorso101, 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 147030] LibreOffice 7.1 and 7.2 are unstable and frequently crash on macOS Catalina and Big Sur.
https://bugs.documentfoundation.org/show_bug.cgi?id=147030 --- Comment #5 from QA Administrators --- Dear George W Gerrity, 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 72514] VaryColorsbyPoint changes legend colors, not point colors
https://bugs.documentfoundation.org/show_bug.cgi?id=72514 --- Comment #14 from QA Administrators --- Dear Dorien James, 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 98292] Automatically create a equation if libreoffice encounters MathML on Drag-and-Drop
https://bugs.documentfoundation.org/show_bug.cgi?id=98292 --- Comment #11 from QA Administrators --- Dear Gunter Königsmann, 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 129370] LibreOffice does not get restored on boot via X Session Management Protocol
https://bugs.documentfoundation.org/show_bug.cgi?id=129370 --- Comment #3 from QA Administrators --- Dear Nate Graham, 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 118445] attempt to link documents circularly freezes writer
https://bugs.documentfoundation.org/show_bug.cgi?id=118445 --- Comment #5 from QA Administrators --- Dear Yury, 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 117889] UI: Selecting an item in a list box scrolls the content
https://bugs.documentfoundation.org/show_bug.cgi?id=117889 --- Comment #4 from QA Administrators --- Dear Balint Fodor, 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 108601] FORMATTING Value of Format - Rows - Optimal Height is not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=108601 --- Comment #16 from QA Administrators --- Dear stefan_lange...@t-online.de, 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 104057] REPORTBUILDER - Mouse over on scrolled down rules in conditional formatting dialog always brings back top rules in view
https://bugs.documentfoundation.org/show_bug.cgi?id=104057 --- Comment #13 from QA Administrators --- Dear Mario Bianchi, 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 104058] REPORTBUILDER - Current setting not reflected in conditional formatting color widgets after close/reopen dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=104058 --- Comment #6 from QA Administrators --- Dear Mario Bianchi, 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 103533] Fileopen dump using Procdump with specific XLSX, no recovery window
https://bugs.documentfoundation.org/show_bug.cgi?id=103533 --- Comment #14 from QA Administrators --- Dear Timur, 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 108917] [META] Cell references bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108917 Jeff Fortin Tam changed: What|Removed |Added Depends on||148127 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148127 [Bug 148127] When selecting parts of a formula referencing cells ranges from another opened window of the same spreadsheet, highlights do not update until the other window is clicked / focused -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148127] When selecting parts of a formula referencing cells ranges from another opened window of the same spreadsheet, highlights do not update until the other window is clicke
https://bugs.documentfoundation.org/show_bug.cgi?id=148127 Jeff Fortin Tam changed: What|Removed |Added Blocks||108253, 108917 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108253 [Bug 108253] [META] Calc cell formula bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108917 [Bug 108917] [META] Cell references bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108253 Jeff Fortin Tam changed: What|Removed |Added Depends on||148127 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148127 [Bug 148127] When selecting parts of a formula referencing cells ranges from another opened window of the same spreadsheet, highlights do not update until the other window is clicked / focused -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57414] File Recovery: Don't save read-only and empty files for recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=57414 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=90 | |318 | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61174] [META] Recent Documents List
https://bugs.documentfoundation.org/show_bug.cgi?id=61174 Bug 61174 depends on bug 90318, which changed state. Bug 90318 Summary: Recent Documents list shouldn't include temporary files like mail attachment copies and Base-Reports-generated files https://bugs.documentfoundation.org/show_bug.cgi?id=90318 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105057] Creating or running Base Reports or creating forms leaves temp files on LibreOffice opening page and recent files menu
https://bugs.documentfoundation.org/show_bug.cgi?id=105057 Justin L changed: What|Removed |Added CC||pierre-yves.samyn@laposte.n ||et --- Comment #5 from Justin L --- *** Bug 90318 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 90318] Recent Documents list shouldn't include temporary files like mail attachment copies and Base-Reports-generated files
https://bugs.documentfoundation.org/show_bug.cgi?id=90318 Justin L changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=57 | |414 | Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #14 from Justin L --- *** This bug has been marked as a duplicate of bug 105057 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146769] Reopen documents from previous session on start
https://bugs.documentfoundation.org/show_bug.cgi?id=146769 Justin L changed: What|Removed |Added CC||jl...@mail.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=57 ||414 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57414] File Recovery: Don't save read-only and empty files for recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=57414 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6769 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57414] File Recovery: Don't save read-only and empty files for recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=57414 Justin L changed: What|Removed |Added Crash report or|https://bugs.documentfounda | crash signature|tion.org/show_bug.cgi?id=90 | |318 | See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=90 ||318 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90318] Recent Documents list shouldn't include temporary files like mail attachment copies and Base-Reports-generated files
https://bugs.documentfoundation.org/show_bug.cgi?id=90318 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=57 ||414 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144512] Please make timing of auto-save a per-document action
https://bugs.documentfoundation.org/show_bug.cgi?id=144512 --- Comment #15 from Justin L --- (In reply to Justin L from comment #14) > -once they have been autosaved, they won't have impact again unless becoming > dirty Wrong! That is only (theoretically) true if UserAutoSave is actually saving the document itself. Otherwise the modify flag remains unchanged. AFAIK, there is currently no way that AutoSave can tell if the document has changed since last AutoSave, so it will run every time (until the user manually saves the file). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156305] Allow to invert selection in Autofilter
https://bugs.documentfoundation.org/show_bug.cgi?id=156305 ady changed: What|Removed |Added Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155661] Skia: Transparency gradient is rendered as solid transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=155661 Aron Budea changed: What|Removed |Added Keywords||bibisected, bisected, ||regression --- Comment #5 from Aron Budea --- This is a regression that started in 7.1, in two steps. First the gradient deteriorates from this commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=6965bb07bb33429a7663a3f3ebe58ed89c4327d9 author Luboš Luňák 2020-09-25 10:00:31 +0200 committer Luboš Luňák 2020-09-25 19:36:26 +0200 "forward axial and radial gradient types to VCL too" Then it's completely gone starting with this commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=8b8a988f38b704e466211bb91a3269756c34222b author Luboš Luňák 2020-11-17 16:49:19 +0100 committer Luboš Luňák 2020-11-17 19:25:42 +0100 "implement also axial gradient for skia" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156297] In Calc, scrolling becomes very slow when hiding (many) columns
https://bugs.documentfoundation.org/show_bug.cgi?id=156297 ady changed: What|Removed |Added Status|NEEDINFO|NEW Keywords||perf Summary|In Calc, when I hide|In Calc, scrolling becomes |columns, the scrolling |very slow when hiding |becomes very slow. |(many) columns --- Comment #5 from ady --- The STR in comment 4 are easy-enough to follow. With _different_ scrolling rates in each version (i.e. other factors could be in place for each version), it could be reproduced since LO 3.3 and up to current Dev 24.2. OTOH, with the same STR, we cannot really be sure that the performance reduction is originated by _hiding_ (so many) columns, or by applying some/any attribute to such a big area. IOW, is _hiding_ the problem? Or is it the "huge" range of "active" cells? Further investigations would be needed. There are probably similar reports open already; let's set to NEW for now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145997] FONT SIZE COMBOBOX: Impossible to type text under certain circumstances (steps in comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=145997 --- Comment #9 from Matt K --- (In reply to Matt K from comment #8) > Confirmed in latest master on Windows 11. Seems to be fixed in Version: 24.2.0.0.alpha0+ master. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57414] File Recovery: Don't save read-only and empty files for recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=57414 Justin L changed: What|Removed |Added CC||jl...@mail.com Version|4.0.0.0.alpha0+ Master |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142132] Save as - possible to close applikation before finished save
https://bugs.documentfoundation.org/show_bug.cgi?id=142132 --- Comment #2 from Justin L --- What is the problem here? So what if the user interface is closed? There would only be a problem if the file save gets corrupted. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77999] [META] Autosave/Autorecovery/Backup copy issues
https://bugs.documentfoundation.org/show_bug.cgi?id=77999 Bug 77999 depends on bug 81146, which changed state. Bug 81146 Summary: Avoid corruption of registrymodifications.xcu https://bugs.documentfoundation.org/show_bug.cgi?id=81146 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81146] Avoid corruption of registrymodifications.xcu
https://bugs.documentfoundation.org/show_bug.cgi?id=81146 Justin L changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57414] File Recovery: Don't save read-only and empty files for recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=57414 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=76 ||992 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76992] LibreOffice Pretends a document recovery is successful, where no AutoRecovery data is available
https://bugs.documentfoundation.org/show_bug.cgi?id=76992 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=57 ||414 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76992] LibreOffice Pretends a document recovery is successful, where no AutoRecovery data is available
https://bugs.documentfoundation.org/show_bug.cgi?id=76992 --- Comment #6 from Justin L --- I think this is probably another version of bug 57414. IIUC, the solution to these bug reports would be that any document that is not modified should be excluded from the recovery process. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59365] FILESAVE: Memory usage after autorecovery/manual savings
https://bugs.documentfoundation.org/show_bug.cgi?id=59365 Justin L changed: What|Removed |Added Hardware|Other |All Status|NEW |NEEDINFO OS|Linux (All) |All --- Comment #6 from Justin L --- This has been untouched for 10 years. It really needs to be confirmed that current LibreOffice still consumes memory during each save. That will be especially important to know for LO 7.6 because it turns on autosave/backups. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137879] LO should know not to try and recover temporary files
https://bugs.documentfoundation.org/show_bug.cgi?id=137879 --- Comment #13 from Justin L --- (In reply to Stéphane Guillou (stragu) from comment #11) > *** This bug has been marked as a duplicate of bug 57414 *** It probably should remain a duplicate, but oh well. I disagree that just because it is in the /tmp directory it shouldn't be in the recovery system - but I can agree that if it is unmodified it doesn't need to be. For example, if someone e-mails me a file, and I open it and then start making changes to it for an hour, what should happen if LO crashes? I would want to be able to have it recovery my hour's worth of changes when LO restarts - even though I hadn't properly saved it to a reasonable location yet. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33201] UI: Highlight (not select) current row and column in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=33201 --- Comment #66 from Massimiliano Vessi --- I need this feature too. Is possible to fund/pay for this feature? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156279] opening documents with languagetool takes ages to open
https://bugs.documentfoundation.org/show_bug.cgi?id=156279 goodgu...@zoho.com changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156279] opening documents with languagetool takes ages to open
https://bugs.documentfoundation.org/show_bug.cgi?id=156279 --- Comment #2 from goodgu...@zoho.com --- i did many experiments and tested various combinations. i could not install LT6.1.1 under LO7.5 (some java/api problems), and on the other hand, LT5.9.1 installed under LO7.6 does not work, i had to find a way to test crosswise. the only combination working: installing LT5.9.1 under LO7.5 and then upgrade to LO7.6 and miraculously LT5.9.1 is usable under LO7.6 AND works fine. no performance problems. so, i'm concluding: it's a LT6.1.1 problem. => my question: how to reassign this bug to LT? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 48416] Allow typing while saving; during autosave LibreOffice doesn't accept typing/input
https://bugs.documentfoundation.org/show_bug.cgi?id=48416 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=69 ||085 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69085] FILESAVE: Key Buffer needed during File-Save process.
https://bugs.documentfoundation.org/show_bug.cgi?id=69085 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=48 ||416 --- Comment #4 from Justin L --- This is effectively a duplicate of bug 48416, but I'll keep them separate since on is talking about regular save and the other is about autosave. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37937] Saving file dialog, no warning about restricted chars in filename
https://bugs.documentfoundation.org/show_bug.cgi?id=37937 Justin L changed: What|Removed |Added Priority|medium |low -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107943] [META] Save bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107943 Bug 107943 depends on bug 32809, which changed state. Bug 32809 Summary: Please warn when saving significant work to file in /tmp! https://bugs.documentfoundation.org/show_bug.cgi?id=32809 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32809] Please warn when saving significant work to file in /tmp!
https://bugs.documentfoundation.org/show_bug.cgi?id=32809 Justin L changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #8 from Justin L --- I imagine this was fixed in LO 5.4 with commit eb9f90186ae52efa7ff884b3e64f5dd59ddc0329 Author: Justin Luth on Fri Jan 20 15:59:25 2017 +0300 tdf#80807 guisaveas: never recommend system's tempdir -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143640] UNO Object Inspector: Crash while clicking on the "Object" tree (debug)
https://bugs.documentfoundation.org/show_bug.cgi?id=143640 --- Comment #22 from Hossein --- (In reply to Julien Nabet from comment #21) > On pc Debian x86-64 with master sources updated today (+gtk3 rendering), I > got no crash or assertion anymore, including after closing the document then > LO. > > Hossein: unless I missed something, could you give a new try with a daily > build from 83a169d04aca94f6f2a5b6ef9fdfba3c0fc4ede3 ? Correct. I no longer reproduce the crash/assertion failure with the latest LO 24.2 dev master. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b6f3129569c22d9d139ca712dcf0db6dc2041565 CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded But, bisect is needed to know which commit actually fixed the issue. Might be changes to sw/source/core/doc/docbm.cxx. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155875 --- Comment #19 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/5d43b773eb9e3e3fd45c627f83d9f57a926ae411 tdf#155875 Tab'd UI commands Writer/Insert in Help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155875 --- Comment #17 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/bb0eda82d211a47996b37fb0f900b32c49ff9074 tdf#155875 Tab'd UI commands Writer/Insert in Help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155875 --- Comment #18 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/3606293451c58ee9b279837041875dcbcc4ad54a tdf#155875 Tab'd UI commands Writer/Insert in Help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117447] FILEOPEN Floating table in attached DOC(X) is lost(hidden) during import
https://bugs.documentfoundation.org/show_bug.cgi?id=117447 --- Comment #17 from Justin L --- (In reply to Justin L from comment #16) > NOT YET FIXED: > -floating_tables.doc from bug 119803 comment 0 confirmed still broken > -missing_table.docx from this bug, comment 0 Fixed with commit 52d265c0d2f2638c386475e58c3ee489ccd3f06c Author: Miklos Vajna on Thu Jul 13 08:14:42 2023 +0200 sw floattable: fix lost floating table right before a hidden para from DOCX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156226] Writer Spell Check prevents manual correction
https://bugs.documentfoundation.org/show_bug.cgi?id=156226 --- Comment #1 from Dennis --- Additional spell check error Original text: The chinese american man The spell check will correct to Chinese american on the first round of spell checking. Invoke spell check again and it will correct to Chinese American. It should be able to capitalize both words with only one round of spell checking. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77999] [META] Autosave/Autorecovery/Backup copy issues
https://bugs.documentfoundation.org/show_bug.cgi?id=77999 Bug 77999 depends on bug 150148, which changed state. Bug 150148 Summary: Backup copies of all files are saved to a single folder https://bugs.documentfoundation.org/show_bug.cgi?id=150148 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68565] Other: Request for capability to save .BAK files in same location as original document
https://bugs.documentfoundation.org/show_bug.cgi?id=68565 Justin L changed: What|Removed |Added CC||lmiro...@yandex.ru --- Comment #6 from Justin L --- *** Bug 150148 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 150148] Backup copies of all files are saved to a single folder
https://bugs.documentfoundation.org/show_bug.cgi?id=150148 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #10 from Justin L --- (In reply to Mike Kaganski from comment #9) > so this is only a dupe of the bug 68565. A more elaborate solution would be bug 89651. But either way, this is a dup. *** This bug has been marked as a duplicate of bug 68565 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156306] New: pdf export of odt document runs in a loop (hangs)
https://bugs.documentfoundation.org/show_bug.cgi?id=156306 Bug ID: 156306 Summary: pdf export of odt document runs in a loop (hangs) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stefan_lange...@t-online.de Created attachment 188389 --> https://bugs.documentfoundation.org/attachment.cgi?id=188389=edit zip file with 4 odt documents to show the problem odt documents with some special properties (I don't know what) cannot be exported to pdf via "Directly export as PDF" because LibreOffice hangs resp. starts to run in a loop: uses cpu and doesn't answer. I noticed the problem after the test of Bug 154035 when I have changed a large document and wanted export it to pdf. The behavior was first found in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 693411e60c6bbd1c2ef25490cc3902f6b2461682 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded In the previous build for Windows64 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 375d423573cf237fb082ed2b4908d8067036d8b2 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded the problem wasn't present yet. Documents to show the problem: Because of the size of my large document (about 130 MB because of many images within) I have created the smaller version "Alte Fotoapparate V6.4.1_pdf_export_hangs.odt". To narrow down the cause of the error I have stepwise reduced the style elements in this document (removed images and footer line, changed headers to "Standard" etc.) until remained "Test_document_pdf_export_hangs.odt". Reproducing the problem: - open one of the documents Alte Fotoapparate V6.4.1_pdf_export_hangs.odt or Test_document_pdf_export_hangs.odt or Test_document_(coloured)_pdf_export_hangs.odt from the attached zip file - try to export the document to pdf via "Directly export to PDF" - Result: LibreOffice hangs resp. loops (runs and uses cpu, but doesn't answer or end) When in the documents "Test_document_pdf_export_hangs.odt" or the coloured version "Test_document_(coloured)_pdf_export_hangs.odt" the coloured section is removed one gets the document "Test_document_shortened_pdf_export_OK.odt. This document can be exported to pdf without any problems. Therefore I suppose the cause of the problem is in the coloured section. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144512] Please make timing of auto-save a per-document action
https://bugs.documentfoundation.org/show_bug.cgi?id=144512 --- Comment #14 from Justin L --- I don't see how separating them would be of any help: -once they have been autosaved, they won't have impact again unless becoming dirty - meaning the user is frequently switching between/editing multiple docs. -if the save of a non-active document affects the working document (likely true) - then having staggered saves would actually be even more disruptive -while if the save of a non-active document doesn't affect the working document - then it is somewhat irrelevant when it auto-saves Staggered saves would just mean more frequent (but shorter) interruptions during idle times. That doesn't sound beneficial to me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=153131 --- Comment #27 from ericbressle...@gmail.com --- Thanks, Barry. Unfortunately I can't run scalc.exe from my command prompt using the text you included in your bug report for https://bugs.documentfoundation.org/show_bug.cgi?id=156290 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143640] UNO Object Inspector: Crash while clicking on the "Object" tree (debug)
https://bugs.documentfoundation.org/show_bug.cgi?id=143640 --- Comment #21 from Julien Nabet --- On pc Debian x86-64 with master sources updated today (+gtk3 rendering), I got no crash or assertion anymore, including after closing the document then LO. Hossein: unless I missed something, could you give a new try with a daily build from 83a169d04aca94f6f2a5b6ef9fdfba3c0fc4ede3 ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Julien Nabet changed: What|Removed |Added Depends on||156215 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156215 [Bug 156215] drag cell expansion copy will result in a crash often -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156215] drag cell expansion copy will result in a crash often
https://bugs.documentfoundation.org/show_bug.cgi?id=156215 Julien Nabet changed: What|Removed |Added Blocks||129062 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156305] New: Allow to invert selection in Autofilter
https://bugs.documentfoundation.org/show_bug.cgi?id=156305 Bug ID: 156305 Summary: Allow to invert selection in Autofilter Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 188388 --> https://bugs.documentfoundation.org/attachment.cgi?id=188388=edit Proposed position for the "Invert" button In Calc I often face the following problem: Suppose I have a large table in a sheet and it has AutoFilter enabled. Now consider a column in this table that has many unique values (hundreds or thousands of them). Imagine now that from these hundreds/thousands of values, I selected 20 of them to filter the table. The problem now is when I simply want to invert the selection, to see the lines that weren't previously visible. Currently I have to clear the filter and uncheck the 20 values one by one, which is tedious and prone to error. A better approach would be to add a "Invert" button to the Autofilter (see attached image) that would simply invert the selection status of all items. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Status|NEW |NEEDINFO --- Comment #2 from Buovjaga --- Why does this meta exist when there is bug 113510? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156296] Basic (Macro) editor font is unreadable, can't zoom in view, can't change font face or its size
https://bugs.documentfoundation.org/show_bug.cgi?id=156296 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Resolution|NOTABUG |WORKSFORME CC||79045_79...@mail.ru --- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> --- Let's change status to WFM. Thanks all -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156109] Mutual exclusion of split-preventing options in Text Flow is confusing.
https://bugs.documentfoundation.org/show_bug.cgi?id=156109 --- Comment #3 from Kazinator --- (In reply to Dieter from comment #1) > Kazinator, for me your proposal is confusing, because what is the meaning of > "none"? There can be only two possibilities: splitting the paragraph or not > not splitting the paragraph. So what happens, if you select "none"? > But let's ask design team. Thanks for your comments. None means there is no split prevention. The paragraph breaks abruptly wherever the page (or other container) ends. Then the radio has two choices for how to prevent splits. Keep the paragraph all together, or use widow/orphan controls. I agree that the proposed wording could be improved because it perpetrates semantic double negatives, which is confusing. The entire category is "split prevention" which is a kind of negative: how not to do something, not to split. So then "none" constitutes a double negative. Do not not split: i.e. split arbitrary. It made sense to me at the time, but I also had to think about it for a moment. A somewhat verbose alternative: Allow paragraph to split across page breaks? (*) Split freely at any line of the paragraph. ( ) Do not split; keep entire paragraph together. ( ) Split, keeping some lines together, as specified: [ ] Minimum Top Fragment [] Lines [ ] Minimum Bottom Fragment [] Lines -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156299] Icon inconsistencies: menu Insert shape and Sidebar Shapes deck
https://bugs.documentfoundation.org/show_bug.cgi?id=156299 --- Comment #1 from Rafael Lima --- Created attachment 188387 --> https://bugs.documentfoundation.org/attachment.cgi?id=188387=edit Screenshot describing the change Just to be clear, I attached a screenshot of what I understood to be the proposed change (see attached image). Is this correct? If so, the actual image used by the Insert - Shape menu depends on which icon theme is selected. For instance, in Breeze Dark the "ShapesMenu" command (menu entry) will redirect to the file cmd/32/basicshapes.pentagon.png. But Colibre Dark will point too insertdraw.png. Maybe we can replicate this in the sidebar as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154190] Make "Edit macro" open previously edited library/module and fix sorting of Object Catalog items to match Basic Macro Organizer
https://bugs.documentfoundation.org/show_bug.cgi?id=154190 freew...@poczta.fm changed: What|Removed |Added Summary|Make "Edit macro" remember |Make "Edit macro" open |previously opened and |previously edited |edited library/module |library/module and fix ||sorting of Object Catalog ||items to match Basic Macro ||Organizer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154190] Make "Edit macro" remember previously opened and edited library/module
https://bugs.documentfoundation.org/show_bug.cgi?id=154190 --- Comment #5 from freew...@poczta.fm --- Created attachment 188386 --> https://bugs.documentfoundation.org/attachment.cgi?id=188386=edit Same listings different sorting in Object Catalog and Basic Macro Organizer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154190] Make "Edit macro" remember previously opened and edited library/module
https://bugs.documentfoundation.org/show_bug.cgi?id=154190 --- Comment #4 from freew...@poczta.fm --- Hi. I've just noticed another minor UX annoyance in the macro editor. Please, look at the attached image. The tree listing inside "Object Catalog" sidebar page is INVERTED compared to the listing in the "Basic Macro Organizer", where the items are sorted alphabetically. Both lists seems to show same items, and I'd expect them to be sorted the same. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124891] [META] Basic IDE bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=124891 Bug 124891 depends on bug 156296, which changed state. Bug 156296 Summary: Basic (Macro) editor font is unreadable, can't zoom in view, can't change font face or its size https://bugs.documentfoundation.org/show_bug.cgi?id=156296 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90796] [META] HiDPI / Retina bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=90796 Bug 90796 depends on bug 156296, which changed state. Bug 156296 Summary: Basic (Macro) editor font is unreadable, can't zoom in view, can't change font face or its size https://bugs.documentfoundation.org/show_bug.cgi?id=156296 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156296] Basic (Macro) editor font is unreadable, can't zoom in view, can't change font face or its size
https://bugs.documentfoundation.org/show_bug.cgi?id=156296 freew...@poczta.fm changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #3 from freew...@poczta.fm --- I see, just tested out daily dev version and it seems the zoom works now. I'm using 7.2.7.2 right now on all of my computers, because Calc and Writer give me much less headaches than anything beyond 7.3 I tried so far until 7.5. But it seems I need to think of upgrading given the other bug 154114 that completele broke Calc has been resolved in latest dev, and also things like pivottables seems to have been fixed to a somewhat usable state. Sorry, mods, you can close this one as resolved or even delete it. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156304] New: In presentation mode, pressing left arrow after last slide won't return to the last slide
https://bugs.documentfoundation.org/show_bug.cgi?id=156304 Bug ID: 156304 Summary: In presentation mode, pressing left arrow after last slide won't return to the last slide Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 188385 --> https://bugs.documentfoundation.org/attachment.cgi?id=188385=edit Sample presentation for testing If you navigate a presentation using the keyboard arrow keys until you reach the black screen saying "Click to exit presentation...", pressing the "left" arrow key should return to the last slide, but instead it returns to the penultimate slide. Steps to reproduce 1) Open the attached sample presentation (it has 3 slides) 2) Press F5 to enter presentation mode 3) Press the "right" arrow key 3 times, which will reach the black screen saying "Click to exit presentation..." 4) Now press the "left" arrow key; this should move to Slide 3; but instead it moves to Slide 2 System info Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR Ubuntu package version: 4:7.5.4-0ubuntu0.23.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156260] multipage floating table collapses when entering text outside of the table
https://bugs.documentfoundation.org/show_bug.cgi?id=156260 --- Comment #4 from Regina Henschel --- If I open attachment 75671 and save it immediately to odt, I get a file with five elements. That is in contrast to the intension to have one table in one frame. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112876] Make use of scroll lock for navigation configurable (it conflicts with system use as keyboard layout indicator)
https://bugs.documentfoundation.org/show_bug.cgi?id=112876 --- Comment #30 from Axel Niedenhoff --- I have surfed the internet a bit and it seems to me that there a number of keyboards out there that use the ScrollLock key for toggling the backlight. I have one myself now and using Calc with this is a pain. So I would like to see this fixed. Note that the above discussion is a lot about Linux, which might make this appear to be a Linux problem. But the same problem occurs on Windows if you have one of those keyboards. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146356] ODT: No easy way to create an empty paragraph before Table of Content if document starts with table of content
https://bugs.documentfoundation.org/show_bug.cgi?id=146356 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=93 ||790 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146565] ALT+ENTER before Table of content does expand the TOC with additional field
https://bugs.documentfoundation.org/show_bug.cgi?id=146565 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=93 ||790 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122497 Regina Henschel changed: What|Removed |Added Depends on||93790 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=93790 [Bug 93790] Insert "Page break" before Summary (Table of Contents) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 Regina Henschel changed: What|Removed |Added Depends on||93790 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=93790 [Bug 93790] Insert "Page break" before Summary (Table of Contents) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93790] Insert "Page break" before Summary (Table of Contents)
https://bugs.documentfoundation.org/show_bug.cgi?id=93790 Regina Henschel changed: What|Removed |Added Summary|Insert "Page break" before |Insert "Page break" before |Summary |Summary (Table of Contents) Blocks||122497, 89606 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6565, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6356 --- Comment #14 from Regina Henschel --- Then let us treat it accordingly. I have added it in the summary and added the meta bugs. And I have added later reports about the same topic. The table of contents (TOC) is a write protected section. So you first need to set the TOC to editable. The go to its start and press Alt+Enter. That inserts a new line before but still in the section. Go to it. Again press Alt+Enter. Now you have line before the section. Delete the additional line inside the section and set the TOC back to not editable. So it is possible, but of cause that is not a user friendly solution. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89606 [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156301] if libre writer is hunging all other libre apps hungs too. (eg. calc).
https://bugs.documentfoundation.org/show_bug.cgi?id=156301 --- Comment #2 from Telesto --- (In reply to Roman Kuznetsov from comment #1) > it's because LibreOffice is a monolith software. All modules use the same > one software core in the same time. One process "soffice" starts if you > start any amount of any LibreOffice modules. > > For fixing this problem someone should rewrite LibreOffice from scratch and > it will not LibreOffice but some another software. You can run different versions of LibreOffice in parallel, so technically it should be possible to launch each module (Calc/Writer) in different process, instead of using a single process managing every mode; I guess A different story would be running each document in a separate process, which obviously even nicer, but that is indeed different design. > I'm sure I saw the same report but I couldn't find it There surely is a report about this somewhere -- You are receiving this mail because: You are the assignee for the bug.
